Help..cant get anything to flash - Tilt, TyTN II, MDA Vario III Android Development

Hi I am using hardspl 3.34
I decided to put android on my kaiser as I love it on my desire..
I flashed the latest android kernel from kallt_kaffe, when booted error messages came up about not being able to mount various locations..and a final one "unable to open persistent property directory"
I tried pressing the D pad to load an Android nbh from and boot and nothing.
I have since tried to reflash both winmo and android kernel images from the sd card and through USB but nothing flashes.
If I try with the sd card, naming the image KAISimg.nbh all I get is a white screen with loading on it..nothing more.
when I try via usb it gets as far as trying to flash the rom, then comes up with a communication errror.
anyone any ideas what has happened and how to fix it.
Regards
Robbie

You've downloaded and flashed the kernel (which allows you to run Android), but have you downloaded an Android build yet?
It sounds like you're missing the androidinstall.tar file in the andboot folder of your SD card.
Find a build in this forum, download the build (should be about 80/90mb or so when zipped) and then place the file in /andboot/
If you've already done this, apologies if that was patronising in any way!
The Kaiser is somewhat picky when it comes to SD cards, it may not read KAISIMG.nbh even if everything is fine. My 1GB Kingston card, for example, is useless when it comes to flashing this way, I had to buy a new 4GB card so I could sort out a rather useless Android build.

Thanks NatAvery
I have the andboot folder with the tar file in, but as I get errors from the android kernel i think that is why it doesn't read it.
My main concern is my inability to flash anything..I have tried a different sd card as you suggested and I still have the same problem, it comes up as loading the KAISimg.nbh but goes no further.
Robbie

Hi Vampires,
Did your issue resolve?.........since even i have a similar issue. I flashed HardSPL first & then flashed a rom from then whenever i switch on the phone it comes to this screen as if loading and is stuck with the error you mentioned ' unable to open persistent property directory'
And this happen to me just like it happen to me .......in the pursuit of having android on the phone.
I'm not able to flash any other rom's just stuck on this screen.

I have the same problem. I also use hardspl 3.34
I flashed the kernel installed the built, bu i didn´t pick the right display setting..
everytime I try to reflash it only says loading.. (left it for about 2 hours)
any ideas?

still looking for a solution, please anyone with usefull info help ..

