yashsingh1/xdaforums huggingface dataset:
[XPERIA X10 Android Development] goroh_kun:
patch for usbloader(to get return value from kernel)

hi

new usbloader can show return value from boot.img.

to get value from kernel, try this patch.

It's only for testing. after geting to boot, I prefer not to use this.

because SP(stack pointer) is not same with normal kernel. it uses

usbloader's stack.

after applying this patch, you can get return value from start_kernel function.

normal start_kernel function, no return function . so you need to change

return value.( in this case, it returns int value)

asmlinkage int __init start_kernel(void)
{
...
return 0x1234 <= the value you want to return to usbloader.

so, you can check the kernel boot correctly before you put return statemnet :)

*** arch/arm/kernel/head.S.org	2010-03-23 16:30:06.000000000 +0900
--- arch/arm/kernel/head.S	2010-07-17 20:21:07.000000000 +0900
***************
*** 77,82 ****
--- 77,83 ----
*/
.section ".text.head", "ax"
ENTRY(stext)
+	stmfd sp!, {r1-r12,lr}
msr	cpsr_c, #PSR_F_BIT | PSR_I_BIT | SVC_MODE @ ensure svc mode
@ and irqs disabled
mrc	p15, 0, r9, c0, c0	@ get processor id
***************
*** 96,102 ****
* above. On return, the CPU will be ready for the MMU to be
* turned on, and r0 will hold the CPU control register value.
*/
!	ldr	r13, __switch_data	@ address to jump to after
@ mmu has been enabled
adr	lr, __enable_mmu	@ return (PIC) address
add	pc, r10, #PROCINFO_INITFUNC
--- 97,103 ----
* above. On return, the CPU will be ready for the MMU to be
* turned on, and r0 will hold the CPU control register value.
*/
!	@ldr	r13, __switch_data	@ address to jump to after
@ mmu has been enabled
adr	lr, __enable_mmu	@ return (PIC) address
add	pc, r10, #PROCINFO_INITFUNC
***************
*** 202,207 ****
--- 203,232 ----
mrc	p15, 0, r3, c0, c0, 0	@ read id reg
mov	r3, r3
mov	r3, r3
+	adr r3, __switch_data + 4
+
+	ldmia r3!, {r4, r5, r6, r7}
+	cmp r4, r5 @ Copy data segment if needed
+ 1:	cmpne r5, r6
+	ldrne fp, [r4], #4
+	strne fp, [r5], #4
+	bne 1b
+
+	mov fp, #0 @ Clear BSS (and zero fp)
+ 1:	cmp r6, r7
+	strcc fp, [r6],#4
+	bcc 1b
+
+	@ldmia r3, {r4, r5, r6, r7, sp}
+	ldmia r3, {r4, r5, r6, r7}
+	str r9, [r4] @ Save processor ID
+	str r1, [r5] @ Save machine type
+	str r2, [r6] @ Save atags pointer
+	bic r4, r0, #CR_A @ Clear 'A' bit
+	stmia r7, {r0, r4} @ Save control register values
+
+	ldmfd sp!, {r1-r12,lr}
+	b start_kernel
mov	pc, r13
ENDPROC(__turn_mmu_on)
[XPERIA X10 Android Development] tewilove:
for these machines which are not completely unlocked, i intended to load a patched spl which allows to execute more oem commands in order to find a way to turn security off for htc tattoo/legend or so. if i can simply load a patched spl to the original physical address, modification of spl will be very light, otherwise i have to relocate every hard coded address. possible?
[XPERIA X10 Android Development] goroh_kun:
hi, can you upload spl image? I'll try to check it we can boot directly.

the address 0x8d000000 is normally used for virtual ram area for linux.

I think spl uses MMU setup and use it. if so, you can use my fastboot to

remap MMU and load your spl and run.

and you have to fill with NOP if there is code for initializing system resources

used by MCPU(modem cpu), or MCPU hang up and ACPU stops too.
[XPERIA X10 Android Development] tewilove:
here it is.

よろしくね。

And considering with a fake kernel when SPL jumps to it then return to SPL, someone managed to do this trick on HTC hero, since I know little about hardware, I'm wondering if this can be done on HTC tattoo/legend/desire or so.
[XPERIA X10 Android Development] goroh_kun:
hi, I checked the legend hboot.

the function from address 0x410, there is code to use MMU.

and then PC move to address 0x9d000800.

and there are MMU table data from 0x98 - 0x40f,

