yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] drkow19:
Understandable. I still haven't tried that yet, but as soon as I get a data plan I'm sure I will. I have to use WinMo for Bluetooth, but that excuse will no longer be valid when your build gets closer to perfection. Right now BT will enable but cannot find my device.

EDIT:

Yes, there are those of us out here who still use HARET. You made us, now you can't turn your backs on us! lol any help is appreciated for both methods.
[Touch CDMA Android Development] mssmison:
We're not turning our backs on you guys, we're simply trying to evolve the project :)

As for bluetooth, have you tried the fix that was posted? I can find my bluetooth device with no issues, just sound isn't 100% yet.
[Touch CDMA Android Development] drkow19:
Hmm cannot find anything about it... What thread was it in?
[Touch CDMA Android Development] stanelie:
No go for me with Haret.

I've been using haret with my files in /sdcard/android on a FAT32 partitioned SDcard for a few months now without problem, this setup does not work at all for me. "failed to reach system.img on sd card"...

Any ideas?
[Touch CDMA Android Development] celticchrys:
video of norootfs install utility working on Vogue with haret

Maybe this will help some haret ppl a little. I still have issues with the builds, as the tattoo freezes at calibration, and the elcair is just too slow, but the install utility works for me using haret to install to SD card.

I just downloaded the base files from post 1, expanded them and copied them into a folder named andboot on my SD card, as instructed in the first post.

Next, put the androidinstall.tar from the build of your choice in the andboot folder as well(I did this different times with both the eclair and tattoo builds, being sure to delete all android files from SD card between each time).

Here's the video of the install utility running:

http://www.youtube.com/watch?v=Ah-ve2Y_F6g

Video #2

http://www.youtube.com/watch?v=1pSsRyxCXDs

Looking forward to more builds and easier updates in the future!
[Touch CDMA Android Development] loserskater:
Just letting all the kaiser people know that I've got a working nbh that gets into the menu. I'm testing it now and will post it in the kaiser forums soon.

EDIT: done, and uploaded. check the kaiser threads! (or my 4shared)
[Touch CDMA Android Development] myn:
Big Bug

Here is what I did.

Configuration: "Sys on SDCard" and "Data on SDCard"

Choose: Install new system

formating..

mke2fs: cannot determine if /dev/block/mcblk0p2 is mounted

mke2fs: cannot determine if /dev/block/mcblk0p3 is mounted

installing...

fixing data.

/data ... no such file exists.....

....

..

.

Then I hit 9 (quit)

9) Quit.

Boots up just fine.

Exit out back into Winmo.

I check out the sdcard looking for a data.img or maybe a system file and can't find anything there.

I do have 2 ext2 partitions setup but I didn't choose that method in the configuration. I have a strong feeling it stored it here.

contents of my bootlog.txt:

sh: 1: unknown operand
Using partitioned system
e2fsck 1.38 (30-Jun-2005)
/dev/block/mmcblk0p2 is mounted. e2fsck: cannot continue, aborting
e2fsck 1.38 (30-Jun-2005)
e2fsck: while determining whether /dev/block/mmcblk0p3 is mounted
/dev/block/mmcblk0p3: clean, 11/66528 files, 8420/265072 blocks
[Touch CDMA Android Development] tatnai:
works great, running on my vogue with ext2 x 2 and haret, mssmison 2.1; just followed instructions. have been able to update, etc - works just fine.
[Touch CDMA Android Development] myn:
For the EXT2 install it says (system.img) and (data.img).

I just choose those two options thinking it would pick up the androidinstaller.tar and load that up into ext2. It began to "format" and then it failed with a bunch of threading errors. It never did boot. Unlike my previous attempt where I picked SDCard (sys and data) and it seemed to install to ext2 anyways..

In any case for the ext2 install is it required that a system.img and data.img be present in the andboot directory?

My bootlog.txt

sh: 1: unknown operand
Using partitioned system
e2fsck 1.38 (30-Jun-2005)
/dev/block/mmcblk0p2 is mounted. e2fsck: cannot continue, aborting
e2fsck 1.38 (30-Jun-2005)
e2fsck: while determining whether /dev/block/mmcblk0p3 is mounted
/dev/block/mmcblk0p3 was not cleanly unmounted, check forced.
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
Block bitmap differences: +(68728--68730)
Fix? yes

Free blocks count wrong for group #8 (7516, counted=7513).
Fix? yes

Free blocks count wrong (225565, counted=225562).
Fix? yes

Inode bitmap differences: +16214
Fix? yes

