[REQ FOR HELP] How to port a ROM to the Liquid

[Guest android76]

I have a problem too with mod the init.rc.

For unpack and repack boot.img I use Perl script's and liquidmkbootimg 0.1

I have read somewhere there is a deploy option (0, 1 or 2 ) but I didn't know how to set it in the script

There is the repack script :

#!/usr/bin/perl -W

use strict;

use Cwd;

my $dir = getcwd;

my $usage = "repack-bootimg.pl <kernel> <ramdisk-directory> <outfile>\n";

die $usage unless $ARGV[0] && $ARGV[1] && $ARGV[2];

chdir $ARGV[1] or die "$ARGV[1] $!";

system ("find . | cpio -o -H newc | gzip > $dir/ramdisk-repack.cpio.gz");

chdir $dir or die "$ARGV[1] $!";;

system ("liquidmkbootimg --cmdline 'no_console_suspend=1 console=null' --kernel $ARGV[0] --ramdisk ramdisk-repack.cpio.gz -o $ARGV[2]");

unlink("ramdisk-repack.cpio.gz") or die $!;

print "\nrepacked boot image written at $ARGV[1]-repack.img\n";

Is there need modifications ? Because at this moment the boot I have made not work

Sorry for my english

Edited October 24, 2010 by android76

[Guest Andrea1Liquid]

I understood the my mistake. Tomorrow I have school, so I have to go to bed now, but tomorrow I will fix the boot.img. Thank Vache :P

[Guest vache]

I have a problem too with mod the init.rc.

For unpack and repack boot.img I use Perl script's and liquidmkbootimg 0.1

I have read somewhere there is a deploy option (0, 1 or 2 ) but I didn't know how to set it in the script

There is the repack script :

#!/usr/bin/perl -W

use strict;

use Cwd;

my $dir = getcwd;

my $usage = "repack-bootimg.pl <kernel> <ramdisk-directory> <outfile>\n";

die $usage unless $ARGV[0] && $ARGV[1] && $ARGV[2];

chdir $ARGV[1] or die "$ARGV[1] $!";

system ("find . | cpio -o -H newc | gzip > $dir/ramdisk-repack.cpio.gz");

chdir $dir or die "$ARGV[1] $!";;

system ("liquidmkbootimg --cmdline 'no_console_suspend=1 console=null' --kernel $ARGV[0] --ramdisk ramdisk-repack.cpio.gz -o $ARGV[2]");

unlink("ramdisk-repack.cpio.gz") or die $!;

print "\nrepacked boot image written at $ARGV[1]-repack.img\n";

Is there need modifications ? Because at this moment the boot I have made not work

Sorry for my english

./liquidmkbootimg --deploy 0 --kernel $ARGV[0] --ramdisk ramdisk-repack.cpio.gz -o $ARGV[2]

P.S : deploy option is only on v0.2, consider using it.

Edited October 24, 2010 by vache

[Guest android76]

Thanks you Vache :P

I have try but didn"t work and I can't find a working link for 0.2 :D

Edited October 24, 2010 by android76

[Guest vache]

http://www.mediafire.com/?sharekey=9e8f128...d217c73094ddc3b

[Guest android76]

Thank you but I have a strange problem : with your link I can download v0.1 but I can't for v0.2 :P

Does someone have liquidmkbootimg 0.2 ? thanks

Edited October 24, 2010 by android76

[Guest thepasto]

Thank you but I have a strange problem : with your link I can download v0.1 but I can't for v0.2 :P

Does someone have liquidmkbootimg 0.2 ? thanks

Take it here

[Guest android76]

Thank you very much thepasto :P

[Guest Andrea1Liquid]

@Vache: I tried a lot, but I can't extract the archive which contains the ramdisk. I do this command:

gzip -dc /root/Scrivania/boot/boot.img-ramdisk.gz | cpio -i

And, no matter what similar command I try I get this:

gzip: /root/Scrivania/boot/boot.img-ramdisk.gz: not in gzip format

cpio: premature end of archive

Don't mind: I extracted it using unpack-bootimg.pl and unpacking the obtained ramdisk with the command I wrote earlier.

Edit: edited init.rc. Going to repack (this time correctly :P)

Edit 2: Thank you from me too, thepasto :D

Edited October 25, 2010 by Andrea1Liquid

[Guest Dario93]

Ok. I finally got this Rom working.Now I'm at school so I'm g oing to release the pre pre alpha this evening! :P (Evils sense 1.24 N1 port)

[Guest Andrea1Liquid]

Did you get wifi and data working? Because at this point the ROM has to have a better hw compatibility than Vache's Sense because it'll be nearly non-sense (:P) to release as a pre-apha...Anyway, good work. I'll release my DJDroid port when I'll get wifi and usb storage working...

@Vache or thepasto or koudelka: I tried all the morning to repack the boot.img, but liquidmkbootimg can't be found (even if it's present) when it has permission to be executed as a program. If I de-flag "execute as a program" it can be recognized, but it gives acces denied. I also setted read & write for ALL users, but nothing, situation doesn't changes. I'm using the properties of the files (the GUI) to set his permissions, not the command line because I'm not very familiar. Can you help me? Ah, I'm using a root account...