so you don't need to afraid about physical address.

you should just load from physical address 0x0 this image.

but the image seems perform hardware initilaization.

you should fill with NOP around this.

for example, you should check 0x50-0x8c, 4b0-4e0.

my usbloader can show result value, so you can insert code like this,

and you can see where the image hang up.

mov r0, #value
blx lr

try it. good luck.
[XPERIA X10 Android Development] adam235:
the problem is that we cant load code at the address 0x0 thats the error i get.

[ 173.999755] kernel_restart_prepare

[ 174.000457] Starting new spl

[ 174.000854] Unable to handle kernel NULL pointer dereference at virtual address 00000000

[ 174.001525] pgd = d89cc000

[ 174.001892] [00000000] *pgd=38a36031, *pte=00000000, *ppte=00000000

[ 174.003387] Internal error: Oops: 817 [#1] PREEMPT

[ 174.004058] Modules linked in: splboot

[ 174.005126] CPU: 0 Not tainted (2.6.29 #2)

[ 174.005523] PC is at v7_coherent_kern_range+0x18/0x44

[ 174.006256] LR is at proc_splboot_store+0x34/0x80 [splboot]

the error must be inside the flush_icache_range call that comes from proc_splboot_store.

any idea how to solve that ?
[XPERIA X10 Android Development] goroh_kun:
you should use the usbloader first, because splboot not support

boot image from 0x0000. after MMU turn off. you can copy your spl memory at 0x0000, and execute easily.
[XPERIA X10 Android Development] adam235:
just to get right that i understand you.

i use your splboot.ko to boot your usbloader. (do i need to change any values at the splboot.ko like SPLADDR as it shows to 0x0 ?)

and then i boot the patched hboot from the usbloader.

thanks
[XPERIA X10 Android Development] goroh_kun:
I don't know how many RAM the legend has.

if there is no memory at 0x30000000, you should change SPLADDR.

and you should modify linker script for usbloader, and re-build it, too.

qsd8250_ffa/boot/boot.ld
[XPERIA X10 Android Development] goroh_kun:
Hey, I checked the legend source from HTC developer center.

the legend RAM is mapped from 0x10000000 - 0x28000000.

so, you have to change SPLADDR.
[XPERIA X10 Android Development] adam235:
im working on a port for the htc desire

/proc/iomem says 20000000-27ffffff : System RAM

going to test it in some minutes.

thanks again for your help

found a small bug in splload.c:

you have to change line 89 to this:

flush_icache_range((unsigned long) s_spladdr,

(unsigned long) s_spladdr + SPLSIZE);

now i need to find out how your usbloader works ;)

fastboot devices doesnt find a device.

ive patched the

qsd8250_ffa/boot/boot.ld like this:

and this is the memory layout:

is there anything else i have to change ?

thanks
[XPERIA X10 Android Development] goroh_kun:
ok, the desire's CPU is not qsd8250, right?

if so, you have to use use board source for msm7227 cpu.

but if you want to do is just load your spl, you don't need to do this.

you should insert a load spl code into begin of _main function.

like this

int _main(unsigned zero, unsigned type, unsigned tags)
{
int (*entry)(unsigned,unsigned,unsigned) = (void*) 0;
int *spl;= (int*)SPLADDR;
int *mem;
volatile loader_param* param = get_loader_param();
mmu_off();
spl = (void*)param->bootimgaddr;
for(mem=0; mem < param->bootimgsize;){
*mem++ = *spl++;
}
ret = entry(0, 0, 0);
...
}

good luck!
[XPERIA X10 Android Development] goroh_kun:
Hi, we have to add MMU table for usbloader for get return value.

/*
* for usbloader
*/
@ldr	r7, [r10, #PROCINFO_IO_MMUFLAGS] @ mm_mmuflags
mov	r6, #0x30000000 >> 20
orr	r3, r7, r6, lsl #20	@ flags + usbloader base
str	r3, [r4, r6, lsl #2]	@ identity mapping

http://hotfile.com/dl/55722401/ba57648/head.S.html

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

I modifying the usbloader for debugging linux kernel boot.

fastboot extends.

memorydump

memorystore

call function

othre extends.

no more needs return value to usbloader, just use software break to back to usbloader

ram_console area implements(you can see linux console from usbloader

warmboot

usbloader start address moved to physical address 0

see you next report. :)
[XPERIA X10 Android Development] adam235:
hi

the HTC Desire also use the qsd8250 cpu. Thats why i dont understand why your usbloader isnt working :/
[XPERIA X10 Android Development] Reb0rn:
how come other phones made their way here 0_o?
[XPERIA X10 Android Development] killerskincanoe:
Bc devs work together. Two minds are better than one. Esp with similar hardware. Let em be plz.. they will work their magic.

xda app on my x10a. finally!
[XPERIA X10 Android Development] biktor_gj:
First of all

UNTESTED. It didn't break anything on my phones, but could do harm. If you're not fixing things on the SPL don't try it. You might break something unrecoverable on your phone.

Now, for devs: declared mtd, faked recovery & boot partitions, and changed keyboard code to allow keyboard presses during boot.

Now you can use menu key to attempt to boot to recovery, home key to attempt to boot to android, and back key to force it to go to fastboot. If it finds invalid data it fallbacks to fastboot, so at this point it will go to fastboot no matter what you do, as it doesn't understand anything on the phone and the partition addresses are all wrong :)

I left out all the old code commented just in case there's something wrong, though I didn't see anything fall apart.

I tried porting the spl to lk (little kernel android bootloader -code aurora-), but it looked like it did some nasty things, so I'll keep working on the legacy loader for now on. There's still a lot of work to do...
[XPERIA X10 Android Development] tewilove:
hi, i tried to make splboot work on armv6 machines.

but when i try to pass a image to /proc/splboot/boot_img, it hangs up. while passing something to /proc/splboot/image is ok.

i also tried many other address for it, but it ends up the same.

here is iomem for tattoo.

02d00000-02d9afff : msm_panel.0
02d9b000-02dbafff : ram_console
02e00000-07ffffff : System RAM
02e26000-03198fff : Kernel text
0319a000-03277def : Kernel data
20000000-26dfffff : System RAM
a0200000-a0200fff : msm_serial_hs.0
a0400000-a0400fff : msm_sdcc.1
a0500000-a0500fff : msm_sdcc.2
a0800000-a0800fff : msm_hsusb
a9900000-a9900fff : msm_i2c.0
a9900000-a9900fff : msm_i2c
a9c00000-a9c00fff : msm_serial.2
a9c00000-a9c00fff : msm_serial
aa200000-aa2effff : mdp
aa600000-aa600fff : msm_mddi.0

and here is the source.

plz help.
[XPERIA X10 Android Development] mayank.1love:
@Bin4ry

good luck with the exam :)
[XPERIA X10 Android Development] Bin4ry:
Thanks :)

Regards

Bin4ry
[XPERIA X10 Android Development] DooMLoRD:
my tests with: SE Stock FW 2.1.A.0.435

I am using files from "kexec_kit_bin4ry3.zip" and boot.img from here

and basebands packages from the baseband collection by rendeiro2005

x10a-2.1.54	booted into OS / no radio / reboot in few seconds / question mark on battery / unknown baseband / unknown kernel

x10i-2.1.54	booted into OS / no radio / reboot in few seconds / question mark on battery / unknown baseband / unknown kernel

x10a-2.1.55	booted into OS / no radio / reboot in few seconds / question mark on battery / unknown baseband / unknown kernel

x10i-2.1.58	booted into OS / no radio / reboot in few seconds / question mark on battery / unknown baseband / unknown kernel

x10i-2.0.49	booted into OS / no radio / NO reboot (rom is stable) / question mark on battery / unknown baseband / unknown kernel

2.0.46	booted into OS / no radio / NO reboot (rom is stable) / question mark on battery / unknown baseband / unknown kernel

2.0.52(J)	booted into OS / no radio / NO reboot (rom is stable) / question mark on battery / unknown baseband / unknown kernel

funny thing is on the 2.0.xx basebands the stock OS doesnt get/detect radio, in "About Phone" -> "Baseband Version" shows up as "Unknown"; more important even after "installing" the custom boot.img the stock OS remains stable without the radio...

so i think, since i was using the 2.1.A.0.435 FW, which i presume is ment for 2.1.5x basebands, it doesnt get radio on 2.0.xx and since it remains stable (no reboot after few seconds of bootup) after applying custom boot.img the problem has to be related to the OS trying to access radio for 2.1.5x, may be thats why it keeps rebooting on 2.1.5x with the custom boot.img
[XPERIA X10 Android Development] DooMLoRD:
how can i help?

i am at a complete loss as to how to use these files in this new zip...

btw best of luck for ur exam ;)
[XPERIA X10 Android Development] Bin4ry:
A last thing to test for you.

