yashsingh1/xdaforums huggingface dataset:
[Droid Eris Android Development] kaiya215:
hey can this be used to port roms from the g1/!mytouch to the eris such as open eclair... just wondering i dont have. pc that i can install programs on at the moment, if possible can somone do this for me i would appriciate it alot..

Sent from my Eris using the XDA mobile application powered by Tapatalk
[Droid Eris Android Development] tazzpatriot:
hey just a question ,do u have to do a full install of ubuntu 17 gig? or can u use smaller ? sorry for the dumb question ,
[Droid Eris Android Development] kaiya215:
okay so i ported a rom as directed flashed it and everything works except i am getting no signal at all...

and when i do a *#*#4636#*#* i dont have the option to switch to cdma or evdo... only showing wcdma preferred and gsm?

any help
[Droid Eris Android Development] dsixda:
Whoa.. 17 gigs? I just chose all the defaults, and I only had an 8GB partition created for VirtualBox.
[Droid Eris Android Development] kaiya215:
six any idea with my error

Sent from my Eris using the XDA mobile application powered by Tapatalk
[Droid Eris Android Development] dsixda:
Nope, I'm no cooking expert and I don't have an Eris. Search for the answer or ask in the forum.

Did you use the Port ROM option?
[Droid Eris Android Development] kaiya215:
okay check it i got everything working except the lightup sensor buttons below the main display.... what lib controls these....? i think i have the wrong file atm,
[Droid Eris Android Development] t2noob:
I have tried porting 3 roms already all from different devices like the g1 droid and stuff like that, and they all never boot..can you tell me what I'm doing wrong or if what I'm doing is even possible?
[Droid Eris Android Development] dsixda:
The FAQ on the main kitchen thread should give you some information on what to do regarding non-booters. This would help me understand the problem as well. Keep in mind that porting roms that were *already* cooked before by someone else will make the porting more complicated and difficult.

Try just cooking a shipped Eris ROM on its own, along with customizations like rooting. Make sure that alone works before you port.
[Droid Eris Android Development] kaiya215:
still cant get these friggin buttons working...

Sent from my Eris using the XDA mobile application powered by Tapatalk
[Droid Eris Android Development] dsixda:
Try doing an "adb logcat" while the phone is connected to your pc, while you push on the buttons.

Someone is trying to port the Xperia X10 to the Nexus One and had similar issue with key mappings:

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

They said to check /system/usr -- maybe copy files from the Eris to here? I don't know.. I'm no expert.

EDIT: Also download the latest version of the kitchen (0.42 now)
[Droid Eris Android Development] kaiya215:
thanks fixed

about to upload

Sent from my Eris using the XDA mobile application powered by Tapatalk
[Droid Eris Android Development] dsixda:
What are you going to upload?
[Droid Eris Android Development] kaiya215:
the rom.. lol
[Droid Eris Android Development] dsixda:
Why? i already told you I don't know anything.
[Droid Eris Android Development] CaptJager:
DSI back with WM kitchen there was a limit on Rom size that you could install tonight I feel that I have found that limit again I will keep checking but I believe that I have been able to flash a 93 meg rom but not a 97.4 meg rom I will keep playing and find out the limit for the Eris Would be nice if a check could be put in to make sure it is not too big to flash depending on what device.... I can not remember back with the WM kitchen what the limits were but it was around the same....Just a lil bit of info and thanks I have been tweeking this fully.... Also any clue why some apk's will install just fine by puting them into the system/app/ dir and some will not? I will play more with removing apk's from the system/app and trying them with the data/app dir. this Eris to me is a throw away meaning not really worried if I screw it up and have not done it yet with everything I have thrown at it including trying to port the Incredible rom to the Eris via your kitchen NOT GOOD. The Eris pb00img boot.img and system.img files have not failed me yet other than the Rom being over sized and aborting during flash. Once the Incredible is rooted I will volunteer for testing. Let me know how I can help with the development of the Kitchen as I am cooking 5-8 times a day trying different things. I would like a basic entry so only the needed apk's would be loaded into the working folder. I personally will be stripping out the junk but the average Joe/Jane will not. I still have some time off and this is where I was able to help GGuru with his WM kitchen, testing and tweeking...... Thanks again..