Free inodes count wrong for group #8 (1932, counted=1931).
Fix? yes

Free inodes count wrong (66082, counted=66081).
Fix? yes

/dev/block/mmcblk0p3: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p3: 447/66528 files (6.7% non-contiguous), 39510/265072 blocks
[Touch CDMA Android Development] mrkite38:
Check Shidell's Eclair thread, a few pages from the end.

Edit: and, to be actually helpful:

http://xdaforums.com/showpost.php?p=5459458&postcount=201
[Touch CDMA Android Development] CyCLoBoT:
When I ran the installer the first time, I selected the option to store system and data on ex2 partition. Yet those two files have been created in FAT32 partition. How did you get yours to work?
[Touch CDMA Android Development] mssmison:
This has worked for me and several others in testing. Make sure you have the base files which included having the mke2fs file in your andboot folder.
[Touch CDMA Android Development] myn:
http://sourceforge.net/projects/androidhtc/files/TheNewWay/basefiles.zip/download which is linked from first post doesn't contain mke2fs in root or andboot folder.

Where can I get the updated basefiles that include mke2fs.

Thanks

01/30/2010 11:49 PM <DIR> .
01/30/2010 11:49 PM <DIR> ..
01/30/2010 11:45 PM 1,134 default-kaiser.txt
01/30/2010 11:45 PM 1,083 default-polaris.txt
01/30/2010 11:50 PM 1,651 default.txt
01/28/2010 11:23 PM 137,216 haret.exe
01/28/2010 11:28 PM 1,484,741 initrd.gz
01/28/2010 11:26 PM 320 README-BASEFILES.txt
01/28/2010 11:28 PM 1,452,220 zImage
8 File(s) 85,940,445 bytes
2 Dir(s) 12,701,073,408 bytes free
[Touch CDMA Android Development] tatnai:
I am choosing ext2 for my install as well and thought it was going there, but yeah I've just noticed now that I have a /andboot/data.img and /andboot/system.img, in addition to the backup files I have there. will delete them and see if it still boots. also, maybe if we check for things to go on sdcard they will go to ext2 instead? will investigate.

EDIT1: renamed /andboot/system.img and /andboot/data.img. android refused to boot. apparently it was using these, even though I used ext2 for my defaults before intalling androidinstall.tar eclair2.1. then, i changed my defaults to sdcard (no ext 2). ran the installer. now, after running installer with regular sdcard selected and booting into eclair, check /andboot and there is no system.img, and no data.img. I think these two option sets got reversed . . .
[Touch CDMA Android Development] garringm:
Its amazing to look at how many people are still using haret to boot, it has been the goal from the beginning to rid these phones of those horrible winmo systems. I have been running from nand for a week or so now and love it TATTOO is much faster running it how I have to run it on my tilt. And with this new bootloader it runs as fast as ION. I personally can't wait till someone gets more working on it so I can use it daily. Thanks to all the devs who have worked so hard on this keep it up
[Touch CDMA Android Development] CyCLoBoT:
...then, i changed my defaults to sdcard (no ext 2). ran the installer. now, after running installer with regular sdcard selected and booting into eclair, check /andboot and there is no system.img, and no data.img. I think these two option sets got reversed . . .[/QUOTE]

I did a clean install through sdcard again and after selecting the sdcard option for both files, it did store them in Ext2 partitions.
[Touch CDMA Android Development] stanelie:
Windows Mobile is still necessary if you want to mess with the phone's radio internals with ##778 (PST), ##3424 to expose the serial interface to the radio, changing voice codec, changing ESN and so on. Those features are not yet available under Android, hence the need to dual boot and still use Haret.

These are my reasons anyway... until I can access those features from within Android...
[Touch CDMA Android Development] jamezelle:
why do you even need to mess with those? if your phone works, gps works, and data works, you really dont need to access that stuff. :o
[Touch CDMA Android Development] stanelie:
I need to mess with those because my Telus phone is a Touch Pro, and the Android port for it is not yet usable. So, when I want to mess with Android, I switch to a Vogue that I got off of ebay for cheap. Since I can't just pop in a sim card to make it work, I had to clone my Touch Pro to the Vogue to have it work as my phone on Telus.

Hence my need for Haret/windows Mobile...
[Touch CDMA Android Development] jamezelle:
ahhh got it;)
[Touch CDMA Android Development] ritzky:
i'm using nike, put all the files in the andboot folder, but when i press vol up when booting via haret, i cant find the installer menu. tried vol down, dpad button, but the menu just wont come up. any thoughts? thx
[Touch CDMA Android Development] Reddog80p:
When applying new updates do older installupdate.tar files need to remain in the andboot folder or can they be removed?

