Develop Bugs

To **All Rom cookers** to avoid making Full and Lite version use PocketPC Installer

Dear Sirs and senior members and members:
At the beginning I would like to make it clear why I called the Title like that, not to make me important or to gain more readers, its because I appreciate the great efforts that have been done in this Forum to make it great and to help each other to find new ways to make your work better and better.
My Suggestion this time is to avoid the unnecessary copies of the same Rom build with all the extras or without anything “Full, Lite, Big storage etc…” and I think all of the Rom cookers faced the problem that they cant make a Rom which will make all the members satisfied, and many of them got the problem that as soon as they are finished with there ROMs a new versions appears of the same programs included in there ROMs and that way the cant be called NEW because of some old things, and the most weird thing that the Rom cookers make is to include many programs in the Rom that an be installed separately on the memory card which I can understand at all they work hard for very long time to make a fast and stable Rom as possible and they put all the extras in the Rom which make it heavy without any reason programs like “Winrar, Adobe acrobat reader, Adobe Flash lite, Real Player, etc…” puts many megabytes in the device memory and the Rom.
My SUGGESTION is very simple please use some kind of a program Like PocketPc installer (http://www.pocketpctoolkit.com/WhatIsIt1_PPCInstaller.php) which you make include all what you want of programs in it and port it with the Rom which we can copy to our memory cards to install the chosen programs that any one of us likes on the device memory or the memory card just like some modified copies of Windows XP which asks after the installation which programs to install , Please make a look at this program to get more detailed information about the idea.
Thank you for your kind Patience to read the Long post.
Ahmedkom

The foundation of XDA and its tools is built on free and open software, while windows mobile is not, the installers that are used, the build tools that are used, and the other various tools we use are built on donated time, resources, and a willing to share knowledge. We do not however want to use software that requires us to pay for to package the software that we are trying to give to the community to make better.
This is not an advertising forum, nor is this a place to try to make a false plea to our developers/packagers to buy and use software that you may own and are selling.
While your tool could be of use. If you were to release it free, I could see them using it. As for paying for something so we can give the community free roms doesn't seem very smart.
Thanks,
Andrew

exstatica said:
The foundation of XDA and its tools is built on free and open software, while windows mobile is not, the installers that are used, the build tools that are used, and the other various tools we use are built on donated time, resources, and a willing to share knowledge. We do not however want to use software that requires us to pay for to package the software that we are trying to give to the community to make better.
This is not an advertising forum, nor is this a place to try to make a false plea to our developers/packagers to buy and use software that you may own and are selling.
While your tool could be of use. If you were to release it free, I could see them using it. As for paying for something so we can give the community free roms doesn't seem very smart.
Thanks,
Andrew
Click to expand...
Click to collapse
My SUGGESTION is very simple please**(Use some kind of a program Like)** PocketPc installer
Please **(Take a look at this program)** to get more detailed information about **(the idea)**.
I am not and dont have any cnnection to this site or the programm maker to push you to buy anything, and the link that i have gave is just to show you my idea with Pictures and more details .
Thank you for your replay and i would like to know your openion for this idea.
Ahmedkom

Hi ahmedkom,
I totally agree with your idea, rom chefs could make an ultra lite roms as the base rom and including an installer program to run CAB files from memory card. So that everyone could have their custom set of program and setting, and remove/updates could be apply without the process of downloading a new buly rom and take risks of flashing the device every week/few days...
CAB files could do manything from minor settings, registry, file operation to full program installation.
Beside PocketPC Installer, I suggest to use a program called CeleCommand (http://www.yonsm.net/read.php?329) for installer program. Worth try it out coz it can do many tasks..
just my 2 cents.

I totally agree ahmedkom too.

ok, i'm agree with you, but there are differences between integrating the apps and installing them after running the rom, many of apps use windows directory to install some files and that give the OS overload, otherwise if they are already integrated with the rom, they will not overload on the OS.
we have to keep this (lite and full versions) if the user doesn't need some apps integrated on the rom, he can use the lite version then he have to install whatever he wants.
the good thing from cookers is to create lite and full versions with make add ons cabs for the apps were not include on the lite version.
good thread dude for users and cookers .

Although I don't think it's a straight replacement for options, or variations I should say, in a ROM, I do think this looks like a damn useful app.

its a big honor to me to get answers from the seniors and i am very glad for you post its right but i didnt mention the programs that are installed in windows folder i am talking about the programs that we can install in the memory card just like pocket rar ,realplayer, totalcommander,gsfinder,1-calc LITE,tcpmp etc..

[Q]What is The Difference Between MARY and AX3L ROMS

and Who is The BEST ROM ?

There is no such thing as a "best ROM" - it's all up to personal preference
Hi -
There is no one right ROM for Trinity. Here's a quick explanation for what a ROM really is. There are many people on this board who know more about ROMs than I do, so if anyone sees any errors in what I've written, please let me know.
A ROM is a collection of software packaged together that when flashed to your phone installs the software. ROM packages generally consist of four categories of software:
1.) An operating system (some flavor of Windows Mobile, 5 or 6)
2.) Radio software (Radio ROM)
3.) Phone software (Dialer, Task Manager, Multimedia, SMS/MMS software, contact list)
4.) All other software (Adobe Reader, TomTom, etc.)
People create new ROM packages by gathering an operating system, a radio, and a collection of software, and "cooking" them into a single distribution file, usually in the form of a CAB compression file.
The differences between AXL and Mary are in the OS, radio and other software they have mixed together. You have to look at the contents of each ROM yourself and compare to see the exact differences. Although it would be nice, I'm not aware of anyone listing out the differences between the software choices made by each of the main ROM cookers, so you have to do it yourself.
Some important notes on ROM packages:
1.) Any software that is "cooked" into the ROM can't be removed or updated, it's in there permanently until you change your ROM. This is something to consider if you want to be able to upgrade to future versions, and is the reaosn many ROM cookers also make a "lite" version of their ROM.
2.) I'm pretty weak on this, but from what I understand in addition to the normal physical ROM memory, there is a section of physical ROM called "hidden" or "extended" ROM, and the cookers have figured out how to make that ROM available for use. This is why some ROMs show 70+ megs of ROM/RAM available. I think this extended ROM can also be used to store software.
3.) The operating systems (OS's) do continue to change. People get new phones from their telecom operator, and when they dissassemble the phone's ROM, they can extract the new OS's and check the version numbers. There is no way I know of currently to update the OS without flashing a completely new ROM. Different ROMs include different versions of the operating system, although many of the ROM cookers are quick to re-release their ROMs when a new OS comes out.
4.) Any software that can be installed manually can be installed in a ROM. This includes "trial" or "unregistered" versions. For that software, it may be installed on your phone when you install the ROM, but it is a limited-use version and you will need to purchase the software and get a registration code to unlock the full software. If the software is "cooked" into your ROM and you decide not to use it, YOU CAN'T UNINSTALL IT without reflashing to a new ROM. It won't do any harm, but it will use up memory that could be put to better use.
5.) A suggestion on other software: If you flash your OS often, it makes things easier to keep copies of the CAB files for your favorite other cab installations on your SD card, so you can easily reinstall them when you reflash the OS.
6.) Most of the ROMs use the same installer software,which works well and can recover from some errors (just follow the instructions or if no instructions retry the flash procedure). However, some telecom operators install something called a Service Provider Lock (SPL) to prevent people from installing "unapproved" software on their phone. Removing or otherwise getting around this SPL is a process called "unlocking" - if you try to reflash your phone's ROM, and something goes wrong, this SPL could prevent you from being able to fix your phone, making it useless (or "bricked"). There are software packages that should be able to fix a bricked phone (search the board to find), but it is easier to remove the SPL first, so you never have to worry about crashing your phone.
7.) If you remove your SPL, you have technically violated the terms of your contract with your service provider!!!! In daily use, it really doesn't affect them, so they probably won't make a stink about it, and probably can't tell you've done so. But, if you bring it in for service, send it in under warranty, call their service line to get support, the technician will probably see you have removed your SPL, and can refuse to provide service or warranty support. However, the techs are people and depending on the issue may or may not make a big deal about it, but it's certainly within their right to refuse to service for free.
8.) There are differences in telecom providers!!! This is particularly important with respect to Radio ROMs. If you think about it, your phone has to send the right signals to your service provider's radio tower to make a call. The specific information it has to send and the manner in which it sends it are determined by the radio protocol, which is built into the radio software. As a result, some radio software will not work with some providers, and some will work better than others. This difference willbe regional, so consider where you will be using the phone (Asia, Europe, SA, Africa, NA). Some radios could even be configured to specific providers (but I don't know for sure).
9.) Latest vs. most stable - sometimes, the latest versions introduce new bugsor are less stable than others, so consider this as well.
10.) Most of the differences between the ROMs seem to revolve aroudn the cooker's choices for phone software - the dialers, the contact managers, etc. These primarily change the "look and feel" of the phone rather than the raw performance or capabilites. Since look and feel is the big difference, it's impossible to say which look and feel everyone will like - it's a matter of taste / personal preference.
11.) Don't bug the cookers!!!! The people cooking ROMs for us are doing it in their spare time. They're not getting paid to do it, they're just trying to help each other out. While they seem to be interested in hearing about bugs so they can fix their ROMs, pestering them with requests to make some piddly change just for you is rude. Don't pester them with change requests and customizations, and then throw a hissy fit when they don't want to do it your way. If you don't like their ROM, then cook your own.
So, to pick the ROM that works for you, you're probably going to have to try a few out. The combination of OS and Radio will likely be regional (some will not be able to use the latest radio, for example), and form there on in you have to choose which has the dialer/contact manager you like the most, and includes the software you want to have (or go with a lite version).
Good luck!
Mike

