[KERNEL][PreRooted] Stock X10 FW 3.0.1.G.0.75 [FOR UNLOCKED BOOTLOADERS][Dt:11/Sept]

Search This thread

DooMLoRD

Inactive Recognized Developer
Jul 27, 2010
13,187
39,710
Pune
---[ UPDATE ]----

if anyone is using this version i will highly recommend that they update to:
Boot Manager for X10

it has many more features than the ones posted here...

---[ UPDATE ]----


so here is the prerooted stock kernel for unlocked bootloaders...

use [Dev] Bypass "bootloader" [PROPER METHOD] to unlock bootloader...

thanks to the_laser to openly release this unlock...


DO NOT ASK QUESTIONS AS TO HOW TO UNLOCK BOOTLOADER, FOR THAT INFO REFER TO the_laser's thread...


The reason i have created this is till we can do some advanced work using the unlock bootloader users should atleast be able to use the older (bootloader bypass method) kernel loading... with this kernel as base u can mount other kernels using our usual ways :) [that is flashing kernel packages via recovery and using older chargemons for custom kernel loading]




[ features ]

  • this is stock 2.3.3 kernel (2.6.29-00054-g5f01537)
  • additional stuff added: (to ramdisk)
    1. autoroot feature (very simple rooting)
    2. advanced init.d scripts execution support (fixed in v3)
    3. busybox already installed in /sbin
    4. xRecovery-0.3-GBready [thanks to zdzihu] directly integrated in kernel (ramdisk) [no need to worry abt trashed flashes]
    5. xRecovery in ramdisk is given preference over chargemon (so pressing BACK key repeatedly, when u see new logo, w will take u to the recovery in main kernel)
    6. i have also added a fix which will allow the old "reboot into recovery" option in flashtool to now work
    7. to distinguish between which recovery is actually getting called i have changed the background image of xrecovery (check changelog of v2 for details)
    8. corrected Superuser file replacement (if Superuser.apk is already present when the kernel is flashed the first time it will not be replaced) [thanks to Androxyde for pointing that out]


[ Requirements ]

  1. bootloader unlocked device
  2. flashtool
  3. latest SE FW 3.0.1.G.0.75 or ROM based on that FW


[ Donations ]

if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc ;)

PAYPAL DONATION LINK


[ FOR UR INFO ]

if u are going to use any part of the ramdisk i created, atleast credit me and link back to my thread


[ download link ]

  1. x10_2.3.3_stock-with-xrecovery-v3.ftf (changelog)
    [ MD5HASH : 1d0229a86039720f21f0b158599d8168 ]

  2. stock wifi modules [ mirror ] (can be flashed via recovery)

< OLD FILES >


[ how to install ]

  1. flash using flashtool
  2. if required flash stock wifi modules



IF U HAVE UNLOCKED THE BOOTLOADER PROPERLY,
FLASHING VIA FLASHTOOL WILL SUCCEED
AND U WILL SEE NEW BOOT LOGO AT STARTUP


NO MORE SE TEXT LOGO

SOME IMP INFO REGARDING NEW BOOTUP STEPS



icon8.gif



ENJOY!
 
Last edited:

.::Mario27::.

Member
Mar 9, 2011
41
6
i have rom of wolfBreak...4.0.4
i can use this??....

and... what will be the difference??...

sorry for my noob cuestion and for my bad english..
 

Neo.

Senior Member
Dec 19, 2010
780
122
Gods Own Place
@DL: One question,

Do we have any difference in the performance in Bootloader bypass and unlocked bootloader? Since we didn't implement anything that's related to unlocked BL yet (example: 16mil colors). isn't this the same like the one we had before?

(Except for the recovery stable thing we get now).

Is there any noticeable speed since we got unlocked BL and different kernel?
 

DooMLoRD

Inactive Recognized Developer
Jul 27, 2010
13,187
39,710
Pune
Does it have the FPS unlocked and in call volume increase?

NO

this is stock SE kernel... i have just added a lot of things to ramdisk to make life simpler...


Can anybody post flashable .zip with wifi modules?

done... check 1st post

@DL: One question,

Do we have any difference in the performance in Bootloader bypass and unlocked bootloader? Since we didn't implement anything that's related to unlocked BL yet (example: 16mil colors). isn't this the same like the one we had before?

