Database Develop

Kernel compilation for Samsung Galaxy S I9000

Hi all,
we are trying to build our own kernel for a Samsung Galaxy S (I9000XWJVB).
What we did so far:
- Download the correct sources from "opensource.samsung.com"
- Studied the README
- Installed cross-compiler toolchain
- Created ".config" as described in README
- Kernel compiled
Compilation worked fine -> zImage was available (but with only 2mb very)
OK, looks like initramfs is missing.
The first question is now, where to get / how to create a correct initramfs?
We copied the initramfs from Leshak and we extracted an ".cpio" from a working zImage.
Then we tried to use them in the ".config" (CONFIG_INITRAMFS_SOURCE) for kernel compilation.
Resultant zImage was larger (around 6mb) so it looks like something changed.
But once we installed the tared zImage on the phone (using Odin), the phone freezes during reboot.
Any advice how to progress here?
Is it possible to use Leshaks initramfs for all Galaxy S phones? Or is this only for a specific version? The CONFIG_INITRAMFS_SOURCE should point to the "initrd.arm.initramfs_list", correct? And not to the initramfs-folder?
And: Is there a way to get any type of kernel boot debugging message from the booting phone back to the PC (or the phone screen)?
Many thanks in advance!

I don't know much about kernels. But i will try to help. Have you tried other itiramfs or reconfig them?
There are not many people that will know answer so ask some kernel developers like hardcore, supercurio...
Sent from my GT-I9000 using XDA Premium App

Just saw 2nd question. I think that it should point to intiramfs folder. You can zip all kernel files and upload it so i can take a look at them
Sent from my GT-I9000 using XDA Premium App

Hi,
themate1987 said:
I don't know much about kernels. But i will try to help. Have you tried other itiramfs or reconfig them?
There are not many people that will know answer so ask some kernel developers like hardcore, supercurio...
Click to expand...
Click to collapse
we tried four different initramfs now, but ended up always with a freezing phone.
I would like to ask the kernel experts directly, but I'm new to this forum and not allowed to post in the developers forums. I hope that one of the gurus will reply to this thread.
themate1987 said:
Just saw 2nd question. I think that it should point to intiramfs folder.
Click to expand...
Click to collapse
My understanding is that the .list file will describe the structure of the initramfs folder and if this file is present, it should by used in the .config. Otherwise the .config should point to the folder.
Please correct me if I'm wrong.
But anyway, we tried both versions, none worked.
Regards!

PM some kernel developers
Sent from my GT-I9000 using XDA Premium App

Use speedmod kernel patches with the readme file he has given..
or else you can go through supercurio threads also ...
they explained the kernel compilation methods....
thanks

Did you get this to work finally? I too am trying to compile and flash a custom kernel ( For SGS4G) I point my INIIRAMFS_SOURCE to an extracted initram dir, but the resulting boot zImage does not proceed past the initial boot screen(s) Please let me know if you succeeded, and if yes, how.
Thanks!

What I got the problem was about initramfs.cpio.
At that moment , the most important point you know is you should make the file in Linux..
When my friend made me a file is initramfs.cpio , it worked well.
But what I made in window made always troubles for compile.
So if you made a initramfs.cpio with hexeditor in window, try it in Linux again..
Thx!

[Q] self-build stock-kernel not booting

Hi all,
I am having hard time since a couple of days building correct samsung kernel stock forked from here https://github.com/project-voodoo/linux_gt-i9000
I followed build README, modified makefile to point to correct codesourcery cross compiler, followed supercurio notes for localversion...
When I change the original zimage of XWJVB from samfirmware.com with the one I get from the build and I falsh it, the kernel doesn't boot. Am I missing something?
Do I need to include the intiramfs? or Do I need to change the bootloader (I ignore if any cryptographic calculation are made by the original bootloader before loading the kernel)
Thanks

Initramfs are not included in stock kernel sources...that's why it doesn't boot, try with Voodoo initramfs that are surely the best ones!
PS: if u need some help just contact me! i am also a kernel dev since a couple of months
Sent from my GT-I9000 using Tapatalk