This is kernel custom kernel based on SE 435 kernelsources.

Extract boot.img from zip and push it to the phone, start as usual.

Please make baseband tests again, thanks :)

Regards

Bin4ry
[XPERIA X10 Android Development] Aeny:
x10i | J's CM7 RC2 V10a | BaseBand 2.0.46 | boot.img: 22.03.11-00_25

-Same behavior as BB 2.0.52

-(Stock kernel + this BaseBand = WLOD reboot loop.)

x10i | J's CM7 RC2 V10a | BaseBand 2.0.49 | boot.img: 22.03.11-00_25

-Same behavior as BaseBand 2.0.52

x10i | J's CM7 RC2 V10a | BaseBand 2.0.52 | boot.img: 22.03.11-00_25

-Screen not waking up by pressing any buttons, to wake up press any button, then press the screen. If "Screen-on" and/or "Screen-off" animations are enabled in CM-Settings then screen cannot be woken up at all.

-Battery shows a percentage, but does not indicate charging, however the battery level is going up.

-Time seems to update once every few (10~11) minutes instead of every minute & always starts counting from 1/1/1970 -1h:00m at boot.

-WiFi shows "error" under settings but does magically work, just can't be turned off.

-Bluetooth doesn't want to turn on.

-Baseband: "Unknown".

