@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!
ok i got a question:
manually copy/paste the needed files so that i get stock kernel
2.6.29-00054-g5f01537
SEMCUser@SEMCHost #1
Sun Jun 19 22:24:46 2011
previously had Doom´s v4b
than run cmd file but i got this:
how come?
Thks
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)
http://www.x10unlocked.com/
that is the site where i did it...it does it in a super secret way...which i think is the same way setool does it.
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?
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
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
got it ...but. did you have it? these days i ain´t have almost anything
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 kernel
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 . . .
Syntax : bin2sin [input] [partition info, 32 digits] [type] [block size]
Syntax : bin2Elf.exe [nbrOfSegments] [EntryPoint] [Segment1] [LoadAddress1] [Attributes1] ...
@the_laser
1) wht do we do if we want to relock bootloader? i am asking just for having a fail-safe option open...
3) can we now write to /boot partition in OS/recovery? (raw_write)?
yaay my 2.3.3 custom kernel booted
no more SE text logo!!!
@all
KINDLY STOP CHATTING IN THIS THREAD
you can write whatever you want, but it is better stick to semc standards and use SIN files.wht i wanted is the ability to flash boot.img via recovery (raw_write/flash_image)
will that work?
also there seems to be restriction on size of kernel.sin... i tired a large ramdisk and flash was accpeted but ramdisk was unchanged