Hi Simone201,
Thanks for the hint.
I made a progress but phone still not booting.
I edited .config to point to the intiramfs folder
CONFIG_INITRAMFS_SOURCE="~/samsung_initramfs/gingerbread-i9000xwjvb"
CONFIG_INITRAMFS_COMPRESSION_GZIP=y
ONFIG_INITRAMFS_ROOT_UID=0
CONFIG_INITRAMFS_ROOT_GID=0
Click to expand...
Click to collapse
and I was asked to either compress the intiramfs or not. I have tried both options.
once
CONFIG_INITRAMFS_COMPRESSION_NONE=y
# CONFIG_INITRAMFS_COMPRESSION_GZIP is not set
Click to expand...
Click to collapse
and other trail with
CONFIG_INITRAMFS_COMPRESSION_NONE is not set
# CONFIG_INITRAMFS_COMPRESSION_GZIP=y
Click to expand...
Click to collapse
now with the intiramfs, the zimage size increase from 3.3 mb to 5.4 mb but still doesn't match the stock size 5.5 mb
What shall I do?
thanks for your help

Made some progress but still fighting to get it work!
I am already studying scripts of supercurio from github.
I figured out that I have to delete the .igit and .gitignore from the intiramfs (I am using XWJVB from supercurio repository too).
As I understand, it is optional to copy the .ko generated module from my compilation to my /lib/module in my intiramfs. Correct? Anyway, I will make it.
I thought I have to use Sourcery G++ Lite 2009q3-68 toolchain for ARM EABI as cross-compiler (arm-none-eabi-), but start doubting it as some scripts are using Sourcery G++ Lite 2009q3-67 (arm-none -linux-gnueabi-) (for kernel compilation!)
I flashed my phone with all XWJVB module from samfirmaware.com (boot, sbl, data, phone, pda ...) with reformat enabled. it is working. And now I am trying to only flash the pda partition with the zimage I obtain out of compilation.
I am really disappointed that there is no detailed compilation guide.
Anyway, thanks for your help guys!

Help for custom boot loader for Cyanogenmod 7.1

I have installed Cyanogenmod 7.1 and modified my bootanimation. I would like to also modify my bootloader screen, the first screen that appears just after the phone boots. Please help on t this topic! Thanx in advance!

Well that's not as easy as changing the bootanimation.... Cause i think you need to build your own kernel.

Thanx! Could you please make or modify a kernel for the cyanogenmod 7.1 that I'm using. I'm pretty new to this android development, all I know is how to root, change bootanimation, and other basic things. Thanx in advance!

Ya kernel...read it can be changed in the param.lfs without having to build a kernel. Not sure how true this is in the case of mini.

What do I have to read and edit? And where can I find this param.lfs? Thanx in advance dude!

I replies on your other thread in Galaxy Mini General. Try modifying TASS.rle in root folder. I don't know if you need to unpack-then-repack your boot.img though.
Edit :
Since this "TASS.rle" doesn't exist in CM7 update zip file, then it means you do have to unpack your boot.img, open the ramdisk folder then edit the extracted TASS.rle" using image editor or something. I never modified TASS.rle so I don't know exactly how to do it.
If you're using Windows, you can use dsixda kitchen+custom cygwin package+Java Dev Kit to do the unpack+repack. It's somewhere in xda.
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone

Thanx a lot dude! But are you sure it'll work? I'll try it out, but is there any simpler method than this. Some way that I can modify it using my phone itself? By the way are you using cyanogenmod 7.2 RC 3 by squadzone? How is it? Please give the link too... thanx in advance!

