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
Related
Going to preface this with the fact that I'm relatively new to the dev scene. I'm still learning, but we all learn by doing right?
This dump is taken from my rooted UK retail O2 Galaxy Nexus. Rooted using adb method (not superboot method) - http://forum.xda-developers.com/showthread.php?t=1352004
Not entirely positive these are done perfectly (especially the .zip) but I think that may creatable from my dd image anyways. I'd appreciate someone with dev experience looking over these and okaying them, and maybe regular users staying away from trying to do anything with these until someone more experienced says they're alright?
I just figured that seeing I uploaded these for 2 people I may as well make them publically available for all.
I'm also including the steps I took inside code tags for anyone to point out any mistakes I may have made.
DD Image as requested by Maximilian Mary:
Code:
su
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/system of=/sdcard/galaxynexussystem.img
Available here: http://www.megaupload.com/?d=KXFYSMT2 or http://multiupload.com/CPP4L2553Y
Zip file as originally requested by Revolution
I followed http://www.robmcghee.com/android/creating-an-android-update-zip-package/ - Thinking back I realise I probably didn't need to sign it, whoops
Code:
## Create folders dump, dump/system, dump/META-INF/com/google/android
cd dump
adb pull /system system
## Edited /META-INF/com/google/android/update-script with:
## show_progress 0.1 0
##
## copy_dir PACKAGE:system SYSTEM:
## set_perm_recursive 0 0 0755 0644 SYSTEM:app
## show_progress 0.1 10
##
## Zip system and META-INF folders into gnsys.zip
## Signed using testsign.jar
Available here: http://www.megaupload.com/?d=KXFYSMT2 or http://www.filesonic.com/file/3935308085/gnsys-signed.zip
If anyone spots anything wrong with either my commands or my files, please reply with what I did wrong so I can learn from that, thanks.
el3ctrik said:
Going to preface this with the fact that I'm relatively new to the dev scene. I'm still learning, but we all learn by doing right?
This dump is taken from my rooted UK retail O2 Galaxy Nexus. Rooted using adb method (not superboot method) - http://forum.xda-developers.com/showthread.php?t=1352004
Not entirely positive these are done perfectly (especially the .zip) but I think that may creatable from my dd image anyways. I'd appreciate someone with dev experience looking over these and okaying them, and maybe regular users staying away from trying to do anything with these until someone more experienced says they're alright?
I just figured that seeing I uploaded these for 2 people I may as well make them publically available for all.
I'm also including the steps I took inside code tags for anyone to point out any mistakes I may have made.
DD Image as requested by Maximilian Mary:
Code:
su
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/system of=/sdcard/galaxynexussystem.img
Available here: http://www.megaupload.com/?d=KXFYSMT2
Zip file as originally requested by Revolution
I followed http://www.robmcghee.com/android/creating-an-android-update-zip-package/ - Thinking back I realise I probably didn't need to sign it, whoops
Code:
## Create folders dump, dump/system, dump/META-INF/com/google/android
cd dump
adb pull /system system
## Edited /META-INF/com/google/android/update-script with:
## show_progress 0.1 0
##
## copy_dir PACKAGE:system SYSTEM:
## set_perm_recursive 0 0 0755 0644 SYSTEM:app
## show_progress 0.1 10
##
## Zip system and META-INF folders into gnsys.zip
## Signed using testsign.jar
Available here: http://www.megaupload.com/?d=KXFYSMT2
If anyone spots anything wrong with either my commands or my files, please reply with what I did wrong so I can learn from that, thanks.
Click to expand...
Click to collapse
Thanks
Let my ROMs rock
---------- Post added at 03:46 PM ---------- Previous post was at 03:34 PM ----------
netchip said:
Thanks
Let my ROMs rock
Click to expand...
Click to collapse
UPDATE: I've unpacked the img file and imported the proprietary files.
So we can make ROMs
It appears MU is returning an error if you try to access the files.
I've uploaded the 2 files to other mirrors too, apologies if anyone has tried to grab these and failed.
I'm about to have some fun with this right now , i'm home from school i'm about to eat & work on something .
netchip said:
UPDATE: I've unpacked the img file and imported the proprietary files.
So we can make ROMs
Click to expand...
Click to collapse
I don't get it. What's here that's not at http://code.google.com/android/nexus/drivers.html#maguroitl41d ?
Sent from my Nexus S using XDA App
matt2053 said:
I don't get it. What's here that's not at http://code.google.com/android/nexus/drivers.html#maguroitl41d ?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
That arent not all the needed files
Sent from my GT-I9100
Can I ask for boot image as well?
mike1986. said:
Can I ask for boot image as well?
Click to expand...
Click to collapse
You can generate your own with the AOSP repos
Sent from my GT-I9100
netchip said:
You can generate your own with the AOSP repos
Sent from my GT-I9100
Click to expand...
Click to collapse
Got one already, thanks
Why do you work with every single device , just saying ? Are you going to get the Galaxy Nexus , cause your doing work for the Amaze also now . I don't get it .
mike1986. said:
Got one already, thanks
Click to expand...
Click to collapse
Revolution said:
Why do you work with every single device , just saying ? Are you going to get the Galaxy Nexus , cause your doing work for the Amaze also now . I don't get it .
Click to expand...
Click to collapse
Because I like what I'm doing Is there any problem with it?
Nope , just asking a question .
mike1986. said:
Because I like what I'm doing Is there any problem with it?
Click to expand...
Click to collapse
@mike1986 - You cooking up anything for the DHD?
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.
EDIT: do not convert updater to update script. Your rom will not boot. When asked decline.
Update: now supports T-Mobile, AT&T and Sprint Models Enjoy!
*This is just a quick fix mod to bring support to the dsixda's android kitchen
*This for new users that would like to edit their favorite rom
*I did not make this software all i did was simply extracted the stock recovery.img and added support for our device.
Credits to the kitchen be longs to dsixda and the orginal thread here: http://forum.xda-developers.com/showthread.php?t=633246
MOUNTING POINTS:
/boot emmc /dev/block/mmcblk0p20
/system ext4 /dev/block/mmcblk0p16
/data ext4 /dev/block/mmcblk0p29
/cache ext4 /dev/block/mmcblk0p18
/recovery emmc /dev/block/mmcblk0p21
/sdcard datamedia /dev/null
/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
VIIRU§ said:
*This is just a quick fix mod to bring support to the dsixda's android kitchen
*This for new users that would like to edit their favorite rom
*I did not make this software all i did was simply extracted the stock recovery.img and added support for our device.
Credits to the kitchen be longs to dsixda and the orginal thread here: http://forum.xda-developers.com/showthread.php?t=633246
You can get the edited kitchen that supports our device here: https://www.dropbox.com/s/yytrca4l72khtrw/Android-Kitchen-0.223_MODDED.tar.gz
MOUNTING POINTS:
/boot emmc /dev/block/mmcblk0p20
/system ext4 /dev/block/mmcblk0p16
/data ext4 /dev/block/mmcblk0p29
/cache ext4 /dev/block/mmcblk0p18
/recovery emmc /dev/block/mmcblk0p21
/sdcard datamedia /dev/null
/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
Click to expand...
Click to collapse
Might want to add the model_variants too
Posting this here, as well. Just in case someone finds it useful.
You can get Heimdall 1.4 for Win32 here:
https://bitbucket.org/benjamin_dobell/heimdall/downloads/heimdall-suite-1.4.0-win32.zip
Just wiped and returned to a completely virgin MDL install on my device. Then used Heimdall to grab the PIT file. You can download the file here:
https://dl.dropboxusercontent.com/u/21231693/gs4.pit
I then used the Heimdall to print the PIT information which you can download here:
https://dl.dropboxusercontent.com/u/21231693/gs4PIT_info.txt
Mr Impossible said:
Might want to add the model_variants too
Click to expand...
Click to collapse
I only added support for The T-Mobile GS4 not any other variants of the Galaxy S4
Sent from my SGH-M919 using xda premium
VIIRU§ said:
*This is just a quick fix mod to bring support to the dsixda's android kitchen
*This for new users that would like to edit their favorite rom
*I did not make this software all i did was simply extracted the stock recovery.img and added support for our device.
Credits to the kitchen be longs to dsixda and the orginal thread here: http://forum.xda-developers.com/showthread.php?t=633246
You can get the edited kitchen that supports our device here: https://www.dropbox.com/s/yytrca4l72khtrw/Android-Kitchen-0.223_MODDED.tar.gz
MOUNTING POINTS:
/boot emmc /dev/block/mmcblk0p20
/system ext4 /dev/block/mmcblk0p16
/data ext4 /dev/block/mmcblk0p29
/cache ext4 /dev/block/mmcblk0p18
/recovery emmc /dev/block/mmcblk0p21
/sdcard datamedia /dev/null
/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
Click to expand...
Click to collapse
How did you get the mount points? I have a Sprint GS4 and I have spent several hours trying to pull the mount points so I can add Kitchen support for the Sprint GS4 but have been unsuccessful.
I have tried cat /proc/mounts from adb shell and it doesn't return what I would expect. I have also looked at the .FSTAB file in system/ect and am unsure how to interpret it to get mount points in a form like you have listed.
Any help would be greatly appreciated.
Landon4444 said:
How did you get the mount points? I have a Sprint GS4 and I have spent several hours trying to pull the mount points so I can add Kitchen support for the Sprint GS4 but have been unsuccessful.
I have tried cat /proc/mounts from adb shell and it doesn't return what I would expect. I have also looked at the .FSTAB file in system/ect and am unsure how to interpret it to get mount points in a form like you have listed.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
I pulled if from the stock recovery image... thats how I do it. I can add support for your device too if u like
Sent from my SGH-M919 using xda premium
VIIRU§ said:
I pulled if from the stock recovery image... thats how I do it. I can add support for your device too if u like
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
That would be awesome. If you wouldn't mind could you teach me how to pull it myself from the stock recovery? I am trying to do as much as I can to learn but I have hit a wall on this one.
Landon4444 said:
That would be awesome. If you wouldn't mind could you teach me how to pull it myself from the stock recovery? I am trying to do as much as I can to learn but I have hit a wall on this one.
Click to expand...
Click to collapse
I know 2 different ways to do this the manually way and the lazy. And I myself much rather use option 2. Lol.... so do u have ubuntu and your build environment setup?
Sent from my SGH-M919 using xda premium
VIIRU§ said:
I know 2 different ways to do this the manually way and the lazy. And I myself much rather use option 2. Lol.... so do u have ubuntu and your build environment setup?
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
I really appreciate you taking the time to help me with this. I do have Ubuntu and my build environment set up as described in some of the guides on XDA.
Landon4444 said:
I really appreciate you taking the time to help me with this. I do have Ubuntu and my build environment set up as described in some of the guides on XDA.
Click to expand...
Click to collapse
Okay download a sprint GS4 rom and a AT&T GS4 and pull the build.prop from both and upload them and send me the link.
Sent from my SGH-M919 using xda premium
VIIRU§ said:
Okay download a sprint GS4 rom and a AT&T GS4 and pull the build.prop from both and upload them and send me the link.
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
I just sent you a PM with a Google drive link to the Sprint and ATT build.prop files.
I also followed a procedure to extract the recovery.img using an advanced option in the kitchen in an effort to get the mount points from the recovery.fstab file which did not give me what I was hoping for. I have also put the recovery.fstab file on google drive.
Landon4444 said:
I just sent you a PM with a Google drive link to the Sprint and ATT build.prop files.
I also followed a procedure to extract the recovery.img using an advanced option in the kitchen in an effort to get the mount points from the recovery.fstab file which did not give me what I was hoping for. I have also put the recovery.fstab file on google drive.
Click to expand...
Click to collapse
That's wat u need to get the mount points from recovery.fstab of the device u want to add support for. Im not sure why u getting that error if you pulled that from jfltespr recovery.img but no worries I added support sprint and att version....
Sent from my SGH-M919 using xda premium
VIIRU§ said:
That's wat u need to get the mount points from recovery.fstab of the device u want to add support for. Im not sure why u getting that error if you pulled that from jfltespr recovery.img but no worries I added support sprint and att version....
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
Thanks. I guess my recovery.fstab file should not have come out like that?
Landon4444 said:
Thanks. I guess my recovery.fstab file should not have come out like that?
Click to expand...
Click to collapse
Lol no... and your welcome...
Sent from my SGH-M919 using xda premium
VIIRU§ said:
Update: now supports T-Mobile, AT&T and Sprint Models Enjoy!
*This is just a quick fix mod to bring support to the dsixda's android kitchen
*This for new users that would like to edit their favorite rom
*I did not make this software all i did was simply extracted the stock recovery.img and added support for our device.
Credits to the kitchen be longs to dsixda and the orginal thread here: http://forum.xda-developers.com/showthread.php?t=633246
Download: https://www.dropbox.com/s/fg4kb1eor5di4bn/Android-Kitchen-0.223_rev2.tar.gz
MOUNTING POINTS:
/boot emmc /dev/block/mmcblk0p20
/system ext4 /dev/block/mmcblk0p16
/data ext4 /dev/block/mmcblk0p29
/cache ext4 /dev/block/mmcblk0p18
/recovery emmc /dev/block/mmcblk0p21
/sdcard datamedia /dev/null
/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
Click to expand...
Click to collapse
You tested?
Enviado desde mi SGH-I337M usando Tapatalk 2
So did you get it working?
I had already updated the kitchen with necessary files for AT&T, Rogers/Bell/Telus, T-Mobile and I9505 as well as various other script files that needed changing. However, it gets stuck at boot screen.
https://github.com/dsixda/Android-Kitchen/tags
My discussion here:
http://forum.xda-developers.com/showthread.php?t=2283070
EDIT: Please don't distribute entire versions of my kitchen that have been modified and passed off as a particular version number. Only submit individual files.
There's no need to test the points are just the same as our only a minor edit was need im 99.999% sure it will work all USA versions stated in the op
Sent from my SGH-M919 using xda premium
dsixda said:
So did you get it working?
I had already updated the kitchen with necessary files for AT&T, Rogers/Bell/Telus, T-Mobile and I9505 as well as various other script files that needed changing. However, it gets stuck at boot screen.
https://github.com/dsixda/Android-Kitchen/tags
My discussion here:
http://forum.xda-developers.com/showthread.php?t=2283070
EDIT: Please don't distribute entire versions of my kitchen that have been modified and passed off as a particular version number. Only submit individual files.
Click to expand...
Click to collapse
Yea it's working. I edited a rom on my tmo version and my cousin's AT&T version. This was never intended to as a distribution of your work. Nor have I ever taken credit for if. In fact I'd much rather you test it and update the official thread.
No credit needed I just figured you was retired like you thread started so I added support to meet the needs of my own laziness. I was talking to a new kernel dev and told him he couldn't use the kitchen to split boot.imgs faster. So I posted thinking others here might want it. Then a sprint user wanted help abd about 15 AT&T user PM me for support and well here it is lol. Thats the story feel free to take over from here....
Sent from my SGH-M919 using xda premium
Awesome, great work!
Can you post an updater-script from these files, so that I can compare? Thanks.
dsixda said:
Awesome, great work!
Can you post an updater-script from these files, so that I can compare? Thanks.
Click to expand...
Click to collapse
Looks like their is an error in converting the updater to an update I didn't catch it cause I always manually edit my updater. I'm checking your verify_update_ script. Then its converting to an update the script is reporting part of the updater that it should not be...
EDIT: it's also rewriting the script as
format("ext4", "EMMC", "/dev/block/mmcblk0p16");
mount("ext4", "EMMC", "/dev/block/mmcblk0p16", "/system"); "0 /system/
instead of
format("ext4", "EMMC", "/dev/block/mmcblk0p16", "0", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p16", "/system");
Hi, here is tool for making flashable zip in few commands! No need root! In few commands your rom is ready for sharing or flashing with CMW ! You can dump any rom! NOTE: all your rom changes which is in your phone will be included in rom.zip (for example busybox, su...etc)! Tool will be usefull for dumping next Sony stock rom, but allso all rom is supported! Enjoy!
For no rooted devices:
adb push romgen /data/local/tmp/
adb shell
cd /data/local/tmp
chmod 755 romgen
Code:
./romgen C6903 honami /dev/block/platform/msm_sdcc.1/by-name/system /dev/block/platform/msm_sdcc.1/byname/userdata /dev/block/platform/msm_sdcc.1/by-name/cache [COLOR="Red"]/dev/null[/COLOR] /storage/removable/sdcard1/rom.zip
/dev/null must be used as a boot partition since no rooted devices have no access to these device!
For rooted devices:
adb push romgen /data/local/tmp/
adb shell
su
cd /data/local/tmp
chmod 755 romgen
Code:
./romgen C6903 honami /dev/block/platform/msm_sdcc.1/by-name/system /dev/block/platform/msm_sdcc.1/byname/userdata /dev/block/platform/msm_sdcc.1/by-name/cache [COLOR="Red"]/dev/block/platform/msm_sdcc.1/by-name/boot[/COLOR] /storage/removable/sdcard1/rom.zip
Download tool:
http://forum.xda-developers.com/showthread.php?t=2533585
munjeni said:
Hi, here is tool for making flashable zip
Click to expand...
Click to collapse
is it stable already?
I mean the Meta-INF generated completely?
thanks gonna try this if the tool complete
nelikp said:
is it stable already?
I mean the Meta-INF generated completely?
thanks gonna try this if the tool complete
Click to expand...
Click to collapse
Yesterday I noticed bug There is bug when folder is empty or when symlink is inside folder but there no other files! So when tool generate zip these folder is missing in zip but updater-script have line "set perm to folder" which not exist, so installation aborting because a missing folder Will try to solve them soon! Do not flash generated zip since you will get boot loop (you can only if you add missing folders to zip)! I will make new version soon, hope clean!
New version is out! Hope all bugs solved! Bug is solved by creating empty file .placeholder to all existing folders so zip for sure now have all mised folders, than placeholders is auto removed at finish of the installation
I am hope eerything is right now, but I will test and let you know if generated zip is installable with sucess!
New working version finaly, sorry! Now I tested tool and found another 2 bugs, first one was "zip fail to store file which contain special characters like *()...etc", and seccond one was wrong format of the permssions in updater-scrip. Now all things is solved, I have tested tool, tried to install generated zip, installed zip, and bum. Everything is ok now, enjoy!
Hi mate...nice to see you here
If I'm correct, you have some great work and kernels in your biography
Sent from my C6903 using Tapatalk
funky0308 said:
Hi mate...nice to see you here
If I'm correct, you have some great work and kernels in your biography
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
No space left in my signature :laugh: One oftopic question, anyone have info when Sony will anounce 4.4.2 ?
munjeni said:
No space left in my signature :laugh: One oftopic question, anyone have info when Sony will anounce 4.4.2 ?
Click to expand...
Click to collapse
Yeah...I'm using Tapatalk so can't see...but, as I said, I know who you are and we will be very happy if you join Z1 development :thumbup:
It should be out (most likely) in a first few days on april (let just hope it won't be first April and we.won't be April's fools )
Some of Z2 apk files are already out and if that guy who already post few things managed to post Z2 system dump - we could have something even earlier
Sent from my C6903 using Tapatalk
I am allready in development on Z1 Compact but curently I have problem in semc_colorizable (going to start working in MIUI), so first of all I need to solve all things related to the recompiling framework-res and full removal of the semc_generic_uxp... by now have no luck Did you have luck on framework-res on Z1 using apktool ? I have managed to recompile/compile them by now, but boot loop on colorizable things since my modificaions on framework / framework-res is not complete .
munjeni said:
I am allready in development on Z1 Compact but curently I have problem in semc_colorizable (going to start working in MIUI), so first of all I need to solve all things related to the recompiling framework-res and full removal of the semc_generic_uxp... by now have no luck Did you have luck on framework-res on Z1 using apktool ? I have managed to recompile/compile them by now, but boot loop on colorizable things since my modificaions on framework / framework-res is not complete .
Click to expand...
Click to collapse
@munjeni bro, you can try out the Advanced APKtool by @BDFreak bro for the framework-res issues. It's compatible with z1 Compact.
http://forum.xda-developers.com/showthread.php?t=2639400
@munjeni, nice tool, but I need help. I get this error in CWM log every time I try to install my zip; "l:Can't partition non mmcblk device: /devices/msm_sdcc.2/mmc_host
What do I need to do to the updater script? I tried replacing the mount system bit with;
run_program("/sbin/busybox", "mount", "/system");
package_extract_dir("system", "/system");
but I had no luck.
Probably you pased bad command to the romgen since you say /devices/msm_sdcc.2/mmc_host !!! Double check first post before you going to generate zip! Or probably you using an bad cwm which have bad fstab! If no of these 2 simptoms is true than for sure you have modified updater-script by your own way which probably is not ok! Hope this help.
munjeni said:
Probably you pased bad command to the romgen since you say /devices/msm_sdcc.2/mmc_host !!! Double check first post before you going to generate zip! Or probably you using an bad cwm which have bad fstab! If no of these 2 simptoms is true than for sure you have modified updater-script by your own way which probably is not ok! Hope this help.
Click to expand...
Click to collapse
Okay so it's the bad fstab, thanks man
Can anyone make rom for my karbon a39 HD
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.