@the_laser
I bought my phone already unlocked, I mean, from box, it was unlocked to all networks.
1.Which one should I use to unlock BL?
2. And is there any method to know what tool was use unlock the network of the phone? So that we can determined which tool we must use.
Thanks!
Would love to know this!
But, I thought you need to have the old 2.6.29 kernel, not the one modified for 2.3.3? Isn't it right?
that´s the stock one (i think?!?!
) and what the_laser is talkin is about 2.0.xxxx and/or 2.1.xxxx (baseband)
you need ANDROID 2.1
Sent from my R800i
that´s the stock one (i think?!?!
and what the_laser is talkin is about 2.0.xxxx and/or 2.1.xxxx (baseband)
Sent from my R800i
that just makes no sense. We NEVER had 2.0 so i don´t believe the_laser will reefer that
@the_laser
can you clarify this?
Thks
edit:
2.0.xx versions
2.1.xx versions
Last edited:
I'm a bit confused, wasn't the bootloader unlocked back in July?
http://www.xperiax10.net/2011/07/09/xperia-x10-bootloader-finally-unlocked/
What is new this time?
http://www.xperiax10.net/2011/07/09/xperia-x10-bootloader-finally-unlocked/
What is new this time?
Hey thanks for the reply but my phone is already unlocked i'm just not sure how it was unlocked. I know it's a Phones 4 U one...?
I'm a bit confused, wasn't the bootloader unlocked back in July?
http://www.xperiax10.net/2011/07/09/xperia-x10-bootloader-finally-unlocked/
What is new this time?
What's new is we are able to unlock it on our phones.
It was unreleased back then.
that just makes no sense. We NEVER had 2.0 so i don´t believe the_laser will reefer that
@the_laser
can you clarify this?
Thks
This is the clarification you've been wanting for.
i would like someone who (at least) install this respond. Why? Again...you both make no sense. Why? Check THIS
He´s ON 2.3.3 so.....AGAIN. Why that appear on me?
thks
hi Crowds... u need to downgrade to official SE 2.1 FW and then execute the unlock process...
then u can flash 2.3.3 FW...
aZuZu has a good idea... may be u can just downgrade the kernel to 2.1 kernel and then execute the unlock process and then reflash to 2.3.3 kernel to upgrade newest kernel with bootloader unlocked
hi Crowds... u need to downgrade to official SE 2.1 FW and then execute the unlock process...
then u can flash 2.3.3 FW...
aZuZu has a good idea... may be u can just downgrade the kernel to 2.1 kernel and then execute the unlock process and then reflash to 2.3.3 kernel to upgrade newest kernel with bootloader unlocked
got it ...but. did you have it?
these days i ain´t have almost anythingi read that on your thread
EDIT: or may i run his downgrade kernel?
got it ...but. did you have it?
i read that on your thread
try the kernel downgrade & kernel upgrade files posted by aZuZu... those should work...
kernel downgrade: 2.1 kernel
kernel upgrade: 2.3.3 kernel
ok.
just tested and it doesn`t work
always reboot after SE logo so i never able to run the cmd file and then upgrade kernelok.
just tested and it doesn`t work
may be try a FULL flash of first 2.1 FW then run unlock process... then flash 2.3.3 FW...
D
Deleted member 3665957
Guest
Greetings.
due to confusion with simlocks, i made small identification tool.
to find out what tool was used to unlock your phone, use that (View attachment 713763 ) tool.
if you will see "NOT RECOGNIZED SIMLOCK CERTIFICATE", you are out of luck.
due to confusion with simlocks, i made small identification tool.
to find out what tool was used to unlock your phone, use that (View attachment 713763 ) tool.
if you will see "NOT RECOGNIZED SIMLOCK CERTIFICATE", you are out of luck.
Last edited by a moderator:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
159DDeleted member 3665957Greetings.
warning.
if you are not developer, please quit reading that post.
wait for user friendly tool with one big button.
here ( View attachment qsd8250.7z) is toolset to permanently "unlock" semcboot of qsd8250 semc phones ( x10a,x10i, so-o1b )
that means, you can use own kernel and so on.
it is much more better,stable,faster method, than present "bypass".
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 qsd8250_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. 1464 KB/s (585731 bytes in 0.390s) 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 ;) 1531 KB/s (588236 bytes in 0.375s) successfully wrote 0001ff80 Press any key to continue . . .
bingo, your phone now has unlocked bootloader.
if your phone unlocked by setool2 software, use qsd8250_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.
hopefully, mizerable flea and mOxImKo will release something similar for your phone.
to find out what tool was used to unlock your phone, use that ( View attachment s1tool.7z ) tool.
if you will see "NOT RECOGNIZED SIMLOCK CERTIFICATE", you are out of luck.
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. "r8A033"
( 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.
[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.
[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.
we need 2 segments:
segment 1 is unpacked linux kernel image, i.e.
( x10/kernel/arch/arm/boot/Image )
it looks like entrypoint and load address for segment 1 is always same for all qsd8250-based semc phone, it is 0x20008000
attributes for image 0x0
segment 2 is ramdisk.
it looks like entrypoint and load address for segment 1 is always same for all qsd8250-based semc phone, it is 0x24000000
set attributes for ramdisk 0x80000000, that is extremly important.
there is simple kernel example in sinTools\example_build.cmd
ps.
patched semcboot is doing exactly same thing as official "bootloader unlock" ( for some idiotic reasons called "rooting" ) , it skips checking of aARM firmware part ONLY.
it will NOT unlock your phone from network.
after procedure, you CAN use Emma/seUS safely.14DDeleted member 3665957
"unlocked" bootloader does absolutely same things as original, nothing changed.
no need to return back
it is like writing it from scratch.
better build some kernel module for that.
sin signature checking removed totally, you can write anything in phone.
however, there is few restrictions:
1.
partition info and sin type should be proper.
you can check partition info in corresponding original semc firmware files.
2.
semcboot WILL check following and STOP phone in case of failure:
- security zone validity
- FOTA code validity
- mARM ( AMSS or modem code ) validity
- DSP code validity
you can safely build and flash own
kernel_S1-SW-LIVE-AC12-0001-S1-PARTITION.sin
system_S1-SW-LIVE-AC12-0001-S1-PARTITION-WITH-SPARE.sin
userdata_S1-SW-LIVE-AC12-0001-S1-PARTITION-WITH-SPARE.sin
again, do not forget use proper SIN type.11yaay my 2.3.3 custom kernel booted
no more SE text logo!!!
@all
KINDLY STOP CHATTING IN THIS THREAD
THAT'S AWESOME NEWS!
And the X10 gets yet another successful burst from the Dev defibrillator! It is alive and kicking once more!
Here's been the timeline of the X10. It's quite spectacular actually.
-Pre-release. Huge hype and frenzy and craziness
-Release-Even more craziness and hype
-Post-release-dissapointment at locked bootloader and FPS cap and lag
-Most of 2010-dissapointment at lack of updates, 2.1 delay, lack of rooting
-Late 2010-Huge hype about 2.1 and its release, phone rooted, dualtouch, phone alive again
-Early 2011-Great new custom ROMs, phone is alive and kicking, bootloader bypass
-March 2011-Gingerbread update news, Bootloader bypassed, 2.2 Camera
-April-June 2011-Dissapointment over no update by SE
-July-August 2011-Huge craze over upcoming 2.3 update and wild speculation begins
-August 2011-Release of GB. Mixed reviews but mostly positive. New life breathed into X10. Great stuff ported from Arc.
-September 2011-Bootloader UNLOCKED! Even more awesomeness coming up!
Which phone has this kind of history, ever?!
-7DDeleted member 3665957to solve confusions:
to unlock bootloader you DO NOT need to have "network unlocked" phone.
however, if your phone was unlocked from network by any other 3rd-party tool than setool2, your phone will lose radio capability due to mismatched security zone.
to restore radio capability and have unlocked bootloader you will need "unlock from network" phone using setool2.
but not worry, i'm sure, that omnibus software will soon "integrate" that method6DDeleted member 3665957@doomlord:
you can write whatever you want, but it is better stick to semc standards and use SIN files.
maximum partition size is 0x62 blocks ( 0xC40000 bytes ) for x10i
dunno about ramdisk/etc restrictions .
