Credits:
- DooMLord -> his recovery sources on github, and his guidance on assisting me with setting up the build environment and for his kernel.sin unpacker.
- Sony Ericsson -> the kernel with this.
I wanted the stock kernel because of battery drain issues present in many custom kernels, mine included, because although I used the semc sources to compile my kernel, it still had worse battery drain than stock.
I have unpacked the zImage from the kernel.sin in the 4.0.2.A.0.42 and then made that and a modified ramdisk into a boot.img, which you can flash.
This is for people who want to stay with the stock kernel, but want clockworkmod recovery.
Kernel string version:
Code:
2.6.32.9-perf
[email protected] #1
Download: http://dl.dropbox.com/u/13729847/semc/kernels/stockCWM/boot.img
MD5: 1ad7e6db6258b73555f0e6ae73fe4fd6
To flash, use the command:
Code:
fastboot flash boot boot.img
If you are on linux:
Code:
./fastboot -i 0x0fce flash boot boot.img
Don't forget to say thanks if you use this!
Yo installed it the custom recovery works fine and now testing UPDATE-looks like its not starting up for me ill try a reflash UPDATE-its not working properly the system wont start man
Super interested in this since I went back to Stock rom moments ago so I can play FIFA 12. Will this work with the new HK 4.0.2.A.0.58 rom released as I have just put that on.
matknny said:
Super interested in this since I went back to Stock rom moments ago so I can play FIFA 12. Will this work with the new HK 4.0.2.A.0.58 rom released as I have just put that on.
Click to expand...
Click to collapse
wait now dat i think about it i have the same firmware as urs it doesnt work on it weird
matknny said:
Super interested in this since I went back to Stock rom moments ago so I can play FIFA 12. Will this work with the new HK 4.0.2.A.0.58 rom released as I have just put that on.
Click to expand...
Click to collapse
Yes, .42 and .58 use the same kernel.
Will this provide root? I only install Doom's for root & recovery, so if this does I'll use this instead. Thanks.
alreadyused said:
Will this provide root? I only install Doom's for root & recovery, so if this does I'll use this instead. Thanks.
Click to expand...
Click to collapse
No root, but you can flash RootXperia.zip in clockworkmod (search it on google: rootxperia.zip).
Done but having booted after installing and rebooted into recovery (which worked) then restarted to phone it wont boot. Black screen after Sony Logo.
Update: Boots after 15 minutes no battery but now android market is keep coming up unsuccessful
Update 2: It just will not boot so I had no choice but to flashtool 4.0.2.a.0.58 back to default. :-(
matknny said:
Done but having booted after installing and rebooted into recovery (which worked) then restarted to phone it wont boot. Black screen after Sony Logo.
Update: Boots after 15 minutes no battery but now android market is keep coming up unsuccessful
Update 2: It just will not boot so I had no choice but to flashtool 4.0.2.a.0.58 back to default. :-(
Click to expand...
Click to collapse
Actually had market problems myself too, it is very wierd :/
Doesn't work at all for me - fastbooted it left it for a bit
came back and got the red blinking light.
What is the trick to get a stock kernel.sin to a working boot.img ? (Spent most of this afternoon failing to get it to work). All I really want is ro.secure=0 (or ro.debuggable=1). fastbooting CWM is ok for me.
unrandomsam said:
Doesn't work at all for me - fastbooted it left it for a bit
came back and got the red blinking light.
What is the trick to get a stock kernel.sin to a working boot.img ? (Spent most of this afternoon failing to get it to work). All I really want is ro.secure=0 (or ro.debuggable=1). fastbooting CWM is ok for me.
Click to expand...
Click to collapse
Small how-to for creating insecure kernel
1) Unpack kernel.sin to get zImage and ramdisk (tools posted in my other thread)
2) unpack ramdisk
3) edit default.prop and set ro.secure=0 & ro.debuggable=1 then save file
4) repack ramdisk (cpio.gz)
5) repack into boot.img, using zimage + new packed ramdisk, using correct mkbootimg arguments
6) flash using fastboot
7) enjoy
PRO TIP:
Use ONLY LINUX FOR ALL OF THIS ELSE DEVICE WONT BOOT
Sent from my R800i using XDA App
DooMLoRD said:
Small how-to for creating insecure kernel
1) Unpack kernel.sin to get zImage and ramdisk (tools posted in my other thread)
2) unpack ramdisk
3) edit default.prop and set ro.secure=0 & ro.debuggable=1 then save file
4) repack ramdisk (cpio.gz)
5) repack into boot.img, using zimage + new packed ramdisk, using correct mkbootimg arguments
6) flash using fastboot
7) enjoy
PRO TIP:
Use ONLY LINUX FOR ALL OF THIS ELSE DEVICE WONT BOOT
Sent from my R800i using XDA App
Click to expand...
Click to collapse
Thats pretty much exactly what I did. (I did the initial split under windows though I will try again.)
I used the mkbootimg arguments from SE's building kernel blogpost.
help please
please help me somebody i have a problem i cant seem to fix , i flashed the doom kernel then flashed 4.3 icream sandwhich rom exactly like it said to do in the instructions re-booted ,It all booted up fine i played about with the rom for a few hours as you do then i went back to my backed up stock rom ,but heres where the problem happens on restoring my stock rom for some reason my camera doesnt work and playing youtube videos doesnt work and also when i try downloading from the market it just sits there for ever saying downloading but nothings happening i would be really greatfull if somebody can help me resolve this problem thanks..
are you asking this in all thread's?
flash stock rom with flashtool
help
@nickholtus where do i get the stock rom i cant find it plz help and also how do i use this flash tool thing help please somebody i need my phone working again because im going away for the week.
download flashtool
install drivers (in flashtool folder)
download stock (see development .42 .58 or .62)
flash with flashtool
DooMLoRD said:
Small how-to for creating insecure kernel
1) Unpack kernel.sin to get zImage and ramdisk (tools posted in my other thread)
2) unpack ramdisk
3) edit default.prop and set ro.secure=0 & ro.debuggable=1 then save file
4) repack ramdisk (cpio.gz)
5) repack into boot.img, using zimage + new packed ramdisk, using correct mkbootimg arguments
6) flash using fastboot
7) enjoy
PRO TIP:
Use ONLY LINUX FOR ALL OF THIS ELSE DEVICE WONT BOOT
Sent from my R800i using XDA App
Click to expand...
Click to collapse
Hey Doom, I'm trying to follow this, and I'm getting stuck
I downloaded the R800x 2.3.3 (3.0.1.E.0.88) TFT from here: http://forum.xda-developers.com/showpost.php?p=19438024&postcount=12
I unzipped it using xarchiver (installed on arch linux/available on sourceforge)
I ran unpack-kernelsin.pl, and I get two errors (that don't exit out of the perl script):
1) ramdisk written... gzip: no such file or directory
2) cpio: premature end of image
When I try to cpio-ing the ram disk, my computer just sits... How long should I wait, I have a netbook (i know, not the best for doing compiling) and the longest i've let it sit is about 10 minutes (i'm about to let it sit overnight to see if it'll work itself out)
If you could give me any pointers, that'd be outstanding
Thank you,
Pax
paxChristos said:
Hey Doom, I'm trying to follow this, and I'm getting stuck
I downloaded the R800x 2.3.3 (3.0.1.E.0.88) TFT from here: http://forum.xda-developers.com/showpost.php?p=19438024&postcount=12
I unzipped it using xarchiver (installed on arch linux/available on sourceforge)
I ran unpack-kernelsin.pl, and I get two errors (that don't exit out of the perl script):
1) ramdisk written... gzip: no such file or directory
2) cpio: premature end of image
When I try to cpio-ing the ram disk, my computer just sits... How long should I wait, I have a netbook (i know, not the best for doing compiling) and the longest i've let it sit is about 10 minutes (i'm about to let it sit overnight to see if it'll work itself out)
If you could give me any pointers, that'd be outstanding
Thank you,
Pax
Click to expand...
Click to collapse
for such things send me p.m.
is there anything like a stock rom and stock kernel software I could install on my mini pro in case I want it to be back in the state how it originally was when I bought it (v2.3.3) or made the SE update to v2.3.4, e.g. when planing to sell my phone at some point?
Im a bit lost in all the links of roms and custom made stuff in the development forum.
if you use a Official ROM (Called FW in common) you can extract a file named Kernel.sin from it and flash it via fastboot so that you have Official ROM and Kernel.
The latest Mini Pro FW is 4.0.2.A.0.58 in this link: http://forum.xda-developers.com/showthread.php?t=1341460
for flashing stock kernel after extracting it from FW put it in fastboot folder then run this command for the fastboot folder:
Code:
fastboot flash boot kernel.sin
after flashing Kernel, flash FW and all will be like first day!
Hi
I have Samsung Galaxy Player(yp-g70). I want to extract the kernel from a cm7 rom's boot.img made for this device. I tried it with perl sripts, on ubuntu and windows too, but I get the same error:
"android magic not found in boot.img. giving up"
How can I extract the kernel from this boot.img?
(I attached the boot.img, and the scripts)
the same problem
i also got the same issue , my device is htc one x . any one can help?
Use Dsixda android kitchen
Hi Guys,
i got a problem, it is somehow not possible to build a kernel.elf with the mkelf.py from sony, i got the correct header values with objdumb -x from the stock kernel, no chances to get it booting.
i then went on with just building a boot.img, this looks to be working fine, since the official sony ICS updated has not hit Germany, and with the FTF files provided i do not get WIFI working properly, neither with the stock kernel from those ftf, there must be regional changes to the wifi frequenzies ????
my unlocked kernel just boots fine, but as said i am not able to test anything properly since WiFi will not work....
i have attached the boot.img to this thread, flash it with
fastboot.exe flash boot boot.img
unlock bootloader required....
to get su(root), busybox and superuser you need to follow the guide provided here: http://forum.xda-developers.com/showthread.php?t=1839865
there is no recovery included yet,
please let me know if this works for you
cheers
it seemed it would not show up the signal"SONY"
it seemed it would not show up the signal"SONY".
I flashed the boot.img in fastboot mode,
when i pressed the power button,it showed "XPERIA",
I did not know how
This is the latest Flashtool 0.9.13.0:
Download here: http://ul.to/sb8cfqyr
Flashtool is a S1 flashing software that works for all Sony phones from X10 to Xperia Z Ultra. They all use the S1 protocol for flashing firmwares.
This program was originally made to flash sin files downloaded by SEUS or PCC. From time to time, sin files have been bundled into what is now well known FTF (Flash Tool Firmwares). That is the core of Flashtool and the reason of its name.
Flashtool can also easily unlock the bootloader of the phone using the BLU icon as far as the bootloader of your phone is unlockable
The flashing feature as well as bootloader unlock feature are available whatever the phone is recognized or not by the application. What is only mandatory for flashing is to own the FTF file according to the device you want to flash it on.
Why should I use flashtool ?
Once bootloader unlocked, official sony tools do not work anymore.
Using official sony tools, you can only upgrade. No downgrade possible.
Using flashtool, you can choose what to flash and what not to flash. This said, many rooting scenarios are available implying kernel only downgrade to retrieve a patched rooting exploit and then flash back the right kernel.
You said unlocking bootloader ?
This process gives you the opportunity to flash custom roms such as CyanogenMod ROMs.
I invite you to visit the FXP Project that brings CM to xperia devices.
Many other features have been built-in so that Flashtool can also be used to (as far as the phone is recognized by Flashtool) :
Root your phone
Install recovery, busybox, custom kernels
Clean your rom (remove /system/apps apps of your choice) (Be careful, unless you really know what you do, do not modify the default list. This can make your phone stuck at the SE Logo)
Clear dalvik cache
Optimize (install of JIT v2) (plugin for 2.1 phones only from 2010 line)
Customize (installs apps found in the custom/apps folder of the flashtool)
Edit any text file on the device
Rebrand your device