Awesome! Setting up Ubuntu as we speak.

Okay I repacked the nk02 f4 LITE version as instructed..... now to flash it to my own Magic.... the moment of truth...... LOL

So so ? Keep us updated lol !

Originally Posted by ranxoren

So so ? Keep us updated lol !

BRICKED

Second try: Got the T-Mobile logo and Rogers logo in a loop

Originally Posted by parrot5

BRICKED

Second try: Got the T-Mobile logo and Rogers logo in a loop

Forgot to data wipe?
A logcat / ddms trace while booting can help too

Originally Posted by Amon_RA

Forgot to data wipe?
A logcat / ddms trace while booting can help too

Did the data wipe.
The device doesn't come online long enough for adb to see it... DDMS fails to see the device while the device is in the booting loop, and logcat simply says "waiting for device".

Originally Posted by Amon_RA

Forgot to data wipe?
A logcat / ddms trace while booting can help too

I have the same problem, it doesn't matter if you do a wipe or not.

OK I flashed my original boot.img back in. Now the device is stuck on the original "HTC Magic" logo, but at least DDMS picked it up and here are the errors:

06-28 20:13:36.063: ERROR/flash_image(37): error opening /system/recovery.img: No such file or directory
06-28 20:13:36.963: ERROR/RIL Acoustic(32): can't open /dev/htc-acoustic -1
06-28 20:13:38.703: ERROR/AndroidRuntime(33): JNI_CreateJavaVM failed
06-28 20:13:39.063: ERROR/HTC Acoustic(34): Fail to open /system/etc/AudioPara_Rogers.csv -1.
06-28 20:13:39.133: ERROR/A2DP(34): bt_audio_service_open failed
06-28 20:13:39.133: ERROR/A2dpAudioInterface(34): a2dp_init failed err: -111
06-28 20:13:39.133: ERROR/AudioFlinger(34): mA2dpDisableCount is already zero
06-28 20:13:41.103: ERROR/AndroidRuntime(54): JNI_CreateJavaVM failed
06-28 20:13:46.503: ERROR/AndroidRuntime(55): JNI_CreateJavaVM failed
06-28 20:13:50.863: ERROR/AndroidRuntime(58): JNI_CreateJavaVM failed
06-28 20:13:56.593: ERROR/AndroidRuntime(71): JNI_CreateJavaVM failed
06-28 20:14:01.673: ERROR/AndroidRuntime(72): JNI_CreateJavaVM failed
06-28 20:14:06.083: ERROR/AndroidRuntime(73): JNI_CreateJavaVM failed
06-28 20:14:11.493: ERROR/AndroidRuntime(74): JNI_CreateJavaVM failed
06-28 20:14:15.913: ERROR/AndroidRuntime(75): JNI_CreateJavaVM failed
06-28 20:14:21.333: ERROR/AndroidRuntime(76): JNI_CreateJavaVM failed
06-28 20:14:26.743: ERROR/AndroidRuntime(77): JNI_CreateJavaVM failed
06-28 20:14:31.153: ERROR/AndroidRuntime(78): JNI_CreateJavaVM failed
06-28 20:14:36.563: ERROR/AndroidRuntime(79): JNI_CreateJavaVM failed
06-28 20:14:40.973: ERROR/AndroidRuntime(80): JNI_CreateJavaVM failed
06-28 20:14:46.383: ERROR/AndroidRuntime(81): JNI_CreateJavaVM failed
06-28 20:14:50.803: ERROR/AndroidRuntime(82): JNI_CreateJavaVM failed

EDIT:
I restored everything, and the following lines exist in the error log (so we can ignore them, I think)

ERROR/RIL Acoustic(32): can't open /dev/htc-acoustic -1
ERROR/HTC Acoustic(34): Fail to open /system/etc/AudioPara_Rogers.csv -1.
ERROR/A2DP(34): bt_audio_service_open failed
ERROR/A2dpAudioInterface(34): a2dp_init failed err: -111

So really the only errors are:

ERROR/flash_image(37): error opening /system/recovery.img: No such file or directory
ERROR/AndroidRuntime(33): JNI_CreateJavaVM failed

But note that I had to flash the original boot.img back to get these, else DDMS doesn't even pick up the device

Originally Posted by Amon_RA

You can get any custom ROM working on your Rogers Magic and basically on every HTC branded Magic around. If you like to "port" a custom Google-branded ROM to a HTC-branded ROM follow these steps :

- I assume that you have basic Linux knowledge and that you know how to set up your own environment and tools, unpack gz files and cpio them etc...

- Download these tools. They contain the JesusFreke's SignApp, William Enck's splitboot using my recompiled mkbootimg-H binary (including the HTC branded offsets), and a repack pearl script.

Now the actually work :

1. Get the boot.img and recovery.img from your original HTC branded Magic (fastboot my recovery image and use nandroid for this).
2. unpack the boot.img and recovery.img using unpack-H.pl.
3. move both kernels somewhere save, you'll need them later.
4. Download the google branded custom ROM you want to port, most of the custom ROMs come in the form of a update.zip file.
5. Extract the boot.img and recovery.img (if there is one) from the update.zip.
6. unpack the boot.img and recovery.img (same as step 2).
7. replace both kernels with the ones you saved previously in step 3.
8. repack boot boot.img and recovery.img using repack-H.pl
9. copy both boot.img and recovery.img in the update.zip package making sure you overwrite the existing ones inside with the new ones.
10. Sign the update.zip file with SignApp (see readme inside rar).
11. Copy the update.zip file to your SDcard.
12. fastboot my recovery image and choose data wipe and then update.
13. reboot

Good luck

I got this error when repacking (Step 7):

sudo sh ./repack-H.pl boot.img-kernel /home/paul/Booty boot.img
./repack-H.pl: 3: use: not found
./repack-H.pl: 4: use: not found
./repack-H.pl: 7: my: not found
./repack-H.pl: 9: my: not found
./repack-H.pl: 11: die: not found
chdir: 13: can't cd to [1]
./repack-H.pl: 15: Syntax error: word unexpected (expecting ")")

Any ideas? I'm actually confused about setting the path of my ramdisk...

Originally Posted by hotweiss

I got this error when repacking (Step 7):



Any ideas? I'm actually confused about setting the path of my ramdisk...

I think you need to extract that ramdisk.gz, mount the file within, and copy the contents to another directory, which becomes the "path of ramdisk".
(Or, whatever method you like to extract those files... )