Flash Kernel - General Questions and Answers

i have the problem that my sound is to low. i flashed feacore kernel but is not better. i read that a vitaly kernel is better for more higher sound but i dont understand how i install it. There a wrote :
To activate it you need to edit the build.prop file with this :
Code:
debug.gr.swapinterval=0 to build.prop
What the guys mean? Can anyone write a step by step list how i can flash kernel on my KQE stockrom? it seemd that is not the same way like a feacore kernel flash
HHHHEEEEELLLLLPPPPP!!!!!!

asc1977 said:
i have the problem that my sound is to low. i flashed feacore kernel but is not better. i read that a vitaly kernel is better for more higher sound but i dont understand how i install it. There a wrote :
To activate it you need to edit the build.prop file with this :
Code:
debug.gr.swapinterval=0 to build.prop
What the guys mean? Can anyone write a step by step list how i can flash kernel on my KQE stockrom? it seemd that is not the same way like a feacore kernel flash
HHHHEEEEELLLLLPPPPP!!!!!!
Click to expand...
Click to collapse
Ask in your device forum. Anyway for build prop, it is at the system folder and a text file. Find the line that you need to edit and edit it. It its not there, add it.
Sent from my SGH-T959 using xda app-developers app

or has anyone a tip for a kernel which change volume higher which i can flash with odin or cwm or something else. a kernel without change thing in any txt files, only flashing

Goto /system/build.prop and add the line with a text editor. Reboot. That's it.

m_atze said:
Goto /system/build.prop and add the line with a text editor. Reboot. That's it.
Click to expand...
Click to collapse
must i change the kernel before or after this or can i do this anyway

asc1977 said:
i have the problem that my sound is to low. i flashed feacore kernel but is not better. i read that a vitaly kernel is better for more higher sound but i dont understand how i install it. There a wrote :
To activate it you need to edit the build.prop file with this :
Code:
debug.gr.swapinterval=0 to build.prop
What the guys mean? Can anyone write a step by step list how i can flash kernel on my KQE stockrom? it seemd that is not the same way like a feacore kernel flash
HHHHEEEEELLLLLPPPPP!!!!!!
Click to expand...
Click to collapse
to edit build.prop use Notepad++ or a tool from Market to edit it on your phone directly i.e. build.prop Editor then restart phone
usually to flash a kernel you have to enter download/ fastboot mode by a key combination at phone startup and flash it by
Code:
fastboot flash boot boot.img
better is to test the kernel before by this
Code:
fastboot boot boot.img
by this way in case of some problems just restart/remove battery and you revert to previous status (it means the new kernel will boot but never flashes on phone memory)
to work this you need Android SDK and USB drivers
remember : never flash a kernel not made for your phone because of a possible hardware failure
better is to get informed before to do that

ruscan.calin said:
to edit build.prop use Notepad++ or a tool from Market to edit it on your phone directly i.e. build.prop Editor then restart phone
usually to flash a kernel you have to enter download/ fastboot mode by a key combination at phone startup and flash it by
Code:
fastboot flash boot boot.img
better is to test the kernel before by this
Code:
fastboot boot boot.img
by this way in case of some problems just restart/remove battery and you revert to previous status (it means the new kernel will boot but never flashes on phone memory)
to work this you need Android SDK and USB drivers
remember : never flash a kernel not made for your phone because of a possible hardware failure
better is to get informed before to do that
Click to expand...
Click to collapse
what is please the fastboot. i know recovery modus and download modus and what i have to do with this codes????

asc1977 said:
what is please the fastboot. i know recovery modus and download modus and what i have to do with this codes????
Click to expand...
Click to collapse
well take a look here for a tutorial but do not flash anything at this time spend some days searching/ reading about these problems the secret word is search this site has good tutorials for almost everything !

ruscan.calin said:
well take a look here for a tutorial but do not flash anything at this time spend some days searching/ reading about these problems the secret word is search this site has good tutorials for almost everything !
Click to expand...
Click to collapse
ok i taste it and hope i can

So after a lot readings i flashed skyhigh Kernel 1.4d. My Volume is perfekt loud and the System runs :thumbup:
Sent from my GT-I9001 using xda app-developers app

thx for the tip

Has someone a tip for a louder kernel like skyhigh? Its loud but i want louder the sound is good but in navi it can be louder
Sent from my GT-I9001 using xda app-developers app

Related

[TOOL] Kernel Update Utility 0.9 - Flash kernels easily!