(Except for the recovery stable thing we get now).

Is there any noticeable speed since we got unlocked BL and different kernel?

may be the kernels flashed directly might be more stable.. and booting time is reduced... other than that a lot of work will have to be done to make anything else happen...
 
  • Like
Reactions: xXHITMANXx508

DooMLoRD

Inactive Recognized Developer
Jul 27, 2010
13,187
39,710
Pune
I know I know. I am using your old kernel (v04) because this just don't work me. I flashed the .ftf file, then flashed wifi modules but it loaded still the old one (v04) (without working wifi)

this kernel is supposed to be used as BASE kernel for booting other custom kernels (if u want)
 

Berik84

Senior Member
this kernel is supposed to be used as BASE kernel for booting other custom kernels (if u want)

I know, this is stock kernel with some new features and I want to use it.

1. I used v04 for locked bootloader
2. Xperia logo, goroh customized spl screen then xperia logo again
3. I flashed .ftf in this thread with flashtool and then wifi module
4. Then Xperia logo and it is still booting to v04 (goroh customized spl)
 

DooMLoRD

Inactive Recognized Developer
Jul 27, 2010
13,187
39,710
Pune
I know, this is stock kernel with some new features and I want to use it.

1. I used v04 for locked bootloader
2. Xperia logo, goroh customized spl screen then xperia logo again
3. I flashed .ftf in this thread with flashtool and then wifi module
4. Then Xperia logo and it is still booting to v04 (goroh customized spl)

yes thats expected...

that how the older bootloader bypass worked...

if u want to stop booting custom kernel... do the following:
  1. remove /system/bin/chargemon
  2. rename /system/bin/charger to /system/bin/chargemon
  3. then reboot
  4. custom kernel will not boot
 
  • Like
Reactions: pietropizzi

9Lukas5

Senior Member
Dec 14, 2010
3,914
2,076
near Stuttgart
I know, this is stock kernel with some new features and I want to use it.

1. I used v04 for locked bootloader
2. Xperia logo, goroh customized spl screen then xperia logo again
3. I flashed .ftf in this thread with flashtool and then wifi module
4. Then Xperia logo and it is still booting to v04 (goroh customized spl)

Yes, cause the bootloader bypass is working further on. delete chargemon and the bypass isn't working anymore. But don't know if it has any other (maybe bad) effect if you simply delete the chargemon, but I have done it on mine, too. I'm using miui rom.
 
  • Like
Reactions: pietropizzi

