• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[Dev] Building kernel

Search This thread

Blagus

Inactive Recognized Developer
Jun 10, 2010
1,323
1,046
MSM7227 S1Boot has been patched to ignore SIN header signature by the_laser.

You need phone which you either did not unlock by cable, or phone which you unlocked via SEtool2 only.

If you unlocked with Omnius, in C:\ProgramData\Omnius for SE\Backups\Xperia X8
you have file called: Xperia X8_IMEI_DATE_SIMLock.opd

Note, the fixed S1Boot for other tools should come soon.

Restore that TA backup, then use semc.cmd in the_laser's release to unlock bootloader - you'll restore SIM lock this way!
Currently there is no unlocked bootloader for Omnius unlocked phones.

* Kernel build instructions in second post.
* Original post by the_laser with unlock instructions in third post.

What will this allow:
* custom kernels
* better/fully working Gingerbread
* no need for chroot to avoid init crash bug
* overclock/Synaptics fake DT/Cypress real DT/MDDI fix built in kernel

This will not enable:
* real DT on Synaptics digitizer
 
Last edited:

Blagus

Inactive Recognized Developer
Jun 10, 2010
1,323
1,046
To make custom kernel:

1) Compile it.
2) Grab Image, not zImage
3) Make ramdisk.gz (cpio ramdisk content, then gzip the cpio archive)
4) Place both files in ./msm7227/sinTools
5) Name then image and ramdisk, no extension, remove existing files
6) Exectue example_build.cmd
7) Grab result.elf.sin from result.zip, rename to kernel.sin and pack in ftf bundle with patched loader.sin from ./msm7227/loader
8) Flash with FlashTool.
 
Last edited:

the_laser

Senior Member
Feb 15, 2011
271
1,037
Greetings.

warning.
if you are not developer, please quit reading that post.
wait for user friendly tool with one big button.


here ( View attachment msm7227.7z) is toolset to permanently "unlock" semcboot of msm7227 semc phones.

that means, you can use own kernel and so on.

steps,precautions, etc.

unpack archive to any directory.

if you using eset antivirus or similar ****, it will find evil virus in adb.exe.
ignore that, it is not virus in any way, it is standard android debug bridge, bundled in one file to save space and usability.


now, if your phone unlocked officially:

flash phone with standard 2.0,2.1 android firmware,because kernel mapper module compiled for "2.6.29" kernel.

of course, enable "usb debugging"

run msm7227_semc.cmd,
( if you want, examine it before run, it is pretty straightforward. )

you will get similar output

Code:
process requires standard 2.x android firmware.
Press any key to continue . . .
Getting ROOT rights.
1743 KB/s (585731 bytes in 0.328s)
error: protocol fault (no status)
Waiting ...
Removing NAND MPU restrictions via SEMC backdoor. Permanent. Require ROOT rights.
192 KB/s (3087 bytes in 0.015s)
success
Waiting ...
Getting ROOT rights.
Waiting ...
Writing patched semcboot. Two step process
First, we need get access to semcboot area
504 KB/s (8064 bytes in 0.015s)
Second, we need to write semcboot ;)
1130 KB/s (596916 bytes in 0.515s)
successfully wrote 0003ff00
Press any key to continue . . .

bingo, your phone now has unlocked bootloader.

if your phone unlocked by setool2 software, use msm7227_setool2.cmd

if your phone unlocked by 3rd-party software other than setool2, do not run anything -
it will disable radio capability of your phone and you will need to unlock phone by setool2 software.

to find out if you can safely unlock bootloader, here (View attachment s1tool.7z) is tool.

if you will see "NOT RECOGNIZED SIMLOCK CERTIFICATE", you should not use either of .cmd.

hopefully, mizerable flea and mOxImKo will release something similar for your phone.



okay, now about other details.

1.
unlocked bootloader require unlocked loader, yep ?

loader\loader.sin is special unlocked loader, which will be accepted ONLY after your "unlock" semcboot with previous steps.