Kernel Update Utility 0.9​YouTube video​"Making kernel flashing a bit easier"​
About:
This lightweight tool takes a kernel, and flashes it to your device. You can give it the kernel in zImage or CWM flashable zip format. Some people have come across bootloops when using clockworkmod to flash kernels, hopefully this tool will prove to fit better for the job. It can also push and apply kernel modules. I have now flashed a kernel using this tool more times than I can count, and not a single bootloop or failed flash.
This tool is ideal for people who do not want to mess with command lines, and people who want the job done fast and easy.
System requirements:
Windows XP SP2 or higher
.NET 4.0
HTC Sync (or ADB drivers)
Rooted, ENG S-OFF Desire HD
Changelog:
0.9:
- Added support for Lee's kernels
0.8:
- Added support for Kamma's new kernels
0.7:
- Fixed Windows XP file not found -bug
- Optimized the code further
0.6:
- Most cmd windows hidden
- Better instructions in module pushing
- Out of beta!
0.5a:
- Optimized a lot of code
- Improved SU permissions; fixed modules not getting pushed with phones that do not have root adb by default
- Cleans up /system/lib/modules to ensure cp functionality
0.4:
- It is now possible to choose multiple modules
- It cleans up afterwards
0.3:
- CWM zip file flashing, pushes all modules
- Space in filename -bug fixed
0.2:
- Initial release
Click to expand...
Click to collapse
If you like my work, please consider (or just hit the thanks button ):
Hi,
thanks !!
Please add more selections for ko files:
- tun.ko
- cifs.ko
- other
with friendly greet
starbase64
Yeah, I will
I will also make this work with CWM flashable zips, I am programming that in right now.
Hi,
good news, thanks.
with friendly greet
starbase64
It can now flash zip files that would usually be flashed in clockworkmod. Using my app to flash it should reduce the possibility of a bootloop. Also the space in filename -bug has been fixed.
e: Another update, now for selecting and applying kernel modules. Please leave feedback! Is there something I should change? Any features you would like to see in this tool?
Keep in mind that this tool can also be used for recovering from some bootloops, where kernel itself is not properly flashed. In some situations, however, boot.img corrupts in CWM flash, then you will have to restore a partial nandroid.
thanks.. now i wish there is a tool for pushing ENG hboot and CWM recovery .. where is unrevoked
Well, I can enable my tool to flash a recovery, but because flashing hboot is so risky, I think I will not do that feature..
So, are people interested in a recovery flasher?
So now I can flash the .zip files that before I was flashing with the recovery with this application?
Yeah, if those files are kernels. This tool has been tested with Apache14's 1.2 and 1.5 GHz OC/UV kernels.
jkoljo said:
Yeah, if those files are kernels. This tool has been tested with Apache14's 1.2 and 1.5 GHz OC/UV kernels.
Click to expand...
Click to collapse
Wow it's amazing guy!!! i have tried now, with, before my htc desire hd was going in eternal bootloop with origianl rom and 1,2 kernel now it's ok really tank you!!!
No problem, glad it helped!
Hi,
support for german users here > www.handy-faq.de
with friendly greet
starbase64
Noob question but how can you revert back to original kernal?
Not tried this yet But this is What I been waiting for. How long does the process take?
Thanks
Sent from my Desire HD using XDA App
Used this tool to flash the Buzz 1.51GHz Kernel. First off, congrats on such an easy to use tool for noobs like me. It's really simple and straightforward. However, I now have a problem with my wifi not working (just shows 'error' in wifi settings). I'm guessing this is because the module didn't apply properly? I've tried it a couple of times now with the same result...although I fully accept it could be stupidity on my part.
Further info:
I have root (permenant, via visionary+) and S-off (Eng HBoot installed) but not installed clockwork recovery yet.
I start the app, set my DHD to 'charge only', tick 'I understand the risks' and click next.
Browse to the file I downloaded for the Kernel (this one) and click 'next'.
click 'go to fastboot' (phone reboots in fastboot mode) click 'Flash' and something about 'writing zimage' flashes past. Click Next. (phone reboots)
When phone reboots I enter my PIN, unlock the phone and select 'charge only' for the USB connection (this isn't mentioned, but I figure it needs to be connected like this for the adb stuff to work) and press 'apply modules'. Something on my phone requests superuser access (not sure if this is just co-incidence or something the app is doing) so I allow it. Loads of messages flash past on my desktop (I assume this is applying the modules) and the app says 'modules pushed and applied'.
My wifi status shows 'error' so I try a reboot. Still shows error.
Any ideas?
Deicist said:
Used this tool to flash the Buzz 1.51GHz Kernel. First off, congrats on such an easy to use tool for noobs like me. It's really simple and straightforward. However, I now have a problem with my wifi not working (just shows 'error' in wifi settings). I'm guessing this is because the module didn't apply properly? I've tried it a couple of times now with the same result...although I fully accept it could be stupidity on my part.
Further info:
I have root (permenant, via visionary+) and S-off (Eng HBoot installed) but not installed clockwork recovery yet.
I start the app, set my DHD to 'charge only', tick 'I understand the risks' and click next.
Browse to the file I downloaded for the Kernel (this one) and click 'next'.
click 'go to fastboot' (phone reboots in fastboot mode) click 'Flash' and something about 'writing zimage' flashes past. Click Next. (phone reboots)
When phone reboots I enter my PIN, unlock the phone and select 'charge only' for the USB connection (this isn't mentioned, but I figure it needs to be connected like this for the adb stuff to work) and press 'apply modules'. Something on my phone requests superuser access (not sure if this is just co-incidence or something the app is doing) so I allow it. Loads of messages flash past on my desktop (I assume this is applying the modules) and the app says 'modules pushed and applied'.
My wifi status shows 'error' so I try a reboot. Still shows error.
Any ideas?
Click to expand...
Click to collapse
Same issue here, does not push the wifi module
Strange, it does push it for me. I'll investigate. It may have something to do with root rights, does bcm4329.ko appear to your sdcard?
Nope, doesn't appear in sdcard.
For further info I tried it with 0.3 as well, same result.
Also, none of the modules get pushed, it's not just the wifi one.
My app removes the files from sdcard afterwards, so they might not be there anymore when you check it. I have now uploaded a new version with completely new SuperUser access code, also a lot of the code has been optimized.
This version works for me 100%, I just flashed from Apache14's kernel to kamma's kernel and back, wifi worked every time.
Also keep in mind that you should wait for the Android system to fully boot up before trying to push and apply the modules. So wait for "Usb debugging connected" and "Charge only"
Please give feedback!
jkoljo said:
My app removes the files from sdcard afterwards, so they might not be there anymore when you check it. I have now uploaded a new version with completely new SuperUser access code, also a lot of the code has been optimized.
This version works for me 100%, I just flashed from Apache14's kernel to kamma's kernel and back, wifi worked every time.
Also keep in mind that you should wait for the Android system to fully boot up before trying to push and apply the modules. So wait for "Usb debugging connected" and "Charge only"
Please give feedback!
Click to expand...
Click to collapse
Nope, will not push wifi module, all phone settings are as per instructions
Which rom are you on? Do you have HTC Sync 3.0 on your computer?
Try pushing modules manually as per Apache14's thread first post, if it works then the problem is propably in my tool, if it does not work, the problems is at your end.

Froyo (2.2) for HUAWEI U8120 [based on AOSP] (under development)

Froyo 2.2.2 port for Huawei U8120.
Maybe it will work on Huawei U8100/U8110 series, but for now it is focused on U8120.
So I dont know what behavior has on U8100 etc.
I must say a big thanks to Tom_G for his awesome work, especially for his froyo port on pulse.Without his work and his posts
on modaco forum, I will not be able to accomplish this.
kalt kaffe's 2.6.29 kernel.
Android 2.2.2 from aosp with some codeaurora changes.
JIT enabled.
Working:
RIL
Audio
GPS
Bluetooth
Wifi
SD card
Sensors
TSCalibration from codeaurora(still the app needs some improvements.For now use a stick or pen when you calibrate the screen)
Not working/bugs:
camera
broken layout on dialer
sdcard cannot be mounted in pc
Its still under development.This is not a finished rom and its not fully tested.
Probably it has problems that I have not yet encountered.So I would not suggest you to try it,
except if you have some experience and you want to help.
I have tried to make it as plain and simple as it gets.No google apps, no bootanimation etc.When all bugs are fixed then I will include them or I will post
my rom.But there are guys that are more expert in rom cooking than me.
Here is a zip with already compiled image files if someone wants to try it and post any bugs/fixes that have found.I have also uploaded here gapps if someone wants them(gmail,market etc)
Code: https://github.com/tas0s
Device tree: https://github.com/tas0s/android_device_huawei_u8120
Try it at your own risk.
Im not responsible for any damage that this may cause.
v.1 initial build
How to build it:
- Install git and gpg (gnupg).
- Download repo - http://source.android.com/source/git-repo.html
$ mkdir android
$ cd android
$ repo init -u https://github.com/tas0s/platform_manifest.git
$ repo sync
- Extract necessary binaries
Some compiled code from the official eclair roms is re-used in froyo. Because some of this code is not opensources I cannot included in the git repository.
The files can be extracted from any u8120 eclair rom.
Place the rom zip in the android directory an rename it to u8120_update.zip
navigate to /device/huawei/u8120:
cd device/huawei/u8120
Then execute from the android directory
$sh device/huawei/u8120/unzip_files.sh
else you can extract them from a working u8120 phone with an eclair rom (check that adb is enabled)
$device/huawei/u8120/extract_files.sh
- Building the system
Once thats done you can start compiling.
Follow the aosp instructions on setting up the build environment. - http://source.android.com/source/download.html
After the environment is setup.
$ cd android
$ source build/envsetup.sh
$ lunch
Select the device u8120.
$ make
I recommend using multiple threads for make if you have a multi core/processor system. By default make will use
1 thread (-j1), set it to use 2*NumberOfCPUsAvailable (so on my dual core -j4). Reducing the number of threads used will reduce the impact on
system performance while the build is running.
The output will be image files in {buildroot}/out/target/product/u8120/. Flash with fastboot.
$ fastboot flash boot out/target/product/u8120/boot.img
$ fastboot flash system out/target/product/u8120/system.img
$ fastboot flash userdata out/target/product/u8120/userdata.img
$ fastboot reboot
For some reason the generated boot.img fails to boot.Maybe I have something wrong about kernel base etc in the BoardConfig.mk.
For now just use the ramdisk.img and the provided kernel and pack it with dsixda's kitchen or with the huawei-u8100 tools that have been posted on the forum.
Then just use fastboot as stated above.
for the future
thnx for the gifts up to it tomorrow
A question about camera problem, only video or all features?
bitye said:
A question about camera problem, only video or all features?
Click to expand...
Click to collapse
The camera fails after a few secs.When an image appears in the preview window.
I have read that the the way that android handles camera has changed in froyo.In cyanogen they are using a libcamera2 (just libcamera with a few changes I think so it can work with the new framework).
As you can see in the BoardConfig.mk I have already include the libcamera2 statements but not the lib
When I manage to get some free time I would try the libcamera2.Maybe until the end of the week or sooner.
Ρε πατριδα αξιζει η rom ή οχι;
tas0s said:
For some reason the generated boot.img fails to boot.Maybe I have something wrong about kernel base etc in the BoardConfig.mk.
For now just use the ramdisk.img and the provided kernel and pack it with dsixda's kitchen or with the huawei-u8100 tools that have been posted on the forum.
Then just use fastboot as stated above.
Click to expand...
Click to collapse
There's a little fix using bootbuilder for U8120, see this post:
http://android.modaco.com/content/t...l-r1-bootbuilder-for-pulsemini-alpha-release/
In the 6th reply you can find the info you could need it
Good luck!
Hi can you tell me on wich kernel it runs?
the 2.6.32 or2.6.29?
and if wiifi is completly fixed no crashes sleep works mac adress?
thanks
calibration fixed at this repo?
larissamafia said:
Ρε πατριδα αξιζει η rom ή οχι;
Click to expand...
Click to collapse
Πατριωτάκι δεν είναι για καθημερινή χρήση ακόμα.Γιαυτό δεν έχω βγάλει και έτοιμη rom.
@Shiftok:
The calibration is integrated in the framework etc but it has some small issues.
As I say in the first post, it needs improvement.
@Cedric123:
Im using 2.6.29 kernel.The wifi works normally.If I remember right and MAC address.
tas0s said:
@Shiftok:
The calibration is integrated in the framework etc but it has some small issues.
As I say in the first post, it needs improvement.
@Cedric123:
Im using 2.6.29 kernel.The wifi works normally.If I remember right and MAC address.
Click to expand...
Click to collapse
ah okey
does this work?
i extract boot.img
put my own zImage in it
repack boot.img
start Phone?
i rly want my own kernel in the ROM with my overclock funtion adn all my +kalt+kaffes optimizations
cedric123 said:
ah okey
does this work?
i extract boot.img
put my own zImage in it
repack boot.img
start Phone?
i rly want my own kernel in the ROM with my overclock funtion adn all my +kalt+kaffes optimizations
Click to expand...
Click to collapse
The kernel Im using is kalt kaffe's kernel.So I think that if you just replace the kernel and the kernel modules in /system/lib/modules you will be fine.
Im uploading now a zip with the compiled images.
It has the problems I mention in the first post etc.
Just an observation.If the calibration isnt correct the screen is always on landscape mode Propably because it gets wrong screen dimensions.So if you see something like that, calibrate your screen with the TSCalibration app.
When im done with the camera, I will fix the calibration bugs.
Hi. Im testing your rom.
I cannot mount the sdcard on computer. when i press to activate usb storage it does nothing in computer.
EDIT - i cant install anything because i dont have a file explorer to see the sdcard files. can you please add one or make an .img with the stock apps
joilaroi said:
Hi. Im testing your rom.
I cannot mount the sdcard on computer. when i press to activate usb storage it does nothing in computer.
EDIT - i cant install anything because i dont have a file explorer to see the sdcard files. can you please add one or make an .img with the stock apps
Click to expand...
Click to collapse
Thank you very much for the feedback joilaroi.I have updated the first post with the sdcard bug.I tried myself and you are right.I will try to fix it.
As I know the stock android froyo hasnt any file manager/explorer.Maybe we can get it from cyanogens.
For now, you can do this.Flash the gapps update that I have in the first post,setup market etc and download a file manager from the market(ex.astro file explorer).
tas0s said:
Thank you very much for the feedback joilaroi.I have updated the first post with the sdcard bug.I tried myself and you are right.I will try to fix it.
As I know the stock android froyo hasnt any file manager/explorer.Maybe we can get it from cyanogens.
For now, you can do this.Flash the gapps update that I have in the first post,setup market etc and download a file manager from the market(ex.astro file explorer).
Click to expand...
Click to collapse
thanks. its what i am doing. if i find anything i will give feedback
EDIT - Cant install superuser and have permissions. it downloads su-2.3.1-bin-signed.zip to sdcard but its corrupted. maybe its better if its already on .img
Im getting more MFLOPS with 633Mhz in this rom than with 691Mhz with the other kernel. its now with 4.45 MFLOPS vs 4.1MFLOPS. Nice
Do you know where i can find su-2.3.1-bin-signed.zip?
Ubuntu 10.10 x64 under W7 VMWare will be enought for compile?
PC: C2D [email protected],2GHZ 8GB RAM
Laptop: Lenovo T410 i5 vPro 2,4GHz Quad Core 4GB RAM
I think yes

[REF][DEV]How to unpack / repack normalboot.img

Hi all, like you know our phone is different from other cause - to flash the kernel - you need to pack it with the ramdisk files and flash it to the phone as normalboot.img.
Some people want try to build a custom kernel but after they obtain the zImage file they are not able to flash it to the phone.
So here is the "HOWTO" to explain what you have to do for unpack/repack normalboot.img.
You need Linux to do this (also a visrtualized distro).
1- download and unzip the attached file;
2- place the normalboot.img file into the tools folder;
3- go in the root folder and do:
Code:
./unpack-all.sh
4- now you have succesfull unpacked your file. You can find the zImage file in the "kernel" folder and the ramdisk files in the "ramdisk" folder.
Basically now you can do all that you want. If you have a custom kernel overwrite the zImage file with your. If you want edit the ramdisk go in the folder called "ramdisk" and mod what you want.
When you finished do:
Code:
./create_boot.img.sh
Now you will find the .tar file ready to be flashed on your phone with odin.
If you are asking yourself "where can i find normalboot.img file?" the answers are:
1- into the PDA.tar of your Firmware;
2- dump it from the phone with:
Code:
dd if=/dev/block/bml7 of=/sdcard/normalboot.img
Bye
Thanks Buddy..
BTW your posts are always very crisp and enlightening. I appreciate.
regards
I tried the script, and it seems to work. Seems, because it unpacked and repacked fine, and I replaced the kernel with a self compiled one. But, to make it short, the phone didn't boot. It was stuck on the "Galaxy S"-screen.
Any ideas, why a kernel which compiled without errors does not boot? Skin, did you change specific settings for compiling your OC-kernel, besides the overclocking adjustments?
XDA_Bam said:
I tried the script, and it seems to work. Seems, because it unpacked and repacked fine, and I replaced the kernel with a self compiled one. But, to make it short, the phone didn't boot. It was stuck on the "Galaxy S"-screen.
Any ideas, why a kernel which compiled without errors does not boot? Skin, did you change specific settings for compiling your OC-kernel, besides the overclocking adjustments?
Click to expand...
Click to collapse
I think that your kernel version doesn't match with the modules... so in your Makefile change the version name to match it with the stock.... so you have to change the version from 2.6.35.7 to 2.6.35.7-CL..... (don't remember if the number are correct)
Thanks, Skin! That did the trick. Now running self compiled vanilla kernel. Interestingly, it is about 200kb bigger than the stock kernel.
EDIT: Obviously, the repack-script is running fine.
other way to do dis is by using kitchen ..
js rename ur normalboot.img to boot.img den replace the boot.img in ur working directory ..
in the kitchen advanced options , unpack/repack boot.img ...
u ll get the same output
this one is easier as we dont need to remember the commands
XDA_Bam said:
Thanks, Skin! That did the trick. Now running self compiled vanilla kernel. Interestingly, it is about 200kb bigger than the stock kernel.
EDIT: Obviously, the repack-script is running fine.
Click to expand...
Click to collapse
To make it smaller you can use the Buildscript used in the froyo version of kernel source... Amit told me it this morning... and it worked greatly
bajju123 said:
other way to do dis is by using kitchen ..
js rename ur normalboot.img to boot.img den replace the boot.img in ur working directory ..
in the kitchen advanced options , unpack/repack boot.img ...
u ll get the same output
this one is easier as we dont need to remember the commands
Click to expand...
Click to collapse
Commands? You can do it with two mouse click!
Skin1980 said:
To make it smaller you can use the Buildscript used in the froyo version of kernel source... Amit told me it this morning... and it worked greatly
Click to expand...
Click to collapse
Yes, works. But my kernel stays at 3.3MB... still 0.2 larger than the stock one.
By the way: Had a SOD with the self-compiled kernel. Screen didn't wake up from standby, but soft buttons were lid. Guess the info from Samsung that closed source software is missing from the package is correct
i still have sod also with the new compilation mod.... by me sammy is missing something or simply the source are not updated like i supposed....
thanks....this rescued me
---------- Post added at 07:50 AM ---------- Previous post was at 07:20 AM ----------
i have a silly doubt
cud i download the linux kernel v3 from korg and compile it for i9003?or do i have to stick with 2.6.35?
Maybe it would be possible. The main problem are the drivers - they would most likely require major changes. But even CyanogenMod is running 2.6.37 and nothing more recent.
If you want to use a newer kernel, you could try that one, or - to minimize problems - use the 2.6.35.14 bugfix release. This seems most reasonable to me.
XDA_Bam said:
Maybe it would be possible. The main problem are the drivers - they would most likely require major changes. But even CyanogenMod is running 2.6.37 and nothing more recent.
If you want to use a newer kernel, you could try that one, or - to minimize problems - use the 2.6.35.14 bugfix release. This seems most reasonable to me.
Click to expand...
Click to collapse
shoot........404 not found
Those hackers...................
you are our phone's God!
Sent from my GT-I9003 using xda premium
i need help, i try to make stock normalboot.img tar with ur files.
but there is a big bug
phono booting but stay at "samsung" screen.
someone have this bug like me and u says that "chance ur kernel version in make boot file" but i cant find how chance kernel version in make boot file. how can i?
ROM: 2.3.6 JVKPB TUR ROM (galaxy sl i9003)
please help...
Skin1980 said:
Hi all, like you know our phone is different from other cause - to flash the kernel - you need to pack it with the ramdisk files and flash it to the phone as normalboot.img.
Some people want try to build a custom kernel but after they obtain the zImage file they are not able to flash it to the phone.
So here is the "HOWTO" to explain what you have to do for unpack/repack normalboot.img.
You need Linux to do this (also a visrtualized distro).
1- download and unzip the attached file;
2- place the normalboot.img file into the tools folder;
3- go in the root folder and do:
Code:
./unpack-all.sh
4- now you have succesfull unpacked your file. You can find the zImage file in the "kernel" folder and the ramdisk files in the "ramdisk" folder.
Basically now you can do all that you want. If you have a custom kernel overwrite the zImage file with your. If you want edit the ramdisk go in the folder called "ramdisk" and mod what you want.
When you finished do:
Code:
./create_boot.img.sh
Now you will find the .tar file ready to be flashed on your phone with odin.
If you are asking yourself "where can i find normalboot.img file?" the answers are:
1- into the PDA.tar of your Firmware;
2- dump it from the phone with:
Code:
dd if=/dev/block/bml7 of=/sdcard/normalboot.img
Bye
Click to expand...
Click to collapse
Wow you are great !!! Loved it .. so easy .... made my dead phone alive .. you are the best \m/

[DEV] AOSP 2.3 Gingerbread for Optimus3D

If you are not a developer out of here!! these manipulations can definitely brick your phone​
Hi all,
I try to port the source from TI blaze developpement board with OMAP4430 to our O3D.
I followed the tutorial bellow to compile the source of the TI Blaze :
http://www.omappedia.org/wiki/L27.G.3_OMAP4_GingerBread_Release_Notes
(you can see lot of drivers are include in these sources like Graphic, Wifi, etc...)
And Cyanogen tutorial to compile the boot.img with kernel for O3D
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source
But I have meet some trouble because the O3D is not mtd device (cat /proc/mtd display error) and when I try unpacking the O3D boot.img from Rom Manager Backup the tool display : "header is not present in boot.img" so I can do anything...
I get same error boot.img when I have try to use "dsixda's Android Kitchen" tool.
So for the last i try to use directly compiled sources and kernel of TI blaze in our O3D by creating update.zip file with dsixda's tool but the recovery of Rom Manager can't apply it..
I have recover my backup stock rom with Rom Manager with any problem.
Compiled Sources and kernel of OMAP4430
--- EDIT : Finaly I get working boot.img from O3D ---​
How to get boot.img from O3D
Code:
Optimus3D rooted connected to PC with debug mode activated
>./adb shell
>$
open Super-utilisateur app in O3D
>$ su
Accept root acces popup in Super-utilisateur app in O3D
>#
># cat /proc/partitions (display partitions in your O3D, mmcblk0p5 is the boot.img)
># cat /dev/block/mmcblk0p5 > /sdcard/boot.img (dump to sdcard)
boot.img from O3D with tools​
I have made new boot.img with Blaze kernel and new update.zip with dsixda's tool but RomManager recovery refuse to apply it...
Please Help!
Sorry for my very bad english...
Br,
I've same problem, i'm a noob with lg stuff.
maybe boot.img is similar to optimus 2x, i've asked to lg2x kernel developers but without answer
Finaly i have got working boot.img from O3D! look first post.
Perhaps you have an older version rom manager.
what exactly is the difference between the blaze and the stock kernel?
I think they are same kernel.
Can anyone have brickedO3D can try with fastboot command?
Code:
Reboot the phone into bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
I hope that Ricardo (who have porting CM7 into O3D) write a few words to guide us.
zizouth said:
I think they are same kernel.
Can anyone have brickedO3D can try with fastboot command?
Code:
Reboot the phone into bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
I hope that Ricardo (who have porting CM7 into O3D) write a few words to guide us.
Click to expand...
Click to collapse
So the kernel in gingerbread stills "the same" as actually on Froyo? unveliable!
I mean same for modules (drivers) not for fonctionnality
Sent from my LG-P920 using XDA App
zizouth said:
I mean same for modules (drivers) not for fonctionnality
Sent from my LG-P920 using XDA App
Click to expand...
Click to collapse
SO there arent diference on performance? due drivers are the same...
Ok.... I said same because Blaze and O3D use OMAP4430 SO same mean we can porting gingerbread from blaze to O3D .
Sent from my LG-P920 using XDA App
zizouth said:
Ok.... I said same because Blaze and O3D use OMAP4430 SO same mean we can porting gingerbread from blaze to O3D .
Sent from my LG-P920 using XDA App
Click to expand...
Click to collapse
There is something wrong with the omap4430 DPS, because photos suffer from post processing and high level compression....
THats why because photos looks orrible... maybe there is a value lower than usual...
Same happens with droid 3, with the same processor, have the same "effect" on photos like on O3D....
The goal now is booting the O3D with Gingerbread source from blaze, after that we can rebuild the kernel and check the driver to optimise the pictures.
@|ErosizeD| just send you PM, the Optimus 3D have imx072 sensor (5mp).
Br,
zizouth said:
The goal now is booting the O3D with Gingerbread source from blaze, after that we can rebuild the kernel and check the driver to optimise the pictures.
@|ErosizeD| just send you PM, the Optimus 3D have imx072 sensor (5mp).
Br,
Click to expand...
Click to collapse
Sure at all is an IMX072? i cant find that driver on the Kernel ( official ) from LG.
I answered the pm and waiting another answer.
Thx.

[Fastboot]Custom Kernel for Motorola Defy Mini XT320/XT321

First custom kernel for Defy Mini XT320/XT321 is here!
Featured on XDA Portal: http://www.xda-developers.com/android/first-custom-kernel-for-the-motorola-defy-mini-mini-xt320xt32/
@MauroSZ @Bernd.Defy @junk031
Despite us having a locked bootloader, we can boot a custom kernel via fastboot.
Technical Details:
Fastboot is stored as a secondary bootloader in Defy Mini. On older firmwares, the secondary bootloader had fastboot enabled but newer firmwares don't. This is why Motorola left a vulnerability in fastboot which allowed us to fastboot boot img files.
Kernel Source: https://github.com/rootdefyxt320/android_kernel_motorola_tinboost
This kernel is made for Defy Mini stock ROM's.
Details:
Linux Kernel version 2.6.38.6
Features:
-Swap
-Insecure
To Do:
-Add overclock
-Add custom governors
Limitations:
-You must use fastboot everytime you want to boot a custom kernel so it requires a computer.
Instructions:
1. Download boot.img from attachments
2. Download modules.zip from attachments.
3. Make sure you have CWM Recovery, if not download it from Post #41
4. Now boot into CWM Recovery using the batch script or typing the command in cmd
Code:
fastboot boot name-of-recovery.img
4. Now type these commands in cmd:
Code:
adb shell mount -a
Code:
adb push modules.zip /sdcard
Code:
adb shell
Code:
cd /system/lib/modules
Code:
busybox unzip /sdcard/modules.zip
Then it will ask you to overwrite the files, press A on the keyboard.
Now type the next commands in cmd:
Code:
cd /system/lib
Code:
chmod 755 modules/*
Code:
exit
Code:
adb reboot-bootloader
Code:
fastboot boot boot.img
Updated to v2 in Post 8: http://forum.xda-developers.com/showpost.php?p=51104120&postcount=8
Same installation instructions as v1.
Lol, I compiled one for XT530 with OC and undervolt, but never released as thought it would be tough to boot it everytime
Well, nice start. I'm currently working on kexec, would possibly release it when kexec would be ready.
rootdefyxt320 said:
Limitations:
-You must use fastboot everytime you want to boot a custom kernel so it requires a computer.
Click to expand...
Click to collapse
it's possible make it permanent?
sfoot13 said:
it's possible make it permanent?
Click to expand...
Click to collapse
Locked bootloader prevents this. Until I can conpile kexec, I can make it permanent.
rootdefyxt320 said:
Locked bootloader prevents this. Until I can conpile kexec, I can make it permanent.
Click to expand...
Click to collapse
You're a genius! i hope you can have success with the kexec!
You know if swap will make any difference in the performance?
sfoot13 said:
You're a genius! i hope you can have success with the kexec!
You know if swap will make any difference in the performance?
Click to expand...
Click to collapse
I built an 800MHz overclock kernel but beware you can burn your NAND but we can now use @cute_prince method to have a 878 MHz PLL2 overclock without burning NAND It's not modded numbers
rootdefyxt320 said:
I built an 800MHz overclock kernel but beware you can burn your NAND but we can now use @cute_prince method to have a 878 MHz PLL2 overclock without burning NAND It's not modded numbers
Click to expand...
Click to collapse
are you working on it? (878 MHZ overclocking)... thanks for your work bro! :good:
sfoot13 said:
are you working on it? (878 MHZ overclocking)... thanks for your work bro! :good:
Click to expand...
Click to collapse
Hey, I managed to improve the performance of the kernel also by using LZMA compression instead of GZIP, switching to SLUB allocator and deadline I/O scheduler and overclock also.
Kernel v2 Update:
-Uses LZMA compression
-Enabled OTG Support
-Switched to SLUB Allocator
-Added Deadline I/O Scheduler
-Default VDD=7 for better overclocking with Bernd.Defy's overclock module.
-Enable zRAM.
You must install the new modules otherwise device will bootloop!
Thank you so much! OTG support *-* is a great gift!
bro, can you do it permanent? is something uncomfortable always connect the phone to pc, anyway thanks for your work!
sfoot13 said:
Thank you so much! OTG support *-* is a great gift!
bro, can you do it permanent? is something uncomfortable always connect the phone to pc, anyway thanks for your work!
Click to expand...
Click to collapse
I'm busy studying for exams these days. Kexec requires a lot of hard work before we can even boot the kexec custom kernel. Remember, I'm just a 16 year old dev, so got to have priorities in school work first
rootdefyxt320 said:
I'm busy studying for exams these days. Kexec requires a lot of hard work before we can even boot the kexec custom kernel. Remember, I'm just a 16 year old dev, so got to have priorities in school work first
Click to expand...
Click to collapse
Oh sorry, i don't knew! 16 years old dev.? really? you're doing a great work :good:
Well, success on your studies! God bless u
sfoot13 said:
Oh sorry, i don't knew! 16 years old dev.? really? you're doing a great work :good:
Well, success on your studies! God bless u
Click to expand...
Click to collapse
Is USB OTG working for you? Please test it as I don't have any USB OTG equipment and give me feedback on the performance of the kernel
rootdefyxt320 said:
Is USB OTG working for you? Please test it as I don't have any USB OTG equipment and give me feedback on the performance of the kernel
Click to expand...
Click to collapse
i need search my OTG cable, i don't know where is... about the overclock.. it's possible increase it?
sfoot13 said:
i need search my OTG cable, i don't know where is... about the overclock.. it's possible increase it?
Click to expand...
Click to collapse
Use Bernd.Defy's overclock module for now. I have overclocked my Defy Mini to 720MHz using his overclock module.
Go to the thread:http://forum.xda-developers.com/showthread.php?t=2210799
Then extract the defymini_oc.ko out of the zip folder.
Then use adb to push the file:
Code:
adb push defymini_oc.ko /system/lib/modules
Then use these commands in cmd:
Code:
adb shell
Code:
su
Code:
busybox insmod /system/lib/modules/defymini_oc.ko pll2_l_val=75 acpu_freq_tbl_addr=0xc0775b5c cpufreq_stats_tbl_addr=0xc07a971c
rootdefyxt320 said:
Use Bernd.Defy's overclock module for now. I have overclocked my Defy Mini to 720MHz using his overclock module.
Click to expand...
Click to collapse
me only 700MHZ, 720 reboot my phone, i'm using smartassV2 and I/O deadline and the performance is good, a bit better than noop (I/O) and smartassv2 together
Framework-res, Phone and SystemUI modded!
Hi, i edited the framework.res.apk, Phone.apk and SystemUI.apk, i just changed some icons and images, and the color of divisors
Just download the zip files and put it on your SD, boot into CWM recovery, select install update.zip and install the modded files
Make sure you have a backup of your original files.
rootdefyxt320 said:
Is USB OTG working for you? Please test it as I don't have any USB OTG equipment and give me feedback on the performance of the kernel
Click to expand...
Click to collapse
OTG not working, and with the new modules (V2), i have a WIFI "error" using the stock kernel, but i fixed it with the first version of your modules.
sfoot13 said:
OTG not working, and with the new modules (V2), i have a WIFI "error" using the stock kernel, but i fixed it with the first version of your modules.
Click to expand...
Click to collapse
The V2 modules are for the V2 custom kernel as there is substantial changes to the features. The new modules are made for SLUB Allocator instead of the SLAB allocator in the stock kernel. Try using an app to see if OTG is present.
sorry i am geting unzip write: no space left on device ,
i have no experience in this, please help
feline2611 said:
sorry i am geting unzip write: no space left on device ,
i have no experience in this, please help
Click to expand...
Click to collapse
You will have to delete stuff in /system.

Categories

Resources