my question is if you flash "normal" loader.sin after unlock... what happends? Thanks!


p.s.
so now we use new loader and >> new kernel generated by sintools <<

@ the_laser

ive got a so-01b and network unlocked it with SEMC S1 Unlock tool
what should i use ?

qsd8250_semc or qsd8250_setool2 ??

Originally Posted by -- X10B --

@ the_laser

ive got a so-01b and network unlocked it with SEMC S1 Unlock tool
what should i use ?

qsd8250_semc or qsd8250_setool2 ??

semc because it's unlocked by EMMA servers.

@the_laser

thank you for ur work...

have a couple of questions:

1) wht do we do if we want to relock bootloader? i am asking just for having a fail-safe option open...

2) can we modify the S1 loader to accept fastboot commands?

3) can we now write to /boot partition in OS/recovery? (raw_write)?

4) the following:

Originally Posted by aZuZu

my question is if you flash "normal" loader.sin after unlock... what happends? Thanks!


p.s.
so now we use new loader and >> new kernel generated by sintools <<

Originally Posted by aZuZu

my question is if you flash "normal" loader.sin after unlock... what happends? Thanks!


p.s.
so now we use new loader and >> new kernel generated by sintools <<

I don't know if it's related to X10 too but the_laser posted this in X8 thread:

Originally Posted by the_laser

Emma/seUS WILL work flawless with phones using that semcboot, because i'm crafting things properly.
BOTH original and "unlocked" loaders will work.

@the_laser

ok done the steps u said to unlock/bypass bootloader...

hi i used one of the custom 2.1 kernel i had (boot.img), dumped the zImage and ramdisk.gz

then used the sinTools u provided to create a result.elf.sin

then renamed it to kernel.sin and created a new ftf using flashtool (and new loader.sin)

then flashed using flashtool

flashing seemed to be successful

but the SE text logo was still there and the kernel info (in About Phone) did not change...

so basically the modified kernel.sin was rejected by the S1 bootloader

any idea?


EDIT:
seems the kernel zimage HAS TO BE CALLED image and ramdisk.cpio.gz HAS TO BE ramdisk
then it works..

right now stuck at bootloop

Originally Posted by colossus

Ok i have done it early this morning as instructed in the op, to be honest i have noticed no difference, i have done a multitoch test and it is still working on 2 but as this is all new maybe we need the Dev's to step in and tell us what to do with this bootloader unlock.

the bootloader unlock doesnt do anything useful by itself unless you have an unsigned kernal you want to flash. Thats why the post is only intended for devs.

Originally Posted by colossus

Ok i have done it early this morning as instructed in the op, to be honest i have noticed no difference, i have done a multitoch test and it is still working on 2 but as this is all new maybe we need the Dev's to step in and tell us what to do with this bootloader unlock.

seriously why should you get full multitouch if you unlock the bootloader? this makes no sense ... yes you need a custom kernel that has full multitouch support (but i doubt the hardware supports it) and then you ll be able to flash it coz of the newly unlocked bootloader ...

Originally Posted by KingCifer

seriously why should you get full multitouch if you unlock the bootloader? this makes no sense ... yes you need a custom kernel that has full multitouch support (but i doubt the hardware supports it) and then you ll be able to flash it coz of the newly unlocked bootloader ...

you would need completely rewritten multitouch drivers....

What the hell do people thing bootloader unlock does?

Originally Posted by colossus

Ok i have done it early this morning as instructed in the op, to be honest i have noticed no difference, i have done a multitoch test and it is still working on 2 but as this is all new maybe we need the Dev's to step in and tell us what to do with this bootloader unlock.

I think it is rather clear that unlocking the bootloader will
just give us possibilities for new things, not new things immediately.

Now, I want to ask: you downgraded to 2.1 and unlocked the bootloader.
After that, were you able to update to 2.3 again?
Also, can you confirm that SEUS still works?