yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] dsixda:
I don't know anything about your device, dude. Just copy one from an existing ROM that someone made for your device. Anyways you're asking about a non-Galaxy S phone so you'll probably find more help in the Chef section of the forum or in your device's subforum.
[Galaxy S I9000 Android Development] Gvdn:
Ok thx alot. Sadly no subforum for Gio :(
[Galaxy S I9000 Android Development] krazykipa:
CWM issue

I'm having a big problem using the kitchen with regards to entering recovery in any custom ROM I make using the kitchen.

Once I flash the ROM everything is fine and dandy in the OS itself, works 100% and all customizations work flawlessly, but once I try to reboot into CWM whether via 3Button or extended power menu/adb, CWM gives a ton of errors saying it cannot mount volumes and basically recovery is useless. The errors are numerous, I'll see if I can post a pic if needed. The important one I'm thinking is "E:/unknown volume for path /sdcard" repeated for /data, /system, /cache, everything.

I tried eliminating sources of error by basically just inserting a JVS rom and pasting in a kernel (Semaphore JVS) without any customizations, and the error still occurs.

Any help?
[Galaxy S I9000 Android Development] Cranchh:
I'm having the same problem here with CF-Root-XX_OXA_JVS-v4.1-CWM3RFS, I tried to move to DarkCore_4.0_JVS and the device get into reboots (just after activating lagfix).

its 2 days now that im working on stock rom and trying only to root and deOdex... help?
[Galaxy S I9000 Android Development] bhundven:
Will this work for galaxy s 4g? If not, is there any way I can help to add support for it?
[Galaxy S I9000 Android Development] dsixda:
Sorry for the late reply. Check your build.prop's ro.product.device value. If the name doesn't exist under the kitchen's tools/samsung_files/sgs_variants folder then just create a file there with same name.

Unfortunately I don't have the Galaxy S so I cannot test on my own.
[Galaxy S I9000 Android Development] bhundven:
Looks like the SGH-T959V file exists. Thanks for helping me figure that out!
[Galaxy S I9000 Android Development] erbsmokah:
I am having an issue with wi-fi not be able to connect after i have flashed my build.. and thats about it. I'm not sure whats causing it any ideas?

EDIT:

Was the updater-script, i swapped it out with another and all is well.
[Galaxy S I9000 Android Development] burakgon:
There are problem with kernels. I can't change?
[Galaxy S I9000 Android Development] GuestK0045:
is this supported by the sidekick since it has similiar specs to the samsung vibrant?
[Galaxy S I9000 Android Development] dsixda:
If it's basically the same device then it should support it. Just make sure you have an entry in the kitchen for the ro.product.device value. See the note in the 2nd step in Post #1.
[Galaxy S I9000 Android Development] dsixda:
Hi guys, I've made a rare update to the kitchen. Please visit the main kitchen thread (linked in Post #1) for the download link and release notes.
[Galaxy S I9000 Android Development] prescott66:
What to do in this situation:

I have stock rom for SGS+ I9001 (ROMblabla.TAR.MD5) which contains this files:

adsp.mbn

amss.mbn

boot.img

cache.img.ext4

preload.img.ext4

recovery.img

system.img.ext4

...i cant import this ROM :( i know that this forum is about SGS but SGS+ should work too.

kitchen tells me that they can't find factoryfs.rfs...is there a solution? thx
[Galaxy S I9000 Android Development] dsixda:
By SGS+ you mean SGS2? I already have another thread for that.

http://xdaforums.com/showthread.php?t=1227549

Try renaming system.img.ext4 to factoryfs.img and follow instructions for SGS2. Can't guarantee it will work for the newer devices like the Skyrocket though.
[Galaxy S I9000 Android Development] robogo1982:
No, SGS+ is actually an SGS+ (looks like the I9000 but has a faster CPU and a different graphics unit).
[Galaxy S I9000 Android Development] prescott66:
SGS+ is upgraded I9000 named I9001 with faster CPU.i will try to rename that file and give you now if that works...

EDIT: I have renamed system.img.ext4 to factoryfs.img but without luck :( still get message: can't get factoryfs.rfs

can you take a look on that, please? thanks.
[Galaxy S I9000 Android Development] dsixda:
Try renaming it to factoryfs.rfs (Galaxy S format) instead, not factoryfs.img (Galaxy S2). Also I think the I9001 uses different mount points so it may require updating other files as well.

Unfortunately I'm not much involved in this project anymore (or anything keyboard related) due to a damaged wrist so you will need to figure it out somehow.
[Galaxy S I9000 Android Development] prescott66:
After renaming system.img.ext4 to factoryfs.rfs in ROM's TAR package, i got this:

(after selecting "1" in main menu)

Unpacking PDA.tar.md5 ...
factoryfs.rfs

Warning: No zImage found
scripts/sgs_tarmd5_files_to_working_folder: riadok 100: scripts/rfs_files_to_working_folder: File or directory don't exist
[Galaxy S I9000 Android Development] dsixda:
Rename the boot.img to zImage then..
[Galaxy S I9000 Android Development] prescott66:
renamed boot.img to zImage and i get this:

Unpacking PDA.tar.md5 ...
factoryfs.rfs
zImage

NOTE: Ensure you use a rooted kernel (zImage), such as CF-Root, which
allows flashing of custom ROMs. If you instead decide to flash a
stock kernel then you must use Odin afterwards to flash back a rooted
kernel.

scripts/sgs_tarmd5_files_to_working_folder: riadok 100: scripts/rfs_files_to_working_folder: Directory or dile not exist

Would you like to view this ROM's info (y/n)? (default: y): y

Error: update-script not found, cannot continue

Press Enter to continue

...please help me more :(
[Galaxy S I9000 Android Development] dsixda:
I'll take a look later, but other than that, unfortunately there is nothing more I can do. Kitchen only supports the S and S2 and I don't own your device, so I cannot help much.

Edit: found your error and I will fix it when I get home.

Edit2: Fixed. You can re-download the file. Thanks for letting me know!
[Galaxy S I9000 Android Development] prescott66:
IT WORKS now.greeeat :D:D:D

thank you!

so now it can works with I9001 ROM too.

How-To:

1.)Download I9001 ROM(tar.md5 format)

2.)Rename files in archive:

system.img.ext4 --> factoryfs.rfs

boot.img --> zImage

3.)Import in your kitchen

4.)Enjoy