Edited October 25, 2010 by Andrea1Liquid

[Guest Dario93]

Did you get wifi and data working? Because at this point the ROM has to have a better hw compatibility than Vache's Sense because it'll be nearly non-sense (:P) to release as a pre-apha...Anyway, good work. I'll release my DJDroid port when I'll get wifi and usb storage working...

@Vache or thepasto or koudelka: I tried all the morning to repack the boot.img, but liquidmkbootimg can't be found (even if it's present) when it has permission to be executed as a program. If I de-flag "execute as a program" it can be recognized, but it gives acces denied. I also setted read & write for ALL users, but nothing, situation doesn't changes. I'm using the properties of the files (the GUI) to set his permissions, not the command line because I'm not very familiar. Can you help me? Ah, I'm using a root account...

I need to do more testing, if it doesn't have good hw compatibility I won't release it :D

[Guest Borkata]

@Andrea1Liquid: You can use guide and tools from this link http://android-dls.com/wiki/index.php?titl...ack_Boot_Images

I have successfully repacked my boot.img-s using this guide.

[Guest Andrea1Liquid]

I executed the liquidmkbootimg with :

sh ./liquidmkbootimg --deploy 0 --kernel your_kernel.gz --ramdisk ramdisk-repack.cpio.gz -o output_file

BUT, it gives me a syntax error:

./liquidmkbootimg: 2: Syntax error: "(" unexpected (expecting ")")

:P I'm going to re download thepasto's version...

[Guest Andrea1Liquid]

@Andrea1Liquid: You can use guide and tools from this link http://android-dls.com/wiki/index.php?titl...ack_Boot_Images

I have successfully repacked my boot.img-s using this guide.

Did the repacked Boot.img boot? I was following that page too, but I saw liquidmkbootimg (by disc0) and I thought was good to use it. I tried the version from the download link given by Vache. Now I'll try thepasto's one and if it doesn't work too I'll use the generic one. Thank you :P

Edit: Same syntax error. I'll use the generic one...

Edit 2: OMG. I wrote this:

sh '/root/Scrivania/boot/mkbootimg' -cmdline 'no_console_suspend=1 console=null' --kernel boot.img-kernel.gz --ramdisk ramdisk-repack.cpio.gz -o boot.img

And I received that:

/root/Scrivania/boot/mkbootimg: 1: Syntax error: "(" unexpected

What's wrong?

Edited October 25, 2010 by Andrea1Liquid

[Guest Andrea1Liquid]

@Andrea1Liquid: You can use guide and tools from this link http://android-dls.com/wiki/index.php?titl...ack_Boot_Images

I have successfully repacked my boot.img-s using this guide.

Can you give me your mkbootimg?

Edited October 25, 2010 by Andrea1Liquid

[Guest android76]

http://android.modaco.com/index.php?s=&amp...t&p=1425136

[Guest Borkata]

disc0's liquidmkbootimg is for donut only. You should use liquidmkbootimg 2.

http://www.mediafire.com/?sharekey=9e8f128...d217c73094ddc3b

Edited October 25, 2010 by Borkata

[Guest Andrea1Liquid]

Thanks. I'm downloading...

[Guest Andrea1Liquid]

Same syntax error than before:

./liquidmkbootimg: 2: Syntax error: "(" unexpected (expecting ")")

I'm using Ubuntu 64 and I didn't install any compiling tool.

[Guest Borkata]

Try not using pl script and perform steps manually. I think I had same problem because of incorrect getting of path.

[Guest android76]

@all : Someone have an idea on how to fix data ? I don't know what files need to be modified I think it's ril's files in /bin and /lib but I'm not sure

P.S : I'm running Evil NXSense v1.24 port

Edited October 25, 2010 by android76

[Guest Andrea1Liquid]

I already tried manual method, but I get the same error...I'm running Ubuntu 64 bit, any idea?

@android76: data is one of (if not the) most difficult hw to implement in a sense rom. Sense has a different way to handle data, so you have to do a lot of modding in framework.jar to have data working. The only sense ROM that has data working out of the box is the first Desire HD "leaked" dump (newer don't work).

So, you can do 2 things: make an hybrid framework.jar replacing the correct files from the desire hd ROM or directly port the desire HD ROM. That's what Vache wrote me that you'll find a few pages earlier (with the dl link for the dump).

Edited October 25, 2010 by Andrea1Liquid

[Guest android76]

thanks for your answer :P

My Desire HD port have booted but it's fully unusable there are a lot of glitches and it's very very slow and buggy :D

EDIT : Data not working :D

Edited October 25, 2010 by android76

[Guest Andrea1Liquid]

thanks for your answer :P

My Desire HD port have booted but it's fully unusable there are a lot of glitches and it's very very slow and buggy :D

EDIT : Data not working :D

Have you modified the boot.img? Can you upload it?

Can someone with ubuntu 64 bit explain me how he/she repacks hte boot.img? I can't get it to work...

Edited October 25, 2010 by Andrea1Liquid