CaptainJager
[Droid Eris Android Development] dsixda:
Yeah, it's up to the user to figure out these issues with ROM size, bad flashes, etc. There are way too many devices coming out every couple of months for the kitchen to keep up with and determine separate conditions for. ;-) Also, normally a cooked ROM is never larger in size than the original shipped ROM, unless you want to slow down your device. The best tool you can use is "adb logcat" to determine why your device won't boot. There is more info about this in the FAQ (post #3 of the main kitchen thread).

You will never have to worry about bricking your device because you can always boot back a good ROM through the recovery menu... so you don't need to worry about using a secondhand or throw-away device. I cook all the time on my Nexus One, doing little experiments here and there... no worries at all!

Why are you trying to port an HTC Incredible ROM onto a low-res device? That's not going to work and will take tons of work and time to change the image resolutions and CPU requirements.
[Droid Eris Android Development] acmeinc:
I apologize if someone already asked this, I read through this post.

Is there anyway to use a nand backup to create a flashable ROM? Otherwise, I must assume I have to install the Kitchen and then do my setup that way.

I assume I could copy over the boot.img system.img and data.img and zip them up......somehow. From what I've read the boot.img stays as is, but it would seem as if the Kitchem Roms include system not system.img or data.img. Also, I would assume after I get that settled I'd need to zip up the files and sign the zip.

Am I on the right track here?
[Droid Eris Android Development] dsixda:
Not many people have tried using a nand backup to cook their roms in this kitchen, but those who have tried said they had encountered errors. It doesn't hurt to try, however, to find out why it fails. I do intend to try it myself eventually, and maybe have the kitchen correct it if possible.

The kitchen only uses the system.img and boot.img, and outputs the Rom in the same format as a cooked Rom. A shipped Rom uses a different format, however (ie. all the .img files are zipped up into one file without any of them being expanded, and then the file is signed).

When you run the kitchen it will tell you what you need to do at every step.

Hope this answers your question.
[Droid Eris Android Development] acmeinc:
Yes indeed it does.

I have since create 4 ROMS from my nand backup and I am yet to get any to work. Each time I tried to alter minor things to rule out different problems. I'll be sure to post back when I get something that resembles a working ROM from my NAND backup.

I'm too tired to post exactly what I tried. I can say I copied files from the /sdcard/nandroid/$DIR$ in an attempt and I tried numerous functions within the Kitchen :P Maybe tommorrow or when I get it to work I'll post something useful.
[Droid Eris Android Development] dsixda:
What specific errors did you get when trying the nand backup?
[Droid Eris Android Development] acmeinc:
Below is the output I receive from the two ROM's which make it the farthest in the flash process:

Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing Update...
Formatting SYSTEM...
Deleting files...
Deleting files...
Copying files...
E:Can't symlink /system/bin/getprop
E:Failure at line 20:
symlink toolbox SYSTEM:bin/getprop

The output it very similar when I actually do a Wipe of the System, Cache, and EXT. The same /system/bin/getprop error occurs.
[Droid Eris Android Development] dsixda:
Do you have /system/bin/getprop existing under your working folder? If so, delete it and then rebuild the ROM.

Let me know.. thanks
[Droid Eris Android Development] dsixda:
I think I know what the problem may be in the nand backup case.

There are problems with the system.img of your nand backup:

1) the /system/bin folder already has the symbolic links created. During flashing, it tries to create these same symbolic links again, so it complains. These are the files that are 76 KB in size... there about 50 of them. Delete them.

2) the /system/xbin folder already has the symbolic links created if you had "busybox" enabled. So you need to delete the xbin folder, and then in the kitchen, re-root the ROM so that busybox is re-enabled.

Finally you can build the ROM and re-flash.

I can make an update to the kitchen, so that this is done automatically if it detects a nand backup system.img.
[Droid Eris Android Development] acmeinc:
I have done this and the ROM fails at another sym-link spot. This time:

/system/bin/reboot

OMW to work now so I won't get to test this until later. But the logic makes sense considering my newest ROM failed at yet another sym link.

I'll be sure to respond back...lets see work + pens game = tomorrow after noon sometime :P Thanks for the help.
[Droid Eris Android Development] dsixda:
I will try this when I get home after work (I never tried cooking from a nandroid backup!) and will update the kitchen later.

Actually, forget about point #1, because the kitchen will automatically remove all symbolic links under /system/bin.. or at least it should.