-Kernel Version: 2.6.29Bin4ry "SEMCUser@SEMCHost #1".

-no reboots (running 15minutes).

-screen doesn't auto-turn off but dims instead.

-Battery status shows as "unknown" under settings -> about phone -> status.

-No USB.

-LED doesn't light up while charging.

x10i | J's CM7 RC2 V10a | BaseBand 2.1.54 | boot.img: 22.03.11-00_25

-Freezes after 2~5seconds(can't see if WLOD because LED doesn't work).

-(Stock kernel + this BaseBand = WLOD reboot loop.)

x10a | J's CM7 RC2 V10a | BB 2.1.54 | boot.img: 22.03.11-00_25

-Freezes after 2~5seconds->reboot(can't see if WLOD because LED doesn't work).

-(Stock kernel + this BaseBand = WLOD reboot loop.)
[XPERIA X10 Android Development] RaDi:
boot.img: 22.03.11-00_25 / FW: SE 2.1 / BB 2.1.54

its work great !

boot normaly then radio work and WiFi also work !

boot.img: 22.03.11-00_25 / FW: SE 2.1 / BB 2.0.52

freeze on SE logo fo about 5~9 sec | no radio (insert SIM) | Wifi work

@ Bin4ry

good look bro ;)
[XPERIA X10 Android Development] DooMLoRD:
boot.img: 22.03.11-00_25 / FW: stock SE X10a-2.1.A.0.435 / BB 2.1.54

Baseband:

"Unknown"

Kernel Version:

"2.6.29Bin4ry SEMCUser@SEMCHost #1" ;)

phone reboots within few seconds of bootup
[XPERIA X10 Android Development] RaDi:
@ DooMLoRD

good now we have conferm that bin4ry kernel work with .54

i try also 52 but there is no radio !

i reflash the phone with 54 BB but also get no signal !

any idea about this ?

@bin4ry

could we convert the .img to .sin ?
[XPERIA X10 Android Development] Bin4ry:
WOW, which firmware exactly?

Regards
[XPERIA X10 Android Development] Bin4ry:
No, sin is the signature header. For that we need the signing key and we don't have it!

Regards
[XPERIA X10 Android Development] javagreen:
I think it's SE's 2.1, 2.1.A.435 with 2.1.54 Baseband.
[XPERIA X10 Android Development] RaDi:
@ Bin4ry