to Mike (landshark),
thank you and congratulations on your excellent explanation. I wish I read this when I bought my device, would make things much easier.

Great post!!!!
Good work!!!!
will be very usefull!
Thank you!

Wonderful post!!!!
Beautiful work!!!!
will be bloody usefull!
Orz

Sticky pls !

Thanks! Very useful for a noob like me

Question about SSPL
landshark said:
Hi -
There is no one right ROM for Trinity. Here's a quick explanation for what a ROM really is. There are many people on this board who know more about ROMs than I do, so if anyone sees any errors in what I've written, please let me know.
A ROM is a collection of software packaged together that when flashed to your phone installs the software. ROM packages generally consist of four categories of software:
1.) An operating system (some flavor of Windows Mobile, 5 or 6)
2.) Radio software (Radio ROM)
3.) Phone software (Dialer, Task Manager, Multimedia, SMS/MMS software, contact list)
4.) All other software (Adobe Reader, TomTom, etc.)
People create new ROM packages by gathering an operating system, a radio, and a collection of software, and "cooking" them into a single distribution file, usually in the form of a CAB compression file.
The differences between AXL and Mary are in the OS, radio and other software they have mixed together. You have to look at the contents of each ROM yourself and compare to see the exact differences. Although it would be nice, I'm not aware of anyone listing out the differences between the software choices made by each of the main ROM cookers, so you have to do it yourself.
Some important notes on ROM packages:
1.) Any software that is "cooked" into the ROM can't be removed or updated, it's in there permanently until you change your ROM. This is something to consider if you want to be able to upgrade to future versions, and is the reaosn many ROM cookers also make a "lite" version of their ROM.
2.) I'm pretty weak on this, but from what I understand in addition to the normal physical ROM memory, there is a section of physical ROM called "hidden" or "extended" ROM, and the cookers have figured out how to make that ROM available for use. This is why some ROMs show 70+ megs of ROM/RAM available. I think this extended ROM can also be used to store software.
3.) The operating systems (OS's) do continue to change. People get new phones from their telecom operator, and when they dissassemble the phone's ROM, they can extract the new OS's and check the version numbers. There is no way I know of currently to update the OS without flashing a completely new ROM. Different ROMs include different versions of the operating system, although many of the ROM cookers are quick to re-release their ROMs when a new OS comes out.
4.) Any software that can be installed manually can be installed in a ROM. This includes "trial" or "unregistered" versions. For that software, it may be installed on your phone when you install the ROM, but it is a limited-use version and you will need to purchase the software and get a registration code to unlock the full software. If the software is "cooked" into your ROM and you decide not to use it, YOU CAN'T UNINSTALL IT without reflashing to a new ROM. It won't do any harm, but it will use up memory that could be put to better use.
5.) A suggestion on other software: If you flash your OS often, it makes things easier to keep copies of the CAB files for your favorite other cab installations on your SD card, so you can easily reinstall them when you reflash the OS.
6.) Most of the ROMs use the same installer software,which works well and can recover from some errors (just follow the instructions or if no instructions retry the flash procedure). However, some telecom operators install something called a Service Provider Lock (SPL) to prevent people from installing "unapproved" software on their phone. Removing or otherwise getting around this SPL is a process called "unlocking" - if you try to reflash your phone's ROM, and something goes wrong, this SPL could prevent you from being able to fix your phone, making it useless (or "bricked"). There are software packages that should be able to fix a bricked phone (search the board to find), but it is easier to remove the SPL first, so you never have to worry about crashing your phone.
7.) If you remove your SPL, you have technically violated the terms of your contract with your service provider!!!! In daily use, it really doesn't affect them, so they probably won't make a stink about it, and probably can't tell you've done so. But, if you bring it in for service, send it in under warranty, call their service line to get support, the technician will probably see you have removed your SPL, and can refuse to provide service or warranty support. However, the techs are people and depending on the issue may or may not make a big deal about it, but it's certainly within their right to refuse to service for free.
8.) There are differences in telecom providers!!! This is particularly important with respect to Radio ROMs. If you think about it, your phone has to send the right signals to your service provider's radio tower to make a call. The specific information it has to send and the manner in which it sends it are determined by the radio protocol, which is built into the radio software. As a result, some radio software will not work with some providers, and some will work better than others. This difference willbe regional, so consider where you will be using the phone (Asia, Europe, SA, Africa, NA). Some radios could even be configured to specific providers (but I don't know for sure).
9.) Latest vs. most stable - sometimes, the latest versions introduce new bugsor are less stable than others, so consider this as well.
10.) Most of the differences between the ROMs seem to revolve aroudn the cooker's choices for phone software - the dialers, the contact managers, etc. These primarily change the "look and feel" of the phone rather than the raw performance or capabilites. Since look and feel is the big difference, it's impossible to say which look and feel everyone will like - it's a matter of taste / personal preference.
11.) Don't bug the cookers!!!! The people cooking ROMs for us are doing it in their spare time. They're not getting paid to do it, they're just trying to help each other out. While they seem to be interested in hearing about bugs so they can fix their ROMs, pestering them with requests to make some piddly change just for you is rude. Don't pester them with change requests and customizations, and then throw a hissy fit when they don't want to do it your way. If you don't like their ROM, then cook your own.
So, to pick the ROM that works for you, you're probably going to have to try a few out. The combination of OS and Radio will likely be regional (some will not be able to use the latest radio, for example), and form there on in you have to choose which has the dialer/contact manager you like the most, and includes the software you want to have (or go with a lite version).
Good luck!
Mike
Click to expand...
Click to collapse
Sow basicly if I use Soft SPL and install a rom that has no radio and something goes wrong I can return to my original ROM. Is that right?