Yes, go Pens. I live in Ottawa but not a Sens fan ;-) (Grew up in Edmonton during the glory years and after.. Huge Oilers fan.)
[Droid Eris Android Development] dsixda:
Kitchen has now been updated with v0.49. It will now support Nandroid backups.. I have tested it successfully on my Nexus One. Hope it works out for you..
[Droid Eris Android Development] acmeinc:
Unfortunately even with the new version of the Kitchen I still receive the same symlink errors.

To battle this I have removed:

getprop setprop toolbox reboot

This allowed me to successfully flash my ROM. However I am worried because toolbox did not recreate itself. I am going to flash a ROM without removing toolbox
[Droid Eris Android Development] dsixda:
Where did it see "getprop setprop toolbox"?

What kind of ROM was in the Nandroid backup? The original update-script from the ROM gets removed after it is flashed to your device, so the kitchen has to re-create it, but it is almost impossible to "guess" what was in the original update-script.

My kitchen will detect root, busybox and data/app functionality in the ROM and add it to the update-script, but nothing else. If the original ROM had complex operations in the update-script, then the kitchen cannot account for that -- it would be close to impossible, unfortunately.
[Droid Eris Android Development] acmeinc:
The same symlink error as before. So I went in an removed all 72kb files which were getprop, setprop, and toolbox. Turns out the two "prop" files linked to 'toolbox'. So I created a ROM where I left toolbox but removed the others.

This worked.

It was a modified version of the 2.1 OTA-root leak. However I am now checking my original zip (pre-modified) to see if the same links exist. If they do exist perhaps you should update your script so it checks for and removes getprop setprop and reboot .

**UPDATE** These links do exist.

FWIW, I was able to sucessfully ROM my NAND backup! Now for modifications :)
[Droid Eris Android Development] dsixda:
Cool...

Ok, so did my script (v0.49) remove getprop, setprop and toolbox from /system/bin, when you put the *.img files and ran Option 1?
[Droid Eris Android Development] dsixda:
Yeah, it shouldn't matter if they exist or not,

ie.

If they physically exist in your folder, then the update-script should NOT mention symlinks to those files.

If they don't exist in your folder, then the update-script SHOULD try to create symlinks to those files.

EDIT: Send me a link to that exact ROM so maybe I'll have time during the weekend to check it out.
[Droid Eris Android Development] acmeinc:
Unfortunately no. I had to manually remove these.

To recap, I placed the 2 *.img files in the original_update, ran option 1, chose 3, pressed enter.

Another idea....you could automize NAND backups to utilize the data.img as well. This automation would setup the /data/app dir with your apps already set. Just an idea.
[Droid Eris Android Development] dsixda:
Doh.. that's strange. But weren't they symbolic link files in that folder?

Were they under /system/bin or /system/xbin.. or some other folder?

Yeah I could do that some time later. Have you tried doing "unyaffs" on a data.img and seeing what happens?
[Droid Eris Android Development] dsixda:
Just FYI,

I have system/bin/toolbox but not the other two files in my Nexus One's cooked ROM Zip file that was made from my nandroid backup. Also, its update-script contains links to getpropt and setprop (they are links to toolbox).
[Droid Eris Android Development] acmeinc:
From your Kitchen utlitity the location of the 3 files is below:

./WORKING_$DATE/system/bin/

Inside the utility the "links" were actually files the same size of the file they linked to. They all linked to 'toolbox'. However they exist as links on the mobile device. If that all makes sense :)

OMW to work now, I'll have to try this later on tonight. I just 'cp -r' the /data/app dir to the sd card, and then to my computer. I'll also be testing the functionality of the /data/app dir later.
[Droid Eris Android Development] dsixda:
The utility only deletes files of type "L", which are symbolic links. So it should be deleting those two files. If you check the update-script you'll notice that they are mentioned as symlinks (to be created during flashing).
[Droid Eris Android Development] droidkevlar:
used ubuntu very lil but going to give this a shot. im pretty good at reading and ubuntu is very simple to use. wish me luck. :D
[Droid Eris Android Development] acmeinc:
FWIW there is a good video on how to get started on the unlockr:

Part 1

