FORUMS

Galaxy S6 & Edge get €100 Price Cut—New Models Incoming

Samsung has dropped the price of both the Galaxy S6 and S6 Edge by … more

How To Port Fully Featured Sony Xperia Z4 Camera

Xperia Z4’s hardware may not impress, but its software is definitely … more

Experimental TWRP Available For Moto G 2015

XDA Senior Member squid2 has posted experimental builds of TWRP for the Moto G … more

Sunday Debate: How Can We Get a No-Compromise Phone?

Join us in a fun Sunday Debate on Compromises. Come with your opinions and … more

[Dev] Bypass "bootloader" [PROPER METHOD]

159 posts
Thanks Meter: 835
 
By the_laser, Senior Member on 8th September 2011, 01:03 AM
Post Reply Subscribe to Thread Email Thread
8th September 2011, 09:15 AM |#31  
aZuZu's Avatar
Recognized Developer
Flag Zagreb
Thanks Meter: 933
 
More
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 <<
Last edited by aZuZu; 8th September 2011 at 09:37 AM.
The Following 2 Users Say Thank You to aZuZu For This Useful Post: [ View ]
 
 
8th September 2011, 10:26 AM |#32  
-- X10B --'s Avatar
Senior Member
Flag Antipolo
Thanks Meter: 126
 
Donate to Me
More
@ 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 ??
8th September 2011, 10:28 AM |#33  
Blagus's Avatar
Recognized Developer
Thanks Meter: 1,054
 
Donate to Me
More
Quote:
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 Following User Says Thank You to Blagus For This Useful Post: [ View ]
8th September 2011, 10:45 AM |#34  
DooMLoRD's Avatar
Recognized Developer
Flag Gurgaon
Thanks Meter: 39,534
 
More
@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:
Quote:
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 <<

Last edited by DooMLoRD; 8th September 2011 at 11:02 AM.
The Following User Says Thank You to DooMLoRD For This Useful Post: [ View ]
8th September 2011, 11:06 AM |#35  
iridaki's Avatar
Retired Forum Moderator / Recognized Themer
Flag Edinburgh, Scotland
Thanks Meter: 5,063
 
Donate to Me
More
Quote:
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:

Quote:
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.

8th September 2011, 11:33 AM |#36  
DooMLoRD's Avatar
Recognized Developer
Flag Gurgaon
Thanks Meter: 39,534
 
More
@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
Last edited by DooMLoRD; 8th September 2011 at 11:57 AM.
8th September 2011, 11:40 AM |#37  
Senior Member
Thanks Meter: 653
 
More
Quote:
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.
8th September 2011, 11:41 AM |#38  
Member
Flag Vienna
Thanks Meter: 3
 
More
Quote:
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 ...
8th September 2011, 11:44 AM |#39  
Account currently disabled
Thanks Meter: 596
 
More
Quote:
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?
8th September 2011, 11:46 AM |#40  
iridaki's Avatar
Retired Forum Moderator / Recognized Themer
Flag Edinburgh, Scotland
Thanks Meter: 5,063
 
Donate to Me
More
Quote:
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?
8th September 2011, 11:49 AM |#41  
Senior Member
Thanks Meter: 29
 
More
Quote:
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.

Multitouch support is only related to the kernel. Not the bootloader. the_laser's bootloader allows us to flash unsigned sin files, as the signature part of a sin file is now ignored. So I think that the new 'bin2sin' utility creates a flashable file, without the signature included.

I'm not sure if there is a way to change the partition sizes of the phone, though, which could allow for more space for apps, and less for system files etc.

This whole thing should mean that we could flash any OS onto our X10's, like the Windows Phone 7, to a distro of Linux, to Windows CE and more, or just create and use the latest kernel for Android (at the moment), and permanently flash it. We could also make a permanent recovery partition, like with a lot of other android phones.

I'm not a developer yet (maybe after my 3 year Computer Science course at uni, I will be), but I'm just interested in stuff like this, is all.
The Following User Says Thank You to HunteronX For This Useful Post: [ View ]

Read More
Post Reply Subscribe to Thread

Tags
bl unlock, bootloader unlocked, go devs!
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes