Since there is no F2FS support thread, I'll try to help here as much as my knowledge goes (or not).
Thread was opened because our dear friend @bsmitty83 and @aosp managed to do a tremendous non.human work and made possible F2FS tor our beloved GNEX.
Here you'll post some questions and everybody will try to help.
For Windows users, here is the ADB/Fastboot pack:
http://forum.xda-developers.com/showthread.php?t=2588979
Thread under heavy construction
(I'll keep on editing when I arrive home)
First of all, thank you for your availability.
What do you think about grouping the links for kernel and recovery that support f2fs?
I know that many roms will appear, but recovery and kernel are the basis.
Once again, thank you.
Sent from my Galaxy Nexus using XDA Free mobile app
Someone should link and teach the step for f2fs support so normal user can try to create it by themselves :good:
Atento said:
First of all, thank you for your availability.
What do you think about grouping the links for kernel and recovery that support f2fs?
I know that many roms will appear, but recovery and kernel are the basis.
Once again, thank you.
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
That's a good start. Will start on that base Thank YOU.
xzilem said:
Someone should link and teach the step for f2fs support so normal user can try to create it by themselves :good:
Click to expand...
Click to collapse
What do you mean by "teach the step for f2fs support". If you mean to compile a kernel, there are plenty of where to start on XDA.
If you refer on "how to install the testing F2FS kernel by @bsmitty83 and @aosp", I'll do that over this thread. Just wait for it
Anyone converted their 2012 nexus 7 to f2fs?
[poo]
jhonnyx said:
That's a good start. Will start on that base Thank YOU.
What do you mean by "teach the step for f2fs support". If you mean to compile a kernel, there are plenty of where to start on XDA.
If you refer on "how to install the testing F2FS kernel by @bsmitty83 and @aosp", I'll do that over this thread. Just wait for it
Click to expand...
Click to collapse
I mean teach the step to convert other roms to f2fs. I think there's no need to compile a new one just like f2fs for grouper.
xzilem said:
I mean teach the step to convert other roms to f2fs. I think there's no need to compile a new one just like f2fs for grouper.
Click to expand...
Click to collapse
im pretty sure its something in the updater-script within the rom,you just have to change it from mounti ext4 to mounting to f2fs,someone in the dirtyv thread compared the commotio script and a slimkat one and made a slimkat f2fs,plus you have to use the kernel from the alpha commotio rom as well
pattyboi:) said:
im pretty sure its something in the updater-script within the rom,you just have to change it from mounti ext4 to mounting to f2fs,someone in the dirtyv thread compared the commotio script and a slimkat one and made a slimkat f2fs,plus you have to use the kernel from the alpha commotio rom as well
Click to expand...
Click to collapse
I'll be pumped when someone writes a guide on this. Once I can make PAC f2fs I'll be a happy camper.
Convert to F2FS Steps
@Hetalk and @Punkiderma
Can you guys tell us the steps to convert any rom to F2FS?
xzilem said:
@Hetalk and @Punkiderma
Can you guys tell us the steps to convert any rom to F2FS?
Click to expand...
Click to collapse
Just woke up. I'll try to put up something later today.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Hetalk said:
Just woke up. I'll try to put up something later today.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse
xzilem said:
@Hetalk and @Punkiderma
Can you guys tell us the steps to convert any rom to F2FS?
Click to expand...
Click to collapse
Same for me, I'll try to write something as soon as I can
Inviato dal mio Galaxy Nexus utilizzando Tapatalk
How I changed paranoid (pa_maguro-4.4-BETA1-20140603) a f2fs compatible ROM.
1) Download latest dirty f2fs compatible kernel zip file. Extract the file "boot.img" to a temporary location
2) Download ROM zip file.
3) Open ROM zip file using 7-zip. Delete "boot.img" and replace with "boot.img" from the dirty kernel (saved in step#1)
4) Open ROM zip and browse to "\META-INF\com\google\android\". Extract "updater-script" to a temporary folder.
5) Open "updater-script" in a text editor. I use notepad++.
6) Replace string
"mount("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.0/by-name/system", "/system");"
by
"run_program("/sbin/busybox", "mount", "/system");"
Again, replace string
"format("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.0/by-name/system", "0", "/system");"
by
"run_program("/sbin/mkfs.f2fs", "/dev/block/platform/omap/omap_hsmmc.0/by-name/system");"
7) If you need to mount data partition add string
"run_program("/sbin/busybox", "mount", "/data");"
after strings
"run_program("/sbin/mkfs.f2fs", "/dev/block/platform/omap/omap_hsmmc.0/by-name/system");"
"run_program("/sbin/busybox", "mount", "/system");"
8) Add string
"symlink("../bin/fsck.f2fs", "/system/bin/dump.f2fs");"
after
"package_extract_dir("system", "/system");"
also add string
"symlink("mount.exfat", "/system/bin/fsck.exfat",
"/system/bin/mkfs.exfat");"
after
"symlink("mksh", "/system/bin/sh");"
9) If you loaded data partition in step 7 you'll need to unmount it at the end by adding string
"unmount("/data");"
10) Replace original updater script the edited one in the ROM zip.
11) Done.
12) Seriously. It's done. Go test it out.
Basically, all(hopefully) this does is, it make sure that ROM's updater script formats/mounts partitions are f2fs, rather than ext4.
Again, I'm not a developer and have just a little working knowledge of what these commands might do. Use this at your own risk.
I've attached original and updated scripts that I've used. You can use compare (ctrlD) feature in notepad++ and see difference between them.
Hope this helps. All the best. :good:
To all the developers and smart people out here, please feel free to suggest changes, or let me know when there's a more comprehensive guide out there, so I can remove this and link to the improved post.
P.S. This might look complicated, but just takes about 5 minutes, not including download time.
Hetalk said:
How I changed paranoid (pa_maguro-4.4-BETA1-20140603) a f2fs compatible ROM.
Again, I'm not a developer and have just a little working knowledge of what these commands might do. Use this at your own risk.
I've attached original and updated scripts that I've used. You can use compare (ctrlD) feature in notepad++ and see difference between them.
Hope this helps. All the best. :good:
To all the developers and smart people out here, please feel free to suggest changes, or let me know when there's a more comprehensive guide out there, so I can remove this and link to the improved post.
P.S. This might look complicated, but just takes about 5 minutes, not including download time.
Click to expand...
Click to collapse
Nicely done, i will try it thanks :good:
Add some of this step to the thread maybe? F2FS Convertion by @burstlam
Hetalk said:
Basically, all(hopefully) this does is, it make sure that ROM's updater script formats/mounts partitions are f2fs, rather than ext4.
Click to expand...
Click to collapse
I did exactly the same, however for slim there was no need to add some lines.
Simply, from what I saw, replace every line that has mount or format ext4 with the appropriate line for F2FS:
mount("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.0/by-name/system", "/ANYPARTITION");
get replaced by
run_program("/sbin/busybox", "mount", "/ANYPARTITION");
and
format("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.0/by-name/system", "0", "/ANYPARTITION");
get replaced by
run_program("/sbin/mkfs.f2fs", "/dev/block/platform/omap/omap_hsmmc.0/by-name/ANYPARTITION");
obviously:
1.change ANYPARTITION following the partition wrote in your updater script
2. REPLACE ONLY WHAT IS NECESSARY: I think you should not add MORE format partition lines than the one present before. Just replace what you have. If you followed the steps explained by AOSP inside the DIrtyV thread, you should have already all the partition F2FS formatted.
A useful thing to do if you have doubts (is what I've done) is to search if the rom you want to convert already has a F2FS version on another device and compare the scripts (without caring about lines that are different because of the different device). For example, I compared Grouper's F2FS slimkat to maguro one, and thanks to this I've understood that mount/format partitions thing.
^^ Lot better.
I'm guessing it wouldn't be too hard if we modified this to work with our phones: http://forum.xda-developers.com/showthread.php?t=2731666
[poo]
poo706 said:
I'm guessing it wouldn't be too hard if we modified this to work with our phones: http://forum.xda-developers.com/showthread.php?t=2731666
[poo]
Click to expand...
Click to collapse
I downloaded looked at the scripts and when I get a chance I'll try to do it for our device. Maybe this weekend.
There is like only 4 lines that need to be changed in omni updater-script. Am i right?
hi guys...one question, is cm11 rom Compatible with F2FS?!! if not how do it myself?
massoudsh said:
hi guys...one question, is cm11 rom Compatible with F2FS?!! if not how do it myself?
Click to expand...
Click to collapse
Read about 5 posts back. Punkiderma and I have outlines steps for paranoid. You can follow them for cm11 as well. Post your results here.
Related
This kernel is a new one with the recovery STEAM insteaod of the normal one, it support a lot of options, take a look
to use it:
apply extract the zip and apply the tar in odin as pda or also extract the tar and apply the zimage as kernel with heimdall
NOTE this is for the 2 froyo roms i know
EDIT:
V2
This is the v2 version, not many changes but from the SpeedMod Kernel by hardcore i used:
* Optimized compiler flags: -mcpu=cortex-a8 -mfpu=neon -mfloat-abi=softfp -fno-gcse -fprefetch-loop-arrays --param l2-cache-size=512 --param l1-cache-size=64 --param simultaneous-prefetches=6 --param prefetch-latency=400 --param l1-cache-line-size=64
Also there are some memory twaks from that thread, i got 334 of total RAM, please check your SGS before flahsing because by mistake i didnt and now im not sure if it did any change
CHECK camera/vide/radio/tv/games
PD i added ext4 and JFS, but i did not tested them
No go and thank him an zstupy for this great work
Probando...
luismanson said:
This kernel is a new one with the recovery STEAM insteaod of the normal one, it support a lot of options, take a look
to use it:
apply extract the zip and apply the tar in odin as pda or also extract the tar and apply the zimage as kernel with heimdall
Click to expand...
Click to collapse
Is it a fully working Steam??? I will surely try if it is.
i tryed some options and it worked, testing is welcome
Does it replace the CWM? Does it have all the basic CWM functions working? To go back, can we just flash another kernel with CWM or we need to flash a whole ROM?
I guess if you have a 'what's working' list & a 'to-do' list, we can start testing it.
Hello Luis, i put your Kernel in my SGS and now it dont show my IMEI.
I`m using Froyo JPD...
EDIT: Well... I done one Factory Reset and now IMEI turn show again...
What improviment i got with your Kernel? Have BLN?
Cya.
Guto ViP said:
Hello Luis, i put your Kernel in my SGS and now it dont show my IMEI.
I`m using Froyo JPD...
EDIT: Well... I done one Factory Reset and now IMEI turn show again...
What improviment i got with your Kernel? Have BLN?
Cya.
Click to expand...
Click to collapse
i didn't try yet, but it a good thing u to list the improvements done from the stock one.
it should give u more visibility!!
Guto ViP said:
Hello Luis, i put your Kernel in my SGS and now it dont show my IMEI.
I`m using Froyo JPD...
EDIT: Well... I done one Factory Reset and now IMEI turn show again...
What improviment i got with your Kernel? Have BLN?
Cya.
Click to expand...
Click to collapse
Seriously forget about BLN & other petty stuff. Go ahead and make a working STEAM KERNEL..
PS : This is some real good work.
PS2 : You need to put a BOUNTY on it.
PS3: checkout & rename your [ALPHA] to a version # looks good on the Title.
im not doing a lot of improvements, im working on some ideas on the work other ppl does for the other SGSs versions and thinks i would like, like this steam kernel
it is my V3 base kernel, it has tinyRCU, ondemand scheduler and BFQ sched
there is NO BLN because it caused problems with a2dp audio
Will keep a watch on this thread.
great man..lot's of options in steam menu...
some explanation about that? can u provide or give a link about lots of options we have now?
can i put everything in ext2????
everuthing ok unti now
ragin said:
Seriously forget about BLN & other petty stuff. Go ahead and make a working STEAM KERNEL..
PS : This is some real good work.
PS2 : You need to put a BOUNTY on it.
PS3: checkout & rename your [ALPHA] to a version # looks good on the Title.
Click to expand...
Click to collapse
Here we go again.. Please create your own message board where you can edit every topic title to whatever you like!
Ps1: and please stop the non value added replies you're posting all over this board.
Ps2: my apologize for this non value added reply. I'm just trying to make a statement
i wont put a bounty on work that anyone can do, but i really do need money and dont mind on people donating money
i will keep working on steam, but im so short of time that i can not test everything, thats why its alpha, at least on the B version
jersr said:
Here we go again.. Please create your own message board where you can edit every topic title to whatever you like!
Ps1: and please stop the non value added replies you're posting all over this board.
Ps2: my apologize for this non value added reply. I'm just trying to make a statement
Click to expand...
Click to collapse
<----- looks at his thanks meter & smiles,
Can we make the conversion to ext 2, 3 or 4 with this Steam Kernel?
And, it's too complicated to have some overclocking room on near future with this kernel? Like something to make easy to overclock with Set CPU and some setcpu.txt files?
Thanks, Luis! You're one of the most active developers to I9000B and we all should be completely thankful to you!
Keep with the good work! Congrats!
Ok. Running on JFS and everything seems to be ok and pretty fast till now. About 1500 on Quadrant and, just to mention, I've made a full conversion without backup. Wiped out everything to be sure if anything goes wrong it's not caused by apps and past configurations. Missed the ext4 conversion to test. Not tested ext2.
Sent from my GT-I9000B using Tapatalk
Hello Luis, I put your Kernel inside ffabio Froyo light... I change all to JFS, but for now my Titanium Backup doesnt work, i got only FC...
Can be JFS?
Tnx and good work!
Thread's dead?
Oh well...
I'm still running everything on JFS and it's pretty fast and smooth, without bugs as I could see. But after some research found that it could be interesting to put /cache and/or /system to ext2. Anyone already tried this? It really should make some difference?
Thanks! And c'mon! Wake up, people! This is one of the best kernels we have to our i9000B! Let's give some feedback!
ClowReed said:
Thread's dead?
Oh well...
I'm still running everything on JFS and it's pretty fast and smooth, without bugs as I could see. But after some research found that it could be interesting to put /cache and/or /system to ext2. Anyone already tried this? It really should make some difference?
Thanks! And c'mon! Wake up, people! This is one of the best kernels we have to our i9000B! Let's give some feedback!
Click to expand...
Click to collapse
You don't face the time-reset issue at restart?
ragin said:
You don't face the time-reset issue at restart?
Click to expand...
Click to collapse
Nope! But as I said, I've done a full conversion (everything on jfs) and wiped out everything via secret code and via recovery menu, just to be sure it's all clean.
Sent from my GT-I9000B using Tapatalk
Android Development How-To: Compiling the Android/Linux kernel for the Epic Touch 4G.
NOW INCLUDES ROOT!!!
Introduction: This guide is meant for people who want to get started with android development and don't know where to start. This thread can also be used as a reference place for android development on the et4g. This guide well first be on compiling the android kernel and flashing it to your phone and, I well update it on a regular basis for more complex mods and such to get you familiar with the android platform. If at anytime anyone would like to add more to this, pm me with what you would like to add or fix. Android is an open-source wonderland and I feel like more people should experience the fun of android development. Just remember I am not responsible if you do something stupid and break your phone!
First, we are going to get familiar with the android kernel by compiling a stock build and flashing it with Odin to your et4g.
What you need to download to compile the kernel:
Samsung open-source kernel and platform files. Available at: Samsung Open Source
Type in: Sph-d710 in the search bar in the link and download latest source.
initramfs files (More on this later) (includes cwm, busy box, and of course root! Thanks to chris41g for his help.) Files available at: Initramfs Files
Tool chain for compiling: Available at: Arm-toolchain
Preferably Ubuntu or another Distro. Of Linux running on a partition or Virtual machine.
Step 1: Were going to unzip the source you got from Samsung and take a short look around.
unzip the source and unzip the file that says, “SPH-D710_GB_Kernel.tar.gz” and, open it up. You are now looking at the kernel source for the Epic touch 4g! Okay I well not go over to much whats is here but, I well add a more in depth look in the kernel soon.
Scroll to the bottom of the source and you should see a document that says, "makefile". We are just going to add a name for your stock compile of the kernel, to make it a little more special. Open it and go to where it says Extra version and add your last name ,just make it all lower case letters or it wont compile correctly. When you flash it to your phone, the about phone panel in setting well say: Kernel version: 2.6 [last name you chose] now.
Step 2: Lets get started!
Open terminal in Linux and change your directory to the kernel. You do this by putting,
“cd” and then typing where your kernel source is then hit enter. My terminal looked like this:
cd /home/shane/Desktop/SPH-D710_GB_Kernel
Click to expand...
Click to collapse
Step 3: Tell terminal where your tool chains you downloaded are located.
The kernel is compiled using a tool chain, and the terminal needs to know where the tool chain is to compile. (The tool chain is the folder called “arm-2009q3” )Start by typing this in the terminal:
export CROSS_COMPILE=
Click to expand...
Click to collapse
Then after that put where your tool chain is located. Also when you are entering where it is at, you need to put a “/bin/arm-none-eabi-” at the end of the directory. This shows the terminal that the compiling tools are under the folder bin and starts with arm-none-eabi- and the android compilation adds the last word for the compiler program it needs. (you can see this if you go into the bin folder under the “arm-2009q3 folder.) For adding the tool chain I entered this:
export CROSS_COMPILE=/home/shane/Desktop/arm-2009q3/bin/arm-none-eabi-
Click to expand...
Click to collapse
Then hit enter.
Step 4: Clean the kernel, enter configuration files and make the modules.
Enter this command:
sudo make clean
Click to expand...
Click to collapse
Then enter password and hit enter.
Then it well say something like:
make: /opt/toolchains/arm-2009q3/bin/arm-none-linux-gnueabi-gcc: Command not found
Click to expand...
Click to collapse
IGNORE THIS! It is just a fragment in a configuration file that says the toolchain is not in the default location. But, we changed the tool chain location in step 3 so it well compile correctly.
This cleans up and organizes the kernel for compilation.
Now enter this command in terminal:
make c1_rev05_na_spr_defconfig
Click to expand...
Click to collapse
This is the configuration files for the epic touch 4g and well compile the kernel based off what is in these files.
Now were going to compile all the modules so wifi,vibration... work.
Enter this in terminal:
make modules
Click to expand...
Click to collapse
Step 5: Moving the newly compiled modules to the initramfs/lib/modules folder.
We are now going to move the modules from the newly compiled modules to the initramfs files. So that wifi and vibration well be working in our kernel.
*Initramfs files are the root filesystem of the kernel and does processes the kernel can't do itself while its booting.
You can do this by terminal or by hand. We are just moving the modules to the initramfs to be used when compiling the kernel.
You can type this into terminal (Where it says “Path to initramfs” you need to replace with your own path to the initramfs folder + /lib/modules) :
cp drivers/samsung/j4fs/j4fs.ko Path to initramfs/lib/modules
cp drivers/scsi/scsi_wait_scan.ko Path to initramfs/lib/modules
cp drivers/bluetooth/bthid/bthid.ko Path to initramfs/lib/modules
cp drivers/net/wireless/bcm4330/dhd.ko Path to initramfs/lib/modules
cp drivers/samsung/vibetonz/vibrator.ko Path to initramfs/lib/modules
cp drivers/staging/westbridge/astoria/switch/cyasswitch.ko Path to initramfs/lib/modules
Click to expand...
Click to collapse
This copies the new modules out of the kernel source and puts them in the initramfs/lib/modules folder to be used later.
Now once you enter that press enter.
Step 7: Compiling the android kernel with initramfs.
Type this in terminal:
make -j5 CONFIG_INITRAMFS_SOURCE=Path to initramfs file
Click to expand...
Click to collapse
*Remember to replace the “path to initramfs file” with the path to the initramfs file.
Okay this well take anywhere from 5-15 mins. to compile depending on your system.
Step 8: Were done compiling, lets make something flashable for Odin!
Just type in terminal:
cd arch/arm/boot/
Click to expand...
Click to collapse
Then type:
tar cvf MyKernel.tar zImage
Click to expand...
Click to collapse
This well zip up the zimage (the kernel) you just compiled to something flashable in odin.
If you open up the kernel source file and go to arch/arm/boot you well see the zimage you compiled and, the Mykernel.tar file for Odin. Double check and right click on the zimage and make sure it is around 5-6 MB before flashing.
Step 9: Flashing to your phone.
Go to a windows computer and download Odin.(if you have rooted your phone using zedomax's method you should have it installed already)
Okay now open it up and place the Mykernel.tar file in the PDA section of Odin. Now download the drivers for your phone if you haven't.(I assume you already have.) Then put your phone in download mode (hold volume down button and power button on start up and push volume up button when the warning pops up) Now plug your phone into the computer and make sure “auto-reboot” is the only box checked in Odin. Hit start and your phone well be flashed with a kernel you compiled yourself! If you did this right your phone should start up. If it is stuck in a boot loop, immediately put back in download mode and flash to stock. Link available here to stock files:
http://forum.xda-developers.com/showthread.php?t=1409634
and, try to figure out what you did wrong while compiling and try again!
Good job you have finished!
Step 10: The future and your new phone!
I would like to include more android kernel mods and stuff in the future but, wanted to get this out there to get people familiar with the android compiling process. I want this guide to be something people reference as they start to develop, by using the methods here along with kernel and U.I mods on the platform being implemented in the future. My ultimate goal is to at least know I helped at least one person get into android development so, if I helped you please leave a reply or say thanks. If anyone has ideas to add to the post, please pm me.
Have fun developing!
I'll take this...
and this...
One more...
Awesome!!!! I have been patiently awaiting this. THANK YOU SOOO MUCH!!!!
Sent from my SPH-D710 using xda premium
Thank you! Definitely will be referring to this during my free time. Can't wait to see what else gets added
Sent from my SPH-D710 using xda premium
Awesome!! tyvm!!
Wow... How awesome is this? I have been looking for something like this for a long time. I will be watching for updates. Thank you very much.
all u need now is a video tutorial
My man!!! Thank you for this!!
Sent from this phone
Awesome guide, I am looking forward to giving this a go soon. Just curious but how difficult is the process to include a custom recovery?
dtm_stretch said:
Awesome guide, I am looking forward to giving this a go soon. Just curious but how difficult is the process to include a custom recovery?
Click to expand...
Click to collapse
It all depends if you wanted to flash a already made custom recovery (cwm) then we would just haved to root the kernel then build and flash the recovery. If you were to make a fully custom recovery with custom functions made by you then it could get a little more tricky but, I am guessing you just mean flashing a custom recovery like cwm. Which is not terribly hard but, not neccesary easy eather depending on how hard it is to obtain root.
I might update the guide in the future. Showing how to do something like this but, I have a few more ideas for the guide before I include this.
You nailed it, I was curious about adding root and CWM(or a variation of it). I am more than content with figuring out what you have posted so far.
Thank you so much. This is absolutely great!
Sent from my SPH-D710 using XDA App
Awesome guide. Thank u so much for this. Hope for many more.
Sent from my Nexus S 4G using xda premium
Very awesome thanks for the share!!
Sent from my SPH-D710 using XDA App
Great Guide!
Very informative and well put, Thank You.
thank you very much for this! Gives me something new to try out. Thanks again!!!
Sent from my SPH-D710 using Tapatalk
Thanks for this effort. Unfortunately I don't have anything to contribute to your work. I consider myself a budding developer and have been diligently teaching myself to program with the use of some great texts over the last 2 weeks. While I have much to learn this guide and hopefully any additions you make will help me dive nose first into Android development like I've been hoping to for the last couple of years.
I hope you continue to add more into this guide and it becomes a great resource for others like me.
Great Job!
obelisk79 said:
Thanks for this effort. Unfortunately I don't have anything to contribute to your work. I consider myself a budding developer and have been diligently teaching myself to program with the use of some great texts over the last 2 weeks. While I have much to learn this guide and hopefully any additions you make will help me dive nose first into Android development like I've been hoping to for the last couple of years.
I hope you continue to add more into this guide and it becomes a great resource for others like me.
Great Job!
Click to expand...
Click to collapse
I hope it helps!
Hi to all devs here,
I am currently creating a new ROM with modified stock kernel. Currently I have basic features for the ROM and for my kernel, what I have is init.d support. I would like to add the following kernel modules:
DroidWall
Governors and IO Scheduler
BaCem
EXT4
Now, would copying the modules to system/lib/modules do the trick? Or do I need anything else? I'm currently new in creating custom ROMS, so any help/advise is greatly appreciated.
Also, can anyone give me the link for SpareParts.apk? I have seen many spareparts.apk but all of them are from creeds rom.
Thanks,
Carl
you'll need init.d script to call the modules. for bacem tweak, you should put the init.d script from irfan's thread since it also contain the script needed to set the voltage and fix the bug in bacem tweak. for another modules, you'll only need to call the modules in boot via init.d script. you can use these script
Code:
#!/system/bin/sh
insmod <location of modules1>
insmod <location of modules2>
the modules are usually stored in /sytem/lib/modules so you'll need to replace <location of modules> with /system/lib/modules/<module name>. after boot you can check whether if the modules loaded or not by typing "lsmod" in terminal.
EDIT: you can find sparepart.apk in my thread about one pack tweak.
can i use ur kernel in m stock rom...if yes put it
Sent from my GT-S5360 using xda premium
kurotsugi said:
you'll need init.d script to call the modules. for bacem tweak, you should put the init.d script from irfan's thread since it also contain the script needed to set the voltage and fix the bug in bacem tweak. for another modules, you'll only need to call the modules in boot via init.d script. you can use these script
Code:
#!/system/bin/sh
insmod <location of modules1>
insmod <location of modules2>
the modules are usually stored in /sytem/lib/modules so you'll need to replace <location of modules> with /system/lib/modules/<module name>. after boot you can check whether if the modules loaded or not by typing "lsmod" in terminal.
EDIT: you can find sparepart.apk in my thread about one pack tweak.
Click to expand...
Click to collapse
Thank you sir kurotsugi. BTW, do i need to include the extension of the module like this:
Code:
insmod /system/lib/modules/modulename.ko
CarlDeanCatabay said:
Thank you sir kurotsugi. BTW, do i need to include the extension of the module like this:
Code:
insmod /system/lib/modules/modulename.ko
Click to expand...
Click to collapse
Sure...
Sent from my GT-S5360 using xda app-developers app
be carefull if yo're using ext4 as a modules. it should be mounted first before another script running and don't ever change your /data, /system, and /cache partition to ext4.
kurotsugi said:
be carefull if yo're using ext4 as a modules. it should be mounted first before another script running and don't ever change your /data, /system, and /cache partition to ext4.
Click to expand...
Click to collapse
Sir...if i change ext3 to ext4 in ur ope pack tweak, can i mount ext4?
Sent from my GT-S5360 using xda app-developers app
theoritically it will work only if your kernel support it and you have loaded ext4 modules before mount command. never interested to test it. ext3 is easier and better.
kurotsugi said:
theoritically it will work only if your kernel support it and you have loaded ext4 modules before mount command. never interested to test it. ext3 is easier and better.
Click to expand...
Click to collapse
Bro, how to change /system /data and /cache from ext4 to rfs ??
our default system partition is already in rfs. you can modify ext4 file from maroc to revert it.
kurotsugi said:
our default system partition is already in rfs. you can modify ext4 file from maroc to revert it.
Click to expand...
Click to collapse
I know, but somehow i format /cache to ext4. Maybe. Coz when i create backup nandroid file is cache.ext4.tar else is system.rfs.tar and data.rfs.tar
And yes it show in /sys/fs/ext4/stl10 which mean /cache partition fyi i use my kernel that support ext4.
I want to change /cache from ext4 to rfs again but dont know how try with tick repartition in odin still no hope just stuck in download mode.
Code:
ui_print("Starting Operation...");
show_progress(0.1, 0);
unmount("/cache");
ui_print("Formarting cache with rfs...");
format("rfs", "EMMC", "/dev/block/stl10");
ui_print("Mount cache with rfs...");
mount("rfs", "EMMC", "/dev/block/stl10", "/cache");
show_progress(0.1, 100);
ui_print("Done");
ui_print("All praise is due to Allah");
its an updater script. you can give it a shot
Hi devs,
I would like to ask few more n00b questions:
1. Should I put EXT4 at 00EXT4_module or 00bacem-tweak and put ext4 at 01 inside init.d?
2. How do I set the default keyboard for a custom ROM
3. How do I get 14 Toggle Status Bar + Swipe to Clear Notification working on DXLE1? It works on lower firmware version but on DXLE1, it makes the status bar disappear.
PS. I don't want to start another thread so I am asking here. Thanks in advance!
Sorry Sir I can't help u bt advice to change heading so ppl vil cum to knoe wat ur askin by reading only heading
sent using repencis 3.5 wid a2sd
DELETED
Sent from my GT-S5360 using xda app-developers app
Sir....
I just can help no. 2 and 3
2. Choose ur keyboard in Settings>locale and text>choose ur keyboard..this step just make ur keyboard as default
3.u can use system-unsigned and framework.jar in http://forum.xda-developers.com/showthread.php?t=1691397 I use this and work perfectly
Sent from my GT-S5360 using xda app-developers app
shoutokuyaki said:
Sir....
I just can help no. 2 and 3
2. Choose ur keyboard in Settings>locale and text>choose ur keyboard..this step just make ur keyboard as default
3.u can use system-unsigned and framework.jar in http://forum.xda-developers.com/showthread.php?t=1691397 I use this and work perfectly
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
I think he is askin how to make any 3rd party keyboard as a system/default keyboard while compiling rom
I might b wrong bt u tried to help him
sent using repencis 3.5 wid a2sd
press thnxxx
CarlDeanCatabay said:
Hi devs,
I would like to ask few more n00b questions:
1. Should I put EXT4 at 00EXT4_module or 00bacem-tweak and put ext4 at 01 inside init.d?
Click to expand...
Click to collapse
i don't get it. do you mean the script used to call the modules? if yes, it doesn't matter where you put it. you'll only need to make sure that it run before another script, especially a2sd script or similar method. you can easily arrange the sequence by the number and alphabet.
2. How do I set the default keyboard for a custom ROM
Click to expand...
Click to collapse
if you still have the default keyboard, our system will use that as default keyboard. you can remove it so your keyboard will work as default but make sure that your keyboard is working since not all 3rd party keyboard could work as system app.
3. How do I get 14 Toggle Status Bar + Swipe to Clear Notification working on DXLE1? It works on lower firmware version but on DXLE1, it makes the status bar disappear.
PS. I don't want to start another thread so I am asking here. Thanks in advance!
Click to expand...
Click to collapse
if there's no status bar FC issue the problem could come from improper method of compiling the apk. it sometimes happen when we use old apktool version. dxlc and dxle are using similar framework, you can try to use systemUI from another custom rom based on dxlc for an alternative if you can't solve that compiling issue.
Hi All,
I'm starting this thread so that we can compile in one location the methods we attempted to create a zip for the recent Jellybean update, and hopefully advance the creation of this rom. This should be mentioned before starting.
ONLY POST IF YOU HAVE RELEVENT INFORMATION REGARDING THIS JELLYBEAN ROM.
This Includes:
Procedures
Logcats
Test Builds
Helpful Suggestions (Be Specific)
To start, I've attempted the following alterations on the zip level:
Straight System dump with updated updater-script
System dump with default updater script
Modified updater script removing patch elements
Utilizing the Canadian Rom, which flashed and appplying new system.
Swapping out radio flashing and boot.img with shellnutt's boot.img
I also have the following plans:
System Dump on Canadian Rom, and default boot.img
Recursive Deleting of patched files
Example
Code:
assert(apply_patch_check("/system/3rd_party/videowiz/lib/libMvMMAS.so", "65cfe8efc36cf58669e5fb9f30274bc49c3f9703", "e1a051bb2562af8d9b106ef4b875f85a6109ee9e"));
set_progress(0.003080);
delete("/system/3rd_party/videowiz/lib/libMvMMAS.so");
Than initiate the normal package_extract_dir("system", "/system");
Any other information would be great. Some developers have gotten it to flash but not boot.
Also, here's a link to the test builds I released.
http://goo.im/devs/AdriVelazquez/Roms/Nightlies/TestSprint
Thanks to all the developers that have been working on it.
This is what I've tried:
Used the boot.img & system.img. from dump to compile a rom in dxsdia's kitchen. I was able to apply root to the boot.img and compiled a zip but it wont flash. I then added the updater script from the dump but it still wouldn' t flash. Ithink my problem is in the updater script. I didn't take thetime to configure the kitchen properly for the optimus G but will do so tonight. I have the 2 test zips at home and I'll post them tonight if anyone wants to take a look.
Suggestion:
Since houstonns Korean port boots, and all is well except radio, would it also help to look at that system dump along with the Canadian? Maybe something to utilize?
johnq54 said:
Suggestion:
Since houstonns Korean port boots, and all is well except radio, would it also help to look at that system dump along with the Canadian? Maybe something to utilize?
Click to expand...
Click to collapse
I already tried that. That was the test zip I did last night.
Sent from my LG-LS970 using xda premium
I also tried both mentioned here, none worked for me as well. I contacted couple of friends to help us out, Scott (Scrossler cleanrom series) already answer me back, he's looking into it, I will let u guys know if they get something working.
Edit: houston answer as well, he is gonna work on it as well.
LROD'S OPTIMUS G
As I don't own the device I need your guys' help with creating a flashable zip for you guys. Lrod0175 requested my help. What I need is your system mount points. To get those open up Terminal Emulator and enter these commands:
Code:
$ su
# cat /proc/emmc
I need what is printed out.
dastin1015 said:
As I don't own the device I need your guys' help with creating a flashable zip for you guys. Lrod0175 requested my help. What I need is your system mount points. To get those open up Terminal Emulator and enter these commands:
Code:
$ su
# cat /proc/emmc
I need what is printed out.
Click to expand...
Click to collapse
There is no /proc/emmc on my phone, but I've attached what I have in /proc/mounts in case that helps.
grktaurus83 said:
There is no /proc/emmc on my phone, but I've attached what I have in /proc/mounts in case that helps.
Click to expand...
Click to collapse
This is what I was looking for. Thanks!
dastin1015 said:
As I don't own the device I need your guys' help with creating a flashable zip for you guys. Lrod0175 requested my help. What I need is your system mount points. To get those open up Terminal Emulator and enter these commands:
Code:
$ su
# cat /proc/emmc
I need what is printed out.
Click to expand...
Click to collapse
Please, for safety, only use the by-name mount points. Below are the partitions for the American and Candian variants.
http://pastebin.com/Rej3FgQS
Shelnutt2 said:
Please, for safety, only use the by-name mount points. Below are the partitions for the American and Candian variants.
http://pastebin.com/Rej3FgQS
Click to expand...
Click to collapse
I'm using the by-name mount points. Wasn't sure if the Optimus G was proc/emmc or not.
Thanks dastin for answering and thanks guys for getting what he needs to help us.
LROD'S OPTIMUS G
do we have any logcats?
dastin1015 said:
I'm using the by-name mount points. Wasn't sure if the Optimus G was proc/emmc or not.
Click to expand...
Click to collapse
A bit late but might still be helpful to others. Here is a pastie of the by-name goodness as clear as a bell. This is the Sprint varaint
http://pastebin.com/teQmXDX9
If anyone needs anything from the stock JB ROM let me know. I am running it and can provide any files or anything.
_Epic said:
If anyone needs anything from the stock JB ROM let me know. I am running it and can provide any files or anything.
Click to expand...
Click to collapse
Same here
Sent from my LG-LS970 using xda premium
Veritass said:
Same here
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
can either of you post the build.prop? I won't be updating.
interloper said:
can either of you post the build.prop? I won't be updating.
Click to expand...
Click to collapse
How's this?
http://pastebin.com/yjNnR2sh
Sent from my LG-LS970 using xda premium
interloper said:
can either of you post the build.prop? I won't be updating.
Click to expand...
Click to collapse
Here's the build.prop
http://pastebin.com/UXSBvNMj
Provided by epic since I haven't done the update also.
Sent from my LG-LS970 using xda premium
I sent Adriel build.prop file but forgot I could copy text and post to pastebin. That's why we both posted. Lol.
Sent from my LG-LS970 using xda premium
Good morning to all, We have another dev, his name is negamann303 from the evo 3d forum, he's working hard on our project, already send me stuff to test, we will not post anything because these zips are highly flammable and all the testing is done in a spare phone I have, I will keep u guys updated.
LROD'S OPTIMUS G
As well as my own MoDaCo Custom ROM for the 5X, I've created a custom ROM starter template for anyone who wants to have a go. It's a bit different.
Basically, this ROM template will let you create your own custom ROM VERY easily. Easier than ever before. All you have to do is...
download my ROM template zip
make the changes to the system of your phone just as you'd like them for your custom ROM
run some commands on your device via ADB
add the 2 resulting files to the template zip
That's it! No messaging around with install scripts, no rebuilding anything complex, just mod - and go!
Preparation
ONLY if you are completing the process for the first time, you need to set up a file on your microSD card - so launch and ADB shell and type the following commands...
Code:
touch /sdcard/exclude
echo app > /sdcard/exclude
echo priv-app >> /sdcard/exclude
echo delapp >> /sdcard/exclude
ROM build
Once you have your system up and running how you want it, and you're ready to distribute it (just the system and cust dirs mind, it won't pull the data dir, so your personal data is safe), reboot to recovery, launch an ADB shell and type the following commands:
Code:
mount /system
tar -X /sdcard/exclude -zcvpf /sdcard/system.therest.tar.gz /system/
tar -zcvpf /sdcard/system.apps.tar.gz /system/app /system/priv-app /system/delapp
mount /cust
tar -zcvpf /sdcard/cust.tar.gz /cust
You'll then end up with 3 new files on your SD card - system.apps.tar.gz (which is apps and priv-apps from system), system.therest.tar.gz (which, as the name suggests, is the rest of the system partition!) and cust.tar.gz with is the cust partition contents.
Update the template zip with these 3 files and that's it. It's ready to distribute for people to flash via TWRP! If you have updated the boot image, you'll need to replace that too, the easiest way is to do a TWRP backup then pull that file from the SD card and drop it into the template zip as boot.img. That's really it!
I hope this inspires a few people to start playing around with custom ROMs for the 5X... more cool things coming soon!
Oh and the all important template file...
DOWNLOAD - customromtemplate-5x-plk21-b330-r4.zip [ROMRAID] MD5: 524ef13ab773859245c2488ab8271bc0
P
Changelog
r4:
Updated to B330
r3:
Updated to format partitions rather than delete
r2:
Updated to include /cust partition support
r1:
Initial release
Thank you for this your work is much appreciated
Thnx a lot...
Sent from my KIW-L21 using Tapatalk
Thankyou, can I use this script for L-22? And will your MoDaCo rom will work with L-22?
I don't think this one will in its entirety, but you can make your own template by pulling the boot image from the TWRP backup and using the commands above to create the files to put in the zip.
P
Sent from my SM-G928F using Tapatalk
paulobrien said:
I don't think this one will in its entirety, but you can make your own template by pulling the boot image from the TWRP backup and using the commands above to create the files to put in the zip.
P
Sent from my SM-G928F using Tapatalk
Click to expand...
Click to collapse
Oh, I see. I will try after my exams. And MoDaCo rom will support all versions or only L-21?
praxant said:
Oh, I see. I will try after my exams. And MoDaCo rom will support all versions or only L-21?
Click to expand...
Click to collapse
L21 is the only model I can test on currently.
P
Sent from my SM-G928F using Tapatalk
Looking forward to rooting and trying your ROM MoDaCo thanks for your efforts
Sent from my KIW-L21 using Tapatalk
paulobrien said:
L21 is the only model I can test on currently.
P
Sent from my SM-G928F using Tapatalk
Click to expand...
Click to collapse
I tested it on my L24-B140 and it worked just fine. Thanks for sharing
I think it's going to be worth integrating /cust into this too, as they are a lot of things pulled from there (such as the build.prop changes). It'll be simple enough though.
re: non KIW-L21 devices, creating a template for other models shouldn't be any issue at all. I'm getting a US spec Honor 5X, so that'll be helpful.
P
paulobrien said:
I think it's going to be worth integrating /cust into this too, as they are a lot of things pulled from there (such as the build.prop changes). It'll be simple enough though.
re: non KIW-L21 devices, creating a template for other models shouldn't be any issue at all. I'm getting a US spec Honor 5X, so that'll be helpful.
P
Click to expand...
Click to collapse
Are you referring to the cust/hw/USA/prop/local.prop
the rest of the stuff in cust seems pretty standard like (media/bootanimation.zip)
Might as well make all of /cust changeable.
P
paulobrien said:
Might as well make all of /cust changeable.
P
Click to expand...
Click to collapse
so just add tar -zcvpf /sdcard/system.apps.tar.gz /system/app /system/priv-app /cust
or does it need it's own line and an updater-script edit to include it
That should probably work. updater-script will need to include mounting /cust too.
P
paulobrien said:
That should probably work. updater-script will need to include mounting /cust too.
P
Click to expand...
Click to collapse
yeah that worked as expected, only question is their any user info stored in /cust that we might not want to share ?
I didn't check every file in their
No, /cust is read only.
P
Sent from my SM-G928F using Tapatalk
paulobrien said:
No, /cust is read only.
P
Sent from my SM-G928F using Tapatalk
Click to expand...
Click to collapse
So just to be sure, if I want to remove facebook and twitter from /cust/preinstalled/public
I would need to add --> run_program("/sbin/busybox", "rm", "-rf", "/cust/*");
to erase the /cust folder first ? the same way /system is erased / formated
Exactly.
P
paulobrien said:
Exactly.
P
Click to expand...
Click to collapse
Alright, here's my updater-script with all the changes
Code:
ui_print("Flashing boot...");
package_extract_file("boot.img", "/tmp/boot.img");
write_raw_image("/tmp/boot.img", "/dev/block/bootdevice/by-name/boot");
delete("/tmp/boot.img");
ui_print("Mounting system...");
mount("ext4","EMMC","/dev/block/bootdevice/by-name/system", "/system");
mount("ext4","EMMC","/dev/block/bootdevice/by-name/cust", "/cust");
ui_print("Erasing system...");
run_program("/sbin/busybox", "rm", "-rf", "/system/*");
run_program("/sbin/busybox", "rm", "-rf", "/cust/*");
ui_print("Extract Apps...");
package_extract_file("system.apps.tar.gz", "/tmp/system.apps.tar.gz");
run_program("/sbin/busybox", "tar", "zxvf", "/tmp/system.apps.tar.gz", "-C", "/");
delete("/tmp/system.apps.tar.gz");
ui_print("Extract System Files...");
package_extract_file("system.therest.tar.gz", "/tmp/system.therest.tar.gz");
run_program("/sbin/busybox", "tar", "zxvf", "/tmp/system.therest.tar.gz", "-C", "/");
delete("/tmp/system.therest.tar.gz");
sync();
unmount("/system");
unmount("/cust");
ui_print("Done Enjoy !!");
set_progress(1.000000);
For completeness here's the boot.img for the KIW-L24 B140 for any USA users who want to join in
https://www.androidfilehost.com/?fid=24438995911973056