Develop Bugs

[KERNEL] Universal external lagfix (btrfs,jfs,ext4,reiserfs)

This lagfix will mount /data /dbdata /cache on your external SD almost whichever
FS you choose.
You must partition your SD with 4 partitions in this order:
primary FAT32 (size you wish)
primary your_FS 2Gb for /data
primary your_FS 128Mb for /dbdata
primary your_FS 30Mb for /cache
Supported filesystems are btrfs, ext4, jfs, reiserfs
Sizes are given as indication
This kernel mounts filesystems noatime,nodiratime
Kernel includes busybox full and su. adbd starts at boot by default.
You can even mix and match FS like reiserfs on dbdata, ext4 on data and jfs on cache
How to do:
1: partition your external SD appropriately and format it (using i.e. http://partedmagic.com/)
2: flash zImage_0.1 as kernel with Heimdall
or alternatively flash zImage_0.1.tar with Odin
Kernel can be found at http://llorien.org/samsung_galaxys/jpm/universal
This will obviously wipe your data, if you don't copy it first.
I only tested this on the international Samsung Galaxy S GT-I9000 running froyo JPM.
NOTE: Do not flash unnumbered versions
If you want to revert back to the normal behavior, just flash a stock jpm kernel and you should be fine.

Well, this seems very promising.
Thank you Nikademus.
+1
What do you mean by unnumbered versions?

And what about battery life on HD2 if filesystem is on SD it drains more battery?

nikademus said:
This lagfix will mount /data /dbdata /cache on your external SD almost whichever
FS you choose.
You must partition your SD with 4 partitions in this order:
primary FAT32 (size you wish)
primary your_FS 2Gb for /data
primary your_FS 128Mb for /dbdata
primary your_FS 30Mb for /cache
Supported filesystems are btrfs, ext4, jfs, reiserfs
Sizes are given as indication
This kernel mounts filesystems noatime,nodiratime
Kernel includes busybox full and su. adbd starts at boot by default.
You can even mix and match FS like reiserfs on dbdata, ext4 on data and jfs on cache
How to do:
1: partition your external SD appropriately and format it (using i.e. http://partedmagic.com/)
2: flash zImage_0.1 as kernel with Heimdall
or alternatively flash zImage_0.1.tar with Odin
Kernel can be found at http://llorien.org/samsung_galaxys/jpm/universal
This will obviously wipe your data, if you don't copy it first.
I only tested this on the international Samsung Galaxy S GT-I9000 running froyo JPM.
NOTE: Do not flash unnumbered versions
If you want to revert back to the normal behavior, just flash a stock jpm kernel and you should be fine.
Click to expand...
Click to collapse
Can you somehow make this automated? Not a lot of people here are on linux & repartitioning is not really everyone's cup of tea.
Thnaks.

Some bugs:
1.Tried o flash zImage_0.1.tar and that did corrupt the phone system, so beware!!
The zImage in the tar file is named zImage_0.1, it should be named zImage (more on this later).
2.Extracted zImage_0.1.tar and renamed zImage_0.1 to zImage and added it to a tar file using 7-zip and tried using Odin, that did not work, Odin would hang on flashing zImage.
3. Downloaded zImage_0.1 and renamed that to zImage and flashed using Heimdall, this worked, but the phone seemed to continue scan the external SD-card.
4. Powered down the phone and did a cache wipe and a factory reset and rebooted the phone, it booted but then got to a black screen with the return-key and menu-key on all the time.
The card was partitioned using Partedmagic in external card-reader.
Will try again now and report back.

eclair or froyo ?
hi
Can't read anywhere.
Is this lagfix for eclair rom or froyo ?
It seems the mounbt point of external sdcard isn't just the same on those roms.
Op, could you make the light, please ?
Thanks

deli_gt said:
And what about battery life on HD2 if filesystem is on SD it drains more battery?
Click to expand...
Click to collapse
That does not seem to really affect battery usage.

ragin said:
Can you somehow make this automated? Not a lot of people here are on linux & repartitioning is not really everyone's cup of tea.
Thnaks.
Click to expand...
Click to collapse
That is planned, although you will probably have to put a config file somewhere to define filesystems you want.

[Ramad] said:
Some bugs:
1.Tried o flash zImage_0.1.tar and that did corrupt the phone system, so beware!!
The zImage in the tar file is named zImage_0.1, it should be named zImage (more on this later).
Click to expand...
Click to collapse
Well, I just verified and it's called zImage, not zImage_0.1
[email protected]:~/galaxy$ tar xvf zImage_0.1.tar
zImage
2.Extracted zImage_0.1.tar and renamed zImage_0.1 to zImage and added it to a tar file using 7-zip and tried using Odin, that did not work, Odin would hang on flashing zImage.
Click to expand...
Click to collapse
I don't know what created this. But I haven't tested with Odin yet.
3. Downloaded zImage_0.1 and renamed that to zImage and flashed using Heimdall, this worked, but the phone seemed to continue scan the external SD-card.
Click to expand...
Click to collapse
You don't need to rename it to flash with Heimdall.
What do you mean by phone seems to continue scan the external SD?
4. Powered down the phone and did a cache wipe and a factory reset and rebooted the phone, it booted but then got to a black screen with the return-key and menu-key on all the time.
The card was partitioned using Partedmagic in external card-reader.
Will try again now and report back.
Click to expand...
Click to collapse
Did you format the filesystems?

@nikademus
Here is the deal...The zImage_0.1.tar that can be downloaded from the link you provided is not a tar file but a Gzip file, when extracted then there is what appears to be a file named zImage_0.1, this is not a file but a tar file, that is missing the tar extension, by adding the tar extension, i.e renaming it to zImage_0.1.tar then it can be flashed using Odin. The majority of us are using windows, and some of us are using Linux and OSX where these archives might be read right by the operating system, but in windows it can only be checked by using winrar or 7-zip.
I'm not a novice Windows or Linux user, I know enough, and offcourse I did format the 3 partitions as jfs.

Well, I don't know how you have got a gzipped file but I can ensure you that the tar file is a real tar file. I don't use windows at all, so it's a little bit hard for me to test on windows to find the reason behind this.

@nikademus
Details of the zImage_0.1.tar when downloaded from http://llorien.org/samsung_galaxys/jpm/universal/ :
Uploaded with ImageShack.us
Details when the zImage_0.1.tar is extracted:
Uploaded with ImageShack.us
.tar extension added:
Uploaded with ImageShack.us
Details on the file above, viewed by winrar (se the zImage inside it, now this tar file can be flashed using Odin):
Uploaded with ImageShack.us
I hope that these pictures does show what I mean.

nikademus said:
Well, I don't know how you have got a gzipped file but I can ensure you that the tar file is a real tar file. I don't use windows at all, so it's a little bit hard for me to test on windows to find the reason behind this.
Click to expand...
Click to collapse
He's right. Although it's strange that "tar xvf" would extract without the z option (pipe through gzip), but if you rename the file to .tar.gz, then gunzip will work on it, and more importantly, 'file' identifies it as a gzipped file:
[email protected]:~/Downloads$ ls -l zImage_0.1.tar
-rw-r--r-- 1 carl carl 5704623 2010-10-29 21:32 zImage_0.1.tar
[email protected]:~/Downloads$ file zImage_0.1.tar
zImage_0.1.tar: gzip compressed data, from Unix, last modified: Fri Oct 29 13:42:54 2010
[email protected]:~/Downloads$
Click to expand...
Click to collapse
then, rename to .tar.gz and gunzip, and identify again:
[email protected]:~/Downloads$ mv zImage_0.1.tar zImage_0.1.tar.gz
[email protected]:~/Downloads$ gunzip zImage_0.1.tar.gz
[email protected]:~/Downloads$ file zImage_0.1.tar
zImage_0.1.tar: POSIX tar archive (GNU)
[email protected]:~/Downloads$
Click to expand...
Click to collapse

cmf said:
He's right.
Click to expand...
Click to collapse
Thanks, at last
I was trying to point out that the file can be flashed by Heimdall but not by Odin, Odin can only flash tar files, if you flash the file in it's current stat then it will corrupt the system and when the majority here are using Odin this should have been taken seriously, but it appear that it does not matter, unless a member reporting a bug has been spaming the forum and has a load of posts to backup his words.
I'm done testing this release...good luck.

Well, I must admit this is quite strange because this is not gzipped. Which program did you use to download the file? I would say it's probably because the web server compresses pages using gzip to reduce bandwidth and the program who fetched the file did not uncompress the file like it should have done.

nikademus said:
Well, I must admit this is quite strange because this is not gzipped. Which program did you use to download the file? I would say it's probably because the web server compresses pages using gzip to reduce bandwidth and the program who fetched the file did not uncompress the file like it should have done.
Click to expand...
Click to collapse
I used Google Chrome on Ubuntu Maverick x64. I'll try wget and see what happens, but that's an interesting thought regarding mod_gzip or whatever the apache extension is called.
Regardless, perhaps it would be best to supply a .tgz instead? What's the point in tar-ing a single file ? The idea of tar is to pretty much concatenate multiple files into a single file, without compression, isn't it?

cmf said:
I used Google Chrome on Ubuntu Maverick x64. I'll try wget and see what happens, but that's an interesting thought regarding mod_gzip or whatever the apache extension is called.
Click to expand...
Click to collapse
I am not using apache, but the idea is about the same.
Regardless, perhaps it would be best to supply a .tgz instead? What's the point in tar-ing a single file ? The idea of tar is to pretty much concatenate multiple files into a single file, without compression, isn't it?
Click to expand...
Click to collapse
Because Odin only understands .tar format. If you run from linux, just download the zImage_0.1 with tar, you can flash this one with heimdall

Same with wget:
[email protected]:~/Downloads$ wget http://llorien.org/samsung_galaxys/jpm/universal/zImage_0.1.tar
--2010-10-29 23:09:29-- http://llorien.org/samsung_galaxys/jpm/universal/zImage_0.1.tar
Resolving llorien.org... 206.251.244.96
Connecting to llorien.org|206.251.244.96|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5704623 (5.4M) [application/octet-stream]
Saving to: `zImage_0.1.tar'
100%[==========================================================>] 5,704,623 332K/s in 13s
2010-10-29 23:09:43 (442 KB/s) - `zImage_0.1.tar' saved [5704623/5704623]
[email protected]:~/Downloads$ file zImage_0.1.tar
zImage_0.1.tar: gzip compressed data, from Unix, last modified: Fri Oct 29 13:42:54 2010
[email protected]:~/Downloads$
Click to expand...
Click to collapse

nikademus said:
I am not using apache, but the idea is about the same.
Because Odin only understands .tar format. If you run from linux, just download the zImage_0.1 with tar, you can flash this one with heimdall
Click to expand...
Click to collapse
Ah, fair enough.
Strange then!

BTW, "tar xvf" *does* still work on the apparently gzipped file. Which is weird. Unless GNU tar is just being 'clever' by detecting the gzip compression..
At first I was just looking at your output from before where you did tar xvf, but I just tried it myself on the supposedly gzip file. Weird.

[GUIDE] Noob Friendly RFS Browsing/Extracting Guide

Ok guys,
So after having seen a million and one questions on how to extract RFS files and all the complex answers we keep getting on mounting rfs files in linux and blah blah blah (all a waste of time if all you need is to view/extract files from an RFS file from some firmware)... and now there is no excuse for those few requesting other members to extract stuff for them.. you can do it yourself!
Here is the easy/fast way to do it without having to go through all the trouble
NOTE: This, mind you is mainly for extracting/viewing. Not for editing RFS files.
Go to:
-http://www.magiciso.com/
-Download MagicISO (its free trial but that don't matter for viewing/extracting)
-Install
-Open MagicISO
-Hit File->Open
-In the section "Files of type:" - Click the drop down and select "All Files (*.*)"
-Select RFS file of your choosing (For example: factoryfs.rfs where all firmware apps are located)
and..
VIOLA!
Browse/Extract anything you need... No hassles.
To extract you can simply click and drag to another folder/desktop as needed
Cheers!

TY for this guide. Unlike htc hd2 forums I really have hard time getting answers to my questions in tab forums so this kind of guides helps me very much. Again TY.

You sir, are very welcome!
Glad it helped. Thats what we're here for!

Make it a sticky !

add it to the wiki rather than making this post sticky. http://modadroid.com/index.php/Main_Page

Just tried it with UltraISO. It seems to work, too.
Thanks

tovarish said:
add it to the wiki rather than making this post sticky. http://modadroid.com/index.php/Main_Page
Click to expand...
Click to collapse
Its locked for editting

MagicISO didn't work for me. I copied the .rfs file to a directory on Linux and mounted as read/write and was able to modify the file system. Then, I unmounted it and flashed the changes to my GT using Heimdall.
Sent from my SCH-I800 using XDA App

chuckbeasley said:
MagicISO didn't work for me. I copied the .rfs file to a directory on Linux and mounted as read/write and was able to modify the file system. Then, I unmounted it and flashed the changes to my GT using Heimdall.
Sent from my SCH-I800 using XDA App
Click to expand...
Click to collapse
This guide is only for browsing and extracting RFS files hence the name. It is not for modification.

I'm aware of what the original post was explaining. I tried that solution and it failed. That's why I suggested another method. MagicISO didn't work for me. If others try it and it doesn't work for them either, at least they have another solution that will always work and the option to modify the file system, if they so choose.
Sent from my SCH-I800 using XDA App

chuckbeasley said:
I copied the .rfs file to a directory on Linux and mounted as read/write and was able to modify the file system. Then, I unmounted it and flashed the changes to my GT using Heimdall.
Click to expand...
Click to collapse
That's the Linux command line, right ?
#mount -o loop factoryfs.rfs /mnt/rfs
Otherwise on Mac OS X, you can use this:
#sudo mkdir /Volumes/RFS
#sudo hdiutil attach -imagekey diskimage-class=CRawDiskImage -nomount ARCHIVE.rfs
#sudo mount_msdos /dev/disk{n} /Volumes/RFS

daniel.weck said:
That's the Linux command line, right ?
#mount -o loop factoryfs.rfs /mnt/rfs
Otherwise on Mac OS X, you can use this:
#sudo mkdir /Volumes/RFS
#sudo hdiutil attach -imagekey diskimage-class=CRawDiskImage -nomount ARCHIVE.rfs
#sudo mount_msdos /dev/disk{n} /Volumes/RFS
Click to expand...
Click to collapse
Please don't forget when you finished on OSX to run:
sudo umount /Volumes/RFS/
hdiutil detach /dev/disk{n}

i can't open the factoryfs.rfs of a samsung galaxy s. can anyone send me the /lib folder from galaxy s and the flash apk in the app folder...thanks

seven2099 said:
Ok guys,
-In the section "Files of type:" - Click the drop down and select "All Files (*.*)"
-Select RFS file of your choosing (For example: factoryfs.rfs where all firmware apps are located)
and.. VIOLA!
Browse/Extract anything you need... No hassles.
Click to expand...
Click to collapse
Didn't work for me either. MagicISO did extract four files only from factoryfs.rfs.
Two were exe files of significant size... Samsun_Mobile_USB_Driver.exe, and ToolLauncher-Bootstrap.exe.
All the files apk files are probably empedded in the first of those, but no further extraction was possible from the .exe file using MagicISO.
I'm trying to find the origianal VZW Vcast apk files that I stupidly deleted instead of just renaming. I need them so the EC02 update script will run. Any ideas, anyone?

Robin M said:
Didn't work for me either. MagicISO did extract four files only from factoryfs.rfs.
Two were exe files of significant size... Samsun_Mobile_USB_Driver.exe, and ToolLauncher-Bootstrap.exe.
All the files apk files are probably empedded in the first of those, but no further extraction was possible from the .exe file using MagicISO.
I'm trying to find the origianal VZW Vcast apk files that I stupidly deleted instead of just renaming. I need them so the EC02 update script will run. Any ideas, anyone?
Click to expand...
Click to collapse
you could look up the long way of mounting and extracting RFS.. Its a major pain though, why dont you make a post asking for those missing files in the forum.
Better bet.

Robin M said:
Didn't work for me either. MagicISO did extract four files only from factoryfs.rfs.
Two were exe files of significant size... Samsun_Mobile_USB_Driver.exe, and ToolLauncher-Bootstrap.exe.
All the files apk files are probably empedded in the first of those, but no further extraction was possible from the .exe file using MagicISO.
I'm trying to find the origianal VZW Vcast apk files that I stupidly deleted instead of just renaming. I need them so the EC02 update script will run. Any ideas, anyone?
Click to expand...
Click to collapse
I used Root Uninstaller and got rid of a vcastmusic.apk file. It's 4.46mb. Is this what you need?

Where is the thanks button!! It worked for me..!! I needed it!!
one question: I am unable to extract one particular factoryfs.rf of one rom, MagicISO says it is not an image file. Can you help me there?

Use linux disk reader to open ext4 files (even .rfs files can be ext4)
@neo yea magiciso says so on ext4 archives

cdesai said:
Use linux disk reader to open ext4 files (even .rfs files can be ext4)
@neo yea magiciso says so on ext4 archives
Click to expand...
Click to collapse
@cd if i select factoryfs.rfs from linux reader i only get the same single file as the output!! No use yaar

Works for Galaxy Ace's firmwares. Thanks. I'm trying to cook my first ROM for Galaxy Ace (cooper). Wish me luck!

[TUT][20110115][Expert Users & ROM Makers]To add userdata everywhere to your HD2 ROM

[TUT][20110115][Expert Users & ROM Makers]To add userdata everywhere to your HD2 ROM
*FOR EXPERT USERS OR ROM MAKERS ONLY*
*I AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO YOUR DEVICE BY USING THIS*
Features:
- Able to have userdata on NAND or in ext sdcard partition or in /sdcard/.data/data.img
- Check if NAND partition exist
- Check if ext sdcard partition exist
- Resizable data.img (bigger or smaller)
- Able to prioritize data.img, ext or NAND
- Able to copy data from NAND to data.img, or ext to data.img (in this order)
- Write data.log in /sdcard/.data/
- Automatic update data.config if it haven't all options
Click to expand...
Click to collapse
Requirements
Kernel with:
# -File systems: yaffs2, ext2, ext3 (, ext4)
# -MTD partition in /proc/mtd
# -MTD block in /dev/block/mtdblock*
# -SD Card in /sys/block/mmcblk0
InitRD with:
# -/system
# -/proc
# -/sys
# -/data
# -/mfbin
SD Card with first partition as FAT32 or EXT*: mmcblk0p1
SD Card with second partition as EXT*: mmcblk0p2
Click to expand...
Click to collapse
How to use it
In your initrd root
Rename your android init (binary) to init.android
Comment "mount yaffs2 [email protected] /data nosuid nodev noatime nodiratime" in your init.rc
Past mfbin folder
Modify mfbin/.data/data.config with your default setup and "Some variables" in init script
Use new init script and chmod it with 755
Click to expand...
Click to collapse
Download : http://www.multiupload.com/F86WGU6H70
Zip content:
- my initrd.gz example (normally for ManusFreedom or tytung ROM)
- init (extracted from initrd.gz)
- .data folder sample
Click to expand...
Click to collapse
Logical description
To prioritize use data.img over userdata on NAND or ext sdcard partition:
Change data_force_mount to y
To prioritize use ext sdcard partition over userdata on NAND:
Change data_force_mount to n
Change data_ext_priority to y
To prioritize use NAND:
Change data_force_mount to n
Change data_ext_priority to n
Click to expand...
Click to collapse
Use data_copy_to_img=y to copy data from NAND to data.img. If no data on NAND, it try to mount ext partition to copy it to data.img. Works only during creation of data.img (not after).
Click to expand...
Click to collapse
To resize to a bigger data.img (backup your data.img before):
1. If you don't have on sd a directory .data copy .data from install to the root of your sd
2. Open .data/data.config of root of SD Card
3. Change data_size to the size you want in megabytes (recommand not less than 128MB and not over 2GB)
4. Change data_resize to y
5. Boot your phone
6. Wait (time depend)
7. You will be normally under Android
8. You can change data_resize to n for security
To resize to a smaller data.img [CHECK THE FREE SPACE BEFORE SHRINK] (backup your data.img before):
1. If you don't have on sd a directory .data copy .data from install to the root of your sd
2. Open .data/data.config of root of SD Card
3. Change data_size to the size you want in megabytes (recommand not less than 128MB and not over 2GB)
4. Change data_resize to y
5. Change data_force_shrink to y
6. Boot your phone
7. Wait (time depend)
8. You will be normally under Android
8. You can change data_resize and data_force_shrink to n for security
Click to expand...
Click to collapse
Please test it and give feedback.
Thanks meter click .
And if you appreciate my work and want to buy me a drink, please consider making a donation too, thanks.

Added ext sdcard partition support.

manusfreedom said:
Added ext sdcard partition support.
Click to expand...
Click to collapse
Great stuff! I will test it out...

Quick question... how do I create the boot.img using this initrd.gz and the kernel of my choice?

pongster said:
Quick question... how do I create the boot.img using this initrd.gz and the kernel of my choice?
Click to expand...
Click to collapse
the easy way for me is using android itself, put initrd.gz and zimage in /sdcard/boot/
adb shell
mkyaffs2image /sdcard/boot/ /sdcard/boot.img
edit..
this is great, make me so easy creating a rom.. thanks manus

lesjaw said:
the easy way for me is using android itself, put initrd.gz and zimage in /sdcard/boot/
adb shell
mkyaffs2image /sdcard/boot/ /sdcard/boot.img
Click to expand...
Click to collapse
Thanks. I actually created one using mkfs.yaffs2 in linux... but it gave me a kernel error after successfully installing via clockwork... Possible reason as well is the update-script I use... what update-script do you use for your ROM-ZIPs?

pongster said:
Thanks. I actually created one using mkfs.yaffs2 in linux... but it gave me a kernel error after successfully installing via clockwork... Possible reason as well is the update-script I use... what update-script do you use for your ROM-ZIPs?
Click to expand...
Click to collapse
i don't know this for sure, i don't make boot.img for a zip rom, i just put initrd.gz and zimage in boot folder, for update script i use just like raider zip build then compare it with original update script from my original build so i know what i should change in my update script..

lesjaw said:
the easy way for me is using android itself, put initrd.gz and zimage in /sdcard/boot/
adb shell
mkyaffs2image /sdcard/boot/ /sdcard/boot.img
edit..
this is great, make me so easy creating a rom.. thanks manus
Click to expand...
Click to collapse
I actually got the 'NAND kernel open failed' error using another boot.img works though... any ideas to what I'm goofing up?

lesjaw said:
i don't know this for sure, i don't make boot.img for a zip rom, i just put initrd.gz and zimage in boot folder, for update script i use just like raider zip build then compare it with original update script from my original build so i know what i should change in my update script..
Click to expand...
Click to collapse
is your boot folder inside the /system folder? so initrd.gz and zImage inside /system/boot
then you take the META from RaiderX and compare update scripts
before finally creating an update.zip using 1. /system folder and 2. META folder ?

pongster said:
is your boot folder inside the /system folder? so initrd.gz and zImage inside /system/boot
Click to expand...
Click to collapse
No, boot folder is on itself, together with system folder and Meta folder, so we have three folder inside zip
pongster said:
then you take the META from RaiderX and compare update scripts
before finally creating an update.zip using 1. /system folder and 2. META folder ?
Click to expand...
Click to collapse
yes, i need to do that to see if any spesific file permission need to be added

lesjaw said:
No, boot folder is on itself, together with system folder and Meta folder, so we have three folder inside zip
yes, i need to do that to see if any spesific file permission need to be added
Click to expand...
Click to collapse
Thanks.. tried the 3 folders before reading your post... got past the error but its stuck at gogogo...
could you attach the meta folder you use so i can test it out... ?

lesjaw said:
No, boot folder is on itself, together with system folder and Meta folder, so we have three folder inside zip
yes, i need to do that to see if any spesific file permission need to be added
Click to expand...
Click to collapse
so for this manus initrd.gz you just put this in your /boot folder in the romzip and flash away? it must be my update-script then... installing via daf works so i know my system works...

pongster said:
so for this manus initrd.gz you just put this in your /boot folder in the romzip and flash away? it must be my update-script then... installing via daf works so i know my system works...
Click to expand...
Click to collapse
uploading..btw, you can hit me up at gtalk [email protected] rather then we talk about it here..i'm afraid our conversation is getting out of topic from OP thread..

lesjaw said:
uploading..btw, you can hit me up at gtalk [email protected] rather then we talk about it here..i'm afraid our conversation is getting out of topic from OP thread..
Click to expand...
Click to collapse
i know... sorry mods...
back on topic...
did this initrdgz detect your ext partition on sd properly?

New version available (v3)
Added:
- Able to prioritize data.img, ext or NAND
- Able to copy data from NAND to data.img, or ext to data.img (in this order)
- Write data.log in /sdcard/.data/
- Automatic update data.config if it haven't all options

The download file is removed from all servers!!

zooz11 said:
The download file is removed from all servers!!
Click to expand...
Click to collapse
No more direct support for this thread.
You can extract my init script from my updated zip:
http://forum.xda-developers.com/showthread.php?p=11986922#post11986922

Kitchen for HOX

Hi!
i was checking dsixda's Android Kitchen
but he says in topic that doesnt support HOX Rom
HTC One X
- no ROM support, but de-odexing only! (Here is the guide to de-odex)
Click to expand...
Click to collapse
so what kitchen can i use

I use it and it works fine, at least for my needs

madsurfer1 said:
I use it and it works fine, at least for my needs
Click to expand...
Click to collapse
hi!
i can do everything on kitchen but then i have this problem reffered on FAQ
QUESTION: When flashing my ROM I get the error "mount expects 4 args got 3" or similar.
This refers to the fact your mount command takes 4 parameters (e.g. ext4, EMMC, /dev/block/.., /system) and your update-binary file only checks for 3 parameters. You'll have to change the update-binary file to a compatible one, found under the /tools/update_files folder. Just copy the appropriate file and rename to update-binary. e.g. If you're going to be using MTD partitions, copy 'mtd-update-binary' to /META-INF/com/google/android as "update-binary".
Click to expand...
Click to collapse
my english is not so good, so i think i cant understand correctly the solution.
i already copyed the update-binary from my rom.zip to /tools/update_files
i already copyed the update-binary from my rom.zip to /META-INF/com/google/android
but with no sucess.. i did some copy / pasts with that files just to see if ill find a solution, but i have always the same error...
can you or anyone give me a clue / hint to pass this problem ?
i even tryed to create a template in /tools/edify_defs/ just to give support to HOX device in kitchen, but like i said, my english is not so good, and the info i found on the net is not so clear for my understanding :|
any help?
thanks

TOOLS TO WORK ON ROM

Hi!
I let you here some tools to work on ROM.
First One is Brottli (files ROM format) to Ext4, like it say change from brottli format to ext4 format as example system.new.dat.br and system.transfer.list to system.ext4
Brottli_Dat_to_EXT4.zip
Second on ( the one i use more to extract files from ext4 format images) 7z_Ext4_Imgextractor, for this tool you need to extract, enter in work folder, right click on 7z.exe, compatibility and select execute as administrator or it will not work properly.
7z_Ext4_Imgextractor.zip
Third, is the same as 7z_Ext4_Imgextractor.zip but i only use if 7z_Ext4_Imgextractor.zip doesn´t work. Some times extract with a few errors...
Ext4_Imgextractor.zip
And the last one, is a Update.zip, inside you will find system and vendor folders, inside that folder you can paste a directory/file as you find inside the extract image, example if the file is in vendor/etc, you need to create/paste etc directory inside vendor...
Important Only works with directory with 755 permission and files with 644 permission!!!!! You need to know what you are doing...
update.zip
I hope this tools helps you.