---------- Post added at 10:22 PM ---------- Previous post was at 09:55 PM ----------

btw next bug(i think) is, when you convert update-script to updater-script, then kitchen dont found info about working folder.it writes that they cant find update-script...
[Galaxy S I9000 Android Development] phone_user:
Thanks for update :)
[Galaxy S I9000 Android Development] dsixda:
Unfortunately for you the kitchen has no info about the I9001 so it is not going to create a proper flashable ROM. It is not a Galaxy S so you might want to ask around the GS+ forum to get it to work. This thread is for Galaxy S only.
[Galaxy S I9000 Android Development] prescott66:
@dsixda, no.before converting update-script to updater-script, kitchen shows me info about my rom ;-)
[Galaxy S I9000 Android Development] dsixda:
Yes, all ROMs will show information about the working folder. However if you flash it for I9001 you will get a black screen because there is no mount point defined in the tools folder. Anyways like I said, please ask in the SGS+ forum for help on that area. This thread is for Galaxy S users.
[Galaxy S I9000 Android Development] jenablinsky:
i have a problem... i'm on cygwin and i move on the kitchen folder, so i type ./menu and this error appear:

why? how can i solve it?
[Galaxy S I9000 Android Development] mbba67:
Hi dsixda, Sorry about your hand hope it gets well. a dumb Q. how to know to build.prop's ro.product.device value. thanks
[Galaxy S I9000 Android Development] dsixda:
Build.prop is directly under the /system folder. You can get the file through adb or just use Root Explorer app to view it.
[Galaxy S I9000 Android Development] mbba67:
sorry again (dumb of me:o) but i cant seem to find "ro.product.device value" in side Build.prop... look every line but nothing.

Can you help me to make the file please, I upload my phone's build.prop file.

EDIT: Solved!! got the ro.product.device value.
[Galaxy S I9000 Android Development] Entropy512:
Does anyone know a workaround for the fact that extracting symlinks from an RFS image never happens properly?

Instead of getting the proper symlinks to toolbox, I get a bunch of oddball binary files, which have a bunch of garbage characters and the name of the link destination. The kitchen, because it didn't see these as symlinks, doesn't create the symlink commands in the updater-script.

I've had this occur with the Infuse (SGH-I997) UCKJ2 build, and with an RFS dump from my Galaxy Player 5.0 (YP-G70)

To get things to work, I had to manually make a tar backup of /system, then make an ext4 image on my Ubuntu machine from that tar backup, then use that as the input to the kitchen.

All of these occur on a machine running Ubuntu 11.10

