27/May r3.1 - MoDaCo Custom ROM for HTC Desire with Online Kitchen (2.1 / Eclair)

[Guest DevilX]

I download with ~1000KB/s (germany)

are the dalvik-cache script includet now?

EDIT:

:-( still the dropbear bug..

Edited May 7, 2010 by DevilX

[Guest ernest33]

Paul please stop "dropping the bear"...bring it back :D

...ok i 'blacklist' myself :P

PS : Delia is really better. Thanks

[Guest domaboul]

still dropbear error.

download is fater (480 Ko/S)

[Guest Mklass]

Downloading a rom @ 380 kb

I see in your second post Paul,

"pre r2 (kitchen only)

Added 'system dalvik-cache to /cache' script"

What does this do exactly?

[Guest Scottland]

Downloading a rom @ 380 kb

I see in your second post Paul,

"pre r2 (kitchen only)

Added 'system dalvik-cache to /cache' script"

What does this do exactly?

If using A2SD, then it moves the Dalvik cache onto the SD card as well as the apps.

[Guest Paul]

That's not entirely true, it moves the system dalvik-cache to /cache and leaves the data dalvik cache as is.

re: dropbear, the scripts write the password to build.prop in /system, which on desire is RO, so I have to find another way (probably symlinking build.prop to /data or something).

P

[Guest U-Man]

Ok....got it so far.

I couldn't see the SD card in Gparted because i put it in my adapter, didn't think of viewing it in the phone itself somehow.

So now i've created 2 partitions, the first one (from left) in the bar is fat32 but it's called /dev/sdc2....and was created as #2

The other i created as ext3 and is called /dev/sdc1....was created as #1

Is this correct? Do the numbers matter or is it the order (left to right in the graph) that matters?

sorry for all the noobishness, just trying to get it right :P

EDIT:

This is weird.

When i partition in recovery the whole card shows as "unallocated" in Gparted. If i then partition it in Gparted en restart my phone i get a "damaged SD card" wanring there and have to format it....after which it shows as "unallocated" in Gparted again!!

Any ideas?

Anyone? It seems strange that my phone can't use the card when partitioned in gparted nor the other way around.

[Guest domaboul]

QUOTE(schlehmil @ May 6 2010, 19:54)

1. Added missing dropbear files/directories to custom rom from prebuild rom.

2. Re-signed custom rom.

3. Flashed successfully!

(4) quietly brilliant bootscreen is now quiet^^

Can you write an How To? I really want to get my kitchen build running tonight.

## Edit ##

Any news on if the dropbear file in the bake?

1 - download "r1 ROM with default MoDaCo additions" 1st page

2 - extract it

3 - download your cooked rom

4 - open your cooked zip (don't extract it) :

in the extracted "r1 ROM with default MoDaCo additions" take the dropbear repertory ans the dropbear file and copy them at the same place in the zip (i opened the zip with winrar and just drop the file/directory a the right place).

then resign :

guide fom : http://androidforums.com/developer-101/866...gning-roms.html

resign file : http://www.relentlessaddictions.com/Androidstuff/signing.zip

you will need Java SE Development Kit and Java SE Runtime Environment : http://java.sun.com/javase/downloads/index.jsp

Now run the autosign.bat.

You will have to go through commands

1 - (Set PATH variable for SDK) ,

2 - (Set CLASSPATH variable for signing tool)

3 - (Install registry entries).

They are very easy to use and just follow the instructions. If you are asked to confirm and/or replace a file, always select yes!

Now you are finally ready to sign! There are two options to sign the .zip

1)Find the ROM (.zip) and right click and select "Resign Zip". If you use this option a command prompt box should quickly appear and disappear.

OR

2) Using the Autosign.bat, select option 4, and then write the directory and file name of the ROM. For example,

D:\Android\ROMs\YourROMHere.zip

It will hang for a bit at the part where it says "signing", and then it should say something along the lines of "Successfully completed if no errors above"

hope this help

it work for me

Edited May 7, 2010 by domaboul

