Related
i read around for methods on flashing a rom. this is my first time .i did a back up with hpb backup and put hard spl 2 on my phone. from what i read sdcard is the best route to go . my question is do i need to erase everytihng off of my card before doing the rom? or can i leave it all there put the ruu file on there and get started ? maybe i should ask is there a tutorial to how to do the different methods?
a side note how do i know if a rom is friendly to changing the orientation when you slide for the keyboard
Natureboyhcg said:
i read around for methods on flashing a rom. this is my first time .i did a back up with hpb backup and put hard spl 2 on my phone. from what i read sdcard is the best route to go . my question is do i need to erase everytihng off of my card before doing the rom? or can i leave it all there put the ruu file on there and get started ? maybe i should ask is there a tutorial to how to do the different methods?
a side note how do i know if a rom is friendly to changing the orientation when you slide for the keyboard
Click to expand...
Click to collapse
No you don't have to take everything off the card. Make sure your card is 2gig or smaller and not SDHC. Here is a link to the instructions in the wiki:
http://wiki.xda-developers.com/index.php?pagename=Hermes_SDCardFlash
As far as the keyboard orientation you could search in the rom's thread for any reference to it or just flash the rom and see for yourself.
KK13 said:
No you don't have to take everything off the card. Make sure your card is 2gig or smaller and not SDHC. Here is a link to the instructions in the wiki:
http://wiki.xda-developers.com/index.php?pagename=Hermes_SDCardFlash
As far as the keyboard orientation you could search in the rom's thread for any reference to it or just flash the rom and see for yourself.
Click to expand...
Click to collapse
im confused, does the card need to be 2gb or smaller, not sdhc, to properly do hardspl or general. cause ive read the phone only supports 2gb or smaller microsd. but i have also seen the 16gb or 32gb thread, ive seen others saying about using larger than 2gb cards in their phones. im awaiting the delivery of my phone currently and i have a 4gb microsd i use in my htc excalibur i was planning on using. so im majorly confused as to if im going to be able to use it or not, or if i just need a 2gb to do the intial hardspl then ill be fine w/ my 4gb once i go to a cooked rom.
would greatly appreciate some clarity on this all from someone.
WM05 and bootloader only support 2Gb or less though there is an sdhc patch for WM05.
WM06 had the patch to support SDHC cards from 4Gb up to 32Gb. WM6.1 and WM6.5 are also SDHC compliant.
You need a 2Gb or less sd card to flash an OS or different SPL as the bootloader only supports 2Gb or less. Its not upgradeable.
Now that everythings clear as mud,
Cheers...
You could also pick up a 1 gig (or even a 512meg) card on the cheap to do your flashing, and use the 4 gig for your everyday storage in the phone. Then have the best of both worlds!
psylink said:
im confused, does the card need to be 2gb or smaller, not sdhc, to properly do hardspl or general. cause ive read the phone only supports 2gb or smaller microsd. but i have also seen the 16gb or 32gb thread, ive seen others saying about using larger than 2gb cards in their phones. im awaiting the delivery of my phone currently and i have a 4gb microsd i use in my htc excalibur i was planning on using. so im majorly confused as to if im going to be able to use it or not, or if i just need a 2gb to do the intial hardspl then ill be fine w/ my 4gb once i go to a cooked rom.
would greatly appreciate some clarity on this all from someone.
Click to expand...
Click to collapse
You need a smaller than 2gig card for flashing. Everything else you can use your 4 gig card. (As Ultramag69 and Boog321 say) The original question was to do with flashing hardspl or roms only.
KK13 said:
You need a smaller than 2gig card for flashing. Everything else you can use your 4 gig card. (As Ultramag69 and Boog321 say) The original question was to do with flashing hardspl or roms only.
Click to expand...
Click to collapse
HardSPL only needed to install once, after that you can install whatever ROMs you like many times.
True, but if you use the sd card method to install roms you will still need a 2Gb or less sd card...
ultramag69 said:
True, but if you use the sd card method to install roms you will still need a 2Gb or less sd card...
Click to expand...
Click to collapse
Hi Ultramag
I have a problem installing with sdcard.
Have followed the Wiki, have discussed with you previously, Boog and anagarika still no solution. I have elaborated step by step what I did in separate thread.
Do you mind have a look and advise some?
http://forum.xda-developers.com/showthread.php?t=316726&page=34
StefanHou said:
Hi Ultramag
I have a problem installing with sdcard.
Have followed the Wiki, have discussed with you previously, Boog and anagarika still no solution. I have elaborated step by step what I did in separate thread.
Do you mind have a look and advise some?
http://forum.xda-developers.com/showthread.php?t=316726&page=34
Click to expand...
Click to collapse
Did you try formating the SD card on a desktop (or laptop) computer and not phone with Memaid?? Maybe that has something to do with it. Is it a 2gig card or less than 2 gig??
As KK13 said, try a pc to format the card as the steps are right.
Double check that the .nbh is named hermimg.nbh as I know of at least 2 people who named it herming.nbh, small mistake but a critical one.
Remove and insert the sd card then reboot to tri-colour screen. Might do something.
But I strongly recommend using the PC to format the sd card FAT32.
Cheers...
ultramag69 said:
As KK13 said, try a pc to format the card as the steps are right.
Double check that the .nbh is named hermimg.nbh as I know of at least 2 people who named it herming.nbh, small mistake but a critical one.
Remove and insert the sd card then reboot to tri-colour screen. Might do something.
But I strongly recommend using the PC to format the sd card FAT32.
Cheers...
Click to expand...
Click to collapse
Onya dude .. you have a better way with words !!
ultramag69 said:
As KK13 said, try a pc to format the card as the steps are right.
Double check that the .nbh is named hermimg.nbh as I know of at least 2 people who named it herming.nbh, small mistake but a critical one.
Remove and insert the sd card then reboot to tri-colour screen. Might do something.
But I strongly recommend using the PC to format the sd card FAT32.
Cheers...
Click to expand...
Click to collapse
OK, will find SDconverter and try the suggestion, thx KK and Ultramag
*Newbie* Custom ROM Flashing Guide
Just follow the steps start from 1. Don't skip step unless it is an optional step.
PC Requirement: Windows XP, ActiveSync [Don't try to flash with Vista if you are new], 7zip Installed (Google it)
Connect your device to your computer and make sure the ActiveSync icon appeared on your phone before proceeding. 50% or above bettery is a must. Your phone won't charge when flashing.
1. HardSPL (A Big Big Must)
I asume you are using the original ROM from manufacture as HardSPL won't work with custom ROM.
Download HardSPL V7 from here. Unzip the whole things. Execute the "RUUWrapper" thing and select "Force Using SSPL". Check all the boxes in all the steps and continue with updates. Look at your phone and press "Yes" to everything that prompted. Then your phone will restart in Tri-Color mode [a.k.a bootloader] and start flashing HardSPL.
In this case if any errors appear on your computer screen before the update progress start, soft reset your phone, let it boot into Windows and start RUUWrapper again.
If error appear during flashing progress, then you might in deep hell. Try not to worry. Manually put your device into bootloader (Hold On/Off Btn + Left OK Btn, then push the soft-reset btn). Then start the RUUWrapper again.
End of the step you should see 'HardSPL 2.10Olipro' in bootloader mode.
2. Radio Flashing *Optional*
You can choose not to flash your Radio Stack if you satisfy with the existing. Additional, Radio Stack flashing is the main cause of device bricking (the death of your device)
Choose and download your Radio ROM here. Do some research about the Radio ROM that fits you and your country. Recommended the latest 1.56.70.11. Unpack everything and you will see something similar to HardSPL (RUUWrapper). Don't run RUUWrapper this time.
Let's do the safe way. Format your MicroSD card into FAT32 (Kill yourself if you don't know). Then copy the RUU_signed.nbh into your MicroSD. Then rename RUU_signed.nbh to hermimg.nbh. Put your MicroSD into you phone.
Manually put your phone into bootloader mode. Then a different screen with grey background should appear shortly. Press On/Off btn to start flashing. After the process done (it will tell you when it is done, don't try to judge yourself if you feels that 50% is done), soft-reset your phone.
During flashing, put your phone aside and enjoy your coffee. Don't touch it before it ends as this is dangerous. Don't ever fail radio flashing. Careful, careful and careful.
End of this step, you should see R 1.56.70.11 during Windows Boot.
3. Custom ROM Flashing
First, download Dopod 838 Stripped ROM. Then unpack it. Delete your previous hermimg.nbh in MicroSD which you use to flash Radio Stack. Then copy RUU_signed.nbh from Dopod 838 Stripped ROM to your MicroSD and rename it to hermimg.nbh. Put your device into booloader and start flashing like how you flash you radio rom. After it done, give your device a Hard-Reset (Hold Left + Right softkey and press Reset. Slide you keyboard then press R and SPACE). This official ROM from Dopod is very important which need to be flashed before you flash your custom ROM.
Then the last step is get your custom ROM loaded. Download custom ROM from this forum (Recommended from TAI_sw or JoshKoss).
Then simply follow the steps in Dopod 838 Stripped ROM Flashing.
(Then copy RUU_signed.nbh from Custom ROM to your MicroSD and rename it to hermimg.nbh. Put your device into booloader and start flashing like how you flash you radio rom. After it done, give your device a Hard-Reset (Hold Left + Right softkey and press Reset. Slide you keyboard then press R and SPACE).)
Yes. I have grammar mistakes. Sorry!
That's your ROM and don't expect every ROM is stable. You will see some bugs in Custom ROM. Post your bugs at their own thread.
Anything just PM me.
Thanks
-Ziv-
zivkong said:
*Newbie* Custom ROM Flashing Guide
Just follow the steps start from 1. Don't skip step unless it is an optional step.
PC Requirement: Windows XP, ActiveSync [Don't try to flash with Vista if you are new], 7zip Installed (Google it)
Connect your device to your computer and make sure the ActiveSync icon appeared on your phone before proceeding. 50% or above bettery is a must. Your phone won't charge when flashing.
1. HardSPL (A Big Big Must)
I asume you are using the original ROM from manufacture as HardSPL won't work with custom ROM.
Download HardSPL V7 from here. Unzip the whole things. Execute the "RUUWrapper" thing and select "Force Using SSPL". Check all the boxes in all the steps and continue with updates. Look at your phone and press "Yes" to everything that prompted. Then your phone will restart in Tri-Color mode [a.k.a bootloader] and start flashing HardSPL.
In this case if any errors appear on your computer screen before the update progress start, soft reset your phone, let it boot into Windows and start RUUWrapper again.
If error appear during flashing progress, then you might in deep hell. Try not to worry. Manually put your device into bootloader (Hold On/Off Btn + Left OK Btn, then push the soft-reset btn). Then start the RUUWrapper again.
End of the step you should see 'HardSPL 2.10Olipro' in bootloader mode.
2. Radio Flashing *Optional*
You can choose not to flash your Radio Stack if you satisfy with the existing. Additional, Radio Stack flashing is the main cause of device bricking (the death of your device)
Choose and download your Radio ROM here. Do some research about the Radio ROM that fits you and your country. Recommended the latest 1.56.70.11. Unpack everything and you will see something similar to HardSPL (RUUWrapper). Don't run RUUWrapper this time.
Let's do the safe way. Format your MicroSD card into FAT32 (Kill yourself if you don't know). Then copy the RUU_signed.nbh into your MicroSD. Then rename RUU_signed.nbh to hermimg.nbh. Put your MicroSD into you phone.
Manually put your phone into bootloader mode. Then a different screen with grey background should appear shortly. Press On/Off btn to start flashing. After the process done (it will tell you when it is done, don't try to judge yourself if you feels that 50% is done), soft-reset your phone.
During flashing, put your phone aside and enjoy your coffee. Don't touch it before it ends as this is dangerous. Don't ever fail radio flashing. Careful, careful and careful.
End of this step, you should see R 1.56.70.11 during Windows Boot.
3. Custom ROM Flashing
First, download Dopod 838 Stripped ROM. Then unpack it. Delete your previous hermimg.nbh in MicroSD which you use to flash Radio Stack. Then copy RUU_signed.nbh from Dopod 838 Stripped ROM to your MicroSD and rename it to hermimg.nbh. Put your device into booloader and start flashing like how you flash you radio rom. After it done, give your device a Hard-Reset (Hold Left + Right softkey and press Reset. Slide you keyboard then press R and SPACE). This official ROM from Dopod is very important which need to be flashed before you flash your custom ROM.
Then the last step is get your custom ROM loaded. Download custom ROM from this forum (Recommended from TAI_sw or JoshKoss).
Then simply follow the steps in Dopod 838 Stripped ROM Flashing.
(Then copy RUU_signed.nbh from Custom ROM to your MicroSD and rename it to hermimg.nbh. Put your device into booloader and start flashing like how you flash you radio rom. After it done, give your device a Hard-Reset (Hold Left + Right softkey and press Reset. Slide you keyboard then press R and SPACE).)
Yes. I have grammar mistakes. Sorry!
That's your ROM and don't expect every ROM is stable. You will see some bugs in Custom ROM. Post your bugs at their own thread.
Anything just PM me.
Thanks
-Ziv-
Click to expand...
Click to collapse
Hi Ziv
I have flashed over twenty or more cooked ROM, and they are successfully done through Active Sync. As you see in my signature, My IPL is 1.04 and my SPL is 2.10 Olipro.
I have also followed Ultramag and KK suggestion to format the SDCard using PC. And still stuck in bootloader (3 colors) and one more: it states 'Serial' in the bottom color (white).
I also bought the new 1GB SDCard, but the problem persit.
So, is there any other suggestion to try?
StefanHou said:
Hi Ziv
I have flashed over twenty or more cooked ROM, and they are successfully done through Active Sync. As you see in my signature, My IPL is 1.04 and my SPL is 2.10 Olipro.
I have also followed Ultramag and KK suggestion to format the SDCard using PC. And still stuck in bootloader (3 colors) and one more: it states 'Serial' in the bottom color (white).
I also bought the new 1GB SDCard, but the problem persit.
So, is there any other suggestion to try?
Click to expand...
Click to collapse
Ultramag, KK13, Boog & Zocster
Have tested using SD Converter and formatted it with PC, still no use. In the boot loader screen, I stucked with 'Serial' in the white bar. Is this meaning something to you? Any other work around?
Man, I don't have a clue. The only issue I ever encountered was thinking my card was formatted fat32 when it wasn't.
I think this is now beyond me.
StefanHou said:
Ultramag, KK13, Boog & Zocster
Have tested using SD Converter and formatted it with PC, still no use. In the boot loader screen, I stucked with 'Serial' in the white bar. Is this meaning something to you? Any other work around?
Click to expand...
Click to collapse
Well now .. you've got me too. I have only had "serial" showing in the boot loader once and it was because I had the wrong sd card in with no HERMIMG file. Once I put the right one in with the file and reset the device it was ok. All I would suggest is to do a Hard reset and follow all the steps again one by one, triple checking everything. Maybe write everything you do down and post it back here.
Also check your spelling of hermimg.nbh as a simple error will screw up everything...
Also put sd card in then reset to bootloader, hold in all the buttons - ok, power and reset with stylus, until the bootloader comes up.
Cheers...
KK13 said:
Well now .. you've got me too. I have only had "serial" showing in the boot loader once and it was because I had the wrong sd card in with no HERMIMG file. Once I put the right one in with the file and reset the device it was ok. All I would suggest is to do a Hard reset and follow all the steps again one by one, triple checking everything. Maybe write everything you do down and post it back here.
Click to expand...
Click to collapse
KK13, Boog and Ultramag
OK this is what I did last night:
1. Flashing to the shipped AT&T Stripped ROM
2. Having it reflashed with the HardSPL V7 (to ensure the file is non corrupted, I re-downloaded it from some links in some thread and check the file size, they are all the same )
3. Reformating my SD Card with PC for FAT32;
4. Copy the nbh file and rename it with HERMIMG.nbh (recheck three times and I think I get it right. btw, is there any different to write it in capital? );
5. Press OK and Power, then stick the reset button.
6. Go to the boot loader (with 'Serial' on ht white screen)
Hello everyone. I haven't flashed Android to NAND yet but I'd like to try it.
I am sure this question has been asked before but I did try the search and I couldn't find it. Sorry if this has already been asked.
So, for the Kaiser, if I flash Android to NAND (ie: Polymod's most recent) how do you flash back to Windows Mobile?
I'm concerned because USB does not connect properly when Android is running with HaRET ("unrecognized USB device" using XP SP3 couldn't make heads or tails of the drivers in the SDK but then I didn't try installing the whole environment)
So I guess my question is -- even with the device unrecognized, can you still flash it back? If so, how? Is it really simple and easy?
Please let me know and point me in the right direction! Thanks!
aikeru said:
Hello everyone. I haven't flashed Android to NAND yet but I'd like to try it.
I am sure this question has been asked before but I did try the search and I couldn't find it. Sorry if this has already been asked.
So, for the Kaiser, if I flash Android to NAND (ie: Polymod's most recent) how do you flash back to Windows Mobile?
I'm concerned because USB does not connect properly when Android is running with HaRET ("unrecognized USB device" using XP SP3 couldn't make heads or tails of the drivers in the SDK but then I didn't try installing the whole environment)
So I guess my question is -- even with the device unrecognized, can you still flash it back? If so, how? Is it really simple and easy?
Please let me know and point me in the right direction! Thanks!
Click to expand...
Click to collapse
I beleive you can always follow the process here.
Your boot loader should not change when flashing so not being able to use the USB while in Android is not going to prevent your returning back to a stock ROM. I have not tested this but I'm pretty sure that you can always get back to your boot loader screen and re-flash from that point. Can someone confirm that this is the appropriate solution?
deekjx said:
I beleive you can always follow the process here.
Your boot loader should not change when flashing so not being able to use the USB while in Android is not going to prevent your returning back to a stock ROM. I have not tested this but I'm pretty sure that you can always get back to your boot loader screen and re-flash from that point. Can someone confirm that this is the appropriate solution?
Click to expand...
Click to collapse
Did anyone try this solution?
Since the bootloader is still there all you do if not able to flash via async when in android is flash via bootloader
Moved to general as not ROM Dev.
Thanks for the information, guys!! I will have to try it out over this weekend and see how it goes...
I can confirm that flashing via bootloader works fine, also flashing from SD works as well, in fact I keep a 128MB sd with a WM kaisimg.nbh on it handy just in case I need to flash a good WM rom for some reason.
Is there an Android OS with everything working on the Kaiser?
Dukenukemx said:
Is there an Android OS with everything working on the Kaiser?
Click to expand...
Click to collapse
You can see in different post of android rom what works and what doesn't works.
actually, Bluetooth and camera never works for in android 2.x build and some other apps doesn't works
I've been running Android for a few weeks now from this thread:
http://forum.xda-developers.com/showthread.php?t=614382
I've found everything to work with the exception of Bluetooth, video camera (normal camera works fine), and the barcode scanner. Also, my battery life is cut in half, but I have an extended life battery so I get a day or two out of it.
I prefer this method as you can just boot Android at will and can soft reset to go back to WinMo.
Just to let everyone know I did flash WM back just fine since I have HardSPL 3.56 and used the stylus to press the reset + camera button at the same time to get to the tri-color screen.
From there I flashed from USB without any problems.
Thanks again for all the help!
I am having problems reverting back to WM after attempting to install android to NAND. Something happened where the only way I was able to get to the android installer would be if I had the KAISDIAG.nbh file on the SD card so it would get past the tri color hard spl screen . Well as a result, I can't get into boot loader. It shows that screen for a split second, then if I do camera + power and then reset. Then I have to pull the battery. Can someone help me? It seems like it will only go into the Android bootloader, which obviously won't allow it to install a WM rom. SD flashes are my only choice because the usb port is pretty messed up. Any help would be greatly appreciated. Thanks.
The procedure for flashing WM back using SD card is much the same as flashing the Nand bootloader for Android.
First get a WM rom, copy the RUU_Signed.nbh to SD card, rename it to KAISimg.nbh, pull the battery, replace, press power and hold camera button, this should start the flash process.
Note that the SD card must be formatted FAT32, or it will not find the KAISimg.nbh.
If you prefer to flash a stock rom you will usually have to extract the RUU_Signed.nbh from the installer, just open it in winrar.
the reset in android is not working correctly. The correct way to get into bootloader is to pull the battery, wait a few minutes, rpelace the battery, press power and then press and hold camera button, do not use reset.
zenity said:
The procedure for flashing WM back using SD card is much the same as flashing the Nand bootloader for Android.
First get a WM rom, copy the RUU_Signed.nbh to SD card, rename it to KAISimg.nbh, pull the battery, replace, press power and hold camera button, this should start the flash process.
Note that the SD card must be formatted FAT32, or it will not find the KAISimg.nbh.
If you prefer to flash a stock rom you will usually have to extract the RUU_Signed.nbh from the installer, just open it in winrar.
the reset in android is not working correctly. The correct way to get into bootloader is to pull the battery, wait a few minutes, rpelace the battery, press power and then press and hold camera button, do not use reset.
Click to expand...
Click to collapse
Thanks, but unfortunately this still did not work. Have any other suggestions? I think the only way will it even do anything is if I have the KAISDIAG.nbh file on the card. It recognizes that, but then goes straight to linux. IDK what else to do. Could you be a little more clear on the procedure for getting into the bootloader? Thanks.
Ok please follow these steps carefully.
1. Format the SD card, make sure you are formatting it as FAT32, not FAT.
2. Download a Winmo Rom from somewhere handy.
3. Extract the Rom to a handy folder, find the RUU_Signed.nbh file, rename that to KAISimg.nbh
4. Copy the KAISimg.nbh file to the SD card. You should only have one file on the SD card, no folders just the NBH file.
5. pull the battery from the phone, wait at least 5 minutes.
6. Replace the battery. Press Power button, and hold down camera button, until the tri color screen appears.
7. The screen should now change to a white one, and when it's checked the nbh it will ask you to press power key again. do that.
8. Now it should flash the rom, this should take a while, 5-10 minutes, once it's finished you should get a message of success.
9. Now pull the battery again, wait 5 minutes, replace the battery, and power on, you should now boot into Winmo.
Hopefully this should solve your problems, if not then let me know which setp failed and we can work on that stage.
Finally, don't panic, take it slow, it'll all work out
Thanks, but the problem starts at number 6. I am supposed to press the power button, release it, and hold the camera button till it gets to the white screen, right? It's still stuck at the splash screen. I tried holding both and that didn't work either. Anything else I can try? I hope i'm not screwed?
If I put the battery in, boot it up, then push the camera and insert the stylus into the reset hole, it gets to the tricolor screen, then for about 0.5sec it flashes the white screen with a message saying "No image File." I know for sure the .nbh file is there.
I have experienced this before, when I tried to use an SD card that was formatted FAT, when formatting you must make sure it is formatted FAT32, the bootloader cannot read FAT formatted SD cards, even if Winmo and Android can.
I format using a card reader, and in windows it is sometimes easy to overlook the file system type, most SD cards are usually formatted FAT when they are new, and you must change the formatting, or it will just format FAT again.
zenity said:
I have experienced this before, when I tried to use an SD card that was formatted FAT, when formatting you must make sure it is formatted FAT32, the bootloader cannot read FAT formatted SD cards, even if Winmo and Android can.
I format using a card reader, and in windows it is sometimes easy to overlook the file system type, most SD cards are usually formatted FAT when they are new, and you must change the formatting, or it will just format FAT again.
Click to expand...
Click to collapse
Unfortunately, as much as I wish it was, it is not the problem. I'm on a Mac, but booted windows 7 to be make sure it was formatted to FAT 32, which it was. Is there some way I can fix permissions? Every time it runs, I keep getting the error saying that it is in read only mode. I obviously need to get it into writing mode. I don't think the fix permissions option on the installer did anything either.
The eclair build still will not install on my phone. I changed to an earlier .nbh file and now don't need the KAISDIAG.nbh file to get out of the splash screen and into the installer. When I run the install command for NAND, it says it can't mount, "no such file exists", "failed to extract." Keep in mind I haven't even gotten Android installed to NAND, just the installer itself. I can't even go back to WinMo either. It also seems like a permissions error since I believe it said the SD card is read only, but when plugged into my computer I fixed that and now it is read-write, but not on the phone. Please help because I really want to either get this working, or get back to WinMo instead of have this useless phone I currently have. Thanks.
Is there a way to enter the command line from the installer screen?
Tilt Fanatic said:
The eclair build still will not install on my phone. I changed to an earlier .nbh file and now don't need the KAISDIAG.nbh file to get out of the splash screen and into the installer. When I run the install command for NAND, it says it can't mount, "no such file exists", "failed to extract." Keep in mind I haven't even gotten Android installed to NAND, just the installer itself. I can't even go back to WinMo either. It also seems like a permissions error since I believe it said the SD card is read only, but when plugged into my computer I fixed that and now it is read-write, but not on the phone. Please help because I really want to either get this working, or get back to WinMo instead of have this useless phone I currently have. Thanks.
Is there a way to enter the command line from the installer screen?
Click to expand...
Click to collapse
Alright, I'll try and sum up your experiences. Tell us if we're missing anything;
You have the following symptoms
Linux Android-installer works
Tri-color bootloader semi-works
You cannot use the USB
You cannot install polymod's Eclair build
Now, you have mentioned a couple of things you have tried, such as
Replacing the Linux NBH with another version
Fixing permissions on the SD-card
Fixing permissions through the Android-installer
Flashing a WinMO ROM through SD card
You did mention getting other behaviours when you switched to another NBH, such as "KAISDIAG.nbh" not being required.
Now, this is a long shot coming from me, as I have had no troubles with flashing, and the fact that I can use my USB, but since your phone is pretty messed up I guess it can't hurt as a suggestion;
You can flash to other NBH's I take it, as you mentioned you did a downgrade. What I'm a bit curious about is whether you did try to flash to a WinMO rom when you had downgraded to your current NBH.
Also, you said the previous NBH required you to have "KAISDIAG.nbh" on the card to even get working. Did you try and rename a WinMO-ROM's NBH to "KAISDIAG.nbh" and flash that? Might be that the flasher is really constrictive with the file names.
EDIT: Oh, and what about trying to run other Eclair builds? Just to see if you can nail it down to this being a problem of the builds or something more bound to the actual hardware/SPL/NBH's.
Just thought this might be useful to some of the newer users, a list of what I see as the most commonly asked questions, and some misunderstood terms.
What is the difference between Nand, Haret and SD:
Nand; refers to the devices internal memory, which is NAND Flash memory, and is used to hold what is commonly called 'a ROM'. It is this memory which holds the Operating System, and can be 'Flashed' to change the data on it, once flashed it is persistent in memory, meaning that if you remove all power sources it will not lose this data, this is also known as 'Non-volatile Memory'. Nand Flash refers to a specific type of Flash memory, and gets it's name from the way the memory cells are constructed.
SD; Refers to the MicroSD cards we use in our devices, these are also Nand Flash but typically have slower transfer rates than the Nand Flash we have inside the device. typically used to store data, they can also be used to store the Android OS when used with Haret installs.
Haret; often confused with SD. It actually refers to Haret.exe, which is a program used to launch Linux systems from within another OS, such as Windows Mobile, think of it as a Virtual machine system, which allows users to run another OS. In our case, Haret refers to running Android within WM, it does not replace WM in Nand ROM, it does replace it in RAM however, but only until powered down, after that WM will boot from Nand next time the device is powered on.
What is my Panel Type?:
Panel; This refers to the actual LCD panel hardware, there are 3 types in use on Kaiser, and although Type2 seems most common, there are also Types 1 and 3. When running WM the panel type is autodetected and the correct settings are used for the display, however Android has no autodetect, so we must tell the OS which type we are using at boot, in Haret installs this is done with a line in Default.txt, in Nand it is set in the NBH we use to flash the kernel and other boot files needed to run Android. Display issues such as odd pixel colouration, streaks or lines on the display, white screen when exiting sleep, and other noticeable display issues can usually be cured by changing the panel type.
Other useful terms:
NBH; This is the file extension of a file intended for flashing to Nand, most commonly used to flash WM or Android, it can also be used to flash radio or splash screen.
Bootloader/tricolour screen; Both are the same, it refers to the screen display you get if you hold the camera button, and press power, on this screen are a few useful pieces of information, device type, (e.g KAIS130), SPL version, (e.g SPL-3.29.Hard), in the bottom white area it will say 'serial' or if connected to a PC, 'usb'. Remember to remove the SD card before entering Bootloader mode, as the bootloader also scans the SD for a file called KASIimg.nbh, and will run the updater utility if one is found.
HardSPL; This is a specially designed SPL that allows us to flash the Nand with an NBH file that was not signed by HTC, it also prevents itself from being overwritten, so that it is usually possible to reflash as long as we can get into Bootloader mode, this means we can, ( usually ), recover from a bad/corrupt flash.
Build and ROM; In WM terms, a ROM usually refers to a complete, ready to install, single file NBH, custom version of WM. However with Android we do not use the single file approach, and therefore we do not usually use the term ROM. Build is what we usually call a custom Android install. This is roughly equivalent to the WM 'cooked ROM', since each build is designed and built in a particular way, and may be any of the different android 'flavours'.
Flavours; Mostly used to describe the versions of android, these are, in historical order
1.1 - un-named, released feb 2009
1.5 - Cupcake, released april 2009
1.6 - Donut, released sept 2009
2.0/2.1 - Eclair, released as 2.0, oct 2009, and as 2.1, Jan 2010
2.2 - Froyo, released may 2010
3.0 - Gingerbread, scheduled release date, sep-dec 2010.
Odex'ed: As stock, android builds are odex'ed. Odexing involves generating an odex file for each app, which slightly lowers the memory used by the system, and may also speed up execution of apps, the downside is that it is difficult to modify odexed builds in order to tweak or theme them.
DeOdex'ed: a deodexed build is one in which the odex files are moved into the apk's, which slightly increases the memory used by /system, but allows modifications and tweaks to be used.
Deodex Vs Odex: Odex uses less space in /system, boots quicker, especially the initial boot after installation, however themeing is impossible, and various tweaks and modifications probably won't work. Deodexed uses more space in /system, has a slower initial boot, subsequent boots are much quicker, but may be a little slower than odexed, theming is a lot easier, as are modifications and tweaking of the build. ( most custom builds are deodexed due to the ease of theming and modifying ).
Bootsplash/Bootanimation:
The bootsplash is the static picture that appears as soon as you boot the device, usually is stays for 20 seconds or so before being replaced by the scrolling text showing Linux is booting.
The Bootanimation is the animated screen you see after Linux has booted, and usually loops until Android is loaded.
Sim Pin/SIM lock:
SIM Pin is often confused with the SIM lock, the SIM pin is the code you have to enter before using the phone when you start it up, this code is stored on the SIM card itself, and until recently caused a lot of problems, since Android could not decode it properly, this has been fixed in some flavours, Eclair and Froyo, but is still an issue in older flavours, such as Donut.
Sim lock also known as provider lock is a method used my phone service providers to ensure that you only use their service by locking the phone so that it only accepts that providers SIM cards, this lock code is stored on the phone, and may be unlocked by entering a code, or by bypassing it using unlocking software, once unlocked the phone will accept any other providers SIM card.
PUK the PUK is the Personal Unlock Code, and is a code that unblocks a SIM that has been blocked by too many unsuccessful attempts to enter the Sim Pin code, ( usually 3 attempts), this code must be entered to unblock the SIM card, usually the PUK is provided with the SIM Card, however if it is lost then some providers may give you the code, if the SIM has been registered by you.
Please feel free to add to this
Back to Windows Mobile:
If you need to reflash Windows Mobile, for whatever reason, these are my preferred methods:
I recommend using a Card Reader and MicroSD adaptor for working with SD cards, it makes life so much easier than relying on the kaiser to transfer and rename files, since most of us are used to handling files in Windows.
Method 1
1. Download a Stock shipped ROM, do not go crazy getting the latest custom 6.5 ROM, in my experience these often cause problems, if you want to go to Custom ROM's then flash stock first.
2. Extract the RUU_Signed.NBH file from the .exe, ( I use 7zip for this, but other archive utilities my work, winzip, winrar etc), rename the file to KAISimg.nbh and copy to the root of a freshly formatted SD card.
3. Insert the SD card in your Kaiser, pres and hold camera button while pressing power, ( you only need to press power briefly, but keep the camera button pressed until you see the tricoloured screen).
4. Once you get the tricolour screen, ( bootloader ), it should change to a grey screen with blue instructions, basically, press the power button and let it flash.
5. Once flashed, simply pull the battery/press reset and let it go through the first boot process.
Troubleshooting
Common problems with this method are that it will just not recognise the flash file, leaving you at the bootloader screen, this is usually caused by wrongly formatted sd cards, the card must be formatted FAT32. Other reasons are file name issues, make sure you have not accidentally mistyped the filename, or renamed it as kaisimg.nbh.nbh.
Method 2:
If Method 1 fails then the alternative method is USB flashing:
1. Disable Activesync, by unchecking the 'USB' option in Connection settings.
2. Remove the SD and SIM cards from the Kaiser.
3. Press Camera+Power to enter Bootloader.
4 Connect the usb cable, ensure that is says 'USB' at the bottom of the screen.
5. Flash the Stock ROM, usually by double clicking the downloaded stock ROM exe file, allow it to flash, and wait until it is finished before removing the USB Cable.
Troubleshooting
There are a few potential issues with this method also, if this method fails try another stock rom, the last shipped ROM from HTC was Kaiser_HTC_ASIA_HK_WWE_3.34.721.2, this is a generic stock 6.1 rom and should be compatible with most if not all kaiser variants.
Useful Links:
ThoughtlessKyle's Why my Wifi doesn't Work Invaluable Information on recent WiFi Issues, A 'Must Read'......
LCD Panel Information
Tinboot thread ( the thread that launched Nand flashing on kaiser ).
SuperJMN's Android Issues roundup thread ( common problems, as yet unsolved )
Adding language support
Miscellaneous Notes.
Radio Version
Just as in Windows Mobile, Radio Version seems to play as vital a role on Android.
There are a number of problems that may be related to radio version, and just as in WM, the effects are sometimes surprising.
Audio: yes, just like WM the wrong radio version can cause audio issues, ranging from no audio, to more subtle issues such as call audio not working, even though all other audio events work fine.
Wifi: no surprise really, the radio stack controls wifi as well as the more common phone/network activities.
Data/Network: Obvious one, but there are a number of complicating factors here too, geographical location seems to affect radio version, for instance, in the USA, 1.71 radios may offer the best signal, and data rates, while in Europe, using 1.71 may cause a lot of 'No Signal' issues, where the phone seems to drop off the network, the solution is usually an older radio version, in the UK 1.65 seems the best choice for most users, I have also had reports of 1.65 being the best for South Africa, Asis, while Australia seems to do better on 1.70 or 1.71. This may be due to the technology in use in those countries.
GPS Maybe, not sure about this one, had at least one report that a radio downgrade from 1.71 to 1.65 seemed to help with GPS, as far as I am aware the GPS and the Radio stack are not related, but who knows for sure?
Great guide! I was thinking about making similar one myself, but couldn't find free time
I'll maybe try to add something this weekend
hello maybe a stupid question
what is the differents between odex and unodex
sorry for my bad english
kisses
Rose
Not sure if this is a general dumb newbie question but I'm having it across different Android builds. Occasionally I have to reset the phone without shutting Android down. When I restart, any apps that were running at the time have to be uninstalled and re-installed because they now crash on startup (with a "program has stopped working" error.) Is there anything I can do about this?
CassandraN said:
Not sure if this is a general dumb newbie question but I'm having it across different Android builds. Occasionally I have to reset the phone without shutting Android down. When I restart, any apps that were running at the time have to be uninstalled and re-installed because they now crash on startup (with a "program has stopped working" error.) Is there anything I can do about this?
Click to expand...
Click to collapse
Not really a dumb question, however it depends how you are resetting, the reset button is a bad idea, Battery Pull is the preferred method, ( say it with me class, 'Battery Pull Good, Reset Button Bad' ).
However, why do you have to reset without shutdown? This often leads to data corruption, since the OS does not get a chance to synchronise properly before it closes, ( not that a battery pull should be any better, but for some reason it seems to cause fewer problems than resets).
Thanks for the FAQ, it is extremely useful to noob or semi-noob like I am.
Thanks, that's why I decided to start it, and if one person finds it useful, it was worth it
say it with me class
Click to expand...
Click to collapse
This is just hilarious
BTW, I tried some of the reboot apps in the market, non of them seemed to work (on 2.1)
the original reboot menu that you get when you hold the power button did not work at all. it just hangs on the loading circle.
In Froyo however, things are a bit different. the reboot option shuts downs the device instead, I did not try any reboot app yet
Any ideas about this zenity?
zenity said:
Not really a dumb question, however it depends how you are resetting, the reset button is a bad idea, Battery Pull is the preferred method, ( say it with me class, 'Battery Pull Good, Reset Button Bad' ).
However, why do you have to reset without shutdown? This often leads to data corruption, since the OS does not get a chance to synchronise properly before it closes, ( not that a battery pull should be any better, but for some reason it seems to cause fewer problems than resets).
Click to expand...
Click to collapse
I usually battery pull (I lost my stylus and the cheap replacement won't fit in the reset hole ), but I still seem to have problems.
I think my problems are due to a rogue app eating all the CPU. My suspicions are Twitter or Swiftkey. The phone becomes so unresponsive that sometimes a hard reset is the only way to make it useable again. I'll try to avoid it in future if I possibly can.
Tried taskiller? Useful for watching your memory, and killing tasks if needed, osmonitor is also useful for, well monitoring the os
I have noticed that the system does get very unresponsive at times, and it usually means low memory, try an eclair build if you are using a CM6 based one, I usually get about 30+Mb free in normal conditions, and if things start to get too slow, well a tap on the taskiller widget sorts that out
@Duke911:
As far as I am aware there is no real reboot option, in any build, I think it's a kernel issue, or perhaps just not implemented correctly, the safest option is a power off, which performs a proper shutdown, I do know there have been a few issues with data corruption that may be associated with using reboot, or the reset button, since these may cause the system to shutdown to rapidly to sync any data that may be cached, it's similar to pulling an SD card out of the computer, there may be data left unwritten in cache, which is why there is a nice safe removal option
This is a cool wiki for Kaiser Android users! Thank you!
By OP request, I am making this thread a sticky and making some adjustments to the forum. Please PM me if you have any requests. Thanks.
Precious work, Zenity!!!
video call anyone?
Is there any chance of getting a build to support video calling?
Video calling will need working front camera driver at least, which is not supported yet, I do not know if anyone is actively working on this, however, at some time, someone will take up this challenge, just as they have with other things which did not work previously
Sent from my HTC Dream using Tapatalk
hello..
I just want to ask about polymod and cyanogenmod.
what is the function, are they different from eclair or froyo?
thanks ^^
CyanogenMod builds are all Modifications of base android releases, these are complete rebuilds of the system, and include many improvements over the original release.
Polymod is an Eclair Mod based on OpenEclair 1.3 and is modded in a different way to Cyanogen's methods and style.
Most Eclair and Froyo builds are ports and modifications of Cyanogen bases, ( in fact I don't think there are any Froyo builds that are not CM6 based).
For Donut things are different, most builds are modifications and ports of official releases, such as Myn's Warm Donut.
Hello,
I need some help. Install its Android OS, but after he reset my Kaiser again charged WinMo OS. My question is whether it is possible to choose which OS to load first or with any program or edit the file to indicate to launch the first Android.
Sorry for my bad english :S Use Google translator
If you have installed Android to SD card and use Haret.exe then it will always reboot to WM.
You must install to nand if you wish to boot to Android only, which will wipe WM totally and replace it with Android.
The guide stickied at the top of the forum is a good tutorial in doing this
That does bring a good point to my mind though, we could create an exe that loads at startup of wm to auto load haret and startup if the user doesn't cancel in so many seconds (like grub). I keep WM on my phone so I can easily change my droid version and also I know everything works including opening office files (actually that's the biggest sticking point for me keeping it).
Thanks for support. Today I try to flash via NAND method.
Kind Regards
Lybomir
I flash my Kaiser with latest zImage-2.6.32-froyo-09-09-10_21 from here http://it029000.massey.ac.nz/vogue/files/?C=M;O=D and my device loading Android OS very slow, and big problem is : Phone go in screensaver and I try to unlock and screeen stay only in white light, no picture, no widgets... total block. Only solution is it a use Soft reset button or remove batery
Maybe you choose the wrong panel type?
I can read in your signature Duo Boot so I guess you installed onto the SD and use Haret to run Android.
If so, you have to edit the default.txt file locate in ANDBOOT folder and modify the value following htckaiser.panel_type.
You can specify 1, 2 or 3 (most Kaisers use panel type 2)
Wrong panel type may lead to awake problems or wrong colors...
The excessive slowness may be due to a slow SD. Which class is it? Use at least class 4 SD.
---- EDIT -----
In case you already flashed to NAND, to change the panel type you have to choose the right kernel (the kaisimg file) or you can edit the one you flashed following instructions and links you can find in #4 at http://forum.xda-developers.com/showthread.php?t=680518
obviously you have to reflash the kaisimg.nbh but you don't need to flash Android again
I try with 1,2 and 3 but every time show me a this problem, and now i run HaRET and in 2 from 3 times phone block and not response only Soft reset work, and if case phone load complete Android and again in screen seaver system not respond... ;(
I flash my phone with ext2 partition on my sd card/ class 4 8 GB SDHC/ and try with system and data on sdcard an again freez white screen/
Sorry for my bad english
dlink.bg said:
I try with 1,2 and 3 but every time show me a this problem, and now i run HaRET and in 2 from 3 times phone block and not response only Soft reset work, and if case phone load complete Android and again in screen seaver system not respond... ;(
I flash my phone with ext2 partition on my sd card/ class 4 8 GB SDHC/ and try with system and data on sdcard an again freez white screen/
Sorry for my bad english
Click to expand...
Click to collapse
May you try to install a different build and see if you fall into the same problem?
BTW, just after installing, don't start playing soon with the device: initially skip all settings (touch the android, don't set google account and so on) and leave the phone quiet for at least 10-15 minutes: some builds need to copy file to the cache and playing with the device may interfere with this operation leading to unpredictable effects...
Let we know...
It is slow because you installed it on sdcard.. both partition.. if you are on nand. Try install both partition on nand partition.. and try hawks soad rls 3 as me.. its fastest build for kaiser.. and I haven't ever problem with white screen ata awake.. try it in that haws soad ion build.. you can finf it in that forun.. just find it
Sent from my HTC Kaiser Ion using XDA App
I find a solution! Later I post how find solution
Thanks on every in this thread to help me!
dlink.bg said:
I find a solution! Later I post how find solution
Thanks on every in this thread to help me!
Click to expand...
Click to collapse
You're welcome
And I'm waiting to know
Don't suppose any of you have actually seen this thread?
Gen.Y DualBOOT v1.0.6.0
Should work fine on Kaiser, certainly works fine on other devices, such as Diamond, Blackstone etc
zenity said:
Don't suppose any of you have actually seen this thread?
Gen.Y DualBOOT v1.0.6.0
Should work fine on Kaiser, certainly works fine on other devices, such as Diamond, Blackstone etc
Click to expand...
Click to collapse
Hi Zenity... Yes, know that piece of software.
But as You have to boot WinMo (Yes, I Know, not all the services need to be running but system must be loaded and started, GUI must be running and so on) in order to DualBOOT can start, I can guess it's only a partial time-save... isn't it? Did You tried it?
Have not tried it on my Kaiser, since it is Nand flashed, but I think it is what was being asked for really, a way to boot either WM, or straight into Android on SD.
I don't think it will ever be possible for both WM and Android to co-exist on nand, since there simply is not enough room on the internal memory for both.
It is a time saver on other devices I have tried it on, Diamond, Blackstone, however since neither of these devices is nand-flashable this is more what Gen-Y's dual boot was intended for.
If it was possible to run WM from SD then we might be able to truly Dual Boot, in a similar fashion to Windows/Linux on PC, but as far as I know this is not possible either.
zenity said:
Have not tried it on my Kaiser, since it is Nand flashed, but I think it is what was being asked for really, a way to boot either WM, or straight into Android on SD.
I don't think it will ever be possible for both WM and Android to co-exist on nand, since there simply is not enough room on the internal memory for both.
It is a time saver on other devices I have tried it on, Diamond, Blackstone, however since neither of these devices is nand-flashable this is more what Gen-Y's dual boot was intended for.
If it was possible to run WM from SD then we might be able to truly Dual Boot, in a similar fashion to Windows/Linux on PC, but as far as I know this is not possible either.
Click to expand...
Click to collapse
Yes, of course we haven't enough NAND to have both OSes!!!
What I was thinking to (but I'm a lot far to inspect WinMo booting sequence...) is if may be possible to wedge a sort of bootloader running BEFORE the OS loads or in the early booting process and letting we choose to boot WinMo (in NAND) of Android (on SD).
At present moment I've Android running from SD but kernel NANDed (I've got problems running out of NAND and no time to solve them so I'm using the solid build previously installed on SD) so Kaiser boots quickly... and this confirms it's possible boot SD Android without having to load WinMo or Haret. The more relevant matter I can see is that we have to find a way to wedge the bootloader without have to manual modify the WinMo ROM (virtualization is far from be considered on such devices...)
I suppose this is just a "mind exercise" (Sorry, I don't know how to correctly translate an Italian common saying...
Mind exercise describes it perfectly
Not sure why you would run out of space on nand, unless you are loading a lot of apps, and there are ways to run android that may help with that, such as apps2sd, or data on SD partition.
If you must have WM then your only choice would be using Haret.exe, and the most efficient way to dual boot we have at the moment is the Gen-Y solution, which is not ideal, but does offer at least part of what you seek.
The Android bootloader we use (tinboot.s) is not flexible enough to allow dual booting, but may have some information that may be of some use in this
tinboot thread
See what you think anyway
Sorry, I was not able to be clear... I apologize for my English...
When I said "I've got problems running out of NAND" I intended to say "I've got problems - very bad performances - when Android was running from NAND"!!!
Maybe we are a bit OT...
BTW, I was far from software developing for a long while and never developed low level software for Linux/Unix... but in the past I messed up with Z80, 65xx, 68K and x86 platforms's assembly
Recently I need to approach software developing again (but at a really different level...)
I'd like to have spare time to start again, as this world attracts me more. Maybe I'll give it a chance...
Let me understand... tinboot is actually used bootloader?
BTW, just to be clear... I don't need WinMo and I'm giving Android a chance to revive my Kaiser. I'm looking for a fast and stable build and actually I'm running VaniljEclair RLS11 (Yes, I know, I'd try your Polymod 2.1D build... )
Tinboot is the bootloader we use to get android in nand, not being a coder my understanding in limited, however I did think that thread may have useful information for anyone interested in the low level workings of out devices.
I assumed you meant running out of space on nand, lol, i see now what you mean, no need to apologise for you english, it's fine
zenity said:
--- CUT ----
however I did think that thread may have useful information for anyone interested in the low level workings of out devices.
Click to expand...
Click to collapse
And you're right... it's a useful starting point and I'll read it accurately...
Unluckly, I need a lot of spare time (and I don't, at present) to build a solid knowledge base and to start developing for Android.
yes there should be plenty of room for both oses on Nand, I still have over 90 mb on my wm6.5 nand install with come extra apps in there. So if you stripped down both oses you could easily fit them both on nand and still some space left. But then you need to have a boot loader that will be able to load both oses. I think I heard someone say somewhere they are using grub to boot android from nand, that can boot windows also with the right configuration, that would be where to start.
So I have a broken sd card port, which does not read my sd cards anymore. And I was already on scoot's latest android build, but what do you do when something is broken? Well, you go back to factory settings and for our blessed HTC Kaiser or in my case MDA Vario III, this means going back to the abomination called WM (and to make matters even worse it is tmobile themed). But it seems that this also doesn't fix the problem and the sd card is still not read. It does say it needs to format the sd card for it to work, which I then give the permission to do, but it is never able to finish the format.
So my question is fairly simple: how to flash android on your WM device with usb?
thanks in advance!
( I am really stupid, going back to WM )
**I have looked for other guides, but they all assume you to already have android installed on your phone**
It sounds like the ribbon cable is broken for the SD card. The only fix is to replace it, unless there is some other problem with the main board.
So how am I suppose to replace this "riboon cable" do I need to buy some extinct hardware specifically for the kaiser (which probably is impossible to get?) or can I do it some other way. And is there really no way to flash Android on the kaiser via usb, since I think I can manage with only a couple of apps on the internal storage...
Also I have already tried to flash android on my htc kaiser:
- I dragged and dropped the KAISIMG.NBG over the installer of my original t-mobile rom, but somehow it just installs the original rom again and not the KAISIMG.NBG
AFAIK, the only 2 ways to flash anything to a Kaiser is through the SD card or USB port. Noone (to my knowledge) has ever created a RUU-flashable Android package for the Kaiser or any other device, which would be your only option.
Given the constraints on the RAM built into the Kaiser, you would have to build a pretty small package for the install, maybe 55-60MB, use Oli's NBH creator and (hopefully) build an installable package that can be sent via USB with an unsigned RUU updater.
If someone wants to take on the task of stripping an androidinstall package, extracting it and repacking it into a RUU installable NBH, feel free. I know it can be done with a kernel package, but that is only 3MB and goes to the first partition. All the other files would have to go to the correct partitions as well (/system, /data, /cache, etc.).
So how am I suppose to make an installable package? I have the file to get WM to Android, the kernel, and scoots android install package, which I have stripped down to 67 mb.
What should I do with these files? Do you have some kind of instructions?
You would have to figure out how to not only partition the NAND, but direct the kernel and all files to their appropriate partitions.
Someone must have some info on how to do this...
Sent from this addictive thumb magnet...