Thread renamed: added [Q] tag.
Please read the Announcements in the forums regarding posting rules!

Upgrade Rom Without Data Loss...Is it remotely possible?

I recall reading a little while back a message (somewhere, sorry for not remembering) that there was a way (if i remember correctly) to make a ROM Update Utility that wouldn't harm the data on the phone (excluding MicroSD which we have to remove when updating). I don't know the truth to this, but the idea behind being able to upgrade roms and keep personal data (and maybe installed applications) is cool. I know that whenever I upgrade roms the biggest part is reinstallation of my programs (it gets very annoying!). Its not so annoying that i want to toss my Dash against the wall, I just don't like having to do it over and over again (especially with new roms and updates coming out).
Essentially, having to reinstall, and re-setup, my phone with each ROM update is really what keeps me from upgrading a big part of the time (ie: going from the Energy Rom to Ookba's new 3vo ROM). Is there any way to be able to make this process of reinstallation easier?

Have a look here:
http://forum.xda-developers.com/showthread.php?t=520009

orb3000 said:
Have a look here:
http://forum.xda-developers.com/showthread.php?t=520009
Click to expand...
Click to collapse
That was exactly the link I had looked at (and apparently not too long ago either). I read through a good part of it, but its past Midnight here, and I am drowsy beyond belief , so I didn't make much sense of any of it. Essentially I don't cook roms, and it mentioned something about the chef having to make the RUU in a specific way (correct?). Is this in our near future?

Da_G alread made a test ROM and updated the ROM sucessfully for the Raphael. I'm sure our smartphones aren't too far from getting it either. They just have to make some tools for us chefs to use it in our kitchens now Soon.

NRGZ28 said:
Da_G alread made a test ROM and updated the ROM sucessfully for the Raphael. I'm sure our smartphones aren't too far from getting it either. They just have to make some tools for us chefs to use it in our kitchens now Soon.
Click to expand...
Click to collapse
Awesome! Its great to know how active this community is (even for an old-er phone like this )
Keep up the work all you EXCELLET chefs, devs, hackers, programmers, and any other division of making this phone better

ROMs from other phones

Can I use a ROM from one model phone to another. Ex. can I use the ROM from a Blackstone and use it on a Fuze? I know I can use the blackstone radio but how about the ROM?
thanks

fuzeman219 said:
Can I use a ROM from one model phone to another. Ex. can I use the ROM from a Blackstone and use it on a Fuze? I know I can use the blackstone radio but how about the ROM?
thanks
Click to expand...
Click to collapse
NO!
You can't use another device ROM or RADIO.

thank you sir, but you say you cant use the radio either? in other forums people are using different radios, ex. blackstone radio on a raphael, (fuze)

Yes you can use radios in 2 cases:
1) the radios are compatible. If you're not sure, don't flash it.
2) the phone is security unlocked.
Also, to use a ROM from another device it must be dumped and then ported in a Kitchen, you can't just flash it. The Kernel's and drivers just won't work.
Dave