[Guest munkimatt]

re: dropbear, the scripts write the password to build.prop in /system, which on desire is RO, so I have to find another way (probably symlinking build.prop to /data or something).

P

Is there any work-around for this in the mean time? Any ROM I bake fails to install. Also, just out of interest, why has this started happening? I had already installed a ROM from the kitchen previously, it's only been since yesterday they've started failing.

[Guest Linkazoid]

Paul,

Delia is still slow for me..... I'm only getting 20kB/Sec and I'm also on a 100Mb line.

:P

Michael

[Guest munkimatt]

Oh and Delia is one fast woman, I'm getting 200kB/s here!

[Guest Reefster]

400Kbps here in UK

[Guest sanfran]

Hi Paul,

Thanks a lot for the effort!!

I have one question:

I still have problems to get 'A2SD' running. I partionied the SD CARD in recovery mode, but this does not seem to work with your script.

I don't have a linux machine to partition the SD Card, is there another way to get A2SD running without partioning the SD Card on a Linux desktop...?

Thanks!

[Guest Paul]

Dropbear issue resolved for new bakes, apologies!

P

[Guest kayceejayh]

Also having the issue with the batery icon not animating during charging.

[Guest Mklass]

Why don't you include the r1-a2sd-desire-dalvik-fresh-signed.zip

in the Kitchen?

I dont have the animated battery issue. Everything in my baked rom works just fine :P

[Guest Paul]

Mklass - because that's not mine.

P

[Guest Mklass]

OK cool dude.. I'm gonna bake a new rom now and see how the new Apps2SD script works :P

[Guest domaboul]

Dropbear issue resolved for new bakes, apologies!

P

sorry, i try two times after your post (2 differents cooket rom)

error :

E: can't chown/mod /data/dropbear/.ssh

(no such file or directory)

E:Failure a line 363:

set_perm 0 0 0700 DATA:dropbear/.ssh

[Guest BustedFly]

sorry, i try two times after your post (2 differents cooket rom)

error :

E: can't chown/mod /data/dropbear/.ssh

(no such file or directory)

E:Failure a line 363:

set_perm 0 0 0700 DATA:dropbear/.ssh

The same thing occurs with me also

[Guest yabolek]

sorry, i try two times after your post (2 differents cooket rom)

error :

E: can't chown/mod /data/dropbear/.ssh

(no such file or directory)

E:Failure a line 363:

set_perm 0 0 0700 DATA:dropbear/.ssh

+1 here

[Guest Paul]

sorry, i try two times after your post (2 differents cooket rom)

error :

E: can't chown/mod /data/dropbear/.ssh

(no such file or directory)

E:Failure a line 363:

set_perm 0 0 0700 DATA:dropbear/.ssh

Grrr, try now!

P

[Guest Ahri]

Same issue here using the kitchen:

E:Can't chown/mod /data/dropbear/.ssh

(No such file or directory)

E:Failure at line 363:

set_perm 0 0 0700 DATA:dropbear/.ssh


Installation aborted.[/codebox]

I tried mucking around with the update-script but I can't calculate the sha1 for the manifest (sha1sum gives me a longer value than exists in MANIFEST.MF?).

Edit: trying new version now. I'm interested in how to calc the manifest though so I can play about with it in future!

Edit2: working now, cheers Paul. Rebooting.

Edit3: Titanium restore + reboot = fail, as with other people (see below), gonna test out eViL De-SiRe and see how that is while this stabilises

Edited May 7, 2010 by Ahri

[Guest nezorflame]

now finally working :P

[Guest gforums]

Grrr, try now!

P

trying now ...

...

Formatting SYSTEM...

Copying Files ...

...

Rebooting.

Rebooting.

Working. :-)

Thanks Paul

(just my custom boot animation isn't shown up. Isn't it /system/media/bootanimation.zip?)

EDIT:

Phone memory is rather low now...:-(

And: I attached a zipfile of structure /system/media/bootanimation.zip - However the bootanimation still is the original one....?!

Edited May 7, 2010 by gforums