Develop Bugs

NEED Help/Advice

I have a T-Mobile HTC Touch Pro 2. I would like to upgrade this phone to use one of the good operating systems from on these forums and would like to add Android to my phone. However, I have no idea what to do or where to get the correct files that are working.
If someone could help me with what I must do to achieve what I am trying to get done I would appreciate it. I need both instructions and files.
Scott Gleaton

For windows http://forum.xda-developers.com/showthread.php?t=550540
For Android
http://forum.xda-developers.com/showthread.php?t=627997
And my other advice is to read everything you can

Links in the post above tell you most of what you need to know.
You will need to HardSPL before you can flash a new ROM. This is mentioned and linked in the "Flashing for Noobs" thread linked above. But here it is also: http://forum.xda-developers.com/showthread.php?t=550131
I also recommend running Task29 after you HardSPL and before flashing any ROMs: http://forum.xda-developers.com/showthread.php?t=649191
Not fully mandatory, but Task29 formats the phones whole memory, so there is no chance of fragments of the old ROM to mess up the new one.
What ROM is best depend on the individual user. Each cook includes different apps, looks and functionality in their ROMs. So look thru the different ROMs, and pick on that suits you. If you are still at a loss, I personally like the Energy ROM. This guys is very reputable for stable, fast, and aesthetic ROMs. I doubt you would be disappointed.
http://forum.xda-developers.com/forumdisplay.php?f=490
Just read all the instructions carefully before you flash, plus the FAQs on each page, and (at least) the last couple pages of the threads. This will often clue you in to the common issues some people have, and how to solve them.
Project Android for the TP2 is not a full ROM, but is nice because you install on your MicroSD card and boot it from Windows Mobile. WM gets unloaded, and Android is loaded. To get back to WM, you just soft reset. Its not perfect, there are still plenty of bugs (no sound, no Bluetooth, some apps crash or lag). But its pretty functional, and lets you mess around and explore Android, check out the app store and play some of the games, etc. Highly recommended to try it out, if you are curious about Android (and who isn't?).

[Q] tilt 2 energy rom

i new to this stuff but im want to install the energy rom 4 tilt 2 and i jus wanna know if everything still work fine like all functions of keyboard and the icons and if it run sluggish thxs

NRG has included in his ROM a Carrier Provisioning tool. After you flash the ROM, just start the tool, select ATT and the keyboard is automatically configured to ATT's layout, and any other settings which are needed to work on ATT's network. Its super slick, and worked perfectly on my Tilt2.
The Energy ROMs are much better than the stock ROM. Less program memory usage, faster, and more stable. Also, no bloatware, great cooked-in apps, and awesome functionality and looks.
There is still some lag, which is just the way it is with Windows Mobile. But its much better with the Energy ROM. And if you want it even smoother than use the Titanium version. Personally, I use the GTX version, b/c I'm a sucker for eye candy.

thx
can you tell me where i can get one that works so i dont brick my phone please. and i also saw one on youtube with a moving background screen it was like thunder and clouds. its so cool is that the energy rom and where do i get the keboard rom that configures my keboard thanks very much

Yoiu might try the ROM Development subforum, where this question should have been posted.

Yeah, there is a whole sub forum on here which contains all the ROMs you will ever need, tools to flash, instructions, etc.
http://forum.xda-developers.com/forumdisplay.php?f=490
The thread sticky-ed to the top of that forum are extremely useful. The following guide for flashing a ROM is a MUST READ.
http://forum.xda-developers.com/showthread.php?t=550540
Also, you will need to HardSPL your phone before you can flash a new ROM:
http://forum.xda-developers.com/showthread.php?t=550131
And I highly recommend running Task29 after you HardSPL, and before flashing a new ROM to completely wipe the memory, which will prevent any fragments of the old ROM from interferring with the new ROM (which can sometimes cause random bugs):
http://forum.xda-developers.com/showthread.php?t=649191
Read through the first part of the above threads, and at least the last couple pages of each one, too (to say what common or recent issues may have popped up, what problems people have, etc.).
Read and understand all the instructions, and follow them carefully, and you will not brick your phone. It seems intimidating and complicated at first, but its not really that hard (and you will be addicted!). Just prepare properly before you start!

tyronekndrck said:
i also saw one on youtube with a moving background screen it was like thunder and clouds. its so cool is that the energy rom and where do i get the keboard rom that configures my keboard thanks very much
Click to expand...
Click to collapse
That is the weather tab on Sense 2.5 (HTC's interface for Windows Mobile, an updated version of Touch FLO 3D, which your ATT Tilt 2 has on it). Any ROM with Sense 2.5 will have that. It is included on all the Energy ROM versions (except the Titanium versions, which does not have Sense).
As I already mentioned, the Energy ROM already contains the Carrier Provisioning Tool which will configure the keyboard. You don't have to download anything extra to configure the keyboard. If Energy ROM is what you want, then here is the thread:
http://forum.xda-developers.com/showthread.php?t=562773

can u please tell me step by step how to flash it i want the same one you have

Dude, flashing ROMs is something you shouldn't attempt unless you know how to do it. There is tons of info in the ROM Development subforum on the procedure. The procedure is different depending on whether it is an authorized or a cooked ROM. Spend some time reading up on the procedure instead of just asking questions in the wrong subforum.

tyronekndrck said:
can u please tell me step by step how to flash it i want the same one you have
Click to expand...
Click to collapse
Did you read the guides I linked to? The one is called "Flashing your First GSM Rhodium Rom (For Noobs)"! The name kinda says it all. Its VERY step-by-step, and meant to be very simple, straight-forward and idiot-proof. The author put lots of work into these instructions, and did a great job. Use it!
http://forum.xda-developers.com/showthread.php?t=550540
Just download the ROM you want, and follow the noob instructions. Its pretty simple.
But as I said earlier, its a very good idea to read through all the stickied guides I linked, and browse some through the threads (particularly the last few pages). Random glitches sometimes popup. Glitches that other people encountered and found solutions to. So it can save you a lot of headaches (and anxiety) if/when something random happens during a flash.

[Q] Android ROM for Raphael!

Will it be possible to make any true standalone Android ROM without using windows?
And for what device are this settings "RAPH800"?

Currently, no, but there is workaround - a light ROM with dualboot or directly HaRET in autorun.

Neopeek is working on it at the moment. It will come in the next few weeks. Be patient!

e334 said:
Neopeek is working on it at the moment. It will come in the next few weeks. Be patient!
Click to expand...
Click to collapse
could you please give more info or a link

In the next days i will look into dzo's script and adopt our kernel + ramadresses to get a full working nbh so that i can flash it onto my device. Hope everything goes well. This will take some serious concentration. This is what I am going to do:
Compile the kernel from scratch
Strip-out nb.os + nb.payload.os from vogue / kaiser / polaris to see what's going on
Recompile a new test-nbh to NAND-FLASH it as bootloader for Android
And last but not least: Adopt NoMoRootFS
I hope I and my device won't get stuck with this (I only have 1 device to test). If you wanna share your thoughts or contribute this then just answer to this discussion and share your ideas. I will keep you updated on this and in my free time I will also try to update the various Android builds. But I can't promise you to do so.
Click to expand...
Click to collapse
-neopeek
http://www.neopeek.com/en/community...67-Flashing+Android+on+our+devices?groupid=13 (mods please remove if this violates any rule of xda..)

Keep in mind that currently us TP user's DON'T have working camera (working on), and faster power drain (working on.) so if you end up using this rom (when it's done and released in time) you will have a phone that drain's faster then WM (meter usage is PRETTY accurate though itself.), and no camera anymore (until they finish adding support, and THEN add to this guy's kernal for the said ROM.), just so you know this
Currently, dual booting works just fine, and haven't experienced any negative's to date since using it this way. Hope that helps.

Ok. Tnx for the answers.
But can someone explain to me why it is so difficult to make working ROM for TP when the HTC Hero have the same hardware and powered up with Android? I am confused about that.
For what phone are startup settings (RAPH800)?
How much it will be faster with ROM flashed in nand memory than one run by heret in WM?
Tnx

mikx said:
Ok. Tnx for the answers.
But can someone explain to me why it is so difficult to make working ROM for TP when the HTC Hero have the same hardware and powered up with Android? I am confused about that.
For what phone are startup settings (RAPH800)?
How much it will be faster with ROM flashed in nand memory than one run by heret in WM?
Tnx
Click to expand...
Click to collapse
Uhm the Hero comes with Android 'from the factory' - it's a native Android device. Just like WinMo is native to our devices...
The brilliant devs are literally trying to reverse engineer drivers so Linux/Android can run on our WinMo phones.
I forgot to answer your other questions... NAND should give some performance boost, but I don't know how much. Probably not much, it didn't do much for the RHOD - albeit a little.
Phone startup settings, you should have a STARTUPS folder and it should have the RAPH800 startup in there...

Edit: (removed post, question was already answered)
Cant wait for nand support , i loved it on my Kaiser

Theoretical question: Will installation to NAND and starting directly from bootloader affect performance positively?

Corias said:
Theoretical question: Will installation to NAND and starting directly from bootloader affect performance positively?
Click to expand...
Click to collapse
In theory yes, but so far the benefits have been minor, if any. Of course the NAND that is functional for the TP2 isn't technically a full NAND, so it's probably not the best example to use.

arrrghhh said:
Uhm the Hero comes with Android 'from the factory' - it's a native Android device. Just like WinMo is native to our devices...
The brilliant devs are literally trying to reverse engineer drivers so Linux/Android can run on our WinMo phones.
I forgot to answer your other questions... NAND should give some performance boost, but I don't know how much. Probably not much, it didn't do much for the RHOD - albeit a little.
Phone startup settings, you should have a STARTUPS folder and it should have the RAPH800 startup in there...
Click to expand...
Click to collapse
Tnx for the answer. I know that I have RAPH800, but it can't work on my TP, only settings that work are RAPH, and I was wondering for what phone are these RAPH800 settings??

mikx said:
Tnx for the answer. I know that I have RAPH800, but it can't work on my TP, only settings that work are RAPH, and I was wondering for what phone are these RAPH800 settings??
Click to expand...
Click to collapse
I'm not sure how to answer your question. Babijoee's builds have a STARTUPS folder, do you not have this?

NAND ?

Hi developers,
i have a big question:
I read some time ago, that it is possible to install android on NAND of the HD2.
My question is : is it possible to install it on the NAND on the Touch Pro?
Because it is really slow, if i run android over MicroSD card, and it would be awsome ,when android runs faster.
Best regards,
BikerBoy030

At the moment (and to my knowledge) the answer to your question is no. User e334 tried but failed and bricked his phone. You can read more about his attempt in THIS thread. He was attempting to find out a few values that are apparently required but he did leave a few hints of his findings in that thread.
By the way, what version or build (neopeek-variants or xdandroid) are you using and have you updated everything to reflect the latest that is out and relevant.

brick !!! too sad
So, is this the end of hope for NAND on touch pro ???
pls somebody told me !!!

For now, yes :enter sadface of choice here: However, the xdandroid dev team are steadily working at improving stability and adding features some doubted at first; such as camera which is, in testing phase atm. The only thing I can say is that, "it ain't over till it's over!"
n-Joie! (Enjoy)

BikerBoy030 said:
I read some time ago, that it is possible to install android on NAND of the HD2.
My question is : is it possible to install it on the NAND on the Touch Pro?
Because it is really slow, if i run android over MicroSD card, and it would be awsome ,when android runs faster.
Click to expand...
Click to collapse
Just FYI, NAND will not provide any improvements in speed. The optimizations really need to happen in the system, moving to NAND will not solve those problems.
The HD2 guys had a ridiculously complete port of Android when they were still on Haret. We're still not near that stage.
They have it easy, they just rip builds from Desire, etc...

thanks for the fast answer:
that is really sad, that he briked his phone....this is such a sweet phone
I used xandroid, updatet all and could use all programms etc.
But it wasn't smooth...it stocks a bit at all,what it did.
It feels like it used a "bullet-time-mode"
Maybe it would be enought if i willl overclock it to 710 mhz this COULD be enought, but i didn't tested it.
Wich version is more smooth: neopeek or xandroid?
Regards:
bikerboy030

To my knowledge, OC'ing will not help stability. If anything it will make it more unstable. Neopeek builds seem smoother but requires more setup time upfront (multi-partitions and what not). XDAndroid builds may seem rocky at first but are much quicker to setup and it has a nice plug-n-play feel.
n-Joie! (Enjoy)

i had no problems with the stability, it was only too slow.
than i will try neopeek, maybe it feels better.
the problem is: a good friend owns a desire z, overclocked to 1400mhz...that is smooth.....
but if the touch pro works smooth, it would be fine

Well, i can be totally honest to say as far as speed, that XDA android runs quicker then WM does even on my touch pro. I am running wm6.5.5 NRG rom (jan.4), which is pretty zippy to a month ago version of 6.5.5, noticably, but android is actually visually faster. Now that camera is working fine, battery i get around 7-8 hours with little less then normal usage, and would honestly use it SOLELY if it didn't randomly drop data and needed a reset to fix (which i usually just stay in WM when it happens.), but ALSO mostly since at work (IT Tech) i use tethering a lot to grab a driver almost daily (our net connection is 'clear' and is a bit worse in speed then my phone. SAD yes.)

Hmm ... I'm one of those people who eagerly await with great versions of NAND. What exactly is needed to it came to Raphael? Of course, I'm not asking for what must have been fixed and asking, I assume that in theory it already is. Let me add that I've read about, whose founder bricked his Raphael.

Bootloader is required.

Corias said:
Bootloader is required.
Click to expand...
Click to collapse
Ok, I'll ask differently. What is needed to create this Bootloader for Raphael?

GoldAngelo said:
Ok, I'll ask differently. What is needed to create this Bootloader for Raphael?
Click to expand...
Click to collapse
Knowledge of how to write a bootloader? What do you mean?
We have one called tinboot that dzo wrote for the vogue guys. That's what the RHOD is using, but A LOT of work needs to be done to get it to work on other devices. It's not even a full NAND flash for the RHOD....

arrrghhh said:
Knowledge of how to write a bootloader? What do you mean?
We have one called tinboot that dzo wrote for the vogue guys. That's what the RHOD is using, but A LOT of work needs to be done to get it to work on other devices. It's not even a full NAND flash for the RHOD....
Click to expand...
Click to collapse
I would like to know what is needed to version NAND and how this process (creating nand and tools that you need, such as the bootloader and other ) should follow you. Of course, theoretically. Perhaps someone from another country would take on this (not everyone knows looks at XDA;-) maybe after the publication of the national forums that someone will take).

GoldAngelo said:
I would like to know what is needed to version NAND and how this process (creating nand and tools that you need, such as the bootloader and other ) should follow you. Of course, theoretically. Perhaps someone from another country would take on this (not everyone knows looks at XDA;-) maybe after the publication of the national forums that someone will take).
Click to expand...
Click to collapse
I'm no dev, so I won't be able to help you out directly. But look up tinboot, and look at what us TP2 guys have for a NAND bootloader thus far.
ACL has a GIT repo for our NAND tree that is publicly available as well.

We started talking about Raph and Diam nand in the Blackstone thread somewhere around here: http://forum.xda-developers.com/showpost.php?p=11051880&postcount=124
I've compiled the kernel for blackstone-nand and will try to flash this onto my diamond tonight or maybe tomorrow. Wish me luck

detlef25 said:
We started talking about Raph and Diam nand in the Blackstone thread somewhere around here: http://forum.xda-developers.com/showpost.php?p=11051880&postcount=124
I've compiled the kernel for blackstone-nand and will try to flash this onto my diamond tonight or maybe tomorrow. Wish me luck
Click to expand...
Click to collapse
I wish you a lot of luck
If you succed please share your values,maybe we can make it to boot ext2 partition bulids

Is 512 MB of Raphael's internal NAND enough for Android?

Corias said:
Is 512 MB of Raphael's internal NAND enough for Android?
Click to expand...
Click to collapse
More than enough, I thing the G1 had like 192 or something.

arrrghhh said:
More than enough, I thing the G1 had like 192 or something.
Click to expand...
Click to collapse
Yeah,a build is about 150 mb

Gruessle -> Kaiser Froyo Rom

06/16/2011
The screenshots are not important. This is not a theme!
You can install a theme from here, for example if you like.
The theme it comes with is the:
Go Louncher Classical Theme (The new version of it)
The software installed is also not important, because you can remove it.
Google Market is installed, and you can install what ever you like, just like on your computer.
https://market.android.com
This is the actual Android Froyo operating system for the HTC Kaiser
So, stop asking me for screenshots and software installed, it's not relevant.
And the how to install guide is been posted here
Bug reports are welcome, other then that, I don't wont to hear from you.
Don't post a thank you either, there is a bottom for that, and you can also vote on the poll up there, but install and test it first!
Again Bug reports only, please!​
I been working on this for 3 days straight, and figure I'll share what I got.
Everything seems to be working, except the camera is blurry, but that seams to be the norm.
Included is the rom, radio and kernel
ROM: 2.2.1
Kernel: 2.6.25
Radio: KAISER 1.70.19.09
Panel: 2
Key Map: US Normal
Resolution: 240x320
Storage: Nand & Nand
Most everything is installed in userspace and can be uninstalled or upgraded.
Oh got GO Launcher EX installed (Also in user space)
Credits:
I stole ideas from, and used following tools:
Makers of atools
Makers of NBH creator
HTC Flasher
kallt_kaffe
Krazy-Killa
dzo (dzo's posts wore a big help. just wish he would answer his own questions after he found the solution)
n2rjt
and many more.
@todo
Resize NAND partitions to the smaller system size
Original post and download Links are posted on my blog:
http://press.pzzazz.net

Can you write something more about this? Is this your system and kernel(compiled yourself)? Any changes?

MaRekRM said:
Can you write something more about this? Is this your system and kernel(compiled yourself)? Any changes?
Click to expand...
Click to collapse
Yeah witch apps are include. Some yours tweaks or etc... ???

MaRekRM said:
Can you write something more about this? Is this your system and kernel(compiled yourself)? Any changes?
Click to expand...
Click to collapse
That sounds like a trick question.
Yes, at first I compiled everything my self but then to resolve bugs, I looked at other systems and basically stole stuff from them to fix my bugs. In other words, I can't take all the credit, it was a community effort.

Neo2SHYAlien said:
Yeah witch apps are include. Some yours tweaks or etc... ???
Click to expand...
Click to collapse
I removed most everything from the system and installed it in user space. So the system is very lean. You can uninstall what you don't like.

how is the rom？just waiting to see

gruessle ...!! thanks for your efforts in getting this done... I been looking from long time to install Android on my HTC TyTN II. However i was not able to get the proper build...
can you share the screenshots of the build which you provided as well some steps at high level on installing this..
Thanks in advance.

Please, I don't really understand how to go upgrade this. I find it hard to do. Is everything needed packaged in this download, or please can u list things needed to change to android. I'll appreciate your response.

tundelogic said:
Please, I don't really understand how to go upgrade this. I find it hard to do. Is everything needed packaged in this download, or please can u list things needed to change to android. I'll appreciate your response.
Click to expand...
Click to collapse
here is the howto
http://forum.xda-developers.com/showthread.php?t=680518

kkp said:
gruessle ...!! thanks for your efforts in getting this done... I been looking from long time to install Android on my HTC TyTN II. However i was not able to get the proper build...
can you share the screenshots of the build which you provided as well some steps at high level on installing this..
Thanks in advance.
Click to expand...
Click to collapse
The screenshots are not important.
This is not a theme.
You can install a theme from here, for example if you like:
http://golauncher.goforandroid.com/category/themes/
The theme it comes with is the:
Go Louncher Classical Theme (The new version of it)
The software installed is also not important, because you can remove it.
Google Market is installed, and you can install what ever you like, just like on your computer.
https://market.android.com/
This is the actual android froyo operating system.

Anyone else having trouble getting the kernel to install?
I get to 33% and the phone reboots...
Radio installed fine even though I was already using 1.70.19.09, just to be sure I installed everything in the package.

Installed HardSPL 3.34 and a WinMo 6.1 rom (custom) to see whats wrong. Installed L1q1d's kernel and goes right in like it should.
Checked .NBH with NBHCreator and only found 1 thing wrong: kernel set to Eclair instead of Froyo. Changed to Froyo and saved, attempted reflash and still won't go in...
;(Losted);

I also tried to install this kernel but I can't. Flashing in hardspl after few second give folowing error:
00018003
Os Fail
Update Terminate
UPDATE Fail.
Changing parameters in atools not helping. Every another kernel is flashing without problems so it's not phone fault

Gruessle, thanks for your efforts! I want to try your rom but being a noob waiting for more comprehensive list of known errors before flashing it to my kaiser.

Ok, quick "bug report":
After working with the kernel pack multiple times I have come to the conclusion that there might be a bug in the actual kernel file itself, throwing a code back to HardSPL and RUU (how I install).
I first noticed a problem in that the kernel was originally set up for a Polaris and had no resolution set. The size of the file should be unimportant as Scoot's newer kernel is in the order of 3.2-3.3MB in size (with the RIL patch installed it gets even larger), this one is 3,099KB, and l1q1d's is almost always 3,092KB.
The second issue I noticed is with the Froyo package itself... It's split up into many files (open the package in 7zip and you'll see what I mean). Normally, the packer has the files all listed inside the .tgz file, this one has the files inside many other files.
I have thus not installed the system on either phone because (correct me if I'm wrong), the kernel contains the basic directories for where everything is installed, and if I were to try and install this package on say, l1q1d's kernel, the phone would most likely crash because the files would not be found, including /system.
If ANYONE wants to dig deeper into this problem, feel free to message me. Personally, I think we've about finished getting all we can from the Kaiser, and much respect goes out to those who have done all the work in the past, but there's always that glimmer of hope that someone will find a way to pack this into a working rom installable through RUU or HardSPL.
I have one last thing to say:
Gruessle, please do your homework BEFORE posting things like this. There are people out there who still depend on this phone to operate as it is their only phone. I Personally cannot afford to go spend $100-200 on a replacement phone if this one goes down (thats why I have 2 of them). If you post something that does not work on the platform that you say it will, please correct it or move it to the proper forum.

BTW, I call shenannegans on one of the 5-star votes... just sayin'.

Your kernel have fake ;/ . rom works great ;D
sorry for bad english;p

PoXFreak said:
Ok, quick "bug report":
After working with the kernel pack multiple times I have come to the conclusion that there might be a bug in the actual kernel file itself, throwing a code back to HardSPL and RUU (how I install).
I first noticed a problem in that the kernel was originally set up for a Polaris and had no resolution set. The size of the file should be unimportant as Scoot's newer kernel is in the order of 3.2-3.3MB in size (with the RIL patch installed it gets even larger), this one is 3,099KB, and l1q1d's is almost always 3,092KB.
The second issue I noticed is with the Froyo package itself... It's split up into many files (open the package in 7zip and you'll see what I mean). Normally, the packer has the files all listed inside the .tgz file, this one has the files inside many other files.
I have thus not installed the system on either phone because (correct me if I'm wrong), the kernel contains the basic directories for where everything is installed, and if I were to try and install this package on say, l1q1d's kernel, the phone would most likely crash because the files would not be found, including /system.
If ANYONE wants to dig deeper into this problem, feel free to message me. Personally, I think we've about finished getting all we can from the Kaiser, and much respect goes out to those who have done all the work in the past, but there's always that glimmer of hope that someone will find a way to pack this into a working rom installable through RUU or HardSPL.
I have one last thing to say:
Gruessle, please do your homework BEFORE posting things like this. There are people out there who still depend on this phone to operate as it is their only phone. I Personally cannot afford to go spend $100-200 on a replacement phone if this one goes down (thats why I have 2 of them). If you post something that does not work on the platform that you say it will, please correct it or move it to the proper forum.
Click to expand...
Click to collapse
1) The kernel doesn't care where you place the files. Right now I use a debian system with Ferora and Gentoo in a chroot. Both work fine with the Debian kernel.
In other words, if you have a kernel that works for you then use that it should work with the rest of the installation.
2) I don't get what you mean with files are "split up into many files", I am just guessing but you must be extracting it wrong. Maybe it's a windows thing, I haven't used windows in 15 years so I wouldn't be able to help you with that.
3) I have included everything you need to duplicate what I got, which works for me, and it appears to work for others too. Now i don't use that phone much, and there might be bugs I am unaware of, but don't tell me it doesn't work at all, just because you can't get it to work.