i had similar problems before, my system is:
HTC tytn ii (kaiser 130)
Hard SPL 3.34, radio 1.70.19.09
DZO's kernel and froyo 15-07 (latest thas it), NAND flashed
4gb SD card
(109mb internal phone memory after 1st boot)
Haret Install (SD card, run side by side with WinMo)
- dload kallt_kaffe froyo, extract and put andboot in SD card, root, not subfolder
- rename default-kaiser.txt into default.txt
- edit default.txt change panel-type into 2 (panel 1 got some issue with res)
- run haret.exe
- don't press d-pad (center) just yet, wait until message 'press d-pad/volume to ..' then immediately press and hold d-pad until you're in install menu.
- select install, ok
- next, select fix permission (optional, but it fix some prob)
- select quit
- let it boot, no need to press d-pad anymore.
- you may get "unable to open persistent property directory", but no worries, restart phone, run haret again, if still the same, reinstall, sometimes twice install should fix it. (don't ask me why)
NAND flash
- dload DZO's kernel and OS build file.
- use Loser's NBH editor to change panel type to 2, and keyboard type. it will then save as KAISIMG.nbh
- put KAISIMG.nbh into SD card, root.
- make folder andboot inside SD card at root, and copy dzo's android build, rename it to androidinstall.tgz (tar/tgz)
- press and hold power btn + camera btn, reset with stylus
- press power again to flash kernel, then reset after complete
- now it will try to boot android, immediately press d-pad when you see 'press d-pad/volume..' and install (sys on NAND, data on NAND), next step same as haret above.
- you're now officially android.
note: additionally you can also try 'sys on NAND' + 'data on SD Card', --> use this EXT2 partitionto partition your sd card
side note:>
zImage = is the haret version of the KAISIMG.nbh file, it's the kernel.
androidinstall.tar/tgz = the android OS files
hope this helps.
Attn: if you're experiencing battery stucked at 15% or something, go into boot menu (d-pad), backup data, flash winmo rom, charge to 100%, then reflash+reinstall android, restore data. that should fix it.

Related

flashing from the sd card

heyy i really need you'e help, im trying to fet to the bootloader id the diamond but i always end's up in the rgb screen, so please tell me what to do...
From the wiki:
http://wiki.xda-developers.com/index.php?pagename=Diamond_FlashfIS
I have a similar problem. But mine is looking for movihand.mtg file then it goes to loading screen and it hangs. I wanted to flash the Deepshining 8 lite also.
I have a lot of files in my internal storage do i need to clear them and leave only the DIAMING.nbh thanks
i have spl 1.40 also thanks
Hope I can help!
Hey! First to 'avior.almo' You need to make sure you have flashed HardSPL to your device before trying to flash ANY ROM to your device (cooked, or custom, or otherwise!) If you are unsure of what I mean, or have any trouble, see sticky threads #2 and #4 of 'Diamond ROM development' http://forum.xda-developers.com/forumdisplay.php?f=430 (I use HardSPL Olinex 1.40)
Once you have this all in place, then flashing from the SD card is easy; you simply need to download the ROM you wish to flash, extract it (if it's downloaded as a .zip or .rar file) so you can find an '.nbh' file. The '.nbh' file is the ROM itself, and the file that you wish to flash. Once you have extracted the ROM you wish to flash (if you needed to extract at all. You may have downloaded the .nbh file as it is) then whatever the .nbh file name is, you need to rename the .nbh file to 'DIAMIMG.nbh' (without quotation marks).
Once you have done that, you need to copy it to your device's internal memory. To do this, connect your Diamond via USB, and when asked on your device screen, choose the 'Disk Drive' type of connection. Once complete, you can then navigate to the root of your (SD card) Internal Storage by accessing 'My Computer' through Windows explorer, Your device drive letter may be different depending on how many hard disks/CD drives you have in your system. (Mine is drive E Anyway, access your internal storage drive, whatever letter it may be on your system. It will appear under 'Drives with removable storage'. This is where you need to copy the 'DIAMIMG.nbh' file to. (To rdelsol: No, you don't need to clear your internal storage of any files or folders, as long as you have enough space in your internal storage to paste the ROM (.nbh file) that you wish to flash, in the root directory. E.g. 'E:' drive. It can be in there along with your 'program files' folder, or your 'my pictures' or 'my videos' folders. Flashing shouldn't delete any files or folders you have in your internal storage either. Even after flashing, 'DIAMIMG.nbh' should also still be there! (After flashing, you can delete that file)) And I noticed that in your post, you typed 'DIAMING.nbh' whether that was just a typo or not, I don't know, but it needs to be 'DIAMIMG.nbh', if so, that may be where you're going wrong.
So, now that we have the ROM image file in the root directory of your internal storage, you need to enter your device into bootloader mode, which is achieved by (while the device is on) holding down the 'VolDown' and 'back' (<-) buttons, while pressing the little red reset button (under the battery cover). Keep hold of the voldown and back buttons until your device displays the tri-colour screen. The instructions are then shown on-screen of what to do next (PROVIDING YOU HAVE HARDSPL INSTALLED, see beginning of post). Your device should detect the ROM image file (saved as DIAMIMG.nbh) and prompt you to press the power button to begin the flash. All going well, your device will display a progress bar, that when reaches 100% will say 'Update Success'
Now you need to press the red reset button again. After that, your device should begin setup of the new ROM as if it had just been bought. Alignment of screen, and maybe time and date setup, for example. Good luck with flashing and setup!
I have done many internal flashing, but today I tried again installing a new custom rom. Strange thing is that the bootloader says that it can´t find any image file and then quits to boot loader screen. I´ve tryied renaming the file using caps and without caps, and also with old radio in order to just test the flashing capability of the internal memory. No luck.
The phone did flash the same image from customruu. Now i´m thinking that it has to do with my messing with the internal memory for partitioning an ext2 and running (badly) android.
I realocated the ext2 partition and made the fat32 the whole internal memory. i´m not sure if i need to re-format the memory throught linux...
Any ideas why I can´t seem to run the internal flashing anymore?

[Android] & [NAND] Droid ION Donut 1.6 and Hero Blend V242

Hi All,
[ADD 22-jan-2010]
I'm testing now the NAND flashfiles from Diagdave. For newbies: Your kaiser will boot directly to Android.. WinMO is past, history... not anymore on the phone
Very FAST when boot
Have try flash with Droid ION Donut 1.6, Hero Blend V242 and new WarmDonut and all are working.
WORKING: Data, Call , Camera and hard keybord
NOT WORKING: WiFi, GPS, Voice Call, Bluetooth (known issues)
If you want try it yourself. The Kaiser-NAND-Installation.rar contain ony the 3 empty files, emty data.img and rootfs.img - HERE
be aware.. HAVE A WORKING WINMO Flash if you want go back to WinMO
There you have the 6 different flavor of the FLASH file itslef. (Thanks to DiagDave)
320 - Panel 1 - HERE
320 - Panel 2 - HERE
320 - Panel 3 - HERE
428 - Panel 1 - HERE
428 - Panel 2 - HERE
428 - Panel 3 - HERE
480 - Panel 1 - HERE
480 - Panel 2 - HERE
480 - Panel 3 - HERE
INSTALLATION:
Put all the files from the RAR on a empty SD Card
Put the FLASH file on the SD card. Rename it to KAISimg.nbh
Select you Android Build and rename it to system.sqsh and put this on the SD card
Startup in bootloader and flash your phone
Pull out the battery and restart your phone.
When everything is done restart your phone again so the APN will start as well
[INSTALLATION WHEN YOU WANT SWITCH BETWEEN WINMO AND ANDROID]
The reason i start this tread because i think smart guys can programming this ION version so BlueTooth will work also.
I have install a build from the Vogue tread and is SO fast.. The best version i have used at this moment only Bluetooth is not working.
My current WinMo config: (now removed and replaced by NAND andoid flash) but with this config everything was working fine for me in past:
Startup screen:
R: 1.71.09.01 download HERE
G: 25.75.40.03
D: 3.34.00.00 emo
WinMO Rom: Solace 3.1 download HERE
The files u need for this great working Android version (all versions i post here):
Latest Basefiles 16-11-2009 download HERE - Extract to your SD Card
Latest Rootfs download HERE - replace this one over the other of the basefile and your GPS IS WORKING!!!
You can choose between several builds. All are working ok but some of you want different flavors
Droid ION Donut 1.6 / system.sqsh download HERE rename to system.sqsh
Hero Blend V242 / system.sqsh download HERE rename to system.sqsh
Here i have post my own default.txt/startup.txt that i use for both builds:
#alloctest 0x2000
set RAMSIZE 0x07000000
set RAMADDR 0x10000000
set FBDURINGBOOT 0
set MTYPE 1553
set KERNEL zImage
set initrd initrd.gz
#
set cmdline "board-htckaiser.panel_type=2 ppp.apn=internet ppp.username= ppp.password= pm.sleep_mode=0 mddi.width=320 mddi.height=480 lcd.density=160 no_console_suspend board-kaiser-keypad.atttilt=0"
boot
Remarks
Use for Hero Blend: mddi.width=320 mddi.height=480 lcd.density=160
All system.sqsh are using the latest basefile and rootfs given above. When you switch between builds delete or rename data.img OR wipe data if you using fat32/ext2/ext2 SD card
When problem with rotation orientation you can try using zIMAGE-23-10-2009 - download HERE
Kaiser Battery problems you can try solution write on this page
[ADD 31-dec-2009]
All files are on my site - AndroidClone.nl
[ADD 23-jan-2010]
Since started my site there is dowloaded for 32GB of files... (MAX Bandwith is 50GB otherwise i must pay for every GB)
2324 (last update was 1574) times Basefile downloaed
1419 (last update was 1157) times Donut ION downloaded
1184 (last update was 953) times rootfs downloaded
706 (last update was 522) times Hero Blend v242 downloaded
359 (last update was 302) times the zipped empty data image downloaded
Donation welcome to increase the Bandwidth...
Received 10 euro.. Thanks
Hi, how can i configAndroid for work on my Kaiser wit Vodafone IT?
Is the first time that i will try Android with HaRET.
Could you help me?
Thansk.
Tommaso
Hi
Put everything in the ROOT of your Fat32 formatted SD card.
replace default.txt with default-kaiser.txt
start haret.exe within Windows. First time take some time before you see something so please wait...
After configuration is done you can go back to WinMO doing reset your Kaiser
Excuse me, if i post a stupid question...
Where can i find the last default-kaiser.txt?
Thank you very much!
download the files i given. Everything is in there
Ok... This evening, when i return home from work, i will download all, next i will put all on my SD card (i will replace the content of defuaul.txt with the content of default-kaiser.txt) and i will tap HaRET...
[edit]
Excuse me, the content of folders "conf" and "media" where have i to put?
have i to copy the folders to my SD or have i to compy only some files?
have i to modify some files?
[/edit]
I'm looking for finish this working day for try Android!!
Thanks.
Tommaso.
Everything in root. So conf and media need also in the root as folders with their files. SD Card must look like:
CONF
MEDIA
default.txt
haret.exe
initrd.gz
rootfs.img
zImage
system.sqsh
BUT..... The reason of this tread was if a programmer or smart guy can try this and can let work GPS and maybe Bluetooth would be great.
This version of ION Donut is so smooth and fast
does the vogue have working gps with this build? sorry if this is something know, can't search gps, i guess it's too short of a string for the search engine
Hi, i'veput on the SD card the file you tell me...
I have tappedon haret.exe and Andoid start booting.
I saw linux boot string running on the screen, after that, when it was pased 2 minutes my screen goes black. I've attended 5 minutes, after that i did a soft reset.
[edit 1] I tried to attend 10 minutes but nothing change. [/edit]
[edit 2] I tried also use default.txt instead of default-kaiser.txt but haret freez booting, when the loading bar arrive at the end. [/edit]
Have i to sttend lot of time?
Or is my kaiser that don't work very well?
Tommaso
kavejo said:
Hi, i'veput on the SD card the file you tell me...
I have tappedon haret.exe and Andoid start booting.
I saw linux boot string running on the screen, after that, when it was pased 2 minutes my screen goes black. I've attended 5 minutes, after that i did a soft reset.
[edit 1] I tried to attend 10 minutes but nothing change. [/edit]
[edit 2] I tried also use default.txt instead of default-kaiser.txt but haret freez booting, when the loading bar arrive at the end. [/edit]
Have i to sttend lot of time?
Or is my kaiser that don't work very well?
Tommaso
Click to expand...
Click to collapse
Steps in getting android to boot with the latest files.
1. Format your SD card in FAT32 and 2 ext2 partitions(one for the system and other for data) 256mb each. I found a gparted liveCD is the easiest way.
2. Try getting the latest basefiles from here...http://code.google.com/p/vogue-android/
3.Copy files to your fat32 partition, and you want to use a kaiser-default.txt, but change the resolution to what you like(or required) and rename to default.txt and use that. Also make sure you have the right .conf file in the /conf folder on your sd card.
4. Latest kernel makes the screen rotate upside down with the latest ext2 boot method for the kaiser so use the 10/23 zimage.
any way to increase the set amount of internal memory?
Tomorrow i will try... Thank you very much for your help!!!
Tommaso.
ajclai08 said:
Steps in getting android to boot with the latest files.
1. Format your SD card in FAT32 and 2 ext2 partitions(one for the system and other for data) 256mb each. I found a gparted liveCD is the easiest way.
2. Try getting the latest basefiles from here...http://code.google.com/p/vogue-android/
3.Copy files to your fat32 partition, and you want to use a kaiser-default.txt, but change the resolution to what you like(or required) and rename to default.txt and use that. Also make sure you have the right .conf file in the /conf folder on your sd card.
4. Latest kernel makes the screen rotate upside down with the latest ext2 boot method for the kaiser so use the 10/23 zimage.
Click to expand...
Click to collapse
I never have format my SD Card is several partitions... And everything is working. (exept GPS and Bluetooth for the given ION donut build)
Also never understoot will de system automatic detect the 2 ext2 partitions and will it use them automatic? Will also the system work faster?
Calibrate touchscreen:
"You can also calibrate the touchscreen by holding the camera button down (so that the keyboard is showing) while tapping the top right and then the bottom left of the screen. Do this while running the pointer location app in dev tools to check that it works. The keyboard now is the same as on the emulator."
Try this
kavejo said:
Hi, i'veput on the SD card the file you tell me...
I have tappedon haret.exe and Andoid start booting.
I saw linux boot string running on the screen, after that, when it was pased 2 minutes my screen goes black. I've attended 5 minutes, after that i did a soft reset.
[edit 1] I tried to attend 10 minutes but nothing change. [/edit]
[edit 2] I tried also use default.txt instead of default-kaiser.txt but haret freez booting, when the loading bar arrive at the end. [/edit]
Have i to sttend lot of time?
Or is my kaiser that don't work very well?
Tommaso
Click to expand...
Click to collapse
Open the default-kaiser.txt and edit the "htckaiser.panel_type=[Number]" with the number 1, 2 or 3 (try all of them, until it works).
dyetheskin said:
any way to increase the set amount of internal memory?
Click to expand...
Click to collapse
That's set in default. It's already the most you can (should ever) set it to. Remember the kernel and drivers take up memory as well
Android Failure
Hello Everyone,
I'm a newbie at this but I have read all the troubleshooting guidelines. Anyways, I have a Tilt (Kaiser), having issues loading the New Android. I'm the basefiles-20091116, have copied it to my microsd. I have edit Conf / to just have donut.user.
Now, when I run Haret.exe. I use the default-kaiser.txt to load Android, but after a few seconds I get a "Failed to find system.img on Sd card
/bin/shi can't access ttyi job control turned off " message.
Are there any suggestions to fix this issue?
Do you have a system.img/system.sqsh in the root directory of your sd card?
Android failure
To Whitehooptie, no I don't believe I have the system.img/system.sqsh your talking about. I've been looking for that in the basefiles. Can I find the system.img in the basefiles I've recently downloaded?
Cuzimbrownhuh said:
To Whitehooptie, no I don't believe I have the system.img/system.sqsh your talking about. I've been looking for that in the basefiles. Can I find the system.img in the basefiles I've recently downloaded?
Click to expand...
Click to collapse
Read the first post and you can see what you needed....

How to revert back to WM after flashing Android to NAND?

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.

[Q] How I can install Android to my Kaiser? :(

Hello friends!
I want to change my pda's operation system from WM to Android.But i can't do this anymore...I'm trying all the time Eclaire and Myn's Warm Donut and i've read all threads but i cant do this I want to install Myn's Warm Donut to my Kaiser, but when i click the run button, my Kaiser is freezing on this session, and i'm doing soft reset to my Kaiser.
Is anybody explain that step-by-step, How to Install Android on Kaiser?By the way my Kaiser's Radio 1.70...... and HardSPL newest version.
Thanks for everybody.(I'm sorry my poor English)
first edit your default-kaiser just in default then run haret if again it freezes then open default and change the panel no 1 to 2 and then agian try
You can refer to this article:
h t t p:/ / forum.xda-developers.c o m /showthread.php?t=680518
shortly is:
1:format you sd card to FAT32
2: download the nbh files and rename it to KAISimg.nbh and place it on you sd card
3ownload your favorite Android build. On your SD card make a folder called andboot and place the androidinstall.tar file in there. It could also be called androidinstall.tgz. You may have to change settings in Windows to see extensions.
4lace the SD into your Kaiser and hold the Power button and camera button down, then take your stylus and hit the reset button. Follow the instructions on the screen to flash your Kaiser. When flashing is done, reset the device with your stylus.
5:when you see the text " Hold down Volume Up or D Pad",hold down the d-pad.until the install menu appears .you can setup as default
6:selcet "1 install system",if some window popup,just select "yes" and confirm.
7:wait several Minutes,when the menu appears again,selcet "10 quite".it will began booting into android.for the first time, booting maybe taking longer time.
Thanks for reply But i can't do this again.I'm downloaded .nbh file and putted to my SD card and i putted androidinstall.tar file to my SD card into andboot folder.I'm pressed these button everything is ok, loading screen came to my kaiser, it just installed to kaiser but, after same screen is came to me again.i did same things again again..When i reset my kaiser, i saw my WM rom..
Where is the wrong thing?
Thanks for your help.
if you are installing to sd card you need to run haret again to run android if you installed to nand once you install it press exit on the installer menu and wait for android to boot you do not have to install it again
I've changed to .nbh file it updated the firstly.I'm receving that message UPDATE SUCCESS.But while android installation i'm receiving too many errors and it did not installed.
Other error is, for example when i want to install Myn's Donut Android, haret freezed all the time.
Please help, i cant install any android rom :S

[Q] android install..please help!!..ive read guides

hey guys, im sure this is getting old for some..but yes im a newbie, 8925 user. ive read the android install on htc by l1q1d, which i thought brought me in the correct position.. (not to say it wasnt a good guide, im sure it is..im a noob) i was wrong heres what im using and trying to accomplish, i sarted out reading "How to replace Windows Mobile with Android (Guide)" the first thread, i used jump spl 1.93 , flashed hard spl 3.56, flashed radio 1.71.09.01, then i used the htc on droid guide on atools to configure my kernal (which i loaded while in atools, i tried both 2.6.52 and 2.6.32-which is the current one im using )saved the KAISIMG.NBH in the root of my sd card(2GB HP i think its class 4) then set up my androidinstall.tgz(Incubus26Jc's Super FroYo RLS16 All Languages) in the atools mixer with the unique module update in atools V1.0.4 and extracted them together. saved the androidinstall.tgz in the /storagecard/andboot. then used BSE boot script editor, to setup my install-seq.sh which i also saved to the /andboot folder.
Heres my current specs again in line:
jump spl 1.93
hardspl 3.56
radio 1.71.09.01
kernal 2.6.32
Build Incubus26Jc's Super FroYo RLS16 All Languages with atools module update extracted together
when installing , the farthest point i reached was a succesful install of kernal, then reboot, install-seq.sh started---end result "could not determine file system size", failed, failed to format.
im currently trying to use nand for system and sd card for data , not sure what SWAP means?...
as for the seetings for fstab on atools ( which was the most confusing for me), i p
SYSTEM- NAND p2
DATA- sd partition p2
SWAP- sd partition p3
ive also tried system as nand p2, and data as nand p3 and swap at auto, cause i figured im having issues with my sd card , but then it said something about "install update module for kernal". im stumped any information you can helkp with would be greatly appreciated, here a few links to pics of the settings i made in atools, thanks alot
Hmmm, I have just tried that myself and I think it might be a bug in atools - I was changing nand partition sizes and the only combination I could get to work was Atools 1.0.4 with all fstab setting set to auto (I haven't tried Atools 1.0.5 yet, but 1.1.0 didn't work for any combination of settings for me)
Also I've never used the install-seq.sh so I can't help with that.
As a "good" starting point try using Atools 1.0.4 , latest kernel, don't change system/data partition sizes and leave all fstab settings on auto.
Flash that nbh then install through the boot menu (hold D-pad centre on boot)
If that works, then it will be easier to work from there to find out what exactly was causing the problem
huh, yup im learning as i go lol , i have tried to boot without using the install-seq file but have not tried to install with fstab on auto. what does that mean though, if its placed on auto is it going to just pick whatever i feel like at the moment , im assuming system will be on nand , but what about data. and also ive tried looking it up but what does SWAP mean? thanks alot im gonna try what u said
EDIT: ok i tried that out i got into the manual install by pressing the dpad center button, then i picked system and data to be installed on nand , then installed, then quit, then it, loaded for a while then it went to a droid screen and a animated green ball that seemed to be loading but just stayed there and did nothing. so i turned off the phone.... could it be because i didnt press 4. install update(do i even need to)? OR should i have installed system on nand then data on sd partition?
try again, and leave it a bit longer, the first boot of an un-odexed build can take aver long time, maybe about 10 minutes
swap is extra space for RAM, but on the NAND memory or SD card - like a swap partition on linux or a pagefile on windows. By default there is no swap partition used.
option 4: "install update" extracts the contents of an androidupdate.tar or .tgz file in the andboot folder, if you haven't got an androidupdate file you're trying to use then you don't need to use this option
allright ill try it now thanks man
i tried it again, but this time i used thoughtlesskyles not so super froyo rls18 and i waited , and it finally came up its installed ive checked a few things, calling works, wifi ,navigation maps some cool stuff. im gonna use this for a while then try my luck on some other endeavors. thanks again

Categories

Resources