Well, a teacher I had, always told "you can, but you must not". You can jump down from the roof of a highscraper, but you should not have to do it...
So, you MUST NOT flash a ROM of a device into another different one. Yes, you have tools to do it, but you'll probably get an electronic brick to put in any hole of a brick wall.
There's a part of the ROM which is specific for the device. Another part is specific for the OS. So, some parts of a ROM are related to WM6.1 or WM6.5, etc. and some others are related to a device. That's what is called the Kernel, mainly related to a nk.exe file inside the ROM files. In example, we can run WM6.5 into a Kaiser with a nk.exe belonging to a kaiser and WM6.1... BUT for running same OS of a different device, (i.e. Opal's WM6.1 into Kaiser) you'll completely inutilize (maybe forever) the device. Yes, you can do it if sou have enough money to buy another device, but if you don't want it, I suggest you to send me your device or give it for charity, but not to destroy it.
Another thing you can do is, as you were told, "dumping" the ROM, this is extracting all the files and structure, and then port it (this is, adapting it) to your device's needs - this means, getting your specific drivers and kernel files and substituting them into the folders you obtained of the ROM. (Also, getting the correct screen resolution files). In example, nk.exe and other files will be different for a Kaiser and for a Herald. And you should have different Camera files, as the drivers are different for one device and the other one. Also, a Touch HD uses different screen resolution that a Herald... so you must find the correct files for every device.
This looong post is to tell you that using ROMs from other phones is RISKY and also it GETS LOTS OF JOB (and TIME), and you'll always miss something. Only good, big teams, like to do it, not an only person. And they spend days, weeks, and must correct bugs and make trials and risk their devices even if they have lots of experience.

thanks
thanks folks, makes complete sense..
this leads to another question, how do you know if the radio is compatible with another device, ex. the blackstone radio with a raphael? I know the simple answer is to read the forums, which I have, but besides taking someones word for it, how do you know?

fuzeman219 said:
thanks folks, makes complete sense..
this leads to another question, how do you know if the radio is compatible with another device, ex. the blackstone radio with a raphael? I know the simple answer is to read the forums, which I have, but besides taking someones word for it, how do you know?
Click to expand...
Click to collapse
You have to know about the chips in the phone and what's in the radio firmwhere, I leave it upto the experts .
Just take peoples word for it, if in doubt, don't use it.
Dave

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.