Like I said, I never modified TASS.rle so I have no clue if it will work or not. I did unpacked and repacked boot.img several times using dsixda kitchen and they worked.
I don't know if easier method exist, so I only suggest what I know from browsing.
It looks like in order to do what you want, several steps are needed :
1. Unpacking your boot.img into zImage file (kernel) and ramdisk folder.
Anything inside ramdisk.folder will be flashed into your system partition each time you boot your device. Examples are init.rc, default.prop and TASS.rle. You can do whatever you want with these files, say modifiying their contents, but the changes only persist as long as you do not boot your phone, which will restore them back to initial state as I explained above.
2. Converting TASS.rle found inside ramdisk folder into editable format such as PNG
3. Modifying the converted PNG in point 2 (using Photoshop or other app)
4. Re-converting the modified PNG from point 3 back into RLE format
5. Re-packing (compiling) zImage file and ramdisk folder (having modified TASS.rle from point 4) back into boot.img
6. Flashing boot.img from point 5 into your phone.
To make it short, you need to learn how to :
1. Unpack and repack boot.img, which you can do using dsixda kitchen from here : http://forum.xda-developers.com/showthread.php?t=633246
2. Converting RLE to PNG and vice versa. More info here : http://forum.xda-developers.com/showthread.php?p=20128066
3. Flashing boot.img into phone. You can compress your boot.img into TAR (type this in cygwin shell window "tar -cf boot.img.tar boot.img" and flash it using ODIN with one package option or you can create a flashable zip file.
CM 7.2 RC3 works great for me, better than RC2; but that's my personal judgement and there's a chance you will not agree with me after you try it.
Head over to CM 7.2-RC3 by squazone for download link.
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone

@distan
I used Ketut's tools to unpack before...it also had a little something to convert .Rle to raw...only came to my mind now.
Will give this a try tomo.
Shouldn't be that difficult...I think.
And @Nelson
Definitely can't be done in phone.
This is much more than that.

roofrider said:
@distan
I used Ketut's tools to unpack before...it also had a little something to convert .Rle to raw...only came to my mind now.
Will give this a try tomo.
Shouldn't be that difficult...I think.
And @Nelson
Definitely can't be done in phone.
This is much more than that.
Click to expand...
Click to collapse
Nice info buddy, I recall reading his thread too and it's applicable on Galaxy Mini, since both Ace and Galaxy Mini have the same kernel base address and command line parameter (CMIIW).
But I'm not sure if it will work under custom cygwin by dsixda (in case you want to use it under Windows)
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone

distan7 said:
Nice info buddy, I recall reading his thread too and it's applicable on Galaxy Mini, since both Ace and Galaxy Mini have the same kernel base address and command line parameter (CMIIW).
But I'm not sure if it will work under custom cygwin by dsixda (in case you want to use it under Windows)
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone
Click to expand...
Click to collapse
Thanks.
I have Ubuntu on a vm

And for sure ketut's tool will work if you're using a full linux distro
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone

distan7 said:
And for sure ketut's tool will work if you're using a full linux distro
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone
Click to expand...
Click to collapse
Ya...but I didn't try cpio to extract ramdisk..simply clicking it mounted the ramdisk and it's contents were visible...I wonder if I make any change and unmount it will be saved or not?! Then no need to gzip and cpio

Thanx guys! roofrider and distan7 for all your help and support! If I had a bank account, I would have donated by now, but since I don't all I can do is click the thanks button! Thanx a lot dudes!

You're welcome mate
---------------------------------
Sent from my Samsung Galaxy Mini GT-S5570 via xda-dev app
CyanogenMod 7.2.0-RC3-KANG by squadzone

I've attached the tass.rle converted to tass.png thanks to ketut.
but this is only one of the 2 images that appear while booting.
I have to dump the stl6 to find the other i think...but dumping stl5 bricks the phone (stepph) so a little nervous...but i might give it a try.
edit: no harm done.
but stl6 had nothing....anyone got any ideas?
the .jpg or whatever is hidden somewhere, at least that is how it is for galaxy s variants.

[GUIDE] dsixda's Android Kitchen - Now supports GS3 I9300 (Windows/Linux/Mac)

dsixda's Android Kitchen - Now for Samsung Galaxy SIII GT-I9300
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own Samsung Galaxy SIII GT-I9300(T) custom ROMs with the kitchen. This is NOT a guide to help you become Cyanogen or do fancy things with AOSP, but it may be your springboard to bigger things in the future.
Some of you already know about the Android Kitchen. It is a project I started on back in February 2010 to help newbies create their own custom ROMs and learn more about Android. As of the latest versions, you can now create your own Galaxy S3 I9300 ROMs with the kitchen.
NOTE: This guide may also work for other Samsung devices. So if you were told to come here and you have a different device, it was not an error - just make sure you use a base ROM from your own device, not from the I9300! For all other Galaxy S3 variants, this guide might not be exactly the one you're looking for. There may be support for your S3 device in the kitchen, but I'd need to post different instructions. Check the first post of the kitchen thread for any updates for linked instructions.
I'd like to thank klander for testing and providing feedback, which is always appreciated!
[MAIN PAGE] [RELEASE NOTES] [FAQ - page 1] [FAQ - page 2]
​
PROCEDURE FOR MAKING YOUR ROM:
NOTE: If you have a non-I9300 device and were told to follow these instructions, then use a base ROM from that device, NOT a ROM meant for the I9300!! The same steps below, however, (and common sense) should be used.
First, you need a rooted Samsung Galaxy S3 I9300 with a custom recovery menu, which allows flashing of custom ROMs.
Visit the Android Kitchen thread to download the kitchen. Then, follow the link to the FAQ which will show you how to install it on Windows, Linux or Mac OS X. Ensure you read the FAQ carefully.
Put one or more of your base ROM(s) under the original_update folder. For the Samsung Galaxy S3 I9300, there is support for the following formats (that I know of) which can be placed in that folder:
Stock firmware:
system.img, boot.img, cache.img (and optionally: modem.bin)
TAR/ZIP file containing the above. NOTE: If the TAR file name ends with "MD5", remove the MD5 part from the name.
OR Custom ROM:
must be a ZIP file created by the kitchen from the stock firmware (NOTE: The kitchen may NOT support custom ROMs created through other methods such as CyanogenMod, due to potential file structure incompatibility issues)
OR Nandroid backup from custom recovery image:
system.img, cache.img and boot.img
system.ext4.tar, cache.ext4.tar and boot.img
Here are some basic steps to creating your first ROM after you have your base of files under original_update (more options are available in the kitchen):
Start the kitchen with: ./menu
Create a working folder (by choosing your base ROM)
Root your ROM
Add Busybox
Optional: Disable boot sounds
Optional: In the Advanced options menu: De-odex your ROM (your mileage may vary as to whether this works 100%)
Optional: Add or remove the modem.bin from your working folder
Build ROM
The ROM is built into a ZIP file meant for flashing from the custom recovery menu. No Odin. Make a Nandroid backup of your current system before you flash anything!
Some notes:
Just select the defaults whenever you are asked about something in the kitchen and are unsure whether to type 'y' or 'n'.
There are lots of questions answered in the FAQ in Posts 3 and 4 of the main Android Kitchen thread. So please go through that first if you have any issues.
For the benefit of other readers and to prevent confusion, please only discuss the Samsung Galaxy SIII GT-I9300 in this thread!
Most of all, have patience, take your time and enjoy!!

just what i need

I have a de-bloat script if you want a copy to convert to a kitchen script. It's perl calling system values and the kitchen.
Are we still meant to be extracting the img files manually to get them working?

Kangburra said:
I have a de-bloat script if you want a copy to convert to a kitchen script. It's perl calling system values and the kitchen.
Click to expand...
Click to collapse
I'm not doing additional work, but if you'd like you could make a plugin for the kitchen, which would go under the /scripts/plugins folder and can be accessed from the Advanced menu of the kitchen. I can advertise it in the kitchen thread (in the plugins section) as a separate download under your name.
Are we still meant to be extracting the img files manually to get them working?
Click to expand...
Click to collapse
With Cygwin the kitchen will give you instructions on which program to open and how to use it (manually). The programs are found in the kitchen.
With Linux/Mac, it is all automated and very quick.

Just when I thought this kitchen was a goner, you came along and made it work again

I have just put the French zip into the kitchen and it fails to extract the img files.
Available ROMs:
(1) I9300XXDLIH_I9300VFGDLJ1_SFR.zip
Enter selection number (default=1, cancel=0, r=refresh):
Selected I9300XXDLIH_I9300VFGDLJ1_SFR.zip
The new working folder will be named WORKING_101712_171605
Change the name (y/n)? (default: n):
Creating working folder WORKING_101712_171605 ...
Extracting ROM ...
Error: No system folder found!
Press Enter to continue
Click to expand...
Click to collapse
It works after manually extracting so no big deal

Kangburra said:
I have just put the French zip into the kitchen and it fails to extract the img files.
It works after manually extracting so no big deal
Click to expand...
Click to collapse
If the zip contains a tar file then it's not going to work, you need to unzip the tar file.

The best tool for deodex Roms!
THANKS dsixda! :good:
Regards
adesirello (AndyX ROM)

Awesome job mate :good:

tomorrow`s homework !
thanx !

Perfect! Just two days ago i was think at dsixda kitchen! I don`t have enough thanks for this!

Great.
Just what i was looking for.

dsixda said:
dsixda's Android Kitchen - Now for Samsung Galaxy SIII GT-I9300
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own Samsung Galaxy SIII GT-I9300(T) custom ROMs with the kitchen. This is NOT a guide to help you become Cyanogen or do fancy things with AOSP, but it may be your springboard to bigger things in the future.
Some of you already know about the Android Kitchen. It is a project I started on back in February 2010 to help newbies create their own custom ROMs and learn more about Android. As of the latest versions, you can now create your own Galaxy S3 I9300 ROMs with the kitchen.
IMPORTANT: For all other Galaxy S3 variants, this guide may not be exactly the one you're looking for. There may be support for your S3 device in the kitchen, but I'd need to post different instructions. Check the first post of the kitchen thread for any updates for linked instructions.
Click to expand...
Click to collapse
just wanted to let u know that when cooking my rom with ur kitchen, awesome by the way, i was getting constant hang at logo on boot. i went back to the beginning as it worked and booted and just added bit by bit until i found the issue. the issue was adding busybox install run parts. it took me a day to figure this out. i went through kernel to framework and nothing fixed this issue where booting just to logo then stuck. finally deleted working folder, went back to a basic rom, slowly added root, then busybox, deodex etc. i dont know if this issue is specific to just me and my particular build but just putting it out there for others wanting to use this excellent kitchen on their i9305.

L335K1 said:
just wanted to let u know that when cooking my rom with ur kitchen, awesome by the way, i was getting constant hang at logo on boot. i went back to the beginning as it worked and booted and just added bit by bit until i found the issue. the issue was adding busybox install run parts. it took me a day to figure this out. i went through kernel to framework and nothing fixed this issue where booting just to logo then stuck. finally deleted working folder, went back to a basic rom, slowly added root, then busybox, deodex etc. i dont know if this issue is specific to just me and my particular build but just putting it out there for others wanting to use this excellent kitchen on their i9305.
Click to expand...
Click to collapse
Did you create a /system/etc/init.d folder with your custom scripts after enabling the Busybox Run-parts? That option is quite old but I have not seen anyone try or test it with any of the Galaxies. Maybe when you have time next time, do a logcat while it boots and see what the problem is (assuming you had the init.d folder created already). Thanks

dsixda said:
Did you create a /system/etc/init.d folder with your custom scripts after enabling the Busybox Run-parts? That option is quite old but I have not seen anyone try or test it with any of the Galaxies. Maybe when you have time next time, do a logcat while it boots and see what the problem is (assuming you had the init.d folder created already). Thanks
Click to expand...
Click to collapse
yea i created the init.d folder first, (using v29 so it gives u warning anyways), but it still does this. i have to add init.d support manually through my script. but this is awesome, i just gotta remember not to use that feature.. i did both logcat and recovery logs but couldnt make heads or tails of it. it was easier to go back through ur kitchen, add 1 feature at a time until i found the culprit. thanks heaps

Please link to download the kitchen, thank you very much.

misacek said:
Please link to download the kitchen, thank you very much.
Click to expand...
Click to collapse
First post.

This is great!
Thanks dsixda.
YZ.

Please not see me? can give direct link? thank you very much

misacek said:
Please not see me? can give direct link? thank you very much
Click to expand...
Click to collapse
If you refuse to or are unable to read post #1 then you'll have trouble using - and even installing - the kitchen.

[HOWTO] Increase available RAM in ROMs based on "That kernel" and "Those libs"

[HOWTO] Increase available RAM in ROMs based on "That kernel" and "Those libs"
Most Atrix users using ROMs with "That kernel" and "Those libs" are stuck with 778MB or 784MB of available RAM (even after applying the ramfix for international Atrix users), but a few users are reporting getting around 855MB of RAM available on their phones. After a quick comparison of the /proc/cmdline on these phones (and since having more RAM can't hurt), here's a guide how to increase your available RAM on these ROMs. This guide is intended for people who have 778-784MB available on their phone when using ROMs based on "That kernel" and "Those libs" with the original ramfix. DO NOT USE ON OTHER ROMS!
WARNING: STOP NOW AND DO NOT FLASH IF YOU DON'T KNOW WHAT YOU'RE DOING!!!
PLEASE READ AND UNDERSTAND EVERYTHING BEFORE YOU DO ANYTHING!
I have personally tested this with Somebody's CM10 and AtrICS v2.
It should theoretically work with other ROMs based on "That kernel" and "Those libs", but use it at your own risk!
Now, on to the good part:
1. Get your current /proc/cmdline.
You can do this by using terminal emulator and typing:
su
cat /proc/cmdline
Click to expand...
Click to collapse
or by using a root browser and copy your /proc/cmdline to your sdcard.
A note from NFHimself:
NFHimself said:
Hi,
Please emphasize that the script needs YOUR complete /proc.cmdline in there, from a working phone adb session, not recovery adb session as the recovery has it's own possible /proc/cmdline via a different kernel, etc. You are not just editing the mem=?? stuff.
What would be best is to first create a zip that is plain jane what your /proc/cmdline is or one that uses setcmdline with a blank argument or "". That way you can reset to default in case of errors. Or you can just fastboot flash your boot partition, no need for an sbf.
Cheers!
Click to expand...
Click to collapse
2. Download attached file.
3. Edit the updater-script file in the zip.
Extract the zip and find META-INF\com\google\android\updater-script
Windows users: Edit the file using Notepad. DO NOT USE WORDPAD. WordPad changes the Unix-style CR to Windows style CR-LF, which may cause problems.
Once you open the file, find this in the file:
run_program("/tmp/setcmdline", "[email protected] [email protected] [email protected] vmalloc=256M video=tegrafb console=null usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=mbr:d00:100:800,kpanic:2100:400:800 security=tomoyo mot_prod=1 androidboot.serialno=XXXXX00000");
Click to expand...
Click to collapse
Change the red part with your own cmdline, which you got in step 1. Take care especially on the tegrapart and androidboot.serialno parameters. DO NOT USE A TEGRAPART AND/OR SERIAL NUMBER FROM ANOTHER PHONE!
If your original cmdline that you got in step one was:
[email protected] [email protected] [email protected] vmalloc=320M video=tegrafb console=null usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=mbr:1100:100:800,kpanic:2500:400:800 security=tomoyo mot_prod=1 androidboot.serialno=12345ABCDE
Click to expand...
Click to collapse
then you should modify the part of the updater-script mentioned above to look like this:
run_program("/tmp/setcmdline", "[email protected] [email protected] [email protected] vmalloc=256M video=tegrafb console=null usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=mbr:1100:100:800,kpanic:2500:400:800 security=tomoyo mot_prod=1 androidboot.serialno=12345ABCDE"
Click to expand...
Click to collapse
Only the change the red part in the script with the red part in your original cmdline. DO NOT MODIFY ANYTHING ELSE!
4. Save the file, and repack the zip.
5. Flash zip.
6. You should now have 855MB of RAM available. Enjoy your extra 70+MB of RAM.
WARNING: DO NOT FLASH IF YOU DON'T KNOW WHAT YOU'RE DOING!!!
I AM NOT RESPONSIBLE FOR ANYTHING THAT GOES WRONG BECAUSE OF YOU BORKING YOUR CMDLINE!!!
Thanks to: NFHimself for creating the ramfix binary and Ilkinansr92 for his cmdline.

Thanks!!! I will givi it a try.
Edit: Working just fine....thanks again!
from the (m)ATRIX...

Thanks!
Now i have 855mb of RAM available

I have 815mb of ram available and i am using Nottachtrix Rom, i am going to try this method in 2 mins and i will give feedback..
Edit:
it gives me error which number 6 (my rom is working, no problem). i know nottachtirx is not based on that kernel but i had wanted to try it whether work or not.

ramanujan20 said:
I have 815mb of ram available and i am using Nottachtrix Rom, i am going to try this method in 2 mins and i will give feedback..
Edit:
it gives me error which number 6 (my rom is working, no problem). i know nottachtirx is not based on that kernel but i had wanted to try it whether work or not.
Click to expand...
Click to collapse
I got that error too....on JB...but that was because I was doing something wrong.
But I think this is for JB...

Cocolopes said:
I got that error too....on JB...but that was because I was doing something wrong.
But I think this is for JB...
Click to expand...
Click to collapse
are you using something related to "that rom"? (kernel, libs, rom)

jhonnyx said:
are you using something related to "that rom"? (kernel, libs, rom)
Click to expand...
Click to collapse
No...someones Cm10 here...but now is working...I just replace the update script in the zip...and work perfect
from the (m)ATRIX...

successful
oh yeah~
now i have 855mb ram now!
i found that you can copy the file /proc/cmdline to computer,and select the words you need
in this way,you can do it more simple and more safe!

Well. 855 MB RAM. I am using CM10 with that libs.
Thank a lot.

Cocolopes said:
No...someones Cm10 here...but now is working...I just replace the update script in the zip...and work perfect
from the (m)ATRIX...
Click to expand...
Click to collapse
Well, "Somebody's" CM10 IS using the kernel & libs from "That ROM", so I'd say it's very much related.

Can anybody help me i don't even have 500 mb in manage apps - running apps section
International user and using MRom
Sent from Otterbox Atrix 4G Rockz

ranjithkumar1201 said:
Can anybody help me i don't even have 500 mb in manage apps - running apps section
International user and using MRom
Sent from Otterbox Atrix 4G Rockz
Click to expand...
Click to collapse
Have you applied the ramfix? If not download this and apply it and it will fix that problem:
http://forum.xda-developers.com/attachment.php?attachmentid=710806&d=1315237274

Perfect. Thanks !

I hope the OP doesn't mind...
Here's my take on this. I took the source of the cmdline utility and improved it greatly, now it's almost a full-featured kernel cmdline editor. Then I used this new utility in the update script to dynamically edit the system cmdline.
Bottom line: this ZIP should work on all systems without any modifications.
WARNING: not fully tested, use at your own risk!
(If anything goes wrong, it should be easily revertable simply by reflashing the kernel, either from recovery or via fastboot.)
EDIT: added a couple more options, recompiled the cmdline binary and repackaged the ZIP.

ravilov said:
I hope the OP doesn't mind...
Here's my take on this. I took the source of the cmdline utility and improved it greatly, now it's almost a full-featured kernel cmdline editor. Then I used this new utility in the update script to dynamically edit the system cmdline.
Bottom line: this ZIP should work on all systems without any modifications.
WARNING: not fully tested, use at your own risk!
(If anything goes wrong, it should be easily revertable simply by reflashing the kernel, either from recovery or via fastboot.)
EDIT: added a couple more options, recompiled the cmdline binary and repackaged the ZIP.
Click to expand...
Click to collapse
Works beautifully on someone's cm10! Big thanks.
Sent from my MB860

ravilov said:
I hope the OP doesn't mind...
Here's my take on this. I took the source of the cmdline utility and improved it greatly, now it's almost a full-featured kernel cmdline editor. Then I used this new utility in the update script to dynamically edit the system cmdline.
Bottom line: this ZIP should work on all systems without any modifications.
WARNING: not fully tested, use at your own risk!
(If anything goes wrong, it should be easily revertable simply by reflashing the kernel, either from recovery or via fastboot.)
EDIT: added a couple more options, recompiled the cmdline binary and repackaged the ZIP.
Click to expand...
Click to collapse
sorry for ask but i don't get it this is a script to modify the cmdline or is an auto modify tool for the cmdline?

Maibol said:
sorry for ask but i don't get it this is a script to modify the cmdline or is an auto modify tool for the cmdline?
Click to expand...
Click to collapse
Both actually.
It includes a tool that can modify the cmdline, and a script that does modify the cmdline automatically, by utilizing the tool.

ravilov said:
Both actually.
It includes a tool that can modify the cmdline, and a script that does modify the cmdline automatically, by utilizing the tool.
Click to expand...
Click to collapse
thanks nice tool i gon give it a try

Why so some Atrixes have 815 MB RAM and some others 879 MB ?
And ravilov, does your script work on gingerbread ROMs, too?
Sent from my CM7 powered Atrix using TapaTalk \o/

the.cybot said:
And ravilov, does your script work on gingerbread ROMs, too?
Click to expand...
Click to collapse
Actually, I'm not sure. It doesn't seem to work for me. The boot image gets updated correctly but for some reason the new cmdline is not used when the kernel boots. I'm using MROM, latest release. Maybe it works different on another ROM. Maybe this whole cmdline business is specific to stock kernels only. Needs more research.