Part 2
[Droid Eris Android Development] droidkevlar:
ya, found that before, thanks though. seems easy until you want to start editing rosie, toolbar, icons, etc. but hey, it should be fun.
[Droid Eris Android Development] acmeinc:
What are the risks of creating a public ROM from a nand backup? Of course my nand backup will practically be fresh. Mainly the idea is to setup the phone they way I'd like, without putting in an personal information, then nand backing it up and building a custom ROM for that.

I guess my question is, what type of details from my phone will be retained in the ROM? Anything important/security risks? Will the nand backed up ROM even load on other phones?
[Droid Eris Android Development] dsixda:
The system.img doesn't store any of your settings, it just has the operating system. The data.img carries your installed programs and settings for those programs. So if you cook a rom with this kitchen you won't need to worry since we don't use the data.img.

Using your cooked rom from the nand backup onto another device will work. When you did a nandroid restore it compared your device ID with the ID of the backup folder before proceeding. However, for a cooked rom it won't need to do that.
[Droid Eris Android Development] stopxstart:
I'm having some difficulty getting started cooking a custom rom.

I've put the rom zip into the appropriate folder but when I fire it up and try to option 11 it, it errors. Am I missing a step?

Anyone care to help a n00b out?
[Droid Eris Android Development] Framework43:
Wow. Very handy thanks :)

Planning on adding de/odexing scripts?
[Droid Eris Android Development] dsixda:
The video you probably saw is a bit outdated. Use Option 1 to cook any cooked or shipped ROM. Option 11 is to port a ROM from *another device*.
[Droid Eris Android Development] dsixda:
No plans.. I've never played with that feature and there hasn't been much demand for it. Trying to keep the kitchen as simple as possible ;-)
[Droid Eris Android Development] Framework43:
Would be nice though, helps with the editing of the apks and such. I'd very much appreciate it if you were to add it.
[Droid Eris Android Development] dsixda:
I am just worried it will add more complexity to the kitchen. once you modify an APK and sign it, it will require the completed Rom to be signed with the same signature (or so I heard). That will break the simplicity kitchen or cause other kinds of problems.

I will probably leave that to the user to figure out, since I'm more interested in people building ROMs rather than the binaries/apps themselves.
[Droid Eris Android Development] Framework43:
Maybe you could add an -Advanced Settings option?
[Droid Eris Android Development] dsixda:
Well, I don't know how to implement and use this deodexing stuff anyway ;-)

Like I said, rebuilding an apk will cause problems when the ROM is signed.
[Droid Eris Android Development] paintguy:
First Try...Success!

Since the kitchen was designed for inexperienced cooks I thought I would chime in. Took me quite a while to get Virtual Box and Ubuntu configured properly but after I did I took Aloysius V6 Maps and removed several apk's in the kitchen. It booted up the first time and all was OK. This is a lot of fun for us old guys to do a little pseudo programming and play with our phones too. It's becoming addictive. Thanks much and wonderful job!:)
[Droid Eris Android Development] Spencer_Moore:
Nice. good to see some people take initiative and fix what they do and don't like in a rom without having to ask! Thank you for this.
[Droid Eris Android Development] tazzpatriot:
well i got a rom to boot up to home screen seems to be fine except the soft keys ? am i missing something?
[Droid Eris Android Development] dsixda:
I need details... what steps did you do, etc.

If you ported from another device ROM then I can't really help you there, you need to ask around or find out on your own.
[Droid Eris Android Development] notsed:
Using Cygwin and the latest Eris leak I get the following error when I flash the newly rooted ROM

It's the same error every time and it doesn't matter what modifications I do to the ROM. I've tried a bunch of combinations (even just root) and it still happens. Any help would be appreciated.
[Droid Eris Android Development] dsixda:
Is there a system/bin/reboot file in your working folder?

Sorry, I crashed my computer last night so I couldn't check out the ROM.
[Droid Eris Android Development] notsed:
Yep. That's what makes it so strange.
[Droid Eris Android Development] dsixda:
Ok, then you will need to remove it. Do you know if it's a symbolic link or not? Just do an "ls -l" in the system/bin folder to see if it is linked to another file. If it is a symbolic link then the script should have removed it automatically when you first crested the working folder.
[Droid Eris Android Development] notsed:
-rwsr-sr-x 1 MyName None 5628 2010-05-01 01:06 reboot
[Droid Eris Android Development] dsixda:
Ok it's not :-) Thanks. Just remove it and build it again. Please let me know if it complains about more files. I will take a look at this ROM (and maybe fix the kitchen) after I restore my pc ;-)
[Droid Eris Android Development] notsed:
Does that s mean symbolic? There are a few more (ip, netcfg, ping, wifitols) that have that. Should they be removed as well?