EDIT: Blonde moment...they would rewrite the old update as they are named the same LOL my bad! :D
[Touch CDMA Android Development] moisha:
No need to - it's the busybox.
[Touch CDMA Android Development] GriloVirante:
Yes, I guess that this is a further confirmation that vol up/down is not "read" for both Cruise and Kaiser. Looks like the "basis" for these users is broad (I read the whole thread and found 4 or five "me too" already). So, it would be simply great if Jessee would have a look into it or even woudl suggest a fix. I'm not sure if I am representative of all teh other Polaris/Kaiser owners, but I cannot wait one more second to see your (I hear) wanderful Eclaire running on my little toy! :-D

Thanks a bunch plus VAT :-D

Alex
[Touch CDMA Android Development] b.mann:
.nbh file

I'm still a bit confused with the nbh files. is that something that I need to flash from my PC like normal or does it go into the /andboot folder and do its thing there?
[Touch CDMA Android Development] SuperJMN:
Man, you could set yourself as a representative of the Polaris/Kaiser owners whenever you want. At least in my case, I'm not installing any Android build until it is working on my device (keys are uncaught).

@vilord, we need you on the floor.
[Touch CDMA Android Development] jamezelle:
you flash it like a normal rom, keep in mind you will lose winmo....but you can get it back again by flashing any winmo rom
[Touch CDMA Android Development] mblaster:
I am also on a nike.

Seems like the buttons are not recognized correctly. I tried patching the initrd to always boot into the installer by removing the if clause that checks if the volume up key is pressed (@loserskater: it worked like you proposed).

The installer starts, but you cant control anything, as the buttons still don't work. After 2 minutes the installer will crash. If I find some time I will try to find a workaround/solution for this.

mblaster
[Touch CDMA Android Development] GriloVirante:
Sound great. I've tagged this thread, so if you need some help to test, just warn me over it and I'll receive your email. Consider I'll be mostly available after 18:00 CET (East coast American noon, so to understand!).
[Touch CDMA Android Development] GriloVirante:
Hi Hi! That is lovely permission of you, but I don't feel as I'm qualified to represent anybody: representing is a serious thing!! :)

On the other side I'm intrigued by your statement: "I'm not installing any Android build until it is working on device!"... How could you know if it is working on device if you don't install it on the device? :confused:

OK, looks like a silly question, but it is not so silly.. what I mean is: I come from the assumption that the Eclair build will be bootable through HARET or in any case installable beside the existing build. 'cause if this is not the case, then I also woudl have an issue to flash my workign mobile (!) for a test!!
[Touch CDMA Android Development] SuperJMN:
Hi GriloVirante :) Sorry, because I was writing just woken up, and my neurones have a cold start!

I mean that I will not try to install any other build on my device until the new one is ready to recognize the different keymap that Polaris has.

I decide to stay some weeks with WM due to the fact that every night I sleep listening to my favorite podcasts, and the sleep issue makes the battery drain to around 0% in the morning, so it's slowly degrading its capacity :(

I heard the suspend/audio issue is fixed, but unfortunately, it is on the new kernel/systems that don't work with Polaris yet.

It's nice to have you enthusiasm amongst us :D

Best regards from Spain!
[Touch CDMA Android Development] garringm:
Grilo here is a shortcut to the nbh files you need if you are running a kaiser, you may have already seen them though http://xdaforums.com/showpost.php?p=5500958&postcount=66