barmalini said:
Gruessle, thanks for your efforts! I want to try your rom but being a noob waiting for more comprehensive list of known errors before flashing it to my kaiser.
Click to expand...
Click to collapse
barmalini, it appears that a few people have trouble installing the Kernel, but the ROM seams to work for everybody as far as I can tell.
According to my server records the files have been downloaded over 200 times and I have yet to hear a complain about the ROM.
So I would say try to install the Kernel, but if you can't still use the ROM with a Kernel that works for you.
If you have trouble installing from windows you can also try a live CD from debian or knoppix. I installed everything from a Debian system. (Knoppix is based on Debian)
If you don't know what a live CD is then go here for info:
http://wiki.debian.org/LiveCD

PoXFreak said:
Installed HardSPL 3.34 and a WinMo 6.1 rom (custom) to see whats wrong. Installed L1q1d's kernel and goes right in like it should.
Checked .NBH with NBHCreator and only found 1 thing wrong: kernel set to Eclair instead of Froyo. Changed to Froyo and saved, attempted reflash and still won't go in...
;(Losted);
Click to expand...
Click to collapse
PoXFreak,
you are not the only one having trouble, installing the ROM it appears.
I am wondering, are you also using Microsoft Windows to install the ROM?
If so can you try again with Linux, because it worked fine for me.
If you don't have Linux you can use a Live CD
Also if you can't get it to work, try the ROM with a Kernel that works for you.
Please report, I will check back.