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.
Hello all developers of NookTablet team).
I read many threads about good booting of modifitated kernels from SD card. When I compile own kernel based on stock source and then make boot.img I receive only message in UART (yes I have uart access):
Starting kernel ...
After 3-5 sec Nook reboot CPU(.
P.S. To build boot.img I use http://www.freeyourandroid.com/guide/extract-edit-repack-boot-img-windows instruction (thanks to Goncezilla)
I am newbie in Android development, but not in linux development.
Hey guys,
I have a bit of a head scratcher. I am currently trying to flash my new Sanei n10 tablet with CM10 and it is proving much more difficult than I first imagined.
My main problem seems to be that the device just does not want to boot in CWM. I have installed the latest version of CWM (found here) via the Terminal Emulator but it doesn't boot into CWM Recovery, but rather just boots normally. I have also tried using the hard keys to boot into it but all that does is boot me into the default android system recovery (3e) which is useless as it will only update from verified roms.
The device is rooted and I have ROM Manager installed. I have given Terminal Emulator superuser permissions... It just doesn't seem to want to boot into CWM Recovery. I have tried using both ROM Manager as well as NOVO7 Tools to boot into it but I get the same results (device just reboots normally)
I think that it might be something to do with the stock ICS 4.0.4 that came with the device.that is causing me so much hastle, but I was hoping someone out there might have experienced a similar issue or can offer some insight to where I am going wrong.
Thanks in advance!
M
msm1003 said:
Hey guys,
I have a bit of a head scratcher. I am currently trying to flash my new Sanei n10 tablet with CM10 and it is proving much more difficult than I first imagined.
My main problem seems to be that the device just does not want to boot in CWM. I have installed the latest version of CWM (found here) via the Terminal Emulator but it doesn't boot into CWM Recovery, but rather just boots normally. I have also tried using the hard keys to boot into it but all that does is boot me into the default android system recovery (3e) which is useless as it will only update from verified roms.
The device is rooted and I have ROM Manager installed. I have given Terminal Emulator superuser permissions... It just doesn't seem to want to boot into CWM Recovery. I have tried using both ROM Manager as well as NOVO7 Tools to boot into it but I get the same results (device just reboots normally)
I think that it might be something to do with the stock ICS 4.0.4 that came with the device.that is causing me so much hastle, but I was hoping someone out there might have experienced a similar issue or can offer some insight to where I am going wrong.
Thanks in advance!
M
Click to expand...
Click to collapse
here
1. Download the latest ClockWorkMod for Allwinner A10 tablets from here:
http://forum.xda-developers.com/show....php?t=1802268
2. Put all three files in the ZIP inside the root of a MicroSD card and insert it in the tablet
3. Check from the Terminal app inside the tablet to see if the MicroSD card is mounted in /sdcard (just type "ls /sdcard").
4. If the "ls" command doesn't show anything (that's what happened in my case), then you must modify the "install-recovery.sh" file and replace all instances of "/sdcard" with "/mnt/extsd".
5. With the proper "install-recovery.sh" file, run the commands specified in the above xda link (in my case the card is in "/mnt/extsd" instead of "/mnt/sdcard" as the original example shows):
su
cd /mnt/extsd
sh install-recovery.sh
sh reboot-recovery.sh
6. The tablet will then reboot to CWM recovery. Then follow the regular steps to install Cyanogenmod (wipe plus install ROM + GApps + Compatibility). This time the Recovery menu won't care about the files being unsigned and will install them right away!
Hello to the community,
I need to revert to stock kernel on my Sony Xperia Z5 compact ("formfactor" E5823). So I thought flashing the stock kernel which I extracted from the corresponding ".tft"-file will do that. So I flashed the extracted ".elf"-file with flashtool. But after restart I get stuck with the boot logo of Android "Marshmallow".
To avoid further questions I'll describe what I've done to root my device after unlocking the bootloader:
ROOTING:
- I downloaded a ".tft"-file containing Android 6 (32.2.A.0.253 build 1298-1220 R2C) and saved it to my hard disk
- I installed this ".tft" on my Sony Xperia Z5 compact using Flashtool (version 0.9.22.3)
- I opened the ".tft" from my hard disk and extracted the "kernel.sin"
- With Flashtool (version 0.9.22.3) I extracted "kernel.elf" from the ".sin" file
- I rooted the ".elf" using rootkernel (version 5 RC4), using the Options Sony RIC disabled, dm verity disabled, installing SuperSU 2.79, TWRP and DRM-Fix and saved the result to "kernel_rooted.elf"
- I flashed that rooted kernel using Flashtool (version 0.9.22.3) without error
- After rebooting the system was running rooted and without stucking in a boot loop
UNROOTING:
- I flashed the unrooted kernel "kernel.elf" using Flashtool (version 0.9.23.1)
- After rebooting the system get stuck in a bootloop showing the Marshmallow boot logo
And this is what I don't understand:
I use an unmodified stock kernel and get stuck in a boot loop. Another strange thing is that when flashing other rooted kernels (using updated tools rootkernel (version 5.23) and Flashtool (version 0.9.32.1)); for example just with TWRP installed) I get stuck in boot loops, too. The only working kernel is that one I described above.
Can someone tell me what I'm doing wrong?
Thanks for help and greetings from Germany
Not sure if this will help, but did you wipe the cache and dalvik cache?
mhaha said:
Not sure if this will help, but did you wipe the cache and dalvik cache?
Click to expand...
Click to collapse
Thanks for your suggestion.
I did it and it had no effect
Hello all,
I have a question about flashing Lenovo IdeaTab A1000LF (MTK6577 device). I would like to add busybox into initramfs and slightly change init strategy. boot.img from official ROM A1000LF_A412_01_05_130705_USER_DCC was unpacked with abootimg from Fedora repo. I added busybox for armv7l into initramfs/sbin and packed it again with the same tool. New boot.img was flashed into device with Flash Tools 3 (works on virtual machine with Win7) in Firmware Update mode with DA DL All With check sum option. Download mode did not work (there was errors in scatter file, __NODL_FAT partition exactly). Tablet was starting after flashing fow a few seconds. First boot logo was shown and then reboot again. Everything seems to work fine in case of flashing original boot.img. There might be some problems with Checksums or packing/unpacking initramfs (even if I create new boot.img without changes, tablet will not boot correctly). Do you have any ideas?
P.S. I didn't find suitable general thread for such kind of devices and tasks. Maybe you can suggest something.