Related
It is not quite self-explaining how to install Android on our Windows Mobile devices. Therefore I took some time and wrote down all the steps for people who are new to "Android".
More testers -> more experience -> more knowledge -> faster/better development.
I hope this way the forum is kept clean(er) from all kinds of questioned that have already been answered many times.
ReadMe Includes:
- Partitioning
- Device preparations
- Boot loader
- Install steps
- Fixes
- Links
- more...
If you are a developer (you create your own package) feel free to use my ReadMe for your packages (update regularly though).
to download the ReadMe click the [Android Repository] button in my signature.
It goes to a rapidshare page with 3 files, and when I click on the filename Android_README.TXT
or start download, I get the error
The file could not be found. Please check the download link.
ok thanks. i fixed it (rs bug when renaming files ^^)
How would i partition a 1GB SD Card? ie what sizes etc are the last 3 same but the unallocated is just whats left over?
I want to use a spare card rather then the one that came with my HD.
ATHiEST said:
How would i partition a 1GB SD Card? ie what sizes etc are the last 3 same but the unallocated is just whats left over?
I want to use a spare card rather then the one that came with my HD.
Click to expand...
Click to collapse
normally just calculate how i wrote in the readme:
whole space -768 (3* 256) and then the other 3 x 256
but in ur case i would make the swap smaller (i think its not even used at all) and the fat32 bigger; for instance:
fat32 - 384 MB
ext2 - 256 MB
ext2 - 256 MB
swap - 128 MB (rest)
To be honest the bit I find most confusing is all the different versions!
i didnt create any partitions on my card, and android works as good as it does on any, mind you i have not updated the files fo0r a month so alot might have changed
ReadMe updated!
updated a bit...
Geeba said:
To be honest the bit I find most confusing is all the different versions!
Click to expand...
Click to collapse
i agree...
i've been looking these posts here for a couple of days now and i still don't know how to do it....
especially the DualBoot thing...
is it possible to make a little bigger how-to manual?
or at least explain the versioning and the needed thing a little more?
the readme is about 50 times longer than anything else u will find about installing android anywhere else
the different versions are just like in windows mobile, theres not much to explain, its rather up to ur personal preference. doesnt take as long as flashing a wm rom, so its easy to try out more versions, especially with more sd cards.
dual boot is easy:
1. install the cab
2. open the dual boot program and make all your settings, for example: auto boot android (click on the checkbox/ratio under android logo), check auto boot checkbox and check fast boot (means 3 instead of 10 secs).
3. restart your device, DONT LAUNCH HARET because that will destroy all the dualboot settings. if you restart/shutdown the device normally, the settings will be stored and android will automatically booted at next startup (or whatever you set before)
if you have android autoboot and u want to boot wm, just QUICKLY press the wm LOGO when the dual boot screen appears.
i might include this in the readme soon, just dont have the time right now unfortunally
N!ghty said:
the readme is about 50 times longer than anything else u will find about installing android anywhere else
the different versions are just like in windows mobile, theres not much to explain, its rather up to ur personal preference. doesnt take as long as flashing a wm rom, so its easy to try out more versions, especially with more sd cards.
dual boot is easy:
1. install the cab
2. open the dual boot program and make all your settings, for example: auto boot android (click on the checkbox/ratio under android logo), check auto boot checkbox and check fast boot (means 3 instead of 10 secs).
3. restart your device, DONT LAUNCH HARET because that will destroy all the dualboot settings. if you restart/shutdown the device normally, the settings will be stored and android will automatically booted at next startup (or whatever you set before)
if you have android autoboot and u want to boot wm, just QUICKLY press the wm LOGO when the dual boot screen appears.
i might include this in the readme soon, just dont have the time right now unfortunally
Click to expand...
Click to collapse
Thanks for the dualboot help... i'll try that...
the first problem I have encountered yesterday when trying to put Android was SD card formating...
i downloaded the program you said and followed the instructions oh how-to and was not able to do it under Windows 7 with my 16GB SD card... does it even work for Windows 7??? is there another program I can try to do it with???
I have also dualboot on my PC with the Kubuntu being the second OS, but I'm not using it as much as Windows 7... I can try with it if you think it will work.. but first I have to download the 15GB of data from my SD card to my PC, again
I would like to put the Espresso build cause I saw that it has everything working beside the GPRS and camera...
can you tell me what should I download for my Blackstone so it works properly???
thanks alot...
qtype said:
Thanks for the dualboot help... i'll try that...
the first problem I have encountered yesterday when trying to put Android was SD card formating...
i downloaded the program you said and followed the instructions oh how-to and was not able to do it under Windows 7 with my 16GB SD card... does it even work for Windows 7??? is there another program I can try to do it with???
I have also dualboot on my PC with the Kubuntu being the second OS, but I'm not using it as much as Windows 7... I can try with it if you think it will work.. but first I have to download the 15GB of data from my SD card to my PC, again
I would like to put the Espresso build cause I saw that it has everything working beside the GPRS and camera...
can you tell me what should I download for my Blackstone so it works properly???
thanks alot...
Click to expand...
Click to collapse
like the readme says: partitioning is only needed for partitined builds, which means that android uses several partitions to store different kinds of data, for - hopefully - more speed. only glossy uses partitions, espresso doesnt.
for glossy, u can also use ubuntu (download parted magic or something similar) to create partitions.
for espresso, u just need to copy the stuff onto ur sdcard.
but thats all in the readme... i dont have time to explain in detail coz i need to study a whole ****in lot at the moment +.+
N!ghty said:
like the readme says: partitioning is only needed for partitined builds, which means that android uses several partitions to store different kinds of data, for - hopefully - more speed. only glossy uses partitions, espresso doesnt.
for glossy, u can also use ubuntu (download parted magic or something similar) to create partitions.
for espresso, u just need to copy the stuff onto ur sdcard.
but thats all in the readme... i dont have time to explain in detail coz i need to study a whole ****in lot at the moment +.+
Click to expand...
Click to collapse
ok... thanks for the help... you helped me a lot just with the claryfication of the versions that need partitioning and the ones that don't...
i didn't know that...
good luck with studying!!!!
one more question...
I get the following message '' Failed to load file\Storage Card\zImage''
Can you help me with that????
qtype said:
one more question...
I get the following message '' Failed to load file\Storage Card\zImage''
Can you help me with that????
Click to expand...
Click to collapse
meaning u dont have a zImage at all (ur probably using espresso?). so download one from here, copy files onto sd card and rename "zImage.xxxxxx" to "zImage" and ur ready to go.
N!ghty said:
meaning u dont have a zImage at all (ur probably using espresso?). so download one from here, copy files onto sd card and rename "zImage.xxxxxx" to "zImage" and ur ready to go.
Click to expand...
Click to collapse
yep, I downloaded it but I didn't know that i have to rename it...
It did the trick... booting up Android
thanks for all of your help...
updated the readme, not includes DualBoot howto and some other changes...
I managed to get the WiFi working but no matter which zImage I'm using I can't get the 3G to work...
I'm I doing something wrong or did I maybe forgot to do something????
qtype said:
I managed to get the WiFi working but no matter which zImage I'm using I can't get the 3G to work...
I'm I doing something wrong or did I maybe forgot to do something????
Click to expand...
Click to collapse
well, some details about what version you are using would be helpful. however, this is not the right channel to ask this question. i think this question has already been asked several times in other threads. try search function or read the thread for ur version, its probably a version-issue or only for your country/provider
N!ghty said:
well, some details about what version you are using would be helpful. however, this is not the right channel to ask this question. i think this question has already been asked several times in other threads. try search function or read the thread for ur version, its probably a version-issue or only for your country/provider
Click to expand...
Click to collapse
sorry about that...I realized it later that I should ask in another thread that question...
I managed to figure it out... I just needed to manually configure my APN settings...
hi there
i really need your help. i'm trying to install android on my HTC TyTnII. But i'm having problems to install.
can you please help me to get Android run on my Kaiser?
Right now i'm running the windows mobile 6.1. I want to install Android as a secondary OS.
i followed this installation guide.
androidonhtc.com/wiki/Installing_Android
1. I went to this link to download files.
androidonhtc.com/wiki/Latest_Builds_%28Kaiser%29
2. I downloaded the basefiles-20091116.zip
vogue-android.googlecode.com/files/basefiles-20091116.zip
3. Unzipped this zip file. Renamed the default-kaiser.txt to default.txt and moved the whole folder "android" to my storagecard.
4. then i downloaded the haretinstall.zip and unzipped that file as well. I moved the folder "andboot" to my storagecard.
sourceforge.net/projects/androidhtc/files/2010-02-20/haretinstall.zip/download
5. then i downloaded the polymod_2.1g.zip and unzipped that file. I moved the file "androidinstall.tar" to my storagecard as well.
ponack.net/poly/2.1g/polymod_2.1g.zip
6. i clicked than on "haret.exe" and clicked on Run. the android started to load but then it stops. It gives me this error.
--------
....
Checking for partition...
s2fsck 1.41.4 (27-Jan-209)
ext2fs_check_if_mount: No such file or directory while determing whether /dev/block/loop0 is mounted.
/dev/block/loop0 was not cleanly unmounted. check for ced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/loop0: 11/65536 files (0.0% non-contigous), 10335/262144 blocks
losetup: /dev/block/loop1: No such file or directory
Failed
Failed to find system.im on SD Card
/bib/sh: can't access tty1 job control turned off
/ #
--------
Can anyone help me out to solve the problem?
Do i need to do some partition? if yes...how can i do it? i'm using a windows xp OS.
This is how my SD-storagecard looks like:
/[android]
/[android]/[andboot]
/[android]/androidinstall.tar
Thank you for your support.
The androidinstall.tar should be in andboot folder, with all the haret files. andboot must be in root of SD card.
/
/andboot
If you were installing to nand it'd be :
/KAISimg.nbh
/andboot
You do not need to partition the SD card, just make sure it is formatted FAT32, not FAT
hi zenity
thanks for the response. I did what you said. Still having the same problem with the same error message.
how do i check format of my sd card? i've never formated it before. it's the original sd card.
Depends if you have an sd card reader and adaptor for micro-sd, if you do you can just format it in windows.
It's likely that it's formatted FAT, most new pre-formatted micro-sd are formatted FAT as standard, how are you transferring files to the sd at the moment?
i connected my htc with microsoft activesync then transfered the files via windows explorer.
i'm still struggeling to get android run on my device.
are those steps correct? or am i doing something totally wrong?
those installation guide are too complicated for me. the instructions are mostly for total replacement of the OS. But i would like to keep my windows mobile because of tomtom navigator. I want to make both OS run with Dual booting function.
if you are so kind...can you please guide me to make this run? I'll be thankful for that.
Best way to format an SD card is to use a card reader and micro-sd adaptor, I've never tried to format an SD with winmo or through activesync, so I'm not sure how easy that is.
I have transferred the files via activesync before, and that works fine, but your SD card must be FAT32, winmo probably does not know the difference, I'm sure there must be a way to format the card FAT32 in winmo, but I cannot think of one, I'll look into it though. I think total commander is able to show what type of format the sd card is, but don't know if it's able to format it.
All the Haret files plus the androidinstall.tar must be in the andboot folder on the SD card, you do not need any other files or folders on the card, but it should not matter if there are any.
You will need an SD card of at least 1GB, 2Gb is better.
I know the guide is meant for Nand install, but does show the installer screen part clearly, and the install procedure is the same for nand and haret, and shows the installer screen you should see when installing on FAT32, (haret).
Download Card Export or WM5Storage to mount the card. Then format it like you would do with a usb stick.
me too
I get the same error.
I have haretinstall and androidinstall.tgz in the /andboot folder.
I renamed default.txt to default.txt.no
I renamed default-kaiser.txt to default.txt
I edited default.txt to point to zImage-eclair
I tried with the regular zImage
I wait till it ask for dpad or vol up button then I press and hold dpad. It never recognizes? Or thats my guess from what has been said here.
right clicking on the drive from within windows using a card reader it says fat32.
When I press dpad it prints a ^@ to the screen, ironically it does the same key for ok. I don't see how I can hold down the vol up/down key cause its a jog wheel? Should I try dpad down?
Volume Up Is the RIght SOftKey. FOr some build only that work.
@zenity: i manage to format my miniSD to fat32. it was fat before. but the problem is still there..does anyone else know how to deal with this?
as tyler51773 already mentioned..i fi start the "haret" which is stored in "andboot" folder it request to hold down the vol button. although i pressed the vol. button,,,it still doesn't work. getting the same error message like tyler51773
seems like i'm totally lost. someone please help!!!
can anyone write down a clean instruction how to install the kaiser on SD incl. the right link (instead of telling users to find out the right one) without wiping out the windows mobile. this would be more helpful to us.
i'm sure there are other users who might be interested in this too.
thankx
When you run Haret and see scrolling text, immediately hold down the d-pad or vol button. Don't wait for it to ask.
hi all,
i have the same problem. the instructions seems to be bad. i cant run it and tried many things. in install-instructions says "androidinstall.tar" but download is androidinstall.tgz.
i don't know if its a big mistake, but someone should make a new "correct" instruction with correct files. maybe it then will be worked.
i also stuck on "can't found system.img"
greetz an sorry for my english
@dukennukemx: i did what you said. no improvement.
@lenzen24: i'm 100% with you!
i tried again,
but also failed on find system.img on sd-card
hope someone has a solution, becaused i woudn't flash a image over my wm6.5.
greetz lenzen
progress
The right soft key button worked, (i.e. the one right above the mail, to the left of the red phone to the right of the dpad just to be perfectly clear for anyone else).
I got the menu, and then it said unbalanced irq 102, unbalanced irq 86?, unbalanced irq 87? it froze then rebooted.
Second try, I hold down the right softkey after i see the penguin. I get the menu with the ok warning. I try all the buttons the warning stays up. I open up the keyboard. I press enter I now am in the menu.
The install option is missing? I have 1. fix permisions. (vs it saying install?) The dpad doesn't seem to work. I have 7 options. The last option is quit. The 6th one is recovery. 5 is wipe. As I'm staring at errors and not the menu I forget which the rest are. I remember seeing a backup/restore. Then their is wipe. Their was also the wipe cache options.
When I try to navigate the menu its a no go. The only real options I have is fix permissions. That leads to errors due to a missing system.img that hasn't been made yet? And then their is quit. I get to quit using the left opt key, and I can get to fix perms using the right opt key. If i open up the keyboard and try every key the only key the menu responds to is enter. I also tried w/ fn lock, but not shift, no responce to the arrow keys was a bummer. When I accessed a shell I can atleast confirm that qwerty mapping was right, but didn't hang out long enough to see the rest of the keymap.
Should I try zimage-eclair? I will of course do that at some compulsive moment, but hey, maybe I wont, or maybe I will and say I haven't yet - maybe I already have {knowingly or not}.. do I need some options in my default.txt? Should I try a different androidinstall? this is polymod-2.1g
This is actually a Tilt vs a Kaiser.
Thanks for the speedy replies and help!
Tyler
Problems with the install option not appearing are usually caused by not formatting the sd as FAT32, or a wrongly set up sd card, for haret installs, everything goes in andboot folder, for nand, androidinstal.tar, (or tgz), in andboot folder, kaisimg.nbh in root, the install instructions are clear enough, they are just not as easy to follow for inexperienced users, and tilt and kaiser are the same thing, if you look under the battery it will say 'kaisxxx'.
zenity
Your last post you can tell someone got under your skin...
I'm a fairly experienced user. I have had troubles installing android since the nand came along.
I feel that if I were willing to nuke my winmo it would be installed. my primary objective with this phone is voip. I'm hoping sipdroid gets fixed or the reports of sipagent working better than sipdroid are true. I'd like to investigate that. I'm poor and with winmo I pretty much make free calls. Albeit I have reliability issues, and I have lots of things i should script to make things work which is all the more motivation to move over. Especially with winmo7 stripping voip out completely [rumor mill]. Anyhow, I am not willing to nuke my winmo. It's quite cryptic to call the volume key, the volume key, when on the kaiser its the right opt key. Perhaps the problem is that I am running a tilt vs a kaiser, another cryptic difference? good thing we don't have a lot of sidekicks running around either. Anyhow. My card is formatted right. I even tried another almost virgin 2gb card, never been formatted but did have a raw filesystem that was only used on sundays while driving to church, it was freshly formatted with fat32 and still it was a no go.
I also just tried myns build. I get an install option, when I press enter it warns me that it is about to delete my all my stuff. So I would say no, but after feeling wrath I tried to say yes, but of course I can't navigate nothing I push will let me choose yes. So I safely run with no.
If I did have a dpad where it says backup data could I backup my winmo? That makes me feel good I've always wanted that. That feature alone would make my day as it would let me finally upgrade my sacred voip setup w/o fear of having to find all those little f!&@&# registry entries again.
Enter does a carriage return in shell? New line in any event..
Dpad/Ok on the front both print a ^@, so does the side ok button, and so does the keyb ok button. {so does; Winkey, MailKey, GreenPhone{send}}
Dpad/Keyb/Jog Up does a ^[[A
Dpad/Keyb/Jog Down does a ^[[B
Dpad/Keyb Left does a ^[[D
Dpad/Keyb Right does a ^[[C
Left Opt: ^[[26~
Right Opt: [BLANK]
e does ^[[1~
red phone{end} ^[[4~
PwrOff ^[[4~
Admittingly this is using myn's androidinstall.tar as i just got done trying that, not sure if the keymap would vary at all (I highly doubt that). Anyhow I also did see the sdcard mounted. I cd'ed into it and did an ls. Everything showed up. It was mounted rw.
Let me know if I can do anything else to speed along the development.
Hate to ask a dumb question? But why not continue to distribute the sqsh builds if they're so much easier to test out for winmo users? Isn't that what the installer is trying to do is process the androidinstall.tar file into either one of three options one of which is cacheable - the sqsh files?
But still, I'd love to hear I now have a back up option..
Zenity thank you for your hard work and even diligent support! I totally get the stress that comes with messing with software for long periods of time. If it helps we can sacrifice a user to the /dev/null ? Hope you're feeling better.
tyler51773 said:
Your last post you can tell someone got under your skin...
Zenity thank you for your hard work and even diligent support! I totally get the stress that comes with messing with software for long periods of time. If it helps we can sacrifice a user to the /dev/null ? Hope you're feeling better.
Click to expand...
Click to collapse
Lol, sorry if it came over like that, I was typing it at a cafe on my kaiser, so I didn't spend as much time as I usually try to on a post, I usually try to structure them as carefully as possible to avoid misunderstandings
To be more accurate, I feel that the present sets of install instructions do assume a lot more knowledge than a lot of those new to Android actually have, this is not a disrespectful statement, simply that most builds have grown and changed so much, and the users who have been using them have also grown in specific knowledge of the install process, this, naturally, has led to some instructions assuming that those users all know the basics, which of course would be true if there were no new users.
It is difficult to produce a generic set of install instructions, since there are still a number of ways to get android onto our devices, and some builds are designed for other hardware originally, myn's for Vogue for example, so the install instructions tend to be more focused on those devices.
As far as the actual installer is concerned, the only time you will wipe winmo is if you have already flashed to nand, running via haret will not wipe winmo, the warning about wiping the system, or data, applies only to the Android build you are installing.
The present installer will process the androidinstall.tar or .tgz and install either to nand, if that is available, EXT2 partition, again, if available, or FAT32 partition, most commonly known as SD card or Haret install, the actual installation will then unpack the tar file to the proper destination, and on haret will produce a system and data img file, I'm unsure if it produces a sqsh file, since it's been a long while since I ran from anything but nand, but I do understand the confusion the install produces for those wishing to stay with winmo, and would prefer that it was clearer, but as with most of android development, once it works, development ceases until it breaks
Rest assured, unless you flash to nand, your winmo should be completely safe, I have not yet seen anyone wipe winmo using the SD/Haret method, not in all the time that we have been running Android on our kaisers.
I'm confused now however, I was always under the impression that the Tilt was merely another kaiser model, and unless you have forgotten to edit the default.txt file to reflect your hardware, the keypad/dpad should function properly, which as far as the escape sequences you have posted, would seem to be the case, ( dpad centre should give ^@ in console etc), so navigating the installer should be as easy as pressing the left, right up or down keys, followed by centre to choose options.
What I am now tempted to do is reflash my secondary Kaiser to winmo stock, and try a few haret installs just to check out things, since most of the above is mainly from memory, although a lot of the Nand install procedure is similar, may not be identical.
Sacrifices will not be necessary, however offerings may be made of caffeine, and/or chocolate, this may help me continue to function in my role as helpful user, and reduce my occasional visits to the mild irony I call my sense of humour
cool
I feel you about short emails making one sound bad! I made that mistake a few times. I actually hate email. I wrote this very funny email to my advisor, he liked it, and forwarded to his boss - just communicating, not to share a laugh or to complain, but to answer a question he did not know; atleast I was told that as I was then later forced to ask him 'did I make you mad?'. Anyhow I got chewed out for professionalism by the department chair which is not the way to a elect a major. Funny enough, I had decided writing funny was the way to go after i had peeved someone off for writing short almost angry sounding emails. In short I hate email/communicating via text.
I was thinking about the whole solution thing. If i need to do a key remap maybe we could just write up a shell script and I could execute it from /sdcard and then re-execute the installer ? unknown.sh??
Also, if you produce some img files what's to stop you from sharing those? I'd totally be willing to try it, maybe it'll work, maybe it'll break wifi calibration? who knows?
Bug found:
http://code.google.com/p/vogue-android/issues/detail?id=124#makechanges
set cmdline "ppp.nostart=0 pm.sleep_mode=1 mddi.width=240 mddi.height=320 no_console_suspend board-kaiser-keypad.atttilt=1"
just tried to change board-kaiser-keypad.atttilt=1 with no results
Just my .02c
Hi all.
I've been lurking on the Kaiser forum for some time and have found a wealth of very useful info... Except when it comes to running Android via HaRET.
Yes, I know there have been a million questions. Yes, I have seen many of them inserted into what should be straight developer/bug threads. Even so, the "answer" to my issue doesn't work.
From "How to run Polymod’s AWESOME 2.1 Eclare Build and Updates":
Section 2 - Errors and FAQ's
===============================
#1 Failed to reach system.img on SD Card
If you see the error message below:
“Failed to reach system.img on SD Card” then you did not hold the button down correctly. You are seeing this because you missed, disabled or bypassed the install menu.
Click to expand...
Click to collapse
NOT TRUE. I have booted more than 20 times pressing/holding the center button at different times and with different intensities. No matter what I do, I get this blasted error message. Any solution other than the stock one listed above would be cause for hero-worship.
This error can have a number of causes, namely the file system, is the SD card formatted FAT32, ( some cards come formatted FAT16 as standard), or having the SD card set up incorrectly, for haret you need to have all files in the andboot folder.
Provided haret starts correctly, which it is since you cannot reach the post-install stage unless it is booting the kernel, then the only part of the procedure that can go wrong is the installer.
The only things I can think of that would cause the installer not to start is either the card itself, or problems with the andboot folder and/or the files inside.
The only advice I can give at the moment is to calmly start haret, watch the scrolling text until you get the pause, and the 'press d-pad to start installer' text.
At that point if you press the d-pad centre button, and hold it you will see '^@' on the screen, if you do not see the '^@' or see anything else then the installer cannot start, it will only respond to the correct key.
If you see anything else it is possible you have incorrectly set an option in default.txt file.
If all this still fails, then report back with anything you find, I may have some other ideas based on what you find out
+1 on zenitys answer and in addition you are using the correct basefiles to run haret?
Try using the screen as a giant keypad and pressing and holding the center of the screen.
EDIT: Scratch that... It only works as a keypad once the menu is up. Sorry.
that works?
Seriously?
I mean really?
No it bloody does not, ( lol, can't believe i actually tried it ).....
i had this problem and pulled my hair out, eventually i downloaded a different haret basefile and copied to my SD and bam it worked, sorry but i'm i soon after went to nand and erased the haret files so i don't have them anymore.
zenity: Yes, it is FAT32 and yes all files are in andboot. I do see a '^@' when I press the center button if I press it when prompted. If I press and hold as soon as I see Tux, I don't get that character pair. I see a different string of characters if I press one of the other buttons instead. I haven't modified the default.txt file in any way other than to re-name it from default-kaiser.txt.
I am using the files from a haretinstall.zip that I got directly from sourceforge Android HTC project (sourceforge.net/projects/androidhtc/files/... not allowed to post links <_<). The files were under the date 02-13-2010. I have since grabbed two other more current versions of haretinstall.zip and will try them after I post this. I am also using the most current androidinstall.tar and androidupdate.tar from sourceforge, though I have also tried Polyrithmic Eclair 2.1g's androidinstall.tgz.
Thanks all for the replies and I'll try those other haretinstall.zip's while waiting for any other replies.
maybe try a different sd card?
I couldn't get any nbh's to be read off of my 2gb patriot, but when i put in my 16gb sandisk the nbh's worked.
I know this is only marginally related lol, but it's worth a shot?
mr_fosi said:
zenity: Yes, it is FAT32 and yes all files are in andboot. I do see a '^@' when I press the center button if I press it when prompted. If I press and hold as soon as I see Tux, I don't get that character pair. I see a different string of characters if I press one of the other buttons instead. I haven't modified the default.txt file in any way other than to re-name it from default-kaiser.txt.
I am using the files from a haretinstall.zip that I got directly from sourceforge Android HTC project (sourceforge.net/projects/androidhtc/files/... not allowed to post links <_<). The files were under the date 02-13-2010. I have since grabbed two other more current versions of haretinstall.zip and will try them after I post this. I am also using the most current androidinstall.tar and androidupdate.tar from sourceforge, though I have also tried Polyrithmic Eclair 2.1g's androidinstall.tgz.
Thanks all for the replies and I'll try those other haretinstall.zip's while waiting for any other replies.
Click to expand...
Click to collapse
I do remember trying the 2/13 first and that is the one that holding the button did absolutely nothing, it was either 2/14 or 2/20 (those are in my browsing history) that did work for me. It was a "ta dah" moment when the install menu popped up.
deezy7 said:
maybe try a different sd card?
I couldn't get any nbh's to be read off of my 2gb patriot, but when i put in my 16gb sandisk the nbh's worked.
I know this is only marginally related lol, but it's worth a shot?
Click to expand...
Click to collapse
I doubt it, cause its reading the kernel if he is getting the error message. The error message about system.img is because an install hasn't been performed to create a system.img or data.img file on the sdcard.
Actually it's very related, android seems unusually sensitive to SD card issues that winmo simply ignores.
If you have another SD card available then try that, if not then all I can suggest at the moment is reformatting a couple of times, that worked for one of my 2Gb cards that simply would not recognise my NBH files no matter what I did.
An alternative might be to grab kalt_kaffe's zimage from here : http://forum.xda-developers.com/showthread.php?t=660158
this seems to be the best zImage for eclair at the moment. Just download it, put it in andboot with the rest of the haret files, make sure it's named correctly, ( it'll probably need you to delete the zImage file already there anyway, or overwrite if you use a card reader and windows).
Since you are getting the ^@ then the kernel is running properly, that actually only leaves the SD card, the reason you get the other character pair if you press to early is that with some zImages the keyboard may not be set up early enough, which is why I always wait for the pause, never failed me yet.
Maybe... Maybe...
Thanks again all.
It may well be the SD card but a more current set of HaRET basefiles did finally fix the center button issue. I have been able to get android installed but little else. I have a blank screen (with clock, battery and wifi in the top bar) but nothing else.
I'm going to blame this issue particular tar files I used and I will go back and try the Eclaire by Polyrithmic or the one by kallt_kaffe you linked. I didn't really want the Andriod HTC tar files but was using them in an attempt to minimize the variables causing my initial button issue.
If you are going to use polymod may I suggest the 2.1D download linked in my sig, it's only the install.tar, but is pretty stable, and is in fact what I use for my everyday android on my main kaiser.
Since you have a working set of haret files, simply replace the zImage with kalt_kaffe's zImage, replace the installer with poly's 2.1D and you should hopefully be good to go
I tried 2.1d and it locked during the post-install setup. I also tried kalt_kaffe's zImage with both 2.1g and it broke my wifi.
As such, I am back to using 2.1g with the kernel that was originally bundled with it... Even bluetooth seems to work. I can see my lappy but I haven't tried pairing yet. No microphone though as far as I can tell. It'll be awesome once the ethereal developers find a way to make the camera work.
At least now I have something new to play with. I'm eying Warm Donut b/c I like the look but I don't know if I want to undo the working install I have. Never know till you try, right?
I guess this is probably already well-known but my kaiser's camera works under Warm Donut. The pics aren't all that great but it does take them.
If anyone else stops by... I'm having audio problems. I'd had audio problems with all the different Android releases I've tried so far. The main problem is that there is no audio. No alerts, rings or media.
Any suggestions?
mr_fosi said:
If anyone else stops by... I'm having audio problems. I'd had audio problems with all the different Android releases I've tried so far. The main problem is that there is no audio. No alerts, rings or media.
Any suggestions?
Click to expand...
Click to collapse
The way I understand it, that can be affected by your radio firmware... The radio firmware I use without any problems for android is in my sig.
Please post which one you are using, too!
Good call! I hadn't considered my radio version though I have seen numerous posts suggesting that users upgrade... Or at least swap theirs out.
WM6 indicates that my radio version is 1.27.14.09.
Radio 1.27.14.09
Protocol 22.45.88.07h
ROM 1.62.00.00
I'll do a little reading and see if I can't figure out how to swap a new radio (probably the one you're using) in.
Ok that's one old radio, go here : http://forum.xda-developers.com/showthread.php?t=393182, get the 1.71.09.01 linked at the bottom of post #3, it's an nbh file, so just rename it to KAISimg.nbh, put it on SD and flash the same as the Nand nbh, it will not affect anything, just upgrades the radio.
I got the radio nbh and now I am working out how to use nand. Most everything I see is geared toward wiping windows to replace it with android. I don't want to do that yet so I'm trying to parse now to flash this nbh without jacking up my device or the windows that is currently on it.
This method will work in windows for:
SD Cards in memory card readers/laptops
Phone set in memory card mode
HISTORY
Ok i ran into a wall with this one because of three reasons:
1. Laptops SD reader requires drivers to work, ok in windows useless in linux without the driver, so gpart and hirens boot cd out the window there.
2. My kaiser has a 6.1 rom on it and as far as i can remember it doesnt have a work as a memory stick option that appears on later roms like my touch pro had.
3. the touch pro has a broken digitiser and wont register my finger, so i can get the dam thing into usb memory stick mode.
So skip ahead if you dont want the long story of how i got it to work and made it a little easier for other.
Ok first job created a virtual pc with blank 8gb virtual disk and created the file system 1 x fat32 and 2 x ext2 partitions using hirens bootcd. Next i cloned the disk to a ghost32 compressed image file, as its only the file table and no files its really small (36K). So i rar'ed it up and uploaded so other people can use it as well. (5K)
HOW TO DO IT
Download my blank ghost image from :
Then you need ghost32.exe this can be extracted or ran from hirens bootcd and found as part of a Trialware download at Symantecs site: https://www4.symantec.com/Vrt/offer?a_id=32763 (you will need to create a login to download)
From there just run ghost32.exe and have your sd card ready and connected to the machine, be it in reader or a phone set in memory card mode. Select Disk from Image and select the image file on your hard disk. Then select the SD card and adjust the volume sizes as your require, it will complain about locking the drive and took an age on mine (2 mins), but eventually it was done from there just follow your droid guides for installing.
I know this doesnt help the vast amount of people, but if your stuck like i was and could get access to the card under windows and nothing else it works a treat. If however you can access it under dos etc, you may also want to use this way as its much faster than having to burn an ISO and reboot your entire PC just for partition an SD Card.
Hope this helps someone out.
PASSWORD: Android
http://www.megaupload.com/?d=D64ZX4ZH - 5K
Nice solution, I can see this coming in handy for many who may be in a similar situation.
plazma247 said:
HOW TO DO IT
Download my blank ghost image from :
http://rapidshare.com/files/404732241/Android-SD-Image.rar - 5K
Click to expand...
Click to collapse
Since it's only 5k, do you mind posting it here? The link has reached limit, 10 downloads.
Re-mirrored and added to the main post, lol ur lucky it was deleted from the main machine, tho the laptop still had the ghost image
Nice, but can you make one for 4gb sd card
Thanks.
plazma247 said:
Re-mirrored and added to the main post, lol ur lucky it was deleted from the main machine, tho the laptop still had the ghost image
Click to expand...
Click to collapse
Thank you! I'll try it out ..
Dude it will suit any size memory stick you can adjust the partition sizes as it writes them
plazma247 said:
Dude it will suit any size memory stick you can adjust the partition sizes as it writes them
Click to expand...
Click to collapse
gotcha *thumbs up*
Brilliant solution! One of those "Why did nobody think of this before" things.
Hey all,
Wanted to post CM7 here for everyone to enjoy.
Neopeek has been working hard to get this build up and running, he's been doing great work!
Neopeek's Original Post - if you wish to see Neopeek's original post about the CM7 topic.
Also, since now I am using his new ClockWordMod method - CWM Recovery thread
As is stated in the title, this is mainly for devs/testers. Lots of things are broken, and there will be frequent updates.
There are two methods to using this build:
1) ClockWorkMod (requires 3 separate ext2 partitions)
2) Loop'd system.ext2 image (like XDAndroid) [In progress]
The benefit of #1 is a dedicated system/data partition, and *partial* USB mass storage support.
The benefit of #2 is, it's easier .
I still have to work to get #2 up, but I wanted to post #1 ASAP. Lots of work to flesh out the post to, be patient!
I've been holding off on releasing this CWM version of CM7, because I'm still having a lot of bugs with it. Still needs quite a bit of work, but it's getting late for me tonight - I am going to release it, let me know if you guys make improvements, I'd love to incorporate them!
Main issues seem to be related to my durn CDMA device. Need to break into some logs to see what's goin on, it may be a little while! I think GSM folk will be fine. Let me know!
Downloads
Download #1
How-to
Method #1 (ClockWorkMod)
****WARNING****
If you setup dedicated partitions using this method, normal XDAndroid builds will think that you want to use dedicated partitions. I had to modify the init to get it to work correctly (I basically broke the partition detection in the init). It's not pretty, but I don't know of a better way to resolve that issue - let me know what ideas you guys have!
Setup:
You will need to create three (3) ext2 partitions on your SD card. This is not extremely simple, but by no means impossible .
If you're using Windows, I like the Mini Partition Tool. If you're in Linux, I usually use gparted.
This takes a little bit of planning - but in total, I would say you need a minimum of 450mb of space for all three ext2 partitions. So work out how much free space is left (if you want a bigger data partiton, or system partition account for it!) and make that the first partition - FAT32. Make sure all the partitions are "primary", not "logical"! See the partition layout below:
1 - FAT32 Primary (remainder of card)
2 - ext2 Primary (at least 150mb, system partition)
3 - ext2 Primary (at least 250mb, data partition - I wouldn't go over 1gb here)
4 - ext2 Primary (at least 50mb, cache partition)
Don't worry about putting anything in these ext2 partitions, everything is populated by Android and CWM. The FAT32 partition is used to kick off Android, while system, data and cache are all ext2 partitions. Reason for this is, hopefully if things go haywire we can blast out cache, not data . Also, it should be easier to update using this method than previously.
Extract the file. Look at the folder it created (npkboot). Copy the entire npkboot folder to the root of your SD (for now this is required - the init assumes there's a /sdcard/npkboot/tmp folder). There will also be an update.zip, in this case update-cm-7.0.0-neopeek.zip. Put this at the root of your SD card (this makes finding it in the menu much easier!)
Copy the appropriate startup.txt from the STARTUPS folder.
Find haret.exe in th npkboot folder. Run it, and watch the boot process carefully! It will ask you to hold the vol down button to enter recovery, and you have 10 seconds to do so.
Assuming you manage to do this correctly (I had some trouble at first ) you should see an icon like a hat. Wait for the menu.
Buttons:
End key - back (back button seems to do this as well...)
Send key - enter
Vol up - up
Vol down - down (menu button seems to do this as well...)
If this is the first install, go to "install zip from sdcard". Then "choose zip from sdcard" This will install the system image to the system partition from the update.zip.
If you need to wipe the data partition, you can do that under "mounts and storage". You shouldn't need to do this unless you're going from gb -> froyo or visa-versa. Froyo -> froyo should 'just work', as always YMMV.
There are A LOT of options in replimenu. The only ones I have used are install, format /data, /system or /cache and Reboot. According to Neopeek, there are several things that should not be used:
Neopeek said:
* Don't use "factory wipe" in CWM (you have been warned )
* Don't use "format sdcard" unless you know what you do (you have been warned )
* Don't use "partition sdcard" unless you know what you do (you have been warned )
Click to expand...
Click to collapse
Once you've installed Android, go back to the main menu and "reboot system now" There are some bugs, for example "reboot recovery" and "power off" all just reboot the phone to WinMo.
Boot haret again, but this time don't hold the vol down to enter recovery - boot as normal!
#2: Much simpler method, similar to XDAndroid builds.
Extract the file to your desktop. Go into the CM7 folder, look for the STARTUPS folder - grab the appropriate startup.txt, move it to where haret.exe is.
Copy everything in the CM7 folder to the root of your SD card - if you want to run it from a folder, create a rel_path=CM7 statement in your startup.txt after the set cmdline (if you want a different folder, change the CM7.)
Grab the ts-calibration file attached to this post (for RHOD), or go to this post for a list of ts-calib's. You can also create your own on boot, but may have to revert to an older kernel to do so.
Run haret.exe!
****Not Working****
CDMA seems broken - still! I did some testing with hyc's RIL and it's still busted, so there's something in the system image messing with it - Airplane mode was checked, and I could not uncheck it.
In addition, phone.apk seems like a forceclosefest. Neopeek did point this out in his original thread...
Mobile data - broken (Fixed soon)
Wifi - broken (Fixed soon)
System needs optimization for RHOD - was originally build with DIAM in mind - so it's a little slow.
Failed wakes seem pretty bad - sometimes it is quite difficult to wake the phone.
Boot animation seems to be not present - I'm looking into fixing it, probably graphics libs if anything that's broke it.
Dev Content
This new method should be great for anyone who wants to make their own updates - you can easily peek into the system image and make changes at will, then just install the new system image! You can even rolll updates instead of an entire system image if you wish.
The script language in ClockWorkMod is called "Edify", see this thread to learn about the syntax. This is related to the META-INF folder you see in the update zip.
There's a few differences in the rootfs', the main being the init. There's also some additional files it looks like neopeek added for Recovery specifically.
This is amazing work. Props to all involved.
Does anyone have any feedback on this build?
arrrghhh said:
Long story short, you need a ext2 partition and a fat32 partition - ext2 needs to be between 400-600mb, fat32 can just take the remainder of the card's space.
Click to expand...
Click to collapse
Is there a reason for the 600mb upper limit? If I use 1 gb, will it cause problems or will it not use it and just waste card space?
PM message
Arrrgh,
Disregard the PM I sent you.
I read the instruction and like you said, its not simple. So I will wait until you upload the easy to run load.
Thanks
Ltilt2 said:
Arrrgh,
Disregard the PM I sent you.
I read the instruction and like you said, its not simple. So I will wait until you upload the easy to run load.
Thanks
Click to expand...
Click to collapse
Sorry, I need access to a Linux box to do the 'easy' build... I will when I get home tonight from work, promise .
vinceweis said:
Is there a reason for the 600mb upper limit? If I use 1 gb, will it cause problems or will it not use it and just waste card space?
Click to expand...
Click to collapse
You can make it as big as you want I guess... I'm not sure how neopeek sets up the data partition to be honest, I'd have to ask him.
Edit - in lieu of the post below, I adjusted the first post to say it needs to be at least 400mb .
vinceweis said:
Is there a reason for the 600mb upper limit? If I use 1 gb, will it cause problems or will it not use it and just waste card space?
Click to expand...
Click to collapse
I have 700 mb and is working well,you can use as much as you want
Ltilt2 said:
Arrrgh,
Disregard the PM I sent you.
I read the instruction and like you said, its not simple. So I will wait until you upload the easy to run load.
Thanks
Click to expand...
Click to collapse
Is easy just use mini tool partition wizard,delete the main partition on the sd-card
and do two,one fat32 primary and one ext2 primary,then extract the archive and put the proper startups in npkinstall and in root
from the phone run install.exe
and after the reboot use haret.exe
I wonder if CDMA data is working with this...that is my biggest issue with GB right now...
HELICOPTER88 said:
I have 700 mb and is working well,you can use as much as you want
Is easy just use mini tool partition wizard,delete the main partition on the sd-card
and do two,one fat32 primary and one ext2 primary,then extract the archive and put the proper startups in npkinstall and in root
from the phone run install.exe
and after the reboot use haret.exe
Click to expand...
Click to collapse
yeah easy for you to say, that sounds complicated.
I will wait for the other one.
Do you know the ETA?
i have
- downloaded the file cm7new.tar.gz
- made primary fat32 and ext2 partitions
- extracted the file cm7new.tar.gz to the root of the fat32 partition
- got a lot of linux folders
but i am missing
- npkinstall folder
- startup.txt
- install.exe
- haret.exe
- startup folder
Where are these files?
Tippfehler said:
i have
- downloaded the file cm7new.tar.gz
- made primary fat32 and ext2 partitions
- extracted the file cm7new.tar.gz to the root of the fat32 partition
- got a lot of linux folders
but i am missing
- npkinstall folder
- startup.txt
- install.exe
- haret.exe
- startup folder
Where are these files?
Click to expand...
Click to collapse
Still need to upload, sorry!
Tippfehler said:
i have
- downloaded the file cm7new.tar.gz
- made primary fat32 and ext2 partitions
- extracted the file cm7new.tar.gz to the root of the fat32 partition
- got a lot of linux folders
but i am missing
- npkinstall folder
- startup.txt
- install.exe
- haret.exe
- startup folder
Where are these files?
Click to expand...
Click to collapse
I was looking at that too when extracted the files and didn't see what you are also missing.
Sorry about the confusion guys, I probably shouldn't have put the download link up before I was done .
I just fixed it, so #1 is good to go! I'll get #2 up later, thanks.
Another noob question, but the rootfs, kernels, oc, etc from the xdandroid builds will work the same on these?
(...solved...)
it's necessary create a swap partition?
What works in this build?
fishingmedic said:
Another noob question, but the rootfs, kernels, oc, etc from the xdandroid builds will work the same on these?
Click to expand...
Click to collapse
The rootfs is more or less collapsed in these.
Kernels are straight from XDAndroid repo.
OC is the same, startup.txt is fairly similar .
Quincux said:
it's necessary create a swap partition?
What works in this build?
Click to expand...
Click to collapse
Swap is not necessary.
Most things that work in XDAndroid work in here. Lots of other things are broken here tho .
Okay, downloaded and installed without problems.
First impressions:
Absolutely great build in terms of response!
No delays in menus, etc.
Also, this looks like the first build that may have little or no clock delay, so no need for clocksync !!! (to be confirmed since I did not use it very long, die to issues below)
However...
1) No WIFI
2) No Mobile data (2G/3G)
3) camera not working (could be just blackstone)
- maybe other issues, decided to wait for more feedback before continuing, without market access there's little point...
Device: Blackstone
Kernel: extensive testing with provided one (1276), later switched to 1277, to fix audiostuttering, no wifi or mobile data in either...
As a reference, used many NeoPeek / XDAndroid builds, generally got WIFI/Mobile data working until now...
Love to hear if someone else (blackstone?) got WIFI/2G/3G working...
Oh, well, as I understood, this was an early "developer" release, still plenty of room for improvements!
Cheers,
Robbert