yashsingh1/xdaforums huggingface dataset:
[XPERIA X10 Android Development] break1:
Goddamn z, we miss you :) seems like u really know what u're talking about. Hopefully bin4ry and jerpelea will make progress this way :) thank you for 720p fix!
[XPERIA X10 Android Development] Bin4ry:
Hey Zdzihu,

yes you are right =) But we are also patching another things in the kernel, to see what we need to port it to a newer version.

At the moment i'm looking for a way to reset MCPU from miniloader, but maxrfon didn't gave me much hope MCPU will ever release DMA without resetting the phone. I will try to port it like you did, let's see what it makes :P

I think the best approach we can do is hijacking kernelpartition just like system patition. For that i digged out the old more-mtd sources.

Feel free to contribute :) It's all on git.

Regards

Bin4ry
[XPERIA X10 Android Development] Bin4ry:
Fist time i spam myself:

http://xdaforums.com/showthread.php?t=1010873

Regards

Bin4ry
[XPERIA X10 Android Development] MrHassell:
no no no... hoping that you change your mind! Understand and appreciate you have work and studies, you will be sorely missed my friend! :(
[XPERIA X10 Android Development] agentJBM:
Bin4ry, I posted this in your goodbye thread, but if you decide to answer me I think it would be more useful here.
[XPERIA X10 Android Development] aZuZu:
damn...

bastards they killed kenny...

bye [ till you again end up with same phone as some of us.. ]

P.S.

Can make some sale deal for you X10 off the book? :D :D :D
[XPERIA X10 Android Development] DooMLoRD:
sorry for OT (but couldnt resist)

it actually goes like this:

"Oh my God, they killed Kenny! You bastards!"

:D

sorry of spamming
[XPERIA X10 Android Development] chiefy009:
http://xdaforums.com/showthread.php?t=1011941

donation thread if anyone wants to help keep Bin4ry developing the x10
[XPERIA X10 Android Development] _j_:
x-mas came early this year :)

http://blogs.sonyericsson.com/devel...e-boot-loader-in-the-new-xperia™-smartphones/
[XPERIA X10 Android Development] mayank.1love:
way towards bootloader ;-)

do anyone here know something about "qc ril oem hook"?

edit:

qc ril oem hook = Qualcomm Radio Interface Layer OEM Hook
[XPERIA X10 Android Development] -PiLoT-:
Neither is talking to people like dirt

please use respect no matter who it is you talk to

Not only is it a rule its common courtesy

PiLoT
[XPERIA X10 Android Development] mobby0411:
@ j.anderson618 mate i've seen you pasting these all over the place and i'm confused are you just going to be pasting info like this or will you be posting a full guide of how you got to this stage perhaps some video ? nobody will stand up and take notice unless you can back up what your saying with proof i mean with regards to the bootloader not root:cool:
[XPERIA X10 Android Development] ratheen:
do we need to ba able to mount "/" ?

Hi All

I was able to re create what Anderson here said he did here (http://xdaforums.com/showthread.php?t=1011175)

I am not a developer, but is getting a mount on / what you need?

if so i can post a guide of how i got it.

the images below are Anderson's but i have managed to get to the same point.

I am just trying to help. Mods please delete if this is of no use.
[XPERIA X10 Android Development] Yperion:
Every one with a rooted phone can have rw acces to the fs... Thats nothing to do with bootloader...
[XPERIA X10 Android Development] j.anderson618:
http://img17.imageshack.us/i/snap20110330192123.png/

http://db.tt/DDLAfrh

Multiple root certificates my laptop put on my phone.. Microsoft root authority is the one that probably did it though

Copy them to etc/permissions/
[XPERIA X10 Android Development] MrHassell:
/dev/block/mtdblock1 /cache yaffs2 rw,nosuid,nodev 0 0

Remove. Please.

Yeah probably.. Microsoft make great security products. J... may I called you J... Mr Anderson?

I've got to ask you, if you go into the application in your app tray called "Superuser" (the one with the super man logo)... take one of the applications in the allow for root list - or all - and set them to deny or forget... what happens?

EDIT: J.Anderson sent me an xRecovery backup and I've examined it very carefully, thank you J. Nothing at all unusual here as previously mentioned many times. This is very frustrating..
[XPERIA X10 Android Development] Neo.:
I'm really worried. Is anyone working on this project now? I was so damn excited that I kept reading this thread over & over (Refresh ftw). But after looking at b4nary leaving, I broke down. I was pretty darn confident that someone will break the bootloader for sure (It's just a matter of time) but looking at this thread dead I'm just wondering if someones working on it?

Ofcourse, We have VERY good devs like J,zidhu,WB. But is anyone working on bootloader cracking til now. Anything that could lead us to the solution since I don't see any more bootloader issue with future xperias. So I guess we're only left with x10 bootloader challenge!