I am able to use this on a kaiser and install it just fine loserskater was able to come up with working nbh files for the kaiser by using the volume down button only problem now is with data connection and wifi or the lack of on both. data is able to see an available network and at what type of connection but its just not able to connect to it. Would someone over here be able to help out.
[Touch CDMA Android Development] stickus:
I've been attempting to port plemen's HeroBlend build to use this method, but seem to be running into an issue. I can't get the radio to initialize. The system boots and I can get to the home screen, but i haven't had any luck turning the radio on. No data, no voice. Anyone know what I could be doing wrong? I suppose knowing what I should be changing in sysinit.rc could help :) I've been using the sysinit.rc from mssmison's eclair build as a guide.
[Touch CDMA Android Development] GriloVirante:
Mh! Interesting. So apparently someone using a Kaiser WAS indeed able to get to the installation menu by using the volume down key. This is definitely not the case for Polaris (and I own a Polaris, unfortunately.. well, I'm perfectly happy with it, but I have got the issue of the volume down not being received/read).

So, apparently all Polaris owners get to the message: "Failed to reach system.img", as they're not able to interrupt the bootstrap by HARET by pressing volume up/down, so to get to the install menu. Boooo! :mad: I want to see that menue on my Polaris screen (so far I only saw it in youtube :D).

There is no way out apparently: we need a "saint" to make the volume up/down in Polaris read or to re-map to some other key...

In fact, doing the last attempt a few minutes ago, I noticed that the volume up/down does not have any effect on the screen (simply not read). On the other side, when I press on the "wheel" up, I see a "^[[A" (the stuff within the quotes), and when I press on the "wheel" down, I see a "^[[A". I've checked all keys, and:

- volume up/down is NOT read

- quicktalk (what becomes flip screen in Donut) is NOT read

- on/off is read

- camera is read

- up, down, left, right is read

- turn the wheel in both directions is read

- I did not check the initiate/terminate call.. sorry

So MAYBE a solution would be to map the menue launch option to some other key, if available.. is that a solution??
[Touch CDMA Android Development] mblaster:
CrudeWorkaround for all that are not able to use the installer

WARNING: This may blow your device up and eat your SD Card!

I mad some small changes to the initrd.gz, that basically circumvent any interaction with the menu, thus loosing almost all of its functionality... but it can install a system on an nike and perhaps on any other system!

Some changes were all made to the init script:

Added to init @ #set defaults: RM_wipedataforsys="yes"

Changed:

if [ `cat /sys/class/vogue_hw/keys` = "2" ] ; then
if [ ! -f $card/androidinstall.tar ] ; then
export RM_HIDE_install=1
export RM_HIDE_fixapps=1
fi
if [ ! -f $card/androidupdate.tar ] ; then
export RM_HIDE_update=1
fi
/bin/replimenu -f /bin/instscripts/start.menu
fi

to:

if [ -f $card/install ] ; then
/bin/instscripts/installsys
fi

Just use my patched initrd.gz instead of the one with the menu. To install follow the instructions on the first post BUT create an empty file in the /andboot directory named 'install'.

Now use Haret (NAND not tried as there are no .nbh files for nike) to boot. It will automatically install the system and DESTROY YOUR OLD DATA.

The file should in principle work with nand(?)/ext2/system.img, but I only tried ext2.

For normal boot of the system don't forget to delete the 'install' file, otherwise it will reinstall on the next boot.

Btw: Thanks to all that are developing android for our good old htc devices. It is really nice to have a choice between different operating systems!

€: Vilords tattoo doesn't seem to work out well with this. I get ANDROID [SomeNumber] init: Unable to open persistent property directory /data/property errno:2

Eclaire is working, but without data

€€: Tatto installs, I just had a bad file. Stops at cllibration though...
[Touch CDMA Android Development] b.mann:
Ah ok. Currently that's a nogo since my phone is still not completely programmed for PagePlus and I need to program it for data.

Thanks
[Touch CDMA Android Development] JeckyllHavok:
Loserskater used the old installer method for making the new one work
[Touch CDMA Android Development] plemen:
Heroblend is ported and available.

Vilord - would comrpessed tarballs work with this boot? tgz?
[Touch CDMA Android Development] SuperJMN:
On Polaris, I've tried your method. It seemed to work:

- it stated: Installing Android...

- Android installed.

- Later, the screen has turned black and nothing happened.

Eclair 2.1.
[Touch CDMA Android Development] vilord:
okay... sorry i've been away for the weekend :)

1. I need to update the menu to be more descriptive. ext2 on system.img uses a file in /sdcard/andboot, system on SDCard means system on SDCard Partition, same for data.

2. mke2fs is built into busybox now, so you don't need to put it anywhere or get it from anywhere

3. e2fsck isn't working on the system partition because I have things out of order in the init, need to fix

4. the installer doesn't work on anything besides vogue. Sorry guys I didn't realize that key capturing was only performed on the vogue :(

I'll look at a) adding key capturing to kaiser, polaris, and nike in the kernel or b) using a different keylistener

What else?

SuperJMN: eclair might just be booting up, it shows a black screen for about 5 minutes during boot on my device too
[Touch CDMA Android Development] spreeguy:
Kernal Panic !!!

I've never had problems with Haret, even with the new install method (except Vilord's Tattoo build freezes at calibration for me). So I figured I'd give booting from Nand a shot. Unfortunately, I've had no luck getting it to work.

I don't think I'm doing anything wrong. It seems pretty straight forward.

Flash the phone with the nbh file

Create an andboot folder in sdroot

Drop androidinstall.tar into andboot (and basefiles? I've tried with and without)

Boot with VolUp

Install to Nand, then quit.

Unless I'm missing something obvious. I keep getting Kernal Panics. To me they appear to show up completely randomly during install or booting.

When I get lucky and somehow avoid a kernal panic during install, Android will boot up, but freeze shortly thereafter. And of course on reboot I'll get kernal panics.

Edit: Also, I've noticed during install (and maybe other times) I'll see the something about Blocks 291, 443 and 907 is Bad. If it helps I can try and take a picture during install.
[Touch CDMA Android Development] JacenSolo2001:
Yea, the new install is working, but those of us on Kaisers, can do the install but don't have data or wifi. Otherwise it looks great !!
[Touch CDMA Android Development] SuperJMN:
OK, I'm now starting it again to see what happens and now the screen is black. The last line that I remember before the black out was "Setting volume blah blah from 255 to 5", or something like that.

I will post the results soon with an edit to this post.
[Touch CDMA Android Development] mblaster:
Nice to hear that somebody is testing my workaround.

Sound promising. What resolution are you using? On my nike I had the long lasting black screen for 240*320, but for 320*480 i had the xrom android logo.
[Touch CDMA Android Development] Taluven:
Question:

Are these .nbh files compatible with the AT&T Tilt? I have tried to use them and I get incompatible every time I try to flash the file, have tried the custom ruu.exe and also flasing from the sdcard, and neither will work.

Either I am doing something wrong or they won't flash to this device, anyone know?
[Touch CDMA Android Development] SuperJMN:
Eclar 2.1. Using 240x320.

It's installed, and it boots, but it needs way more than 5 minutes to start! (after an interminable black screen).

After the dark, it showed a pop-up with a "the process System is not responding". I chose "wait", and I waited loooong for the interface to appear. It did, as lazily as before, and showed a menu to choose between the Configuration wizard, or some other task that I didn't remember.

I tried to configure it, but noticed that THE TOUCH SCREEN DOESN'T RECEIVE TAPS! I can only use the hard-keys, and the system requires me to touch the Android to start the wizard.

So, no luck :S

Edit: I have tried this build and it happens the same-> touch screen not working.

Edit 2: With the new zImage by @DZO it's still not detecting any touch.
[Touch CDMA Android Development] loserskater:
ALL KAISER/POLARIS/EVERYTHING BUT VOGUE USERS

HERE is the init file i modified. All I did was take the old method used in the rootfs, and applied it to the new method. The only thing I changed was this:

mkdir -m 0755 /system
mkdir -m 0755 /data
chown 1000:1000 /data
mkdir -m 0755 /tmp

[COLOR="Red"]read -s -n3 -p "Press VolDn to launch the installer" -t 5 keypress
if [ $? -eq 0 -a "$keypress" = "[2" ] ; then[/COLOR]
if [ ! -f $card/androidinstall.tar ] ; then
export RM_HIDE_install=1
export RM_HIDE_fixapps=1
fi
if [ ! -f $card/androidupdate.tar ] ; then
export RM_HIDE_update=1
fi
/bin/replimenu -f /bin/instscripts/start.menu
fi

So if the old way worked for you, than you can try applying this init to your initrd.gz and it should work.
[Touch CDMA Android Development] loserskater:
Double post...
[Touch CDMA Android Development] vilord:
wait, so are you telling me that the arrow keys and everything else work fine within the setup tool, it is just volume up that fails?

Well that'd be an easy fix... just map it to a different key :D
[Touch CDMA Android Development] loserskater:
Ya, they all work fine... I'm not too worried about that anymore as much as getting a data connection to work...
[Touch CDMA Android Development] timmey:
yes, thats right. all the other keys work perfectly. i played around with the installer for quite some time now (i simply removed the keycheck, so the menu pops up everytime i boot) and here is what i found out so far on my polaris:

- installer menu works

- tattoo and eclair install works

- tattoo boots to the calibration screen, but the touchscreen doesn´t work

- eclair boots to a black screen and freezes

i tried tattoo with an older kernel i found somewhere in the forum and the touchscreen works with it, but wifi doesn´t and the camera only takes greenish images.
[Touch CDMA Android Development] Spalla:
I installed this through haret a while ago, and it was working pretty good. Then after I installed a few programs and turned it off, the system wouldn't load the next time I booted up. Some "couldn't write files" error or something like that. Any help here as to what I did wrong?