Top Liked Posts

  • There are no posts matching your filters.
  • 32
    ---[ UPDATE ]----

    if anyone is using this version i will highly recommend that they update to:
    Boot Manager for X10

    it has many more features than the ones posted here...

    ---[ UPDATE ]----


    so here is the prerooted stock kernel for unlocked bootloaders...

    use [Dev] Bypass "bootloader" [PROPER METHOD] to unlock bootloader...

    thanks to the_laser to openly release this unlock...


    DO NOT ASK QUESTIONS AS TO HOW TO UNLOCK BOOTLOADER, FOR THAT INFO REFER TO the_laser's thread...


    The reason i have created this is till we can do some advanced work using the unlock bootloader users should atleast be able to use the older (bootloader bypass method) kernel loading... with this kernel as base u can mount other kernels using our usual ways :) [that is flashing kernel packages via recovery and using older chargemons for custom kernel loading]




    [ features ]

    • this is stock 2.3.3 kernel (2.6.29-00054-g5f01537)
    • additional stuff added: (to ramdisk)
      1. autoroot feature (very simple rooting)
      2. advanced init.d scripts execution support (fixed in v3)
      3. busybox already installed in /sbin
      4. xRecovery-0.3-GBready [thanks to zdzihu] directly integrated in kernel (ramdisk) [no need to worry abt trashed flashes]
      5. xRecovery in ramdisk is given preference over chargemon (so pressing BACK key repeatedly, when u see new logo, w will take u to the recovery in main kernel)
      6. i have also added a fix which will allow the old "reboot into recovery" option in flashtool to now work
      7. to distinguish between which recovery is actually getting called i have changed the background image of xrecovery (check changelog of v2 for details)
      8. corrected Superuser file replacement (if Superuser.apk is already present when the kernel is flashed the first time it will not be replaced) [thanks to Androxyde for pointing that out]


    [ Requirements ]

    1. bootloader unlocked device
    2. flashtool
    3. latest SE FW 3.0.1.G.0.75 or ROM based on that FW


    [ Donations ]

    if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc ;)

    PAYPAL DONATION LINK


    [ FOR UR INFO ]

    if u are going to use any part of the ramdisk i created, atleast credit me and link back to my thread


    [ download link ]

    1. x10_2.3.3_stock-with-xrecovery-v3.ftf (changelog)
      [ MD5HASH : 1d0229a86039720f21f0b158599d8168 ]

    2. stock wifi modules [ mirror ] (can be flashed via recovery)

    < OLD FILES >


    [ how to install ]

    1. flash using flashtool
    2. if required flash stock wifi modules



    IF U HAVE UNLOCKED THE BOOTLOADER PROPERLY,
    FLASHING VIA FLASHTOOL WILL SUCCEED
    AND U WILL SEE NEW BOOT LOGO AT STARTUP


    NO MORE SE TEXT LOGO

    SOME IMP INFO REGARDING NEW BOOTUP STEPS



    icon8.gif



    ENJOY!
    4
    x10_2.3.3_stock-with-xrecovery-v2

    this is a test FTF...

    [ features ]

    • main kernel is stock SE 2.3.3 kernel
    • xrecovery in ramdisk is given preference over chargemon (so pressing BACK key repeatedly, when u see new logo, w will take u to the recovery in main kernel)
    • i have also added a fix which will allow the old "reboot into recovery" option in flashtool to now work
    • to distinguish between which recovery is actually getting called i have changed the background image of xrecovery

      (background image of recovery in kernel)........................(background image of recovery in /system)
      icon_error_MOD.png
      icon_error_ORI.png




    [ download link ]

    x10_2.3.3_stock-with-xrecovery-v2.ftf [ mirror ]
    [ MD5HASH : a1fd0e3f8cb909cce550112487824d81 ]

    wifi module is same as stock wifi... incase u still need it grab it from 1st post...
    3
    x10_2.3.3_stock-with-xrecovery-v3

    this is another test FTF...

    [ changelog ]

    • changes from v2+
    • fixed init.d execution, some changes i had made to the ramdisk (in v1) had broken that function, now its fixed ;)
    • corrected Superuser file replacement (if Superuser.apk is already present when the kernel is flashed the first time it will not be replaced) [thanks to Androxyde for pointing that out]

    [ download link ]

    x10_2.3.3_stock-with-xrecovery-v3.ftf [ MD5HASH : 1d0229a86039720f21f0b158599d8168 ]

    wifi module is same as stock wifi... incase u still need it grab it from 1st post...


    please check if:
    1. device boots
    2. inbuilt recovery works
    3. init.d scripts are getting executed

    right now i am working on a few interesting things... will post something when i get it working...
    2
    Ok, all links (include mirrors) are dead.
    I don't know if someone needs it but i uploaded it to Mediafire :

    x10_gb_stock_wifi_modules.zip
    x10_2.3.3_stock-with-xrecovery-v3.ftf
    2
    Hi @DoomLord ( or whoever ), after flashing .ftf, still shows 2.6.29-modFXP-DooMKernel-v04bDooMLord@chaos)), it is, the last Kernel i had before flashing the one in OP... Did i something wrong ? I´ve already Unlocked Bootloader... :confused:

    thats is because u are also using the older bootloader bypass (like me) to load older custom kernels.... this is normal...

    the boot process with unlocked bootloader and THIS kernel will be as follows:
    • if u are using older bootloader bypass to load older kernel (which is fine):
      1. power on device
      2. new android + xperia
      3. Goroh's SPL booting text
      4. custom kernel's bootlogo/bootscreen
      5. bootanimation
      6. OS is finally booted
        and Kernel Version in About Phone will show the TAG of the custom kernel
    • if u are NOT using older bootloader bypass
      1. power on device
      2. new android + xperia
      3. bootanimation
      4. OS is finally booted
        and Kernel Version in About Phone will show 2.6.29-00054-g5f01537