Thanks for your help and I promise I'll leave you alone after this so you can fix your computer :)
[Droid Eris Android Development] dsixda:
No it isn't a symbolic link. A symbolic link is like a shortcut. So when you did ls -l it would have showed an arrow pointing to its source destination. Anyways, looks like it is an actual binary.

Regarding the other files, open up your update-script file under META-INF and check if they are mentioned as symlinks. If yes, then you gotta remove them from system/bin, just like the reboot file. I will eventually make my scripts intelligent enough to check for this.

Thanks
[Droid Eris Android Development] notsed:
It flashed fine after deleting reboot. Thanks again
[Droid Eris Android Development] dsixda:
I have updated the kitchen with a new version that corrects your problem. Thanks for the feedback.
[Droid Eris Android Development] arockj:
Thank you for the work you have done. I have used this kitchen to cook my own rom. Your kitchen cut my time in half. Thanks again.
[Droid Eris Android Development] dsixda:
Only half? haha.. just kidding.

Yes, my main goal was for you guys to save time, and not have you spend countless hours wondering what to do for just small changes to your ROM. :)
[Droid Eris Android Development] dlike:
Was playing with this last night and was very impressed with it's ease. Thinking about stripping Friendtream from one of the sprint roms and applying to Leak3. Got any pointers or is this even possible?
[Droid Eris Android Development] dsixda:
I have no idea man, I am just a newb. ;) I also only own an Nexus One. Use the Port ROM option to port a ROM from another device to your own device. Have fun..
[Droid Eris Android Development] dlike:
Having problems with java can't finish the last step. I did try to install the files as directed on the tutorial from the unlockr but the links provided are for a newer version. This version requires some other files or at least thats what the log file says. here is what I am getting.

dpkg: dependency problems prevent configuration of sun-java6-jre:

sun-java6-jre depends on java-common (>= 0.24); however:

Package java-common is not installed.

dpkg: error processing sun-java6-jre (--install):

dependency problems - leaving unconfigured

dpkg: dependency problems prevent configuration of sun-java6-bin:

sun-java6-bin depends on sun-java6-jre (>= 6.20-dlj-3); however:

Package sun-java6-jre is not configured yet.

sun-java6-bin depends on unixodbc; however:

Package unixodbc is not installed.

dpkg: error processing sun-java6-bin (--install):

dependency problems - leaving unconfigured

Processing triggers for shared-mime-info ...

Processing triggers for desktop-file-utils ...

Processing triggers for python-gmenu ...

Rebuilding /usr/share/applications/desktop.en_US.utf8.cache...

Processing triggers for python-support ...

Errors were encountered while processing:
[Droid Eris Android Development] dsixda:
Well, then read the error message and install the package it is complaining about.

sudo apt-get install ...
[Droid Eris Android Development] AOD13:
I have tried the latest Kitchen (0.51) and it keeps giving me

unzip: command not found

Does this have to do with my version of java? I am on my work computer and cannot upgrade it
[Droid Eris Android Development] dsixda:
Are you using Cygwin? Mac? Linux? If unzip is not found you need to install the binary - Java has nothing to do with zip/unzip.
[Droid Eris Android Development] AOD13:
I am using cygwin with the jcase 2.1v3 cooked rom zip file in the original_update folder and selecting option 1
[Droid Eris Android Development] dsixda:
Please read the instructions before asking questions like this. The link to the setup guide was mentioned in bold lettering right next to the download link. Please save yourself some time and read it. Good luck!
[Droid Eris Android Development] AOD13:
Are you talking this guide?

http://xdaforums.com/showpost.php?p=5646155&postcount=76

I had your kitchen working fine back about a month ago.

Now none of it works.

I did read your guides and just merely updated the kitchen.

I have j2sdk1.4.2_08 installed. As stated in my previous post I cannot upgrade.

Could the version of java be the problem?
[Droid Eris Android Development] dsixda:
You'll need at least Java JDK 6. I'm not sure, but I think yours is JDK 4.
[Droid Eris Android Development] AOD13:
That's what I was afraid of.

Thanks.