to distinguish unlocked semcboot and original semcboot, first letter in version tag of semcboot output will be lower case, i. e. "r8A029"

( same applies for loader version tag )

so, all that stuff with signatures are not for us, so i removed them - loader will ignore signature part of SIN file.

2.
we should make SIN file somehow, right ?
for that i prepared "dumb" bin2sin utility.

Syntax : bin2sin [input] [partition info, 32 digits] [type] [block size]

[input] - is input binary file.

[partition info]
android implementation on s1 semc qualcomm phones based on partitions,so we MUST define it for our file.

you can get required partition info from standard semc sin files, it is first 0x10 bytes of DATA, right after header, i.e.
e10 kernel partition info
03000000010000402001000040000000

[type] - partition type, 9 - partition without spare, 0xA - partition with spare.
kernel partition is partition without spare.
if that parameter omitted, type = 9

[block size] - nand block size, if omitted, it is standard size 0x20000

there is example in sinTools\example_build.cmd

3.
kernel should be prepared specially to be accepted by semcboot.
for that there is tool bin2elf.

Syntax : bin2Elf.exe [nbrOfSegments] [EntryPoint] [Segment1] [LoadAddress1] [Attributes1] ...

we need 2 segments:
segment 1 is unpacked linux kernel image, i.e.
( e10/kernel/arch/arm/boot/Image )

it looks like entrypoint and load address for segment 1 is always same for all msm7227-based semc phone, it is 0x00208000

attributes for image 0x0

segment 2 is ramdisk.

it looks like entrypoint and load address for segment 1 is always same for all msm7227-based semc phone, it is 0x01000000

set attributes for ramdisk 0x80000000, that is extremly important.

there is simple kernel example in sinTools\example_build.cmd

ps.

@blagus:
NAND MPU disabler has only one relation to rFoNe - he took it from setool2, together with entire idea for msm7227 bypass.
your 6-wings friend with many nicks done exactly same.

NAND MPU has nothing to do with memory firewall, so it will not help with kexec things, however, who will care now.

edit:
there was minor flaw in msm7227_setool2.cmd - i forgot to change source bootwriter name and both .cmd wrote same semc boot:

flawed:
@echo Second, we need to write semcboot ;)
bootTools\adb.exe push my7227bootwrite_semcSL /data/local/tmp/my7227bootwrite_setool2SL

correct:
@echo Second, we need to write semcboot ;)
bootTools\adb.exe push my7227bootwrite_setool2SL /data/local/tmp/my7227bootwrite_setool2SL


of course, every developer or man with capability to read fixed it immediately.
just in case, i uploaded "fixed" package.

 
Last edited:

af974

Retired Recognized Developer / Retired Forum Mod
Jan 22, 2008
4,968
1,702
Ok, just because someone is asking what the hell is happened, got a request by Blagus to delete all posts but his first 2 and the_laser one, thread is now closeed untill Blagus will say me to open it.
 

SpyderX

Senior Member
Mar 5, 2011
933
933
Singapore
How to verify if the bootloader on your phone is really unlocked

the_laser (earlier in this thread) said:
unlocked bootloader require unlocked loader, yep ?

loader\loader.sin is special unlocked loader, which will be accepted ONLY after your "unlock" semcboot with previous steps.

to distinguish unlocked semcboot and original semcboot, first letter in version tag of semcboot output will be lower case, i. e. "r8A029"

This means s1tool log file can provide us with verification if we unlocked bootloader correctly.

S1tool link: http://forum.xda-developers.com/showpost.php?p=17374120&postcount=26


Example of log file (mine):

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  
[B][U]9/9/2011 21:45:46 RUNNING S1_EROM VER "r8A029"[/U][/B]
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  
[B][U]9/9/2011 21:45:49 SEMC SIMLOCK CERTIFICATE[/U][/B]
9/9/2011 21:45:49 Elapsed:36 secs.