Also - how do we override the partition map so that the kernel is flashed to the proper place on an unusual device? The Galaxy Player is an unusual device, kind of halfway between a Galaxy S and Galaxy S II in how it is handled.

RFS filesystem (Galaxy S)

Storage is eMMC not STL/BML (Galaxy S II)

Partitions do not match either Galaxy S or GSII - for example, kernel is mmcblk0p11
[Galaxy S I9000 Android Development] lippol94:
Unfortunately the developer shut down the project exactly when he added the first samsung roms compatibility. So not everything is perfect.

For what concern symlinks in the updater-script I suggest you to copy them from another ROM's updater-script, as it's safer and you're sure that works flawlessly.

Edit the flashing point manually. That's the only solution! Plus, you'll get more skilled at this stuff ;)
[Galaxy S I9000 Android Development] dsixda:
Actually the Galaxy S compatibility was added last summer ;) I haven't seen any issues in Linux with symlinks from RFS filesysyem, but I will take a look at it sometime with that version of stock ROM.
[Galaxy S I9000 Android Development] lippol94:
Yep, but it wasn't perfect :p

Now I must say it's great! But the updater-script writing procedure still needs to be done manually.

In fact most of the options available for HTC phone doesn't work properly on Samsung roms (init.d support, copying files on data partition etc).

But really not bad! I love your kitchen! :)
[Galaxy S I9000 Android Development] dsixda:
Yeah the init.d and other kernel-related options are not supposed to work, I think it was mentioned in the kitchen when you select those options.

What do you mean by copying files from data partition? Data/app option should work (at least it does on Galaxy S2).

What needs to be done manually in the updater-script? The basic options require no user intervention.
[Galaxy S I9000 Android Development] Entropy512:
Well, yeah, that's always an option - it's just a bit of a pain. :) Fixing the symlinks is a major pain. In general I just try to stay out of userland, I'm more comfortable down at the bare metal in the kernel. :)

I figured out a workaround, since the last time I used the kitchen to deodex, support for CWM5.x tar-based backups was added:

Make a Nandroid backup

Use that Nandroid backup as the base - kernel will need to be manually added to the flash package at the end of the process, but adding this is a hell of a lot easier than adding the symlinks
[Galaxy S I9000 Android Development] dsixda:
No worries, I was able to reproduce your symlink problem, both in Linux and with MagicISO in Windows. I can have a fix for you in a day or two.

I would NOT recommend copying another updater-script - that doesn't solve the problem, it is a workaround that can lead to other issues if you don't know what you are doing.
[Galaxy S I9000 Android Development] dsixda:
This has now been fixed, please update your kitchen to 0.187. Thanks for your feedback :)
[Galaxy S I9000 Android Development] dsixda:
As the instructions in Post #1 say, do not use non-stock ROMs, such as CyanogenMod. Make sure you read the instructions, don't rush through.
[Galaxy S I9000 Android Development] bunta126:
The ROM we cooked through the kitchen was using the stock SAMSUNG ROM.

That report from the build.prop is showing the ROM that was on the phone when we went to install it.

Is that the reason why the ROM we cooked would not install? If we flash back the original Samsung ROM using ODIN first and then try to reinstall our cooked ROM would that then have the correct partitions recognised?
[Galaxy S I9000 Android Development] dsixda:
Not sure, dude.. but doesn't hurt to try. The parameters in the kitchen are based on stock parameters.
[Galaxy S I9000 Android Development] bunta126:
So we got the cooked ROM to install by flashing the stock samsung ROM back to the device first and after installing a custom kernel the cooked ROM installed fine.

The next problem however is that there is some problem with the root or busybox installation.

When we run adb shell to the device any command we type returns the following response:

C:\>adb shell
$ ls
ls
Öåº▀toolbox├ºé↨═è▒â: error 22
$ df
df
Öåº▀toolbox├ºé↨═è▒â: error 22
$ mount
mount
Öåº▀toolbox├ºé↨═è▒â: error 22
$ cd /sdcard
cd /sdcard
$ ls
ls
Öåº▀toolbox├ºé↨═è▒â: error 22

I've also tried using root access in a file explorer app and it asks for superuser access correctly but then the app fails to work properly with root access.

Any idea what causes this?

We installed chainsDDs root access and added busybox via the kitchen main menu.

UPDATE: Seems each of these commands are just links to the toolbox executable which are not working correctly after building this through the kitchen.

I think we need to recreate all the links in the update-script or something?
[Galaxy S I9000 Android Development] dsixda:
I'm not sure. I have noticed lately that chainsdd's superuser is not working correctly in ROMs.