I really hope someone can break this down.

ON Topic: I have read numerous posts gegarding keys cracked down and used on PS3. Can this be helpful for x10 in anyway.
[XPERIA X10 Android Development] mayank.1love:
Hi,

About the radio interface layer I asked before in this thread, I was decompiling the sony ericsson service menu apk(the menu that appears by pressing home back back home back home home back). In service menu-> sim lock the apk is accessing some part within the mobile to know if its sim locked or not, I am trying to understand the functions used by SE to access the sim lock area.

In service tests-> security the apk initiates some tests to check SEMC key,VIACCESS key and MARLIN key, here too I am trying to understand how the apk uses SE classes to verify the certificates.

The main package that service menu uses for all its functionality is package com.sonyericsson.android.servicemenu.servicetests;

The main point is that from within the package the apk is using qcrilhook.jar which contains SemcPhoneInterfaceManager which by my opinion is what we are looking for. It may the the SE propriety way to access the bootloader area.

I'll post about this with original qcrilhook java codes, simlock checking java code and SemcPhoneInterfaceManager java code so that devs can analyze it properly. If qcrilhook is really what I think it is we can easily access the bootloader by making our own apk and executing it in X10.

Hope this all makes some sense.:p

Regards

Mayank

If anyone here have any more info on qcrilhook pm me.
[XPERIA X10 Android Development] zdzihu:
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
[XPERIA X10 Android Development] Mr. Clown:
Please stay on topic. I'm getting tons of reports from this thread.
[XPERIA X10 Android Development] GreatBigDog:
Here is the missing pic from Z post.
[XPERIA X10 Android Development] away:
hope this helps :)
[XPERIA X10 Android Development] Mr. Clown:
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.
[XPERIA X10 Android Development] maxrfon:
;) 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.
[XPERIA X10 Android Development] maxrfon:
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
[XPERIA X10 Android Development] Mr. Clown:
2nd call, stay on topic!. If not I'll star issuing some bans.
[XPERIA X10 Android Development] zdzihu:
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
[XPERIA X10 Android Development] tremeree:
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.
[XPERIA X10 Android Development] i_rakov:
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....
[XPERIA X10 Android Development] goroh_kun:
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.

:)
[XPERIA X10 Android Development] maxrfon:
Donation thread in ON

Guys, send me your links. I believe you deserve it!

http://xdaforums.com/showthread.php?p=12588947#post12588947
[XPERIA X10 Android Development] MrHassell:
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 :D

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
[XPERIA X10 Android Development] HunteronX:
Amazing stuff, guys! :D

I'll be updating the front page soon.

It's also nice to see you back, goroh_kun. :)
[XPERIA X10 Android Development] MrHassell:
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?
[XPERIA X10 Android Development] aR_ChRiS:
it's not for the x10 though =(
[XPERIA X10 Android Development] Ferrum Master:
Then why the key generation?

-------------------------------------

Sent via X10i Wolfbreak v54
[XPERIA X10 Android Development] coolsid8:
Because it will not be available for all phones.
[XPERIA X10 Android Development] superleeds27:
So MrHassell, is what he says any good? lol
[XPERIA X10 Android Development] Ferrum Master:
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??
[XPERIA X10 Android Development] Ferrum Master:
It is an open site for EMMA where the change logs are kept and doesn't require a login. So screw them...

But it is quite funny for what platform they've added the tamper detection? Not for S1 then? And did they already sniff around Z's alpha patched kernel version for stock 2.1? Then we have spies around here... :D

Tampered detection historically meant altered CID certificate... ie Brown or Blue one...

I think only Mr. Laser could give us a precise explanation what is going on.

Despite the news from SE Dev site, that they will grant an open Boot loader for new phones, what the heck is this!? - root detection... ? The warranty thing is getting quite messed up. One end in SE's department doesn't know/hear what the other one does...

The second thing, that is concerning me most of all - Warranty service. Imagine if some buttons stop working? Blank LCD? And service center detects this evil rooted, kernel patched and so on unit... oh gosh and dear EMMA detects it... ? Bye, Bye warranty?, pay us money? Funny eh?
[XPERIA X10 Android Development] -PiLoT-:
Ok Thread Cleaned and j.Anderson banned
[XPERIA X10 Android Development] Blagus:
Where can we get splboot sources? It was posted long time ago in this thread but Hotfile removed it...
[XPERIA X10 Android Development] zdzihu:
Here's the kernel image with possible in-call volume fix. Howto:

- install the alpha kernel package

- copy this boot.img into /system/kernel

Please let me know whether the call volume is fixed for you (in the "comments/feedback" threads.)

http://www.mediafire.com/?uxc0ht1tyvl0qdx

This is for testers/developers only!