If the line RUNNING S1_EROM FROM VER "#8A029" has a lowercase "r" letter replacing the "#" (RUNNING S1_EROM FROM VER "r8A029"), your bootloader has been unlocked :D. If it has an uppercase "R" replacing the "#" (RUNNING S1_EROM FROM VER "R8A029"), your bootloader is NOT unlocked :(.

Cheers :D,

SpyderX
 
Last edited:

Paul1989

Senior Member
Aug 6, 2011
263
329
Im confused !!

are you saying my phone has to have been sim unlocked for this to work because i have not had my x8 sim unlocked and i unlocked my boot loader perfectly fine. and thanks to the devs for all their hard work. :D now just gotta compile my own kernal :D
 

lotus13

Senior Member
Welcome to S1 identify tool

TO CONNECT NEXT PHONES
X10 Xperia,E10 Xperia Mini,E15 Xperia X8,U20 Xperia Mini Pro
LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
PRESS AND HOLD "BACK" BUTTON...

PLEASE ATTACH TURNED OFF PHONE NOW

RUNNING S1_EROM VER "r8A029"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "0020/00BC"
LOADER VERSION: "R4A045"

MODEL (from GDFS): E15i
SOFTWARE VERSION: 1236-9291_2.1.1.A.0.6
CUSTOM VERSION: 1241-4091_R3B
FILESYSTEM VERSION: WORLD-1-8_2.1.1.A.0.6
SERIAL NO: CB511RZG51

SEMC SIMLOCK CERTIFICATE
Elapsed:56 secs.

Success ! ty Dev ! you r the best !
 

DeFcOn

Senior Member
Jun 21, 2011
864
243
Győrszemere
Success ! ty Dev ! you r the best !

i turned off my phone, click button in s1tool and connect my phone to computer with pressed back button? and nothing writes only
2011. 09. 09. 19:02:20 Welcome to S1 identify tool
2011. 09. 09. 19:03:03
2011. 09. 09. 19:03:03 TO CONNECT NEXT PHONES
2011. 09. 09. 19:03:03 X10 Xperia,E10 Xperia Mini,E15 Xperia X8,U20 Xperia Mini Pro
2011. 09. 09. 19:03:03 LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
2011. 09. 09. 19:03:03 PRESS AND HOLD "BACK" BUTTON...
2011. 09. 09. 19:03:03
2011. 09. 09. 19:03:03 PLEASE ATTACH TURNED OFF PHONE NOW
2011. 09. 09. 19:03:03
2011. 09. 09. 19:03:39 PROCEDURE STOPPED BY USER
2011. 09. 09. 19:03:39 Elapsed:250 secs.
Please help...
 
  • Like
Reactions: BIG JD

lotus13

Senior Member
i turned off my phone, click button in s1tool and connect my phone to computer with pressed back button? and nothing writes only
2011. 09. 09. 19:02:20 Welcome to S1 identify tool
2011. 09. 09. 19:03:03
2011. 09. 09. 19:03:03 TO CONNECT NEXT PHONES
2011. 09. 09. 19:03:03 X10 Xperia,E10 Xperia Mini,E15 Xperia X8,U20 Xperia Mini Pro
2011. 09. 09. 19:03:03 LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
2011. 09. 09. 19:03:03 PRESS AND HOLD "BACK" BUTTON...
2011. 09. 09. 19:03:03
2011. 09. 09. 19:03:03 PLEASE ATTACH TURNED OFF PHONE NOW
2011. 09. 09. 19:03:03
2011. 09. 09. 19:03:39 PROCEDURE STOPPED BY USER
2011. 09. 09. 19:03:39 Elapsed:250 secs.
Please help...

1.TURN OFF YOUR PHONE.
2.Open S1tool.CLick DO JoB(right side)
3.On your phone:
a.Pressing the back key.connect you phone.untill s1tool says:SEMC SIMLOCK CERTIFICATE
b.DO NOT RELEASE THE BACK KEY!
 

lovex8

Member
May 23, 2011
47
15
1.TURN OFF YOUR PHONE.
2.Open S1tool.CLick DO JoB(right side)
3.On your phone:
a.Pressing the back key.connect you phone.untill s1tool says:SEMC SIMLOCK CERTIFICATE
b.DO NOT RELEASE THE BACK KEY!

Don't have the step 3.On your phone

Just
1.TURN OFF YOUR PHONE.
2.Open S1tool.CLick DO JoB(right side)
3.Pressing the back key.and then connect you phone.untill s1tool says:SEMC SIMLOCK CERTIFICATE
b.DO NOT RELEASE THE BACK KEY!
 

lotus13

Senior Member
Don't have the step 3.On your phone

Just
1.TURN OFF YOUR PHONE.
2.Open S1tool.CLick DO JoB(right side)
3.Pressing the back key.and then connect you phone.untill s1tool says:SEMC SIMLOCK CERTIFICATE
b.DO NOT RELEASE THE BACK KEY!


LOOOOOOOOOOOOOOOL =)))

