Hello,
This is AnyKernel for Optimus 4X HD. What it does is that you can now flash any kernel on top of a rom without having to worry about the ramdisk.
It will extract your current ramdisk and replace only the zImage, aka kernel image, and modules.
Original development by koush. I just modified it to work well on our device.
I upload the 4 most used kernels used right now for p880. Kernel developers can update their topics also and use this for their future builds.
All credits go to the original kernel developers.
As usual you flash through CWM, TWRP,
Download
Enjoy!
XDA:DevDB Information
AnyKernel for Optimus 4X HD, a Tool/Utility for the LG Optimus 4X HD
Contributors
ezet
Version Information
Status: Stable
Stable Release Date: 2013-10-16
Created 2013-10-16
Last Updated 2013-10-16
thnks dude you're awasome..
Maybe i stupid question but i don't understand.
With this thing we can flash a 4.2.2 kernel on 4.3 Rom or we can flash a kernel for special pac man on normal aokp?
Sent from my LG-P880 using xda premium
Nemeziz 56th said:
Maybe i stupid question but i don't understand.
With this thing we can flash a 4.2.2 kernel on 4.3 Rom or we can flash a kernel for special pac man on normal aokp?
Sent from my LG-P880 using xda premium
Click to expand...
Click to collapse
You can flash on top of any rom yes. 4.3 kernel has the selinux modules included but atm it won't make any real life difference having them or not. From these kernels only optimus prime i think doesn't support selinux.
Στάλθηκε από το LG-P880 μου χρησιμοποιώντας Tapatalk 2
@ezet
We can flash those kernels (4 uploaded kernels) over any rom.
Developers need to include this feature on their own for new updates:silly:.Am i getting it wrong?
m.heydari2016 said:
@ezet
We can flash those kernels (4 uploaded kernels) over any rom.
Developers need to include this feature on their own for new updates:silly:.Am i getting it wrong?
Click to expand...
Click to collapse
You are getting it right.
Hello
Will work in MIUI V5?
Thx
chevellemendes said:
Hello
Will work in MIUI V5?
Thx
Click to expand...
Click to collapse
AnyKernel as in any ROM. So yes it will work in MIUI and any other ROM for Optimus 4x.
Sweet, time to go kernel-crazy!
Hi nice project, but i dont know if it is work in stock rom and if can i use with the multirom. Thanks for sharing by the way!
Iodak kernel does not work properly on ProBam. Unknown IP address, MAC address unknown, WiFi does not work.
Thanks
Best regards
varadinum said:
Iodak kernel does not work properly on ProBam. Unknown IP address, MAC address unknown, WiFi does not work.
Thanks
Best regards
Click to expand...
Click to collapse
+1, but with MIUI V5
varadinum said:
Iodak kernel does not work properly on ProBam. Unknown IP address, MAC address unknown, WiFi does not work.
Thanks
Best regards
Click to expand...
Click to collapse
chevellemendes said:
+1, but with MIUI V5
Click to expand...
Click to collapse
Thx for the report. It appears i've messed up a with with iodak packing.
Please download it again i've put up an updated version of v8 and v8.5 it should now work fine.
Yeah! Iodak kernel works. You did it.
Best regards
iodak´s v8.5 kernel works well on stock rom. I´m on Zaiben´s latest version.
Thanks
---------- Post added at 05:07 PM ---------- Previous post was at 05:00 PM ----------
Can you do this with Optimus Prime V2.7 kernel? Not the version of TheFerhatKing of course. His version has problems on bluetooth. Maybe directly from the source the problem is solved if that is the problem of course.
Thanks.
Many thanks, seems to be a good idea!!!
If have 2 hints for it atm:
1. Iodak uses settings in Ramdisk for his kernel. If we repack his kernel simply with a ramdisk for a Rom, his kernel wont work completely right. Tried to repack IodakV8 for PAC-MAN Rom and got problems with cpuquiet. So I wrote Iodak and thats his answer: http://forum.xda-developers.com/showpost.php?p=46495910&postcount=1243
I think, if a kernel is developed this way (with changes in ramdisk), AnyKernel wont work...
2. Some of us use MultiRom. For MultiRom its necessary, a command in updater-script have be be in one line (not break into more lines). Also it have to change the mountpoints, it cant write secondary rom to same "system" as primary. So hardcoded mountpoints (especialy for system) wont work.
May be the updater-script could look like this (MultiRom does some code-interpreting for mountpoints, but I´m really not sure how to change!):
Code:
assert(getprop("ro.product.device") == "p880" || getprop("ro.build.product") == "p880");
ui_print("XXX kernel for Optimus 4X HD P880");
set_progress(1.000000);
ui_print("");
ui_print("AnyKernel Updater by Koush.");
ui_print("");
ui_print("Installing kernel...");
#mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system");
run_program("/sbin/busybox", "mount", "/system");
package_extract_dir("system", "/system");
unmount("/system");
package_extract_dir("kernel", "/tmp");
set_perm(0, 0, 0777, "/tmp/mkbootimg.sh");
set_perm(0, 0, 0777, "/tmp/mkbootimg");
set_perm(0, 0, 0777, "/tmp/unpackbootimg");
set_perm(0, 0, 0777, "/tmp/busybox");
set_perm(0, 0, 0777, "/tmp/unpack_add_init.sh");
#run_program("/sbin/busybox", "dd", "if=/dev/block/platform/sdhci-tegra.3/by-name/LNX", "of=/tmp/boot.img");
run_program("/sbin/busybox", "dd", "if=/dev/block/mmcblk0p2", "of=/tmp/boot.img");
run_program("/tmp/unpackbootimg", "-i", "/tmp/boot.img", "-o", "/tmp/");
run_program("/tmp/mkbootimg.sh");
run_program("/sbin/busybox", "dd", "if=/tmp/newboot.img", "of=/dev/block/mmcblk0p2");
ui_print("");
ui_print("Done!");
Also I´m not sure if we could use "dd" in MultiRom updater-script or if we need to use another command for copying the files...
Bogeyof said:
Many thanks, seems to be a good idea!!!
If have 2 hints for it atm:
1. Iodak uses settings in Ramdisk for his kernel. If we repack his kernel simply with a ramdisk for a Rom, his kernel wont work completely right. Tried to repack IodakV8 for PAC-MAN Rom and got problems with cpuquiet. So I wrote Iodak and thats his answer: http://forum.xda-developers.com/showpost.php?p=46495910&postcount=1243
I think, if a kernel is developed this way (with changes in ramdisk), AnyKernel wont work...
2. Some of us use MultiRom. For MultiRom its necessary, a command in updater-script have be be in one line (not break into more lines). Also it have to change the mountpoints, it cant write secondary rom to same "system" as primary. So hardcoded mountpoints (especialy for system) wont work.
May be the updater-script could look like this (MultiRom does some code-interpreting for mountpoints, but I´m really not sure how to change!):
Code:
assert(getprop("ro.product.device") == "p880" || getprop("ro.build.product") == "p880");
ui_print("XXX kernel for Optimus 4X HD P880");
set_progress(1.000000);
ui_print("");
ui_print("AnyKernel Updater by Koush.");
ui_print("");
ui_print("Installing kernel...");
#mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system");
run_program("/sbin/busybox", "mount", "/system");
package_extract_dir("system", "/system");
unmount("/system");
package_extract_dir("kernel", "/tmp");
set_perm(0, 0, 0777, "/tmp/mkbootimg.sh");
set_perm(0, 0, 0777, "/tmp/mkbootimg");
set_perm(0, 0, 0777, "/tmp/unpackbootimg");
set_perm(0, 0, 0777, "/tmp/busybox");
set_perm(0, 0, 0777, "/tmp/unpack_add_init.sh");
#run_program("/sbin/busybox", "dd", "if=/dev/block/platform/sdhci-tegra.3/by-name/LNX", "of=/tmp/boot.img");
run_program("/sbin/busybox", "dd", "if=/dev/block/mmcblk0p2", "of=/tmp/boot.img");
run_program("/tmp/unpackbootimg", "-i", "/tmp/boot.img", "-o", "/tmp/");
run_program("/tmp/mkbootimg.sh");
run_program("/sbin/busybox", "dd", "if=/tmp/newboot.img", "of=/dev/block/mmcblk0p2");
ui_print("");
ui_print("Done!");
Also I´m not sure if we could use "dd" in MultiRom updater-script or if we need to use another command for copying the files...
Click to expand...
Click to collapse
For 1 there are two options. Either hardcode the settings at kernel config or include an init script that does the job. Either way there are options to make a kernel universal without having to deal with the ramdisk.
For the 2nd one it should work the same way yes. You can try it on MultiBoot and report if it's working or not, me personally i don't use multiboot at all so can't test it atm.
ezet said:
For 1 there are two options. Either hardcode the settings at kernel config or include an init script that does the job. Either way there are options to make a kernel universal without having to deal with the ramdisk.
For the 2nd one it should work the same way yes. You can try it on MultiBoot and report if it's working or not, me personally i don't use multiboot at all so can't test it atm.
Click to expand...
Click to collapse
Thanks! I know there are options, I only want to say, there could be problems like IodakV8. The developer of the kernel should solve it, I´m not the developer...
For MultiRom it seems u cant use "dd". So I would have to modify the "dd" which reads the boot.img and the "dd" which writes the repacked boot.img. But I dont know how, cause I´m not familiar with the necessary commands. What commands I could use instead "dd", what do u think?
Does iodak have v8.5?
i can just see v8.0 now at their site
ezet said:
Hello,
This is AnyKernel for Optimus 4X HD. What it does is that you can now flash any kernel on top of a rom without having to worry about the ramdisk.
It will extract your current ramdisk and replace only the zImage, aka kernel image, and modules.
Original development by koush. I just modified it to work well on our device.
I upload the 4 most used kernels used right now for p880. Kernel developers can update their topics also and use this for their future builds.
All credits go to the original kernel developers.
As usual you flash through CWM, TWRP,
Download
Enjoy!
XDA:DevDB Information
AnyKernel for Optimus 4X HD, a Tool/Utility for the LG Optimus 4X HD
Contributors
ezet
Version Information
Status: Stable
Stable Release Date: 2013-10-16
Created 2013-10-16
Last Updated 2013-10-16
Click to expand...
Click to collapse
Bogeyof said:
Thanks! I know there are options, I only want to say, there could be problems like IodakV8. The developer of the kernel should solve it, I´m not the developer...
For MultiRom it seems u cant use "dd". So I would have to modify the "dd" which reads the boot.img and the "dd" which writes the repacked boot.img. But I dont know how, cause I´m not familiar with the necessary commands. What commands I could use instead "dd", what do u think?
Click to expand...
Click to collapse
What error does dd give you? You can try using the included dump_image. It didn't work for me at first place but you can check it for yourself too i didn't go any further with it since dd did the trick for me.
Related
Hello all. Jdfroyo is a free community based distro of HTC Sense ROMs for the Droid Incredible. My Main goal was to bring the community a fast, yet very polished rom based off HTC Leaks and official releases for the EVO and Incredible.
This ROM is based off of the Official OTA for the Inc. It is deodexed, zipaligned, and all bloat is removed, yet the rom still features the very handsome Sense-UI interface by HTC.
Sense Version includes:
1. Deodexed
2. Zialigned
3. Most bloat removed
4. VERY FAST!!!!!
5. Can be stably overclocked to 1.2 ghz !!!!
6. Can be used with HYdra or KING Kernels.
Bloat Removed:
Mode 10 and Magic smoke livewallpaper
VZNav
Footprints
MyVerizon
Footprints Widget
VisualVoicemail
Amazon MP3
Vanilla Version:
All Sense Bloat removed- including weather, clockwidget, and Rosie!
Themed vanilla
General Changelog:
9/7 update- added buildprop edit so wifi scans every 2 mins, removed oj wake
RC3- fixed boot.img problem and temed vanilla ROM
v2.5- inital revival of jdfroyo
Link: Downloads - MOD Edit: Links Removed
FAQ:
Q. Why should I flash your ROM? There are others just as good.
A. The jdfroyo project aims to provide a very customized rom that most usere will like. It is stble, fast and not buggy.
Q. You had some boot.img bugs in previous bugs. Is that dangerous?
A. The boot.img contains the kernel and ramdisc, so the boot.img bug did cause severe overheating, and couldnt mount emmc, but that bug was cleared up in RC3, so no worries (actuaslly i replaced the whole boot.img)
Q. Does this give me root?
A. If you flash a coustom recovery after flashing the RUU (and have S_off) Then it gives you SU perms again, but not for anyone who wasnt previously rooted before.
Q. Are there any specific risks in flashing this
A. THere are potential risks in flashing ANY rom (even the ruu). This rom was tested and proven that it is ok for day to day use and will not brick.
Q. What is this based off?
A. The newer versions (2.5 and up) are based on the offical 2.2 release, and versions before v2.5 is based on the old 7/27 leak.
Q. Why dont you have screen shots up? We have only been asking you for weeks.
A. I am putting up some screens tonight. They will be here and on my site.
Q. What is your site?
A. check my sig (and no i am not trying to website spam)
Q. What is required before flashing this ROM?
A. S_OFF, custom recovery (Clockwork or AMON_RA) the 2.15 radio and 92hboot.
Q. Where can i find the things you mentioned in the previous answer?
A. 1.SOFF: www.unrevoked.com/forever
2. Closkwork or Amon ra: Clockwork can be found on unrevoked.com/forever , Amon can be found floating around on XDA
3. 92 hboot and 2.15 radio: can be found on adrynalyne's site
PLEASE eNJOY MY ROM!!!!!!!!!!!!!!!!!!!!!!
Isn't this the same thing as before?
Sent from my HTC Incredible
no it has various fixes, mostly the wifi fix....and for the sense version, i ixed the buildprop whaer ot said jdfroyo vanilla....it is very different from the version that i posted here last eek, but if you followed me on AF, then this is a bit similar
I thought you said you were done developing for the incredible.
I mean, I couldn't care less... just wondering why you decided to come back after two times of saying it.
And stable at 1.2.... hmm. I'd like this to be tested by others before I try this.
Hehe
Sent from my ADR6300 using XDA App
Lcsglvr said:
I thought you said you were done developing for the incredible.
I mean, I couldn't care less... just wondering why you decided to come back after two times of saying it.
And stable at 1.2.... hmm. I'd like this to be tested by others. Hehe
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Its hard to stay away
Link isn't working.
try it now
I don't think anybody likes you
Sent from my ADR6300 using XDA App
theguitarguy58 said:
I don't think anybody likes you
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
its not about liking me, its about liking my rom
jdkoreclipse said:
its not about liking me, its about liking my rom
Click to expand...
Click to collapse
I don't think anybody likes your rom.
Sent from my ADR6300 using XDA App
Touche...let's get back in topic
theguitarguy58 said:
I don't think anybody likes your rom.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Sent from my ADR6300 using XDA App
Is it just me, or do you always come out with a new version of *cough* a rom with almost the same name and number as skyraider. I guess it's like"the distinguished gentleman", if you have a familiar name, people will vote. At least make some attempt to be different so no one accidentally downloads this crap. How about POS ROM VERSION, oh hell, does it really matter?
And you use the same bull**** op almost every time. "Sorry no screens or info, just check my website, but I'm not spamming my website, and if it doesn't work, use other peoples fixes who I'll give no credit to ever never, but my rom is prefect and full of awesome." Give it a rest bud.
So this STILL isn't posted with the guidelines laid out by the moderators... do you ever learn?
http://forum.xda-developers.com/showpost.php?p=7885067&postcount=30
Berzerker7 said:
So this STILL isn't posted with the guidelines laid out by the moderators... do you ever learn?
http://forum.xda-developers.com/showpost.php?p=7885067&postcount=30
Click to expand...
Click to collapse
He's gotta be a relative or something right?
Berzerker7 said:
So this STILL isn't posted with the guidelines laid out by the moderators... do you ever learn?
http://forum.xda-developers.com/showpost.php?p=7885067&postcount=30
Click to expand...
Click to collapse
screenshots are in the first post!!!!!!!!!111
theguitarguy58 said:
I don't think anybody likes your rom.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I don't know the story since I just joined a few weeks ago but that made me laugh, thanks ! great wit sir!
Sent from my ADR6300 using XDA App
jdkoreclipse said:
screenshots are in the first post!!!!!!!!!111
Click to expand...
Click to collapse
I have to tell skyraider that my pinch to zoom isn't working with his rom, cuz those screens must be hella small.
Rather than continuing to have to discuss what is obvious to us all, let's try the objective approach with this. I downloaded jdfroyo Sense (for comedic value, honestly) and opened up the updater-script.
Going through this in sequence (I did not change the ordering):
So far so good.
Code:
format("MTD", "system");
mount("MTD", "system", "/system");
Deleting files on a freshly formatted filesystem. What's supposed to be there?
Code:
delete_recursive("/system/etc/init.d");
delete("/system/xbin/a2sd");
delete("/system/xbin/apps2sd");
delete("/system/xbin/e2fsck");
Data isn't mounted, but delete operations are running, on /data.
Code:
delete_recursive("/data/dalvik-cache");
delete_recursive("/data/boot-cache/");
delete_recursive("/data/a2sd/");
delete("/data/.dalvikcache");
delete("/data/dta2sd.log");
Runs a script against /data, which still isn't mounted. Then extracts the contents of his zip to it. Into the void.
Code:
run_program("check_data_app");
package_extract_dir("data", "/data");
set_perm(0, 0, 0777, "/data/dalvik-cache");
Deleting more files on a newly formatted volume.
Code:
delete("/system/xbin/busybox");
delete_recursive("/system/xbin");
Oh, now we'll put some files on system. Since we've formatted it and deleted files which weren't there.
Code:
package_extract_dir("system", "/system");
I could go on but I think the point is clear. He's either not reading his updater-script, doesn't understand any of it or both. I'm going with both. So yeah, download at your own risk.
Still using evo framework?
Hey does anyone know what the artifact is in the middle of the 3rd screenshot?
Since I don't have much time to keep on updating my BlendMIUI so I decided to writte a program to give you guys the chance to build BlendMIUI for your own with latest MIUI sources in just few minutes!
Q:What is BlendMIUI Speed-Porting Software For XPERIA 2011
Ans:This is a short program trying to help you guys to build your own BlendMIUI rom for Xperia 2011 in just few minutes.
Q:How to use it?
Unlock Bootloader first!
1.Download BMSPS(BlendMIUI Speed-Porting Software) then unpack it to anywhere you like(Windows environment).Btw,you should install JAVA SE JRE first or it won't works because it needs JAVA environment to sign the rom.You can goto oracle.com/java to download the latest Java SE JRE.
2.Download latest MIUI rom for Desire HD from miui.us(or anywhere you want).
3.Rename the rom you just downloaded as MIUI.zip then put it into BMSPS/MIUI_DHD_ROM directory.(Do not rename it as MIUI.zip.zip!)
4.Run BMSPS_luancher.exe to start.
5.Do as follows then it will automatically create update.zip under the BMSPS directory.
Then you have two choices:
=>Help youself:
6.Put the update.zip rom to your SD-card.
7.Flash BlendMIUI kernel(I have put it into \BlendMIUI-kernel directory) or DooMKernel for MIUI.
8.Use CWM-recovery to flash the update.zip rom.
=>Use Auto-Flash Function
You don't need to do anything on your phone,it will help you to do all works automatically and boot into the new system!
Features:
1.Support Devices: Xperia Arc,Xperia Arc S,Xperia NEO,Xperia NEO V,Xperia Ray.
2.Latest CM7.2.0 rebuilted sources as base.
3.Automatically port MIUI for your device then output unpdate.zip and sign the rom to let you flash it into your device directly.
4.Your choice Function (addons)
5.Fully working Auto-Flash Function
P.S: CM7 sources and kernel for XPERIA RAY are come from bheremans.
Changelog for Version 02:
1.Add moded Packageinstall to let you chose where you would like to install your apps including SD-card.
2.Fixed function to remind you to install java-jre if update.zip is not created.
3.Small changes.
Changelog for Version 03:
1.Fixed PackageInstaller and Torch FC problem when using the ROM from www.miui.com as base.
2.Automatically recognize MIUI version (Depends on the MIUI rom you use) and change Build version for porting rom.
3.Add "Your Choice" function to help you customize your own BlendMIUI rom(BlendUI,DSPManager,Tweaks,Audios from SE).
4.[For DEVs] Whole-New Source code:More easy to read,more easy to add new language(I mean the BMSPS itself) and new functions.
Changelog for Version 04:
1.Disable echoing information for better display.
2.Fixes and improve performance of BMSPS.
3.Add "Auto-Flash" function to help you flash BlendMIUI automatically
Changelog for Version 04.3:
1.Add Xperia Ray ST18i support(All sources for Xperia Ray are come from bheremans).
2.Fixed Auto-Flash function.
3.Fixed ADB Detective bug which cause the software stuck at entering into Auto-Flash function when you input "yes".
Changelog for Version 04.7:
1.Add Xperia Neo V support.
2.Fully working Auto-Flash function (You don't need to do anything on your phone now until it boots into the new system.BMSPS will help you to do everything automatically.)
3.Some small changes
WARNING:This is not an update-package and you'd better delete all old files if you have installed early version of BMSPS.
Make sure you have unlocked bootloader before using this tool.Baseband 56 is recommanded.
Download links:
BMSPS V04.7: http://www.mediafire.com/?4xxna5rim6txmmn
Latest Source Code @ github.com/JasonStein
[Credit]
Bheremans,Eamars,FXP,DooMloRd,enzo...
Please report bugs with screenshots!
Great...!!!
Only one question...!!! What about the kernel...???
great tool !
Now everyone can make his own personal miUI !
thanks man
adiktz said:
Great...!!!
Only one question...!!! What about the kernel...???
Click to expand...
Click to collapse
here is what he said for the kernel.
7.Flash BlendMIUI kernel(I have put it into \BlendMIUI-kernel directory) or DooMKernel for MIUI.
Click to expand...
Click to collapse
Sounds so cool! thanks
Just tried it for 1.11.18 and it works perfectly, a million thanks!
EDIT:
Because I'm lazy and I don't wanna boot into Win7 each time (I just have it for gaming), I compiled the BMSPS_launcher for use on my Fedora installation. I thought I'd upload it here, if anyone else using Linux wants to give it a try.
You just need the zip and unzip packages installed, in addition to the pre-requisites mentioned by Jason.
I attached the modified source file and the binaries for 32 and 64-bit installations.
@Jason: I hope this is fine with you. If not, let me know and I'll remove them. Thanks again for all your work.
Wow! So nice of you guy.
Sent from my LT15i using XDA App
crimilde said:
Just tried it for 1.11.18 and it works perfectly, a million thanks!
EDIT:
Because I'm lazy and I don't wanna boot into Win7 each time (I just have it for gaming), I compiled the BMSPS_launcher for use on my Fedora installation. I thought I'd upload it here, if anyone else using Linux wants to give it a try.
You just need the zip and unzip packages installed, in addition to the pre-requisites mentioned by Jason.
I attached the modified source file and the binaries for 32 and 64-bit installations.
@Jason: I hope this is fine with you. If not, let me know and I'll remove them. Thanks again for all your work.
Click to expand...
Click to collapse
Sure,go ahead,it would be much convenient to Linux users.
Btw I have updated my latest sources on github and I will keep on adding more functions to BMSPS.
crimilde said:
Just tried it for 1.11.18 and it works perfectly, a million thanks!
EDIT:
Because I'm lazy and I don't wanna boot into Win7 each time (I just have it for gaming), I compiled the BMSPS_launcher for use on my Fedora installation. I thought I'd upload it here, if anyone else using Linux wants to give it a try.
You just need the zip and unzip packages installed, in addition to the pre-requisites mentioned by Jason.
I attached the modified source file and the binaries for 32 and 64-bit installations.
@Jason: I hope this is fine with you. If not, let me know and I'll remove them. Thanks again for all your work.
Click to expand...
Click to collapse
Btw you can compiled it for Linux and pack whole things into an package like what I did and give me the download link so that I can attach it to my post.
crimilde said:
Just tried it for 1.11.18 and it works perfectly, a million thanks!
EDIT:
Because I'm lazy and I don't wanna boot into Win7 each time (I just have it for gaming), I compiled the BMSPS_launcher for use on my Fedora installation. I thought I'd upload it here, if anyone else using Linux wants to give it a try.
You just need the zip and unzip packages installed, in addition to the pre-requisites mentioned by Jason.
I attached the modified source file and the binaries for 32 and 64-bit installations.
@Jason: I hope this is fine with you. If not, let me know and I'll remove them. Thanks again for all your work.
Click to expand...
Click to collapse
I have checked your file,there is a mistake:
Code:
if( Device==1 )
{
chdir("DATA/LT15i/");
system("zip -r -u ../../temp.zip *");
}
should be:
Code:
if( Device==1 || Device==2)
{
chdir("DATA/LT15i/");
system("zip -r -u ../../temp.zip *");
}
Cuz LT15i & LT18i share most files
WOW really thanks i just updated my BlendMIUI it works like a charm !
thank you soo much
Edit: Thanks for adding DSPManager !! ^_^
it works soo great on my ARC !!
JasonStein said:
I have checked your file,there is a mistake:
Code:
if( Device==1 )
{
chdir("DATA/LT15i/");
system("zip -r -u ../../temp.zip *");
}
should be:
Code:
if( Device==1 || Device==2)
{
chdir("DATA/LT15i/");
system("zip -r -u ../../temp.zip *");
}
Cuz LT15i & LT18i share most files
Click to expand...
Click to collapse
Ooops, you're right, I must've deleted it by mistake. Thanks for pointing it out!
I'll recompile the thing tomorrow morning and send you the package.
Sent from my LT15i using xda premium
Is there any way to edit this rom to something we want like which APKS are installed and default launcher that kinda stuff?
this is great. it would be accelent if i could chose the language that i whant to install instead of english(not in the cmd window, but for the ROM itself).
can you make a feature for this? only then you will not only be A king you will be THE king.
@Jason: Ok so I've compiled the v2 you posted for Linux 32bit/64bit and archived the whole thing:
EDIT: Reuploaded
http://www.mediafire.com/?9uemvociipaopnn
PS - the source code is attached to the post for your reference. I commented out the Windows-specific lines (instead of deleting them) and put the Linux version below for an easier comparison.
Just one thing, I noticed that even if the update.zip was properly signed and created, the program would still display "5. Failed!" but then clear the screen and show that update.zip was successfully created...
I added an extra condition like below in the Show_Progress function and now it's fine:
Code:
if( i==5 && Step==5 && Out_Check()==0 ) printf("Failed!\n");
crimilde said:
@Jason: Ok so I've compiled the v2 you posted for Linux 32bit/64bit and archived the whole thing:
http://www.mediafire.com/?8vz0xxpyq69afo3
PS - the source code is attached to the post for your reference. I commented out the Windows-specific lines (instead of deleting them) and put the Linux version below for an easier comparison.
Just one thing, I noticed that even if the update.zip was properly signed and created, the program would still display "5. Failed!" but then clear the screen and show that update.zip was successfully created...
I added an extra condition like below in the Show_Progress function and now it's fine:
Code:
if( i==5 && Step==5 && Out_Check()==0 ) printf("Failed!\n");
Click to expand...
Click to collapse
Yes,I made a little mistake:
Code:
void Sign_Rom()
{
Show_Progress(4);
system("java -jar signapk.jar testkey.x509.pem testkey.pk8 temp.zip update.zip");
system("del temp.zip");
Show_Progress(5); // Delete this line!!!
}
Code:
Show_Progress(5);
shouldn't be there.Just remove this line and it will be fine.
I will keep on updating my source code to add more useful functions to give you more choices and let it become not only a speed-porting software but also an MIUI rom customization tool.The early version of BMSPS is quite short with some basic functions and it's not written in a standard way.I'm going to do some changes and if you like to contribute to it,you can always fork my source code and add your own things including some useful functions and I will be appreciate.
P.S:
I will release next version of BMSPS with some useful functions before MIUI 1.11.25 released.
JasonStein said:
Yes,I made a little mistake:
Code:
void Sign_Rom()
{
Show_Progress(4);
system("java -jar signapk.jar testkey.x509.pem testkey.pk8 temp.zip update.zip");
system("del temp.zip");
Show_Progress(5); // Delete this line!!!
}
Code:
Show_Progress(5);
shouldn't be there.Just remove this line and it will be fine.
Click to expand...
Click to collapse
Yeah, you're right, it's better to just remove that line instead of adding an extra condition. I'm reuploading now and I'll update the link in my post above once it's done.
crimilde said:
Yeah, you're right, it's better to just remove that line instead of adding an extra condition. I'm reuploading now and I'll update the link in my post above once it's done.
Click to expand...
Click to collapse
And it's done.
Thanks. Updated the MIUI to the latest version. This is so awesome
Hi there!!!
I noticed that there lot's of user's complaining about error in selecting network. So, here i present you the ril files pulled from old an nightly which had a working netwok selection.
This is probably not for FUNNY SIM'S!!!
Patch
http://db.tt/ZOoEGNB5
Undo-Patch
http://db.tt/hWJmfHTY
BEFORE FLASHING, ADD THIS LINE TO YOUR BUILD.PROP..
rild.libpath=/system/lib/libril-qc-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM <-----
ro.telephony.ril_class=lgeqcom <-----
Sent from my LG-P500 using xda premium
Please don't complain about the same files having the same md5. My brain won't let me remove it..
Sent from my LG-P500 using xda premium
Thank U
peter joe said:
Thank U
Click to expand...
Click to collapse
Did it work for you pls put a detail which country and sim..
Edit: and there is always a THANKS BUTTON to begin with..
Sent from my LG-P500 using xda premium
> great buddy this is really helpful +1
neko95 said:
> great buddy this is really helpful +1
Click to expand...
Click to collapse
does it work for you neko?
> This work.. but not all people knows how to set/reconfigure build.prop to add those lines.. I suggest you make an updater script which includes the build.prop lines.. but not to over wright the existing build.prop, it should only add those few lines..
neko95 said:
> This work.. but not all people knows how to set/reconfigure build.prop to add those lines.. I suggest you make an updater script which includes the build.prop lines.. but not to over wright the existing build.prop, it should only add those few lines..
Click to expand...
Click to collapse
Or upload thier build.prop here???? Maybe
Sent from my LG-P500 using xda premium
dnle71 said:
Or upload thier build.prop here???? Maybe
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
> no .. I mean people who had build.prop tweaks like from zeppelinrox 3g boost or v6.. this will break those. if it would be over write with a whole build.prop.. So what needed is a script that only updates build.prop let me try to make you one..
neko95 said:
> no .. I mean people who had build.prop tweaks like from zeppelinrox 3g boost or v6.. this will break those. if it would be over write with a whole build.prop.. So what needed is a script that only updates build.prop let me try to make you one..
Click to expand...
Click to collapse
you mean this?
#!system/bin/sh
setprop ril.subscription.types=NV,RUIM;
setprop ro.telephony.ril_class=lgeqcom;
Sent from my LG-P500 using xda premium
dnle71 said:
you mean this?
#!system/bin/sh
setprop ril.subscription.types NV,RUIM;
setprop ro.telephony.ril_class lgeqcom;
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
> you need init.d just to execute a script to build.prop? coz no use updater script to add this to build.prop
I really want to try it baddly but I have an old baseband with "old baseband" fix and it appears that both fixes/patches overwrite at least one file. I will have to reflash the rom and flash new baseband to try it when I'll find some free time.
Thanks for the fix
-Arturo- said:
I really want to try it baddly but I have an old baseband with "old baseband" fix and it appears that both fixes/patches overwrite at least one file. I will have to reflash the rom and flash new baseband to try it when I'll find some free time.
Thanks for the fix
Click to expand...
Click to collapse
Time to upgrade!!..
Sent from my LG-P500 using xda premium
dnle71 said:
Time to upgrade!!..
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Ok I tried the network selection fix..
After trying to search for networks my phone rebooted.
I'm on Polish "Play" network.
I don't know whether I have a funny sim or not.
My phone bootloops....
Actually I have made similar patch (but without undo patch!).
My contains less files and was meant for mentioning in CM issue 5182 Manual network operator selection fails (those who suffer from this problem, please vote for it!). Warning: My patch doesn't have undo patch and it overwrites build.prop, it is made for CM 7.2 RC3 and is purely experimental.
It was created after asking mik_os why manual network selection works in his unofficial CM port, but doesn't work in official CM 7.2 RCs. Here is mik_os answer:
mik_os said:
DavisNT said:
mik_os said:
DavisNT said:
Hi!
How did you manage to get manual network operator selection working on your Cyanogenmod ports for LG P500?
Can you give me a link to source code and/or a comment for Cyanogenmod official port developers?
Issue on CyanogenMod bugtracker is here: https://code.google.com/p/cyanogenmod/issues/detail?id=5182
Thanks a lot!
Click to expand...
Click to collapse
It's easy. CM has temporary switched to old RIL:
https://github.com/CyanogenMod/andr...mmit/49e0b810423dcf94f458e7cf3c2bb90900a7be9e
The old RIL does not properly supports Network Selection in our device. And CM will not fix this because this is temporary.
Click to expand...
Click to collapse
Can I switch my phone back to new RIL by adding back these lines to /system/build.prop (or other changes are also required)?
Code:
ril.subscription.types=NV,RUIM
ro.telephony.ril_class=lgeqcom
Click to expand...
Click to collapse
You also need change this libraries:
https://github.com/koush/proprietary_vendor_lge/commit/65568a688c73962049b2f28de6d108cf05f90772#p500
Click to expand...
Click to collapse
Also I have a question to everybody, especially mik_os and official CM devs. In my patch all files that were updated during library revert mentioned by mik_os are replaced by versions before revert, /system/lib/libdll.so is deleted, but /system/bin/rild is left, because if I delete it, radio doesn't work at all. Also every file, except /system/bin/rild in CM 7.2 RC3 flashable zip is the same as in library revert checkin mentioned my mik_os, but rild is different. Why so - what other changes in rild have been made?
Update: mik_os gave me this link to changes which fixed Manual Network Operator selection with old RIL (Froyo RIL that is contained within mik_os and official CM 7.2 builds): https://github.com/mik9/android_frameworks_base/compare/88b5c4b8eb...2ae66fc39b
Thanks mik_os!
Warning: Patch is only for official CM 7.2 RC3!
I love you! Really thanks what about cm9 it works also there?
Sent from my LG-P500 using XDA
DavisNT said:
Actually I have made similar patch (but without undo patch!).
My contains less files and was meant for mentioning in CM issue 5182 Manual network operator selection fails (those who suffer from this problem, please vote for it!). Warning: My patch doesn't have undo patch and it overwrites build.prop, it is made for CM 7.2 RC3 and is purely experimental.
It was created after asking mik_os why manual network selection works in his unofficial CM port, but doesn't work in official CM 7.2 RCs. Here is mik_os answer:
Also I have a question to everybody, especially mik_os and official CM devs. In my patch all files that were updated during library revert mentioned by mik_os are replaced by versions before revert, /system/lib/libdll.so is deleted, but /system/bin/rild is left, because if I delete it, radio doesn't work at all. Also every file, except /system/bin/rild in CM 7.2 RC3 flashable zip is the same as in library revert checkin mentioned my mik_os, but rild is different. Why so - what other changes in rild have been made?
Click to expand...
Click to collapse
yes that was the basis of my patch too.. but i did not review all files that is not needed to be replace but my brain don't want to....
DavisNT said:
Actually I have made similar patch (but without undo patch!).
My contains less files and was meant for mentioning in CM issue 5182 Manual network operator selection fails (those who suffer from this problem, please vote for it!). Warning: My patch doesn't have undo patch and it overwrites build.prop, it is made for CM 7.2 RC3 and is purely experimental.
It was created after asking mik_os why manual network selection works in his unofficial CM port, but doesn't work in official CM 7.2 RCs. Here is mik_os answer:
Also I have a question to everybody, especially mik_os and official CM devs. In my patch all files that were updated during library revert mentioned by mik_os are replaced by versions before revert, /system/lib/libdll.so is deleted, but /system/bin/rild is left, because if I delete it, radio doesn't work at all. Also every file, except /system/bin/rild in CM 7.2 RC3 flashable zip is the same as in library revert checkin mentioned my mik_os, but rild is different. Why so - what other changes in rild have been made?
Click to expand...
Click to collapse
Well i'll be damned it works ...thank you
It works also for me
@DavisNT
I have tried your patch on my LGP500 with (CM 7.2 nightly 20120617 + patch NeuDLI http://forum.xda-developers.com/showpost.php?p=27616022&postcount=3314) installed.
It seems to work well, the only drawback is to get a misidentification of my "actual" ROM labelled "CM7.2RC3 and 20120526".
Manual selection works well ... Calls and 3G data also. :fingers-crossed:
Thanks a lot for your work!
If these two patches could be integrated by Adam (adfad666) in the official CM 7.2 next nigthly, it would be a huge progress in the LG-P500 version of CM 7.2.
I took the liberty to slightly improve the RIL fix:
In the improved flashable zip the build.prop is not overwritten, but instead the init script of dnle71 is added. In this manner the build.prop is not touched thus preserving any tweaks made therein and also the CM version etc.
(Until someone can tell me how to use apply_patch in the updater-script to patch the build.prop I believe this is the cleanest way)
Furthermore I also added the "old" rild executable so that all RIL files are from the same stage, although apparently this was not absolutely necessary.
Thanks very much dnle71 and DavisNT for your work that I only combined!
Just the usual word of caution: I did test this on my P500 and it worked. For everyone else, however: Use at your own risk!
I will teach you build ROM.
Lets get some ROCK!!!
Operating System
First step is having a fully functional linux distro. You can choose what you prefer, I'm using ubuntu and I write commands for it. You can use OSX too, as I know, but I've completely no idea how, I never had a Mac.
Well, talking about linux, you need a 64bit distribution, so if you have an old 32 bit processor youn cannot go ahead.
To check which version do you have, type in a shell
uname -a
If the results include "x86_64" you're ok.
Required Packages
You need to install some little packages, to be able to proceed, you can do this with your favorite package manager:
sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-dev:i386 g++-multilib mingw32 openjdk-6-jdk pngcrush schedtool tofrodos python-markdown libxml2-utils xsltproc zlib1g-dev:i386
Some systems need some trick to install all this package, is your care to check this process completed correctly and fix eventually problems.
Install "repo"
Repo is the program that handles synchronization between our pc and the repository, in this case Cyanogen's one. To install do:
mkdir -p ~/bin
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
So we have downloaded and added executables flag to it. Now we need a folder to store locally the sources, you can put it everywhere, but to be coherent with other guides, I do:
mkdir -p ~/CM10/
Repository initialization
Well, now it's time to initialize our source folder to correctly sync with repository:
cd CM10
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
Nota: Maybe the repo command is not recognized. In this case you can restart the shell or te machine.
Download
Now is download time! Write this command and get a fresh beer, you have to download several GB of data, please wait.
repo sync -j16
The "-j16" switch may be modified as you want, is the number of concurrent thread downloading from repo. 16 is my value, for a 100Mbit connection, maybe you can decrease a little to match your line speed. Someone uses 8 threads for an 8Mbit ADSL line.
Download precompiled files.
There are some others files needed, like the toolchain, including GCC, to compile code.
~/CM10/vendor/cm/get-prebuilts
Another small wait time and we're ready!
Add sources code for GT540
Copy sources from https://github.com/mmxtrem/device_lge_swift to ~/CM10/device/lge/swift
Or extract this archive http://depositfiles.com/files/1chflk58r to ~/CM10/device/lge/swift
Build
Great, we're ready to build!
The build process takes some hours, so be patient. My notebook, takes more than 10 hours!
cd CM10
source build/envsetup.sh && brunch swift
Install
When is ready, we can find the result here:
~/CM10/system/out/target/product/swift/cm-10-XXXXX-JellyBeanSwift-XXXX.zip
This is the package to be flashed in recovery mode.
There are Gapps included.
Update
If you want to update your build, you have to do only this:
cd CM10
repo sync
and build again!
P.S. Dont forget write Credit my name, when will be publish your ROM. Good Luck!
[Guide] How to use Github
http://forum.xda-developers.com/showthread.php?t=1877040
Wow I always wanted to try this out! Thanks for the surprise tutorial!
Wow wow wow.. forget my post in the other thread. This thing miro, this thing here is possible your best contribution to this community.. I'm getting my old gt540 back from my brother and trying these right tomorrow..
I actually thought about asking you for such a tutorial but scratched it as I didn't believe you would do it. But thank you again and again.. I was so wrong
I've just one question, we do the build, ok and we try it, ok, but if we find any bug, where we solve it?! and where we put the corrects librarys for our phone?!
Sorry i'm just very noob
Miroslav is best men on a whole world
Thank you so much for this tutorial
Btw is gt540 msm 7x27 ? if yes could someone try to build this kernel for our phone https://github.com/Californication/lge-kernel-msm7x27-ics-3.0.8
-bfar97- said:
I've just one question, we do the build, ok and we try it, ok, but if we find any bug, where we solve it?! and where we put the corrects librarys for our phone?!
Sorry i'm just very noob
Click to expand...
Click to collapse
+1
Sent from my LG-P990 using Tapatalk 2
smileydr0id said:
Miroslav is best men on a whole world
Thank you so much for this tutorial
Btw is gt540 msm 7x27 ? if yes could someone try to build this kernel for our phone https://github.com/Californication/lge-kernel-msm7x27-ics-3.0.8
Click to expand...
Click to collapse
Yes, gt540 is msm7x27
smileydr0id said:
Miroslav is best men on a whole world
Thank you so much for this tutorial
Btw is gt540 msm 7x27 ? if yes could someone try to build this kernel for our phone https://github.com/Californication/lge-kernel-msm7x27-ics-3.0.8
Click to expand...
Click to collapse
https://github.com/Californication its my repo!
lge-kernel-msm7x27-ics-3.0.8 - not working. I did try port it from LG L5. Kernel not starting, kernel not finish.
lge-kernel-msm7x27 - kernel from SDSL and AOSP, I ported it from https://github.com/CyanogenMod/lge-kernel-msm7x27 for LG 7227 devices (P500/510/C660/and other), but it dont have latest fixes.
Please dont write stupid massages like "smiles" or +1 or other, make it clean! Devs only, if you want build ROM real, if no go spaming into other thread!
XiproX said:
Yes, gt540 is msm7x27
Click to expand...
Click to collapse
https://github.com/Californication its my repo!
lge-kernel-msm7x27-ics-3.0.8 - not working. I did try port it from LG L5. Kernel not starting, kernel not finish.
lge-kernel-msm7x27 - kernel from SDSL and AOSP, I ported it from https://github.com/CyanogenMod/lge-kernel-msm7x27 for LG 7227 devices (P500/510/C660/and other), but it dont have latest fixes.
Click to expand...
Click to collapse
damn
-bfar97- said:
I've just one question, we do the build, ok and we try it, ok, but if we find any bug, where we solve it?! and where we put the corrects librarys for our phone?!
Sorry i'm just very noob
Click to expand...
Click to collapse
^ This, make a guide for this, or is just all "lets google it"?
thanks for that tut miroslav !!
i would be happy if you can make example of bug fixing/driver porting (something simple as example).
Oh, nice post Miro
But one thing, why don't you post how to make device files. It would be of more use as people will try to make their own sources and a good chance that they could make their own device in collaboration. :good:
i've ear i can do a build in a 32bits processor too! but you know xD do what was said up please!!
Could someone try to build this because I can't cause I have 32bit system in my PC.
We need JB for daily use!
Why are you using -mfloat-abi=softfp
why not -mfloat-abi=hard ?
aaa801 said:
Why are you using -mfloat-abi=softfp
why not -mfloat-abi=hard ?
Click to expand...
Click to collapse
forgot about this line, not using for ROM. it need only for android-ndk for kernel building.
Niquel97 said:
We need JB for daily use!
Click to expand...
Click to collapse
Just do it! (c. Nike)
P.S. Dreams-dreams-dreams.... :laugh:
miroslav_mm said:
forgot about this line, not using for ROM. it need only for android-ndk for kernel building.
Click to expand...
Click to collapse
So should work fine if set to hard yes?
i'm getting this error when compiling:
Install system fs image: out/target/product/swift/system.img
out/target/product/swift/system.img+ maxsize=262225920 blocksize=135168 total=277360512 reserve=2703360
error: out/target/product/swift/system.img+ too large (277360512 > [264929280 - 2703360])
al3000 said:
i'm getting this error when compiling:
Install system fs image: out/target/product/swift/system.img
out/target/product/swift/system.img+ maxsize=262225920 blocksize=135168 total=277360512 reserve=2703360
error: out/target/product/swift/system.img+ too large (277360512 > [264929280 - 2703360])
Click to expand...
Click to collapse
Yes, me too, the build comes so big that it fails the size checks on the default partition layout.
To avoid that change the contents in device/lge/swift/BoardConfig.mk, I've used these values:
Code:
# PARTITIONS
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00500000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00900000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x0010B07600
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x007478A00
BOARD_FLASH_BLOCK_SIZE := 131072
I believe you can still zip up the right files in out/target/product/swift/ to have a signable update zip, the command "make otapackage" which I found somewhere didn't seem to work.
[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.