Trying to build a rom based on Ion but with MCR custom kernel

[Guest jmmL]

I've got to the stage where I've replaced the kernel provided in the Ion download with the MCR kernel. I now have a working directory with a boot.img, recovery.img, system.img and userdata.img.

Now I'm getting lost. I want to create an update-signed.zip. I zipped up these four files (is this even the right thing to do?). How do I then sign this .zip? I used a tool call testsign from http://forum.xda-developers.com/showthread.php?t=551711 , which produced an error:

jamie@karmic-laptop:~/Projects/pulse/roms/attempt1$ java -classpath /home/jamie/bin/testsign.jar testsign attempt1.zip attempt1-signed.zip

Exception in thread "main" java.lang.UnsupportedClassVersionError: Bad version number in .class file

	 at java.lang.ClassLoader.defineClass1(Native Method)

	 at java.lang.ClassLoader.defineClass(ClassLoader.java:620)

	 at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)

	 at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)

	 at java.net.URLClassLoader.access$100(URLClassLoader.java:56)

	 at java.net.URLClassLoader$1.run(URLClassLoader.java:195)

	 at java.security.AccessController.doPrivileged(Native Method)

	 at java.net.URLClassLoader.findClass(URLClassLoader.java:188)

	 at java.lang.ClassLoader.loadClass(ClassLoader.java:306)

	 at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)

	 at java.lang.ClassLoader.loadClass(ClassLoader.java:251)

	 at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)

[Guest jmmL]

Right, well the error was solved by using Java 1.6. I had downgraded to .5 because this was recommended for developing the main android build.

I've now got a signed file, but I'm nervous about trying to apply it. How will I be able to do a nandroid restore if I completely wreck what's currently on my pulse? Where can I upload the file?

[Guest Paul]

Yeah, nandroid backup first and you'll be fine!

P

[Guest jmmL]

Yeah, nandroid backup first and you'll be fine!

P

Okay I've done another backup. In the event that things go wrong - how will I be able to apply the backup if I can't get to the "Quick Boot" app?

I tried applying mine anyway, and it failed with "update-script not found", which I hadn't included. I'm not really sure what needs to go in here. How much can I copy from the one included in MCR-1.4.1? What do I need to put here?

The upload to rapidshare has just finished: http://rapidshare.com/files/319470622/attempt1-signed.zip

Apologies if this isn't allowed. That version lacks an update-script, but my upload connection is so poor I thought I better start uploading now, so others can have a go.

[Guest Paul]

You can use 'fastboot boot recoveryimage.img' on the AmonRA recovery image to get into it.

P

[Guest jmmL]

You can use 'fastboot boot recoveryimage.img' on the AmonRA recovery image to get into it.

P

Thanks. It went wrong on attempt2 complaining about the dumpstate symlinks. It looks like the symlinks are already created in the Ion system/bin - do I need to re-state them in the update-script?

Attempt3 failed - I was expecting it to.

Copying files...

E:Can't symlink /system/bin/getevent

E:Failure at line 9:

symlink toolbox SYSTEM:bin/getevent


Installation aborted.

Here's what I'm using as an update-script:

show_progress 0.1 0


format SYSTEM:

copy_dir PACKAGE:system SYSTEM:


#symlink dumpstate SYSTEM:bin/bugreport

#symlink dumpstate SYSTEM:bin/dumpcrash


symlink toolbox SYSTEM:bin/getevent

symlink toolbox SYSTEM:bin/getprop

symlink toolbox SYSTEM:bin/iftop

symlink toolbox SYSTEM:bin/ioctl

symlink toolbox SYSTEM:bin/kill

symlink toolbox SYSTEM:bin/log

symlink toolbox SYSTEM:bin/notify

symlink toolbox SYSTEM:bin/schedtop

symlink toolbox SYSTEM:bin/sendevent

symlink toolbox SYSTEM:bin/setprop

symlink toolbox SYSTEM:bin/smd

symlink toolbox SYSTEM:bin/start

symlink toolbox SYSTEM:bin/stop

symlink toolbox SYSTEM:bin/ttycom

symlink toolbox SYSTEM:bin/vmstat

symlink toolbox SYSTEM:bin/watchprops



set_perm_recursive 0 0 0755 0644 SYSTEM:

set_perm_recursive 0 2000 0755 0755 SYSTEM:bin


set_perm 1014 2000 0550 SYSTEM:etc/dhcpcd/dhcpcd-run-hooks

set_perm 0 2000 0550 SYSTEM:etc/init.goldfish.sh

set_perm 1002 1002 0440 SYSTEM:etc/dbus.conf


set_perm_recursive 1002 1002 0755 0440 SYSTEM:etc/bluez

set_perm 0 0 0755 SYSTEM:etc/bluez


set_perm 0 3003 02755 SYSTEM:bin/netcfg

set_perm 0 3004 02755 SYSTEM:bin/ping


delete DATA:app

delete DATA:init.sh

delete DATA:local

delete DATA:dalvik-cache

copy_dir PACKAGE:data DATA:

set_perm 1000 1000 0771 DATA:app


show_progress 0.1 10


show_progress 0.2 0

write_raw_image PACKAGE:boot.img BOOT:

show_progress 0.2 10

Are the errors a permissions issue - or do I not need to symlink stuff to toolbox as the links appear to be already created?

Edited December 11, 2009 by jmmL

[Guest jmmL]

I knew this was stupid.

The phone now won't properly boot up. It gets past the android screen and then simply has an underscore in the top left.

I'd really appreciate some urgent help; this is a bit nerve-wracking!

[Guest martinbrook]

I knew this was stupid.

The phone now won't properly boot up. It gets past the android screen and then simply has an underscore in the top left.

I'd really appreciate some urgent help; this is a bit nerve-wracking!

Don't panic. I remember the first time I was faced with this, you think I've bricked it.

Drop back to recovery using fastboot and restore your backup or the

Martin

[Guest jmmL]

Don't panic. I remember the first time I was faced with this, you think I've bricked it.

Drop back to recovery using fastboot and restore your backup or the

Martin

For some reason adb etc won't work on my linux machine, so I've dived back into Windows. Everything is now back to normal.

Just in case anyone else has this happen to them the steps are:

• boot in to the blue bootloader screen (hold volume down and the red button, then turn on)
  
• run "fastboot boot recovery.img" where recovery.img is AmonRA's image.
  
• Do a nandroid restore
  

Phew.

[Guest jmmL]

Making a bit of progress. Sorted the update-script issues (I hope!). It seems that the symlinks can't already exist, so I deleted them.

Now I'm actually at the stage of the update-script writing the boot.img....

[Guest jmmL]

Okay attempt number 7 finally successfully wrote the boot.img. On rebooting it seemed to enter a endless reboot cycle.

Hmm. I'll upload #7 for people to have a look at, but I'm chalking this up as a dead end for the time being.