--- q6audio.c~ 2011-04-05 08:29:25.653333350 +0200
+++ q6audio.c 2011-04-05 08:29:25.696666684 +0200
@@ -54,7 +54,9 @@
static struct q6_hw_info q6_audio_hw[Q6_HW_COUNT] = {
[Q6_HW_HANDSET] = {
.min_gain = -900,
- .max_gain = 600,
+ //.max_gain = 600,
+ // zdzihu: let's get loud!
+ .max_gain = 1199,
},
[Q6_HW_HEADSET] = {
.min_gain = -1900,

Cheers,

z
[XPERIA X10 Android Development] Mr. Clown:
Back on topic please.
[XPERIA X10 Android Development] -PiLoT-:
http://xdaforums.com/showthread.php?t=1024295
[XPERIA X10 Android Development] goroh_kun:
current usbloader

Hi, I uploaded current test version usbloader.

usbloader0 can boot directly from linux kernel.

cat usbloader0 > /proc/splboot/image
echo > /proc/splboot/boot

usbloader is mapped in physical address 0x0000,

this binary is included in usbloader0.

I tried to copy to 0x00 and automatic boot it.but it doesn't seems work well.

I'll debugging this problem.

but you can memcpy this image to 0x00 by fastboot, you can boot it.

on the screen after booting the usbloader0,

we can see where usbloader binary loaded.

input_data=300057cc
input_data_end=3000f73c

we can re-copy to 0, like this command from your PC command prompt.

fastboot getvar memcpy0,300057cc,9f70
fastboot getvar go0

here, 9f70 = 3000f73c-300057cc

you can boot your spl

fastboot flash mem0 /path/to/spl
fastboot getvar go0

here, mem0 means upload image to 0, if you want to upload different addrees,

you can use mem02b00000, mem01000000, etc.

I added many command to check how the CPU internal memory works.

fastboot getvar memcmp0,300057cc,9f70
- to check memcpy correct.

fastboot getvar memcpy0,300057cc,9f70
- memcpy from 0x300057cc to 0x00, size 9f70

fastboot getvar dump0,20
- show memory dump from 0x0000, 0x20(32) unsigned integers

fastboot getvar go0
- call function from 0x00,
if you want boot usbloader0, just call "fastboot getvar go30000000".

fastboot reboot
- clear screen

fastboot flash mem0 testbin
- upload testbin to 0x00

fastboot getvar mem0,4
- get memory through from 0x00-0x10.
I use this command for dump memory.
I attached a script named dump2mem.sh help you to get mem.

http://hotfile.com/dl/56074792/6f8edc4/usbloader_20100718.zip.html
[XPERIA X10 Android Development] goroh_kun:
to dump ram_console

xperia uses the linux ram_console, it uses memory 0x37fe0000-0x38000000.

so you can see linux console log , by dumping the area from 0x37fe0000.
[XPERIA X10 Android Development] goroh_kun:
current usbloader

Hi, I uploaded current usbloader.

http://hotfile.com/dl/56214684/24f6a11/usbloader_20100719.zip.html

New feature.

memset

log

memdump speed up

interrupt handling

see you next report..
[XPERIA X10 Android Development] goroh_kun:
current works

Hi, just Yesterday night in Japan Local time,

I success to boot my own linux kernel, built fron source code, e-Sheep from SE.

but I have to disable many things like oncrpc, proc_com.. etc.

It's just because of Modem cpu crashed.

It seems when I boot SPL from original kernel. it goes crash.

from usbloader, I tried to use proc_com but I couldn't to use.

proc_com is used to ask something to modem cpu, like rebooting, turn off, play music,..etc).

so now I'm analizing whe modem crashed when usbloader bootup.

one idea is I have to notify restart Application CPU to Modem CPU.

There is interface to notify the reboot event to Modem CPU.

I can send this event, by this command.

mount -t debugfs debugfs /sys/kernel/debug
chmod 666 /sys/kernel/debug/modem_notifier/reboot_start
echo > /sys/kernel/debug/modem_notifier/reboot_start

I tried this, and we can see kernel log the event is reached to kernel driver.

after then, I tried to use proc_comm interface from usbloader.

but it's not work..

it seems more things I have to do before boot the usbloader.

see you next report.
[XPERIA X10 Android Development] irkkso:
great work!

great work! I've been watching each new post in this topic ...
[XPERIA X10 Android Development] biktor_gj:
About the baseband, you have to reboot armv6 cpu, then boot qualcomm's bootloader in there to make it boot again. Proc comm won't reply until the OS inside the baseband is loaded, and it won't boot until you tell it to. Also, we trash smem when booting the spl (we cut the kernel "the hard way" when we boot it), so unless we reboot it and let it write again and don't overlap the memory segment it will crash again.

Also mmu doesn't seem to be turned off before booting, and the cache doesn't seem to be stopped, so that will trash it all too. Resetting all the hardware on usbloader init.S would be a good idea...