When i said : On your phone , i meant that the next steps should be done on the phone.as you see a.b.c.
you r an idiot.sorry for telling you this
 

ognjenr

Member
May 24, 2008
16
1
Aftrer connecting i got this message
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
llbug:[\\?\USB#Vid_0fce&Pid_adde#5&256bc46a&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}] open error: "The device does not recognize the command"
Elapsed:30 secs.
where is the problem?
 

SpyderX

Senior Member
Mar 5, 2011
933
933
Singapore
By the way devs, I noticed that bootloader unlocking process puts 4 files in /data/local/tmp (expl, fixPart, mapper_2.6.29.ko and (in my case) my7227bootwrite_semcSL) and executes them.
Is it safe to remove these files? If no, what happens if we remove this files? And what happens if we format our phone's /data partition? Will these files be removed?

Sorry for asking so many questions but these questions are quite important as these pertain to S1Boot and meddling with S1boot can cause hard bricks :(.
 

XperianPro

Senior Member
Nov 19, 2010
2,256
868
Mars
By the way devs, I noticed that bootloader unlocking process puts 4 files in /data/local/tmp (expl, fixPart, mapper_2.6.29.ko and (in my case) my7227bootwrite_semcSL) and executes them.
Is it safe to remove these files? If no, what happens if we remove this files? And what happens if we format our phone's /data partition? Will these files be removed?

Sorry for asking so many questions but these questions are quite important as these pertain to S1Boot and meddling with S1boot can cause hard bricks :(.

android delete all files in this folder by each reboot,so after reboot they will be deleted.
 

SpyderX

Senior Member
Mar 5, 2011
933
933
Singapore
android delete all files in this folder by each reboot,so after reboot they will be deleted.
No, android doesn't. I've rebooted my phone 6 times ever since unlocking my bootloader and the files are still there. Please do your research and experiment with what you have read before posting false information :mad:, especially because you are a "pro".
 
Last edited:

SpyderX

Senior Member
Mar 5, 2011
933
933
Singapore
@moaj
Now that's very strange. Can you put an empty file in /data/local/tmp, reboot, and then see if the empty file is still there? Post your results here.

@Devs

To reiterate in case you only read the last few posts:

By the way devs, I noticed that bootloader unlocking process puts 4 files in /data/local/tmp (expl, fixPart, mapper_2.6.29.ko and (in my case) my7227bootwrite_semcSL) and executes them.
Is it safe to remove these files? If no, what happens if we remove this files? And what happens if we format our phone's /data partition? Will these files be removed?

Sorry for asking so many questions but these questions are quite important as these pertain to S1Boot and meddling with S1boot can cause hard bricks.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 114
    Greetings.

    warning.
    if you are not developer, please quit reading that post.
    wait for user friendly tool with one big button.


    here ( View attachment msm7227.7z) is toolset to permanently "unlock" semcboot of msm7227 semc phones.

    that means, you can use own kernel and so on.

    steps,precautions, etc.

    unpack archive to any directory.

    if you using eset antivirus or similar ****, it will find evil virus in adb.exe.
    ignore that, it is not virus in any way, it is standard android debug bridge, bundled in one file to save space and usability.


    now, if your phone unlocked officially:

    flash phone with standard 2.0,2.1 android firmware,because kernel mapper module compiled for "2.6.29" kernel.

    of course, enable "usb debugging"

    run msm7227_semc.cmd,
    ( if you want, examine it before run, it is pretty straightforward. )

    you will get similar output

    Code:
    process requires standard 2.x android firmware.
    Press any key to continue . . .
    Getting ROOT rights.
    1743 KB/s (585731 bytes in 0.328s)
    error: protocol fault (no status)
    Waiting ...
    Removing NAND MPU restrictions via SEMC backdoor. Permanent. Require ROOT rights.
    192 KB/s (3087 bytes in 0.015s)
    success
    Waiting ...
    Getting ROOT rights.
    Waiting ...
    Writing patched semcboot. Two step process
    First, we need get access to semcboot area
    504 KB/s (8064 bytes in 0.015s)
    Second, we need to write semcboot ;)
    1130 KB/s (596916 bytes in 0.515s)
    successfully wrote 0003ff00
    Press any key to continue . . .

    bingo, your phone now has unlocked bootloader.

    if your phone unlocked by setool2 software, use msm7227_setool2.cmd

    if your phone unlocked by 3rd-party software other than setool2, do not run anything -
    it will disable radio capability of your phone and you will need to unlock phone by setool2 software.

    to find out if you can safely unlock bootloader, here (View attachment s1tool.7z) is tool.

    if you will see "NOT RECOGNIZED SIMLOCK CERTIFICATE", you should not use either of .cmd.

    hopefully, mizerable flea and mOxImKo will release something similar for your phone.



    okay, now about other details.

    1.
    unlocked bootloader require unlocked loader, yep ?

    loader\loader.sin is special unlocked loader, which will be accepted ONLY after your "unlock" semcboot with previous steps.

    to distinguish unlocked semcboot and original semcboot, first letter in version tag of semcboot output will be lower case, i. e. "r8A029"

    ( same applies for loader version tag )

    so, all that stuff with signatures are not for us, so i removed them - loader will ignore signature part of SIN file.

    2.
    we should make SIN file somehow, right ?
    for that i prepared "dumb" bin2sin utility.

    Syntax : bin2sin [input] [partition info, 32 digits] [type] [block size]

    [input] - is input binary file.

    [partition info]
    android implementation on s1 semc qualcomm phones based on partitions,so we MUST define it for our file.

    you can get required partition info from standard semc sin files, it is first 0x10 bytes of DATA, right after header, i.e.
    e10 kernel partition info
    03000000010000402001000040000000

    [type] - partition type, 9 - partition without spare, 0xA - partition with spare.
    kernel partition is partition without spare.
    if that parameter omitted, type = 9

    [block size] - nand block size, if omitted, it is standard size 0x20000

    there is example in sinTools\example_build.cmd

    3.
    kernel should be prepared specially to be accepted by semcboot.
    for that there is tool bin2elf.

    Syntax : bin2Elf.exe [nbrOfSegments] [EntryPoint] [Segment1] [LoadAddress1] [Attributes1] ...

    we need 2 segments:
    segment 1 is unpacked linux kernel image, i.e.
    ( e10/kernel/arch/arm/boot/Image )

    it looks like entrypoint and load address for segment 1 is always same for all msm7227-based semc phone, it is 0x00208000

    attributes for image 0x0

    segment 2 is ramdisk.

    it looks like entrypoint and load address for segment 1 is always same for all msm7227-based semc phone, it is 0x01000000

    set attributes for ramdisk 0x80000000, that is extremly important.

    there is simple kernel example in sinTools\example_build.cmd

    ps.

    @blagus:
    NAND MPU disabler has only one relation to rFoNe - he took it from setool2, together with entire idea for msm7227 bypass.
    your 6-wings friend with many nicks done exactly same.

    NAND MPU has nothing to do with memory firewall, so it will not help with kexec things, however, who will care now.

    edit:
    there was minor flaw in msm7227_setool2.cmd - i forgot to change source bootwriter name and both .cmd wrote same semc boot:

    flawed:
    @echo Second, we need to write semcboot ;)
    bootTools\adb.exe push my7227bootwrite_semcSL /data/local/tmp/my7227bootwrite_setool2SL

    correct:
    @echo Second, we need to write semcboot ;)
    bootTools\adb.exe push my7227bootwrite_setool2SL /data/local/tmp/my7227bootwrite_setool2SL


    of course, every developer or man with capability to read fixed it immediately.
    just in case, i uploaded "fixed" package.

    23
    MSM7227 S1Boot has been patched to ignore SIN header signature by the_laser.

    You need phone which you either did not unlock by cable, or phone which you unlocked via SEtool2 only.

    If you unlocked with Omnius, in C:\ProgramData\Omnius for SE\Backups\Xperia X8
    you have file called: Xperia X8_IMEI_DATE_SIMLock.opd

    Note, the fixed S1Boot for other tools should come soon.

    Restore that TA backup, then use semc.cmd in the_laser's release to unlock bootloader - you'll restore SIM lock this way!
    Currently there is no unlocked bootloader for Omnius unlocked phones.

    * Kernel build instructions in second post.
    * Original post by the_laser with unlock instructions in third post.

    What will this allow:
    * custom kernels
    * better/fully working Gingerbread
    * no need for chroot to avoid init crash bug
    * overclock/Synaptics fake DT/Cypress real DT/MDDI fix built in kernel

    This will not enable:
    * real DT on Synaptics digitizer
    15
    To make custom kernel:

    1) Compile it.
    2) Grab Image, not zImage
    3) Make ramdisk.gz (cpio ramdisk content, then gzip the cpio archive)
    4) Place both files in ./msm7227/sinTools
    5) Name then image and ramdisk, no extension, remove existing files
    6) Exectue example_build.cmd
    7) Grab result.elf.sin from result.zip, rename to kernel.sin and pack in ftf bundle with patched loader.sin from ./msm7227/loader
    8) Flash with FlashTool.
    7
    So make it and we will have one.

    I can't understand why this kind of people still stay in this community.
    2
    How to verify if the bootloader on your phone is really unlocked

    the_laser (earlier in this thread) said:
    unlocked bootloader require unlocked loader, yep ?

    loader\loader.sin is special unlocked loader, which will be accepted ONLY after your "unlock" semcboot with previous steps.

    to distinguish unlocked semcboot and original semcboot, first letter in version tag of semcboot output will be lower case, i. e. "r8A029"

    This means s1tool log file can provide us with verification if we unlocked bootloader correctly.

    S1tool link: http://forum.xda-developers.com/showpost.php?p=17374120&postcount=26


    Example of log file (mine):

    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  
    [B][U]9/9/2011 21:45:46 RUNNING S1_EROM VER "r8A029"[/U][/B]
    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  
    [B][U]9/9/2011 21:45:49 SEMC SIMLOCK CERTIFICATE[/U][/B]
    9/9/2011 21:45:49 Elapsed:36 secs.

    If the line RUNNING S1_EROM FROM VER "#8A029" has a lowercase "r" letter replacing the "#" (RUNNING S1_EROM FROM VER "r8A029"), your bootloader has been unlocked :D. If it has an uppercase "R" replacing the "#" (RUNNING S1_EROM FROM VER "R8A029"), your bootloader is NOT unlocked :(.

    Cheers :D,

    SpyderX