The other thing to do is, if you're using CFRoot in your ROM, then you don't need to use the option to root or add busybox. I think cfroot already installs it automatically (at least it does on my SGS2).
[Galaxy S I9000 Android Development] bunta126:
We actually built this ROM again from the kitchen without installing root and busybox but it did the same thing.

I can see in the files in /system/bin that several of them are actually executable files and the rest of them are showing as 32 byte data file types. The contents of which show a reference to toolbox but don't seem to be showing as links correctly.

It seems like when the kitchen extracts the files from the source tar and sets up the working folder that these files are not being created as links correctly.

After we build the ROM the files are just data files instead of links.

I have used your kitchen to build another ROM for a different phone type and did not have any such problem so it's rather confusing to me since these are symlinks in the source tar from samsung which flashes onto the phone fine but when building the ROM from the kitchen they are no longer symlinks.
[Galaxy S I9000 Android Development] dsixda:
Did you update to the latest version?? Your toolbox issue was mentioned right before your first post a few days ago.
[Galaxy S I9000 Android Development] dsixda:
@Entropy512 or anybody else - I have not received a single feedback regarding this symlink fix which was done for your issue. It worked for me, but nobody followed up.
[Galaxy S I9000 Android Development] IshouldntbeHere:
does the kitchen support cm9? I couldnt split the boot.img
[Galaxy S I9000 Android Development] dsixda:
Nope, based on the instructions in Post #1 it only supports stock firmware or ROMs made with the kitchen from stock firmware.
[Galaxy S I9000 Android Development] IshouldntbeHere:
Thanks i really need to learn to read.
[Galaxy S I9000 Android Development] jenablinsky:
hey guys how to run it in ubuntu 11.10?
[Galaxy S I9000 Android Development] dsixda:
Hi guys, just made an update to the kitchen to add Mac OS X support for the RFS filesystem used by the Galaxy S.
[Galaxy S I9000 Android Development] alkhafaf:
Hello dsixda

Thanks alot for your kitchen and for this awesome guide.

can u please tell me what is the importance of signing the rom, when i build the rom I am asked to sign. What will the signing do ? any restrictions? And what are the disadvantages of not signing?
[Galaxy S I9000 Android Development] dark_knight35:
Most CWMs require a signed package. I think signing is saver, as it safes the structure of the package in META-INF.
[Galaxy S I9000 Android Development] alkhafaf:
thanks man....:)

---------- Post added at 06:58 PM ---------- Previous post was at 06:22 PM ----------

can i choose the option to optimize all the apk?

I read that some apk files should not be optimized..

From Perka's Guide:

"In apk manager folder /place-apk-here-to-batch-optimize you put

framework-res.apk, twframework-res.apk and all system apks but not these:

AxT9IME, Camera, Email, MMS, Phone, Screen Capture, Settings, Swype, Thinkdroid, Voice search"
[Galaxy S I9000 Android Development] aler:
help

hi dear dsixda

how to put stock rom(1 file) ? for example XWJW7

extrat the file by 7zip or not?
[Galaxy S I9000 Android Development] dsixda:
http://xdaforums.com/showpost.php?p=17443001&postcount=1

Please read the instructions, I'm not going to help you read. ;) Make sure you extract the files so that the supported format is used.
[Galaxy S I9000 Android Development] OrglCe:
Do I have to put all these file in my original_update folder???
[Atrix 4G General] nucentury08:
Im at fry's as we speak I was going to buy this 86$ HD media dock for Atrix the one with hdmi and 2 USB 2.0 ports the reason I want it is to plug in random USB items like mouse keyboard flash drive my question is one is that what the 2 USB ports are for anyways? And 2 can I do it on the Atrix screen no laptop dock or big screen like I just wanna plug in a mouse and have it show up on the small Atrix screen while docked can that be done? ?
[Atrix 4G General] jeremyshaw:
That is what the three USB ports are for. :)

However, as to your second question, I don't know the answer.
[Atrix 4G General] Ronaldo_9:
both can be done with GB update/rom
[HTC EVO 3D] ssojyeti2:
Is it possible?
[HTC EVO 3D] trell959:
Well HTC removed this out of their roms, but I dont see why it couldn't be ported
[HTC EVO 3D] mmmajor:
+1

Sent from my 3VO 3Deeezy
[HTC EVO 3D] MeteorFlare:
I would love to have this as well, I miss having my wallpaper go from left to right!
[HTC EVO 3D] life64x:
I been in Rosie decompiled lately and noticed settings I wonder if it will work. In srttingutil.smali, I think that's the name if it, I am at work so not sure there is a flag called isWallPaperMovable. Try to set this to true. I think that was the var name.
[EVO Shift 4G General] im.nick.hello:
Ok so I was flashing a new splash screen and on the reboot it wont boot passed it now, I can get into clockworkmod recovery but I don't know what to do. I've flashed back my old splash and same thing, won't boot past.

please help
[EVO Shift 4G General] Rooster85:
Restore a nandroid
[EVO Shift 4G General] im.nick.hello:
is there any other way... i havnt made one in a while

is there a way to get through in safe mode?
[EVO Shift 4G General] strapped365:
If you don't have a nand the safest thing to do is reflash, It's good for you every now and then anyways
[EVO Shift 4G General] im.nick.hello:
do nands include splash screens? could i just make one now then do a ruu or some thing.. re-root, then restore?
[EVO Shift 4G General] FdxRider:
No the splash screen won't change unless you ruu.

Edit: you should try to use a different splash screen ie.. go thru the steps to flash a new splash screen but use a different one. Sounds like maybe the file you used maybe corrupted in some way.
[EVO Shift 4G General] im.nick.hello:
i did that... after i flashed i flashed back to my old one...

what im saying is if i made a nand backup now then if i did a ruu to fix the splash issue then re root then restore to my nand would the problem still be there?
[EVO Shift 4G General] FdxRider:
No,If you did a nand of what you are running now, then ruu'd the ruu would replace the splash img. Then once you re-rooted then restore your nand you would have the splash img. that is in the ruu then you could try again to replace the splash img that you want.
[EVO Shift 4G General] im.nick.hello:
ok thanks...

first im going to try

reflashing cm7 179

then backing up and flashing a ruu

then restore

thanks for the help!
[EVO Shift 4G General] FdxRider:
Not a problem let us know if you need more. :)
[EVO Shift 4G General] im.nick.hello:
while backing up it kept saying stuff like

cant mount /cache/recovery/log

cant open /cache/recovery/log

cant mount /cache/recovery/command

stuff like that... also i might just do a advanced restore data to cm7
[EVO Shift 4G General] im.nick.hello:
ok now i have a problem...

backup is frozen on backing up .android_secure

what should i do?
[EVO Shift 4G General] im.nick.hello:
nevermind.. fixed it
[EVO Shift 4G General] im.nick.hello:
ok now i have a problem... my backup wont restore

it says md5 mismatch, is there anything i can do?
[EVO Shift 4G General] crump84:
Run the ruu.

Sent from Gingerbread Speedy 4G
[EVO Shift 4G General] im.nick.hello:
i did.. im trying to restore a backup after a ran it... right now im running one of my old backups, the one i just made before the ruu has a md5 mismatch

EDIT:

found a couple links, going to try now

http://xdaforums.com/showthread.php?t=714114
[General Questions and Answers] hellfire666:
HI all

I just got down a unlocked Inspire 4G and I have only Edge and GPRS for data

cause there are no operator where i live that support the 1900 Band..

I called the Shop they said they have a Captivate and a Samsung Focus and its cheaper and they will refunfd the extra

sooooo I love the Inspire they way it feels and looks...and Sense of-course

but with only 2G speeds, is it really worth to keep it.

or the practical solution is to Return it and Get a Captivate or a Focus??

Since captivate and focus supports Tri-Band 3G so i will get 3g with them 2 phones

Please lend me your thoughts to help me decide
[General Questions and Answers] MartyLK:
Wow...that's a hard choice. The Inspire is the best one of them all and is a superior phone in every way. But unless you are able to use WiFi most of the time, it would be seriouly handicapped.

Keep it if you have plentiful access to WiFi. Otherwise go with the Focus. But don't expect the customization of Android or the number of apps. The Focus will be more like an iPhone for usability.

If music quality is important, go with the Captivate. It has a superior audio chip from Wolfson. The GPS, though, will be buggy.

Actually, the more I think about it, I would definitely go with the Captivate. That sweet Samsung sound quality is worth it.
[General Questions and Answers] hellfire666:
Hmmm

How is the Samsug Focus I mean since you use the phone accroding to your SIggy

How is WINP7 im inetersted in that platform have seen it but never used it...

are there good apps for the Wp7?? Mango will be a great update

so then Focus or Captivate arrrgh!!!

Choices Choices... i hate them :P