Bootloader Cracking : Devs only
- Thread starter HunteronX
- Start date
- Status
LOL - it's a wee bit small..
Undelete it. I didn't see the picture (@ work they block everything),
@ janderson = I've been deleting your posts since the beginning of the week
. Stop spamming my inbox also.Everyone happy now?.
Back on track.
Bootloader is broken/bypassed!
Big bad huge font to avoid confusion =)
@Goroh_kun:
Buddy, I know you're still reading this forums so... I just want you to know that you are absolutely BRILLIANT. You're a STAR.
BIG thanks for all your contributions into this project! Nothing, and I mean NOTHING would happen without you.
@devs:
@SE: lads, it's your turn now - please unlock it already. I promise we won't brick our phones
@all: DON'T ask for details. I will post here when I'm ready to do so. Today (I guess?) is the Arc release date and stuff, I don't want to mess around...
Still busy working abroad,
Cheers,
z
He reads the board for sure...Thanks to Bin4ry for his belief and efforts.
To all the rest guys/users, russian, chinese, etc forums:
I guess we need to make a good donation to the team right? Or you gonna just use it silently thinking it's supposed to be so by itself? It was good year research to make it happen, so feel a bug inside before you donate
Tschus.
Guys, first, congratulations on great work lately
Second, can someone FINALLY give me simple and precise answer to this question:
What is bootloader, in your terms?
Second Program Loader (SPL)/EROM of SE's phone (S1Boot)/something else?
It's very easy to understand if you read 80-VA593-1_A_AMSS_7500_Secure_Boot_Architecture.pdf
Sorry can't post it here but you can google it to see.
YW
2nd call, stay on topic!. If not I'll star issuing some bans.
Ok, here we go. It wasn't the April Fool thingy
The bootloader has been bypassed using the kexec/miniloader method
We are able to boot custom kernels now!
I'll keep it short as I'm quite busy today... I haven't had much luck with disabling MPU nor resetting a MCPU - it failed no matter what I did. Same thing with porting shutdown procedures into miniloader. But when I found out that the custom kernel doesn't reboot on baseband 52, I switched to the .504 sources and restarted the work. Using the debugfs tips by Goroh, I realised some stuff I'd rather to keep in between the developers here... And then *poof* - the green USB led appeared and I knew I was getting there!
Anyway... this is the first release of the fully working custom kernel (flashable via xRecovery). I haven't had much time to work on it so it's kind of proof-of-concept. Tested for 48h without any problem (not even a reboot).
FreeKernel-alpha1:
http://www.mediafire.com/?d8v914keiqsmc3n
This is the alpha version of custom 2.6.29 kernel based on the SE sources. I do not plan to work on this release anymore - it is just for testing purpose. From today on I'll start to port SE stuff to the latest (GBread) kernel.
Changes:
- removed 32 fps cap
- implemented netfilter (Droid wall, native USB/wifi tethering etc.)
- undervolted to 0.950mV to save battery
- don't remember what else I did, I bet something nasty
- super ugly boot logo!
Requirements:
- baseband .52 + the relevant kernel
- clean 2.1 ROM, compatibile with .52 baseband (e.g. .504)
- working xRecovery
Please note I am not responsible for any damage this software may cause to your device! Use it at your own risk!
There is absolutely no support for this alpha release!
Big thanks to (no particular order): Goroh_kun, Jerpelea, Bin4ry, Maxrfon, Biktor_gj and everybody else who contributed into X10 custom kernel development.
At first the relevant kernel patches/sources will be delivered to the recognised X10 developers. Later on everything will be released as it's obviously Open Sourced.
Please refrain from posting comments in this thread - it's for developers only. Spamming will only make our task harder to accomplish!
Cheers,
z
The bootloader has been bypassed using the kexec/miniloader method
We are able to boot custom kernels now!
I'll keep it short as I'm quite busy today... I haven't had much luck with disabling MPU nor resetting a MCPU - it failed no matter what I did. Same thing with porting shutdown procedures into miniloader. But when I found out that the custom kernel doesn't reboot on baseband 52, I switched to the .504 sources and restarted the work. Using the debugfs tips by Goroh, I realised some stuff I'd rather to keep in between the developers here... And then *poof* - the green USB led appeared and I knew I was getting there!
Anyway... this is the first release of the fully working custom kernel (flashable via xRecovery). I haven't had much time to work on it so it's kind of proof-of-concept. Tested for 48h without any problem (not even a reboot).
FreeKernel-alpha1:
http://www.mediafire.com/?d8v914keiqsmc3n
This is the alpha version of custom 2.6.29 kernel based on the SE sources. I do not plan to work on this release anymore - it is just for testing purpose. From today on I'll start to port SE stuff to the latest (GBread) kernel.
Changes:
- removed 32 fps cap
- implemented netfilter (Droid wall, native USB/wifi tethering etc.)
- undervolted to 0.950mV to save battery
- don't remember what else I did, I bet something nasty
- super ugly boot logo!
Requirements:
- baseband .52 + the relevant kernel
- clean 2.1 ROM, compatibile with .52 baseband (e.g. .504)
- working xRecovery
Please note I am not responsible for any damage this software may cause to your device! Use it at your own risk!
There is absolutely no support for this alpha release!
Big thanks to (no particular order): Goroh_kun, Jerpelea, Bin4ry, Maxrfon, Biktor_gj and everybody else who contributed into X10 custom kernel development.
At first the relevant kernel patches/sources will be delivered to the recognised X10 developers. Later on everything will be released as it's obviously Open Sourced.
Please refrain from posting comments in this thread - it's for developers only. Spamming will only make our task harder to accomplish!
Cheers,
z
Last edited:
New Thread for feedback purposses
In order to keep this thread clean I create a new thread where feedback for this alfa release can be post.
I hope this help to keep this thread on topic while given the opportunity to devs to get feedback from the community.
Since future releases would be done through recognized devs, this thread would be only for Z's alpha release.
In order to keep this thread clean I create a new thread where feedback for this alfa release can be post.
I hope this help to keep this thread on topic while given the opportunity to devs to get feedback from the community.
Since future releases would be done through recognized devs, this thread would be only for Z's alpha release.
A little something I made to review zdzihu's work.
http://www.youtube.com/watch?v=-MItVzcgq74
Z/devs, if you find this offensive/inappropriate please PM me and I will take it down, no questions asked. I would not want to offend you.
MOD. If you think that this is not the appropriate thread/or spam, feel free to move the post
EDIT: Tested on Trip's latest MIUI release, and it's a no go. The FPS2D averaged at 30...
EDIT2: as a matter of fact, it brought the kernel back to stock, even though i flashed through xrecovery...
EDIT3: Very smooth live wallpapers. no noticeable performance decrease.
EDIT4: @Z. Just fyi, I think you set the CPU voltage too low, because I got a couple of random shutdowns. And they didn't seem like the regular "somethingwrongwiththesystem" shutdowns. So, just for the future reference, if you are going to undervolt your other kernels, know that this is too low. Note shutdowns. not FC/restart
I love my phone again....
http://www.youtube.com/watch?v=-MItVzcgq74
Z/devs, if you find this offensive/inappropriate please PM me and I will take it down, no questions asked. I would not want to offend you.
MOD. If you think that this is not the appropriate thread/or spam, feel free to move the post
EDIT: Tested on Trip's latest MIUI release, and it's a no go. The FPS2D averaged at 30...
EDIT2: as a matter of fact, it brought the kernel back to stock, even though i flashed through xrecovery...
EDIT3: Very smooth live wallpapers. no noticeable performance decrease.
EDIT4: @Z. Just fyi, I think you set the CPU voltage too low, because I got a couple of random shutdowns. And they didn't seem like the regular "somethingwrongwiththesystem" shutdowns. So, just for the future reference, if you are going to undervolt your other kernels, know that this is too low. Note shutdowns. not FC/restart
I love my phone again....
Last edited:
Great job!
Hi, long time no see.
It's goroh.
> zdzihu.
I'd like to say, Your strong effort and indefatigableness achieve this brilliant work!
I have parted with my X10a, but I'm looking forward to see development goes on.
Hi, long time no see.
It's goroh.
> zdzihu.
I'd like to say, Your strong effort and indefatigableness achieve this brilliant work!
I have parted with my X10a, but I'm looking forward to see development goes on.
Donation thread in ON
Guys, send me your links. I believe you deserve it!
http://xdaforums.com/showthread.php?p=12588947#post12588947
Guys, send me your links. I believe you deserve it!
http://xdaforums.com/showthread.php?p=12588947#post12588947
True Multiboot (coming up) next...
Awesome! Goroh, Bin4ry, Zdzihu! Just a few hours.. We will have a widget as you described Bin4ry to handle the loading of the custom kernels and side loading via loading xRecovery
I've got the sources for an Eclipse project, based on DooMLoRD mod in /system/bin/chargemon = used classes from Apache.org to handle string replacement and is just a simple Widget... P.M if you like these source - happy to provide!
Best Regards!
MrHassell
Awesome! Goroh, Bin4ry, Zdzihu! Just a few hours.. We will have a widget as you described Bin4ry to handle the loading of the custom kernels and side loading via loading xRecovery
I've got the sources for an Eclipse project, based on DooMLoRD mod in /system/bin/chargemon = used classes from Apache.org to handle string replacement and is just a simple Widget... P.M if you like these source - happy to provide!
Best Regards!
MrHassell
Last edited:
MrHassell talks to Sony Ericsson
http://blogs.sonyericsson.com/devel...e-boot-loader-in-the-new-xperia™-smartphones/
Resistance is futile ;-)
EDIT 1:
"If your phone can connect to Fastboot, the boot loader can be unlocked. For earlier products such as the Xperia™ X10, we cannot allow the boot loader to be unlocked due to technical and legal reasons."
EDIT 2:
A boot loader with unlock functionality would unlock all Xperia™ X10s. But we cannot do that since we have agreement with several operators regarding what software is in the devices.
EDIT 3:
So I contacted Sony Ericsson with a few questions to ask, mainly as I think we all really deserve to know this. Many people feel in some way they have been 'duped' or tricked by SE with the X10 device and the implementation of such extreme (unnecessary?) security measures in the boot loader, I feel torn between my head and heart on how to place these questions, but anyone who has read my posts over the few month's will know I speak from the heart.
This is a copy of my post and questions - Mr Karl-Johan Dahlström - Senior Program Architect (Sony Ericsson)
What role does > Octopus / Marlin DRM the Sushi client and Nautilus web services have to play in Android mobile phones?
What is your position regarding Copyright law and firmware modification being legal?
How do you respond to your restrictive boot loader is in effect hampering this consumer right, in effect making any agreements that you have in place with your "suppliers", legally void?
April 1 an official bypass to the boot loader lock was delivered and previous efforts have also worked, in the lead up to this event. Soon this protection scheme, will be completely redundant.
How does Sony Ericsson respond to this?
http://blogs.sonyericsson.com/devel...e-boot-loader-in-the-new-xperia™-smartphones/
Resistance is futile ;-)
EDIT 1:
"If your phone can connect to Fastboot, the boot loader can be unlocked. For earlier products such as the Xperia™ X10, we cannot allow the boot loader to be unlocked due to technical and legal reasons."
EDIT 2:
A boot loader with unlock functionality would unlock all Xperia™ X10s. But we cannot do that since we have agreement with several operators regarding what software is in the devices.
EDIT 3:
So I contacted Sony Ericsson with a few questions to ask, mainly as I think we all really deserve to know this. Many people feel in some way they have been 'duped' or tricked by SE with the X10 device and the implementation of such extreme (unnecessary?) security measures in the boot loader, I feel torn between my head and heart on how to place these questions, but anyone who has read my posts over the few month's will know I speak from the heart.
This is a copy of my post and questions - Mr Karl-Johan Dahlström - Senior Program Architect (Sony Ericsson)
What role does > Octopus / Marlin DRM the Sushi client and Nautilus web services have to play in Android mobile phones?
What is your position regarding Copyright law and firmware modification being legal?
How do you respond to your restrictive boot loader is in effect hampering this consumer right, in effect making any agreements that you have in place with your "suppliers", legally void?
April 1 an official bypass to the boot loader lock was delivered and previous efforts have also worked, in the lead up to this event. Soon this protection scheme, will be completely redundant.
How does Sony Ericsson respond to this?
Last edited:
latest change log for EMMA... (same for SEUS)
2.11.4 2011-04-04 A new URL is used when communicating with the server. It might therefore be required to modify the local firewall settings so that traffic is allowed towards this new URL.
URL: emma.extranet.sonyericsson.com
Port: 80
Upgraded client platform.
Tampered phones detection added.
Rooted phones detection added.
TAMPERED? Who did that??
2.11.4 2011-04-04 A new URL is used when communicating with the server. It might therefore be required to modify the local firewall settings so that traffic is allowed towards this new URL.
URL: emma.extranet.sonyericsson.com
Port: 80
Upgraded client platform.
Tampered phones detection added.
Rooted phones detection added.
TAMPERED? Who did that??
- Status
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
161Bootloader is broken/bypassed!
Big bad huge font to avoid confusion =)
@Goroh_kun:
Buddy, I know you're still reading this forums so... I just want you to know that you are absolutely BRILLIANT. You're a STAR.
BIG thanks for all your contributions into this project! Nothing, and I mean NOTHING would happen without you.
@devs:
@SE: lads, it's your turn now - please unlock it already. I promise we won't brick our phones
@all: DON'T ask for details. I will post here when I'm ready to do so. Today (I guess?) is the Arc release date and stuff, I don't want to mess around...
Still busy working abroad,
Cheers,
z144Ok, here we go. It wasn't the April Fool thingy
The bootloader has been bypassed using the kexec/miniloader method
We are able to boot custom kernels now!
I'll keep it short as I'm quite busy today... I haven't had much luck with disabling MPU nor resetting a MCPU - it failed no matter what I did. Same thing with porting shutdown procedures into miniloader. But when I found out that the custom kernel doesn't reboot on baseband 52, I switched to the .504 sources and restarted the work. Using the debugfs tips by Goroh, I realised some stuff I'd rather to keep in between the developers here... And then *poof* - the green USB led appeared and I knew I was getting there!
Anyway... this is the first release of the fully working custom kernel (flashable via xRecovery). I haven't had much time to work on it so it's kind of proof-of-concept. Tested for 48h without any problem (not even a reboot).
FreeKernel-alpha1:
http://www.mediafire.com/?d8v914keiqsmc3n
This is the alpha version of custom 2.6.29 kernel based on the SE sources. I do not plan to work on this release anymore - it is just for testing purpose. From today on I'll start to port SE stuff to the latest (GBread) kernel.
Changes:
- removed 32 fps cap
- implemented netfilter (Droid wall, native USB/wifi tethering etc.)
- undervolted to 0.950mV to save battery
- don't remember what else I did, I bet something nasty
- super ugly boot logo!
Requirements:
- baseband .52 + the relevant kernel
- clean 2.1 ROM, compatibile with .52 baseband (e.g. .504)
- working xRecovery
Please note I am not responsible for any damage this software may cause to your device! Use it at your own risk!
There is absolutely no support for this alpha release!
Big thanks to (no particular order): Goroh_kun, Jerpelea, Bin4ry, Maxrfon, Biktor_gj and everybody else who contributed into X10 custom kernel development.
At first the relevant kernel patches/sources will be delivered to the recognised X10 developers. Later on everything will be released as it's obviously Open Sourced.
Please refrain from posting comments in this thread - it's for developers only. Spamming will only make our task harder to accomplish!
Cheers,
z