it`s 2.1.A.435 just like javagreen said and DooMLoRD vonfirm that :)
[XPERIA X10 Android Development] Bin4ry:
Okay then please a few more tests with SE stock image:

2.1.A.435

@All:

Please test my boot.img with kit3 method via chargemon on this basebands:

X10i:

2.1.54

2.1.58

X10a:

2.1.54

2.1.55

Can be found in rendeiro2005's Baseband Collection thread!

Thanks for testing.

Please post detailed results like DooMLoRD done here: Klick

Will look in your results, but i will not work on this today, like i said -> tomorrow exam!

But Jerpelea is also watching the thread and is working in background :P

Regards

Bin4ry
[XPERIA X10 Android Development] shvyue:
I'm new to this but what i did is, copy all files from bootkit to /data/local/tmp

adb shell

$ su

# chmod 06755 run.sh

# ./run.shls

Phone shows fast-usb reboot, then a cute dog at top-left, then xda-developer with brown background.

SE stock image:

2.1.A.435

x10i-2.1.58 white led after xda-developer image then reboot with SE logo, etc

x10i-2.1.54 white led after xda-developer image then reboot with SE logo, etc
[XPERIA X10 Android Development] RaDi:
good lack Bin4ry !

test report :

X10 2.1 .435

BB54

run gr8 ,with Xda then reboot in se rom with radia and i test wifi and its work also!

edit :

BB58 also just like above !

>after we have sacsesfully loud Bin4ry kernel , could we have muiltitouch(not just dual) ? thanx
[XPERIA X10 Android Development] -- X10B --:
here's a video of BB .58 running on kexec_kit_bin4ry3 with the new boot image.

sorry for the super low resu on it i had to use my old phone to record lol.....:D
[XPERIA X10 Android Development] thermoska:
It is locked (by marlyn , if I understood guys correctly), you can not see it.

Push files into the data/local/tmp.

you can see how to in HowTo document which is included in zip file

correct me if i missunderstood something :) ..
[XPERIA X10 Android Development] Asdoos:
Yeah but i have an x8 and i don't think that the boot.img are the same. Ill give a try when I'm at home. Are there any brick problems?
[XPERIA X10 Android Development] thermoska:
x8 needs its own boot.img .. it was written many times before ..
[XPERIA X10 Android Development] Asdoos:
Thats the reason why i want to know how to get this file

@bin4ry

Is this a modded boot.img In the zip. (Und viel Erfolg in deinem Test :) )
[XPERIA X10 Android Development] Bin4ry:
Let's concentrate on X10 first, X8 needs other modifications like X10. Bootimage was not downloaded from phone, it was created fully on our own.

First X10 -> then others. Procedure may be similar, but not same!

(Danke, morgen Mathe Prüfung in der Uni -.-)

Regards

Bin4ry
[XPERIA X10 Android Development] Androxyde:
Flashtool update 0.2.9.1

Edit : Removed 0.2.9.1 update as I updated the full package on the FLASHTOOL thread.
[XPERIA X10 Android Development] lzyllp:
How to back to SE original Kernel？
[XPERIA X10 Android Development] Aeny:
x10i | Build: 2.1.A.435 | BaseBand: 2.1.54 | boot.img: 22.03.11-00_25

-Booted into OS: YES

-Radio: NO

-Reboot in few seconds: YES

-Questionmark on battery: YES

-BaseBand: Unknown

-kernel: 2.6.29Bin4ry SEMCUser@SEMCHost #1

x10i | Build: 2.1.A.435 | BaseBand: 2.1.58 | boot.img: 22.03.11-00_25

-Booted into OS: YES

-Radio: NO

-Reboot in few seconds: YES

-Questionmark on battery: YES

-BaseBand: Unknown

-kernel: 2.6.29Bin4ry SEMCUser@SEMCHost #1

x10i | Build: 2.1.A.435 | BaseBand: 2.1.54(a) | boot.img: 22.03.11-00_25

-Booted into OS: YES

-Radio: NO

-Reboot in few seconds: YES

-Questionmark on battery: YES

-BaseBand: Unknown

-kernel: 2.6.29Bin4ry SEMCUser@SEMCHost #1

x10i | Build: 2.1.A.435 | BaseBand: 2.1.55(a) | boot.img: 22.03.11-00_25

-Booted into OS: YES

-Radio: NO

-Reboot in few seconds: YES

-Questionmark on battery: YES

-BaseBand: Unknown

-kernel: 2.6.29Bin4ry SEMCUser@SEMCHost #1

:p

Back to CM7 for me, SE's rom felt like playing a game @ 2FPS.

~Aeny
[XPERIA X10 Android Development] Androxyde:
When you boot into a modded kernel, the next reboot will take you to the original kernel.
[XPERIA X10 Android Development] laill:
Please do read,instruction is included in the kexec file

This is dev. thread,not a thread for TL and DR

@Bin4ry,

Reports on 0.24 firmware boot.img: 22.03.11-00_25

Fail to boot after executing the script ,error occurs

After showing the xda logo and the black screen with - on the top left hand corner,it reboots with normal kernel.

JPG is attached

View attachment 548968

May be it is my fault on running them,still trying

cheers,

L

Edit,

After using Androxyde&Bin4ry Flash tool to install the kernel(this time the bootimg is the one in kxec pack3),the error message only shows

# cd /data/local/tmp

cd /data/local/tmp

# chmod 06755 run.sh

chmod 06755 run.sh

# ./run.sh

./run.sh

failed.

,without saying permissions.....

Can anyone confirm if the flashtool can reboot into custom kernel cause it fails to work for me
[XPERIA X10 Android Development] brandoncw:
In order to help keep this thread clean I will start a how to thread. It would be helpful to post your results here NOT in the new thread. The thread will be here http://xdaforums.com/showthread.php?p=12290523#post12290523
[XPERIA X10 Android Development] laill:
But I though SU permission is already gained

you can see # in the picture

regards,

L
[XPERIA X10 Android Development] DooMLoRD:
for instructions on how to install these files

for instructions on how to install these files go here

any queries regarding those instructions should be posted only in that thread...

post in this thread only if u have something useful to report...

for general discussion go here
[XPERIA X10 Android Development] DooMLoRD:
tested on Stock SE FW: x10i_2.1.1.A.0.16_Era_Poland

tested using Flashtool beta v0.2.9.1 and boot.img included in flashtool (it is same as bootimg-22.03.2011-00_25h.zip)

x10a-2.1.54	booted into OS / no radio / reboot in few seconds / question mark on battery / unknown baseband / "2.6.29Bin4ry SEMCUser@SEMCHost #1" kernel

x10a-2.1.55	booted into OS / no radio / reboot in few seconds / question mark on battery / unknown baseband / "2.6.29Bin4ry SEMCUser@SEMCHost #1" kernel

x10i-2.1.54	booted into OS / no radio / reboot in few seconds / question mark on battery / unknown baseband / "2.6.29Bin4ry SEMCUser@SEMCHost #1" kernel

x10i-2.1.58	booted into OS / no radio / reboot in few seconds / question mark on battery / unknown baseband / "2.6.29Bin4ry SEMCUser@SEMCHost #1" kernel
[XPERIA X10 Android Development] 28spawn:
pressing down volume button in after lines and before xdadevelopers give me access to the recovery =P
[XPERIA X10 Android Development] PoTi_96:
stock one or xrec?
[XPERIA X10 Android Development] mpasanthosh:
Custom kerenel

x10i-2.1.54	firmware: 2.1.A.0435 booted into OS / no radio / reboot in few seconds / question mark on battery / unknown baseband / "2.6.29Bin4ry SEMCUser@SEMCHost #1" kernel
[XPERIA X10 Android Development] -- X10B --:
stop Posting asking whats the progress... wait and it will come...

kernel test progress...

im using bb52 J's rom..

radio -- ok but intermitent

earpiece speaker - ok

loudspeaker - not working

multitouch - not working

headset - ok

mobile data 3g - not working

to slow to wake up when screen fall asleep needs 2 push on home button.

need more libs resources

baseband error but has radio... nice is'nt

t.y j,b,z,doomlord and everybody behind this small progress...
[XPERIA X10 Android Development] PoTi_96:
Same here with x10i .54 BB, same bootimg...

But second time booting into custom kernel the battery worked for me and third time i got radio for 2-3 seconds after unlocking screen (directly after Boot)
[XPERIA X10 Android Development] pato66:
bb54 wolfbreak 2.2.1	booted with custom kernel / no radio / question mark dont reboot, stable.

cheers
[XPERIA X10 Android Development] tremeree:
First I want to congratulate all the great devs that every day give us hoppe to finally get the product that SE denies us. I know that right now there is a method to bypass the bootloader. However I want to post this link. I remember that somebody said that maybe, just maybe the keys used in PS3 could be used to open our bootloader. I'm not sure if this keys are already known to the commmunity neither if it is really relevant for us, but better to be safe than to be sorry, right?

I apologize if this is of no use. In such a case please delete.

Keep the great work!!!!
[XPERIA X10 Android Development] zdzihu:
@Bin4ry, Jerpelea

Gentlemen, don't waste your time patching kernel - it just won't work.

Please take a look into HARET sources (arch-msm.cpp). HTC Leo (HD2) boots Android just fine without reseting MCPU - and we should focus on that approach.

I ported the following shutdown procedures to the Goroh's usbloader:

shutdownTimers();

shutdownInterrupts();

shutdownSirc();

shutdownDMA();

and it still fails... but this is definitely _the way_ to go.

Cheers,

z