yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] Bladergroen:
Hi,

To begin, I am new to this forum, so hello to you all. I registered because I am having a lot of trouble getting my HTC Polaris changed to Android. I hate the WM6.1 system on it, so this looked like a quick and easy way to have fun with my smart-phone again. Besides that I like to play around and see how much everything can be tweaked :). Slowly I'm getting interested in learning some coding language as well :cool:

Anyway, I am more of an end-user and not very handy with coding, tweaking terms and all, but I've looked around a bit and now getting some knowledge of things. I downloaded Atools 1.06 and followed all instructions on the site: sourceforge.net/apps/trac/androidhtc/wiki/HowToInstallWithAtoolsHaret.

I have python 2.7.1 installed on my Mac Leopard as well. But I get the following error when I try to open the chosen androidinstall.tar in the Mixer function:

Exception in Tkinter callback

Traceback (most recent call last):

File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-tk/Tkinter.py", line 1410, in __call__

return self.func(*args)

File "atools-1.0.6.py", line 2296, in addnew

filename = filedialog.askopenfilename(**self.file_opt)

File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-tk/tkFileDialog.py", line 125, in askopenfilename

return Open(**options).show()

File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-tk/tkCommonDialog.py", line 48, in show

s = w.tk.call(self.command, *w._options(self.options))

TclError: bad initialfile "" file does not exist.

So please help! I'm trying to get it right for 2 days now :(.

Many thanks,

Reno
[Touch CDMA Android Development] dertester123:
This could be a problem with python 2.7, try 2.6. As far as i know this was recommended in the atools thread as well.

Otherwise if nbh and bootscriptgenerator works, you dont need the mixer atm. Just take the update from liquids thread:

Here: http://xdaforums.com/showthread.php?t=848921

I think the files Mixer would add are in this update as well and you need this for working wifi!

/OT

As starter i would try this:

1)Atools NBHCreator:

Kernel 6.25: set your device, resolution and panel type, OC to~500mhz

2)Bootscriptgenerator:

Klick for first install and then add the tick for install update(the update is the file from liquids thread)

3)Now put on your sdcard:

/polaimg.nbh (from nbhcreator)

/andboot/androidinstall.tar (the one you prefer)

/andboot/androidupdate.tar (from thread above)

/andoot/install-seq.sh (from bootscripgenerator)

As builds i would recommend:

Fat Free

or

My Favorite NotSoSuper RLS18
[Touch CDMA Android Development] l1q1d:
Atools update to 1.1.1:

- fix bugs of 1.1.0
[Touch CDMA Android Development] l1q1d:
do this little test, if you install on nand left auto on both for the kernel git and edit other parameters.
[Touch CDMA Android Development] wondercow:
Sorry, no luck. I opened atools 1.1.1, clicked the button to download from web. It filled in Vogue, 240x320, Froyo, system nand p2, data nand p3 automatically. I changed nand p2 and nand p3 back to auto for both. Then I clicked the "include more settings" box and ticked "alter lcd density". Saved, flashed the kernel, and got

sh: 0: unknown operatnd
AutoMode for system
mount: mounting /dev/block/mtdblock2 on /system failed: no such device or address
AutoMode for data
mount: mounting /dev/block/mtdblock3 on /data failed: no such device or address

Is this the test you meant me to do?
[Touch CDMA Android Development] l1q1d:
Could you please post your latest nbh?

I need to check is there is some problems with other platforms.
[Touch CDMA Android Development] wondercow:
Non-working VOGUIMG.NBH attached. This is the one where I enabled "change lcd density", although I really didn't need that feature.
[Touch CDMA Android Development] l1q1d:
i just release atools 1.1.2 probably now the nand problem is fixed.

Try it and let me know.
[Touch CDMA Android Development] wondercow:
Hmm, no go with 1.1.2 either. I first hit the download from web button, left everything alone (sys on nand p2, data on nand p3), and hit save to write VOGUIMG.NBH. Flashed, and got the same "mounting /dev/block/mtdblock2 on system failed: No such device or address" etc message. The second time, I switched the fstab to use Auto mode, but got the same problem. The third time, I tried including other settings and ticked prevent data on boot just in case it needed more settings like you suggested before. Same outcome, though.

Thanks for working on this! Don't lose too much sleep over it though--most of the time I am happy with the stock .NBH available on the git and don't really need atools for my Vogue.
[Touch CDMA Android Development] casacristo:
Ok, I did that (with kernel .32 though ) the install-seq.sh script kicked in and quite inmediately said it

Using boot install script

starting script

mount: mounting /dev/block/mtdblock2 on /system failed: No such device or address

(so still no good)

I then tried with the .25 kernel from atools 1.1.2 and same result...

NEWS:

I tried atools 1.1.2 with clemsys kaiser kernel

Modified the panel type, the keyboard type and the fstab point for DATA (as it was installing to NAND instead of the desired SDCARD partition) and works fine, so I think atools is more or less fine but the current git kernels are a mess

I would like to request that atools officially support ´stable´ 2.6.32 kernels such as clemsys (the one I have posted the URL above)
[Touch CDMA Android Development] l1q1d:
Did you download the file using the download button?

I'll not link clemsys's until he did not submit the file on sourceforge (i can't point the download link to xda attachment)

and i'll not link to the dzo file because only one developer (dzo) can submit on it.

Both clemsy and dzo has access to git.

Request to them to add it on the project server.
[Touch CDMA Android Development] casacristo:
Yes, I tried the download button both for the .32 and .25 kernels the result is the same (see my previous posting)

I will ask clemsy to upload his kernel to sourceforge...
[Touch CDMA Android Development] l1q1d:
Do you have the same result downloading the file without the download button?
[Touch CDMA Android Development] casacristo:
If you mean VOGUIMG-320-FROYO-11-29-10.NBH then yes, same result.
[Touch CDMA Android Development] l1q1d:
I just update the git with latest kernel update.

I also release atools 1.1.3 and i test latest kernel with atools in my kaiser and it works (i set all in auto and no other options)
[Touch CDMA Android Development] casacristo:
Could you (or somebody else) try to set panel type 1?

Since your kaiser is not type 1, it should look bad, but I bet it will look normal...
[Touch CDMA Android Development] casacristo:
3 tests

Ok, I went ahead and tried atools 1.1.3

I did 3 tests:

1st test:

1) Download the .32 .nbh

2) Set Device to kaiser, res=240x320, version=Froyo, Panel Type 1 (it really is a type 1)

and keymap to QWERTZ

on Fstab:

Left System on Nandp2

and set Data to sd partition p3 (which exists and is just fine)

Saved the KAISIMG.NBH

Then downloaded the androidupdate.tgz (from within atools)

Finally set the boot script to install system and update,format system and data, delete dalvik cache

The result:

It worked (it installed and the panel type was correct)

2nd test:

Exactly as above except in adition to the default options I ticked:

- Include more settings

- Prevent data connections on startup

- Alter CPU overclocking (set to 450)

The result:

It worked (it installed and the panel type was correct) BUT now it does no longer connect to my WPA/WPA2 network.

It goes as far as ´obtaining an IP from my_wpa2_wifi´ and then after a few seconds shows ´disconnected´ (and yes I did apply the update

with the latest modules)

Needless to say with clemsys kernel the wifi works fine

3rd test:

As the second but also ticked battery capacity simple settings set it to 1600

The result:

It could not find mtdblock2 (same error as I posted in the previous page)

My conclusion: There seems to be a bug in atools when setting the battery capacity... and a wifi module bug ...
[Touch CDMA Android Development] l1q1d:
i will check the battery capacity problem but

for wifi could you submit a log? There is no reason for a this bug on wifi.

In the first try wifi works?

Edit:

a made a simple change on battery, i release 1.1.4 with this fix.

I tested sys:nand,data:nand,prevent data,cpu:450 and wifi works as usual.
[Touch CDMA Android Development] casacristo:
Thanks for your prompt action.

So you mean you fixed a bug you found in 1.1.3, released 1.1.4 with this bug fix, tried those settings and wifi was able to connect to a WPA protected network?

If you can confirm then I will try myself tonight...

For the record, after I noticed the wifi bug yesterday, I flashed clemsys .nbh and the problem persisted, then I reinstalled System (without the androidupdate tar ball that comes with current kernels) and then is when it worked fine.

Is your wifi WPA TKIP or AES?
[Touch CDMA Android Development] casacristo:
with atools 1.1.4 downloading kernel 2.6.32

I tried at work with PEAP and mschapV2 (which worked fine last time I tried with an older rom) and it fails at the obtaining ip address stage

Then I tried an open network (both are known to work fine with my colleagues motorola droid) and same thing After ´Obtaining IP address´ I see a quick ´disconnected´ and back to ´Obtaining IP address´
[Touch CDMA Android Development] casacristo:
adb logcat

Here is the adb logcat with with wifi failing on ´obtaining address´

Seems to be a problem with the dhcpd daemon?

http://pastebin.com/R63PzQSE
[Touch CDMA Android Development] l1q1d:
maybe you forget to fix permission...

so it's not a problem with atools or kernel...
[Touch CDMA Android Development] casacristo:
You were right, fixing permissions fixed the issue.

Can I request for atools 2.1.5 that in the boot script creation screen when you tick ´install update´ it automatically ticks ´fix permissions´
[Touch CDMA Android Development] l1q1d:
Apply update in

simple action

select it automatically

in advance mode it doesn't select it (because it is

advance

mode).

i will not change that.
[Touch CDMA Android Development] casacristo:
No problem, will pay more attention next time.

Thanks a lot for your work and your help!
[Touch CDMA Android Development] En1gma:
if version "donut" is chosen haret-script will not be saved

because when you press "save"-button, nothing happens
[Touch CDMA Android Development] l1q1d:
i'll check, thank you
[Touch CDMA Android Development] Josue_181:
As I do a backup of all the system inclusive /system/app with attools?
[Touch CDMA Android Development] arvinchugh:
Atool for windows

Is there any place i can find this tool for windows 7? i tried searching around bt i cudnt find it.. i dont have phython linux in my laptop..

any help would be appreciated thanks
[Touch CDMA Android Development] l1q1d:
@Josue_181: yes

@ arvinchugh: install python on windows and run the script (is cross platform)
[Touch CDMA Android Development] Josue_181:
@l1q1d: But how do the backup this is what I am asking...
[Touch CDMA Android Development] l1q1d:
Atools->BSE:

Select partitions for system (C) and data (D)

Select backup phone (R)

Save the install-seq.sh (A)

put the file in your SDCARD /andboot

power on the phone

wait

wait

wait

wait

wait

wait

when it finishes android starts as usual.

You have a new tgz file in your andboot dir (the backup).

If you want to install the backup:

rename the file to androidinstall.tgz

Atools->BSE:

Select partitions for system (C) and data (D)

Select first install (J)

Save the install-seq.sh (A)

put the file in your SDCARD /andboot

power on the phone

wait

wait

wait

wait

wait

wait

when it finishes android starts with the backuped system
[Touch CDMA Android Development] l1q1d:
you can also backup only the /system using tar system (R)
[Touch CDMA Android Development] Josue_181:
And as I install the file resulting system.tar in another ROM that is not that I am using currently?
[Touch CDMA Android Development] l1q1d:
the system.tar is a "ROM" so you mix files from different "ROM". It's your choice.
[Touch CDMA Android Development] Josue_181:
And as add a file explorer to the ROM that I want to install, I would like to add it manually but not is how to do it, try with 7zip but I could not do it, I want to upgrade fresh froyo but I need a file Explorer to restore my things with titanium backup.
[Touch CDMA Android Development] chourmovs:
when i use atool 1.1.4, select polaris, and download last 2.6.32 liquid kernel

it save under VOGUEIMG.NBH

and when i flash it i get this

i didn't have such an issue with 1.0.x version

think that's a bug
[Touch CDMA Android Development] chourmovs:
ok sorry

i saw my mistake and your little code improvement possibility ;)
[Touch CDMA Android Development] mrkite38:
I think this issue persists. I was able to use the stock nbh from git, but running it through atools caused it not to work.
[Touch CDMA Android Development] l1q1d:
Which version did you use?
[Touch CDMA Android Development] mrkite38:
1.1.7
[Touch CDMA Android Development] NFHimself:
This isn't working for me either on the HTC Vogue.
[Touch CDMA Android Development] cycloid:
Seconded, I came here to post this exact request.

Would like ability to set the WHEEL_PRESS too.

Also the top-left OK button doesn't respect the setting of the front OK button, it does something completely different!

Brilliant, handy tool though, very good work!
[Touch CDMA Android Development] PeterDLai:
Same issue for me. I wanted to try clemsyn's Kaiser kernel on my Vogue but could not get past the "mounting /dev/block/mtdblock2 on system failed: No such device or address" error.
[Touch CDMA Android Development] l1q1d:
try with this

http://androidhtc.git.sourceforge.n...e;hb=6fdeb5da8e54021aa9893e442ea5b0ea01bd42cf
[Touch CDMA Android Development] NFHimself:
That works, thanks for the update. :)
[Touch CDMA Android Development] grktaurus83:
I'm on a Vogue, using version 1.2.0, and I'm getting the

Can't open '/dev/mtd/mtd2 : No such device

Failed

Failed to format

error...

Any idea how to get around that?
[Touch CDMA Android Development] l1q1d:
Which kernel did you use? Which options?
[Touch CDMA Android Development] X46X:
2 l1q1d: Hi, I have a question: Latest .25 kernel don't need your patch/update? If I try download it through atools 1.2.0 I have "pop-up": "Latest verzion don't need anymore."
[Touch CDMA Android Development] l1q1d:
The first update contains modules for 2.6.32 and 2.6.25 because latest kernel (both) have a new initrd with autoswitch between them.

The other update works only with old kernels.

If you don't apply the update and the modules are missing android stop booting and give you a error.

So you need it only if the releaser had not insert the modules already in the rom.
[Touch CDMA Android Development] X46X:
Ok thanks. I have a one question. Can I unpack this Update/Patch and put everything to androidinstal and overwrite it? Or I must do a propertly update in boot menu?
[Touch CDMA Android Development] l1q1d:
i ate lazy people! Read the help in atools before asking!

I lost my time for it!!
[Touch CDMA Android Development] chourmovs:
solid patience :p
[Touch CDMA Android Development] grktaurus83:
I was using the latest kernel that was posted on dzo's site.

Kernel Options:

set cmdline "ppp.nostart=0 mddi.width=240 mddi.height=320 msm_sdcc.msmsdcc_fmax=32000000 pm.sleep_mode=0 no_console_suspend hw3d.version=1"

Settings in A-Tools:

Vogue

Froyo build

Native resolution (240x320)

Overclock to 480MHz

Overclocked GPU

Standard key map

I tried creating a zimage from A-Tools too, but that didn't change my result.

I was trying to boot into Scoot's Cyanogen Mod 6.1.2 RLS6.

Thanks for your time, man.
[Touch CDMA Android Development] l1q1d:
Are you using haret?
[Touch CDMA Android Development] grktaurus83:
I'm on NAND.
[Touch CDMA Android Development] l1q1d:
Disable overclok and retry.
[Touch CDMA Android Development] grktaurus83:
A little clarification since I was a bit confused before.

I listed the kernel parameters just for ****s and giggles in case that mattered (which it shouldn't for NAND). I forgot that the kernel was loaded into the NBH (it's been a while since I've updated my stuff).

When using A-Tools, I downloaded the latest copy of the kernel (as per the directions in the how-to link at the end of the first post) and followed that step by step.

Also, Scoot just posted some Vogue kernels in his CM6 thread. I tried the OC version and I got the same problem (failed to mount).

Edit: Going to try the non-OC version now...

Edit 2: Non-OC version gives the same results.
[Touch CDMA Android Development] l1q1d:
Did you have the same problem with non edited kernel?

(Download it using the link in my signature)
[Touch CDMA Android Development] grktaurus83:
The latest kernel mounts for me.

Unfortunately, I get a kernel panic during boot on Scoot's RLS6 (which is the problem I had with my original kernel).
[Touch CDMA Android Development] chourmovs:
i think i've messed with atools options

I found a good setup on polaris with latest 2.6.32 kernel with system on nand and data on sd card (2 ext4 partition done manually with gparted)

to make it better i decided to alter system/data partition and give everything to the system as data was now on sd card (maybe i missed something with my ridiculous comprehension)

Anyway from this point, i was not able to have good performance with nand/sd android and even after having flash again with "not altered partition" nbh, i can't get a good and speed setup

what is strange is that if i do a task 29 it doesn't change anything and that WM setup are very slow or broken too

it's like system/data partition was still altered

My question : do you understand my problem and if so can you explain

how can i reverse partition to the original or erase everything ?

thank you for your answer
[Touch CDMA Android Development] l1q1d:
the only thing is that the nand corrupted sectors are too much.

The partitioning on nand is virtual, there aren't two real partition on it.

When you change with atools the values you change the start/stop sector where begin/finish the "partition" (this is way you can't see them with task 29). Every time you change the partition you need to create a fs (yaffs) that specifies where file are located.

So when you install windows, it uses all the space avaible. If there are too many bad blocks they will not be allocated.

Try to reflash windows but if you got more then 20 bad blocks when you reinstall android i think that you need a new phone.
[Touch CDMA Android Development] chourmovs:
thank you liquid

when it didn't work, i noticed that android/preference/sd card and memory/ told me that internal memory (total and left) were 0mb :D

By the way, i succeed recovering nand by running a WM install to the end, as you said

after that i flashed a simple 2.6.32 kernel generated with atool and setup a cyanogen rom nand/sdcard and i get back a good speed , now android see my internal memory :D

during the setup, linux only claim about 1 bad block, maybe i'm lucky :p (is there a way to recover bad block ?)

I noticed too that my created ext4 partition was turned into ext2 during install, but it's ok like that :confused:

i noticed very nice progress with latest 2.6.32 kernel, no more corruption and very fast system, even more with data on sd card

Thank you for your excellent and hidden work
[Touch CDMA Android Development] l1q1d:
you're welcome :-)
[Touch CDMA Android Development] soprus:
does not work leftrsoft key as "volume down"

but rightsoft work as volume up

KAISER TyTNII !!!

2.6.32

any distro
[Touch CDMA Android Development] grktaurus83:
Kinners posted a recently compiled kernel that works for the Vogue and solves the problem I was having with mounting.

Anyone on the Vogue that needs it can find it here.

I'm still not sure why I couldn't get ATools to pull the latest sources and generate a kernel for the Vogue, but I hope that helps other people that are having this problem.

Make sure to drop a thanks to kinners. I'm just the messenger.
[Touch CDMA Android Development] edokrat:
What is a stupid windows user ????

I do not speak like this.

Lets be COOL OKEE ?
[Touch CDMA Android Development] WnG88:
Any corruption issues with this kernel?
[Touch CDMA Android Development] l1q1d:
@WnG88: OT!!!!
[Touch CDMA Android Development] Aiex Rlder:
hmm quick question:

is anyone having problems using this? i recently switched laptops from one running xp to windows 7. having installed python i can't see to get atools or any other script to run using python, it opens a command box briefly and then closes again :(
[Touch CDMA Android Development] WnG88:
Heh, I'm not knocking your kernel l1q1d. Your work is great and appreciated. I think you're the last one standing too now. I use an older version of your kernel myself. Was questioning whether that 'recompiled' kernel for vogue had any issues. There seem to be mixed posts that say there are still issues and others say that it is fine.
[Touch CDMA Android Development] agungwap:
Great tools...

I just tried to help solving mounting NAND Partition problems.

At Atools, line 2154

writeon+=" mtdparts=msm_nand:0x00300000@0x1600000(boot),0x00040000@0x01900000(root)"+str(sys)+"@0x01900000(system),"+str(data)+"@"+str(dataoffset)+"(userdata)"

there is missing ","

should be :

writeon+=" mtdparts=msm_nand:0x00300000@0x1600000(boot),0x00040000@0x01900000(root),"+str(sys)+"@0x01900000(system),"+str(data)+"@"+str(dataoffset)+"(userdata)"
[Touch CDMA Android Development] l1q1d:
good to know, i'll update it but i can't test it on vogue...
[Touch CDMA Android Development] agungwap:
Tested on me.. and fully function for all tools. :D
[Touch CDMA Android Development] edci:
my power button was not working so i tried to reassign the keys using the keymapper but doesnt work. whatever key i assign to wake up the phone - it doesnt work. any ideas?
[Touch CDMA Android Development] l1q1d:
It could be a software problem, did you have the same problem with all rom?
[Touch CDMA Android Development] robberviet:
I've follow step by step but I'm stuck at 31 because I can't enter bootloader.It seem that my camera button is broken,i can half press it but not full press(like in camera i must change to half press in order to take phoho)

Any other way to get through this?
[Touch CDMA Android Development] l1q1d:
No, i'm sorry there is no way from there because if you flash from windows you can't revert to teh bootloader anymore.
[Touch CDMA Android Development] robberviet:
It's hopless?I was so eager to try android on my phone :( So I will try to fix the button or keep using WM then.

Thank you anyway :D
[Touch CDMA Android Development] erups:
Hi guys.

Sadly my phone went for assistance.

So I unshelved my htc polaris and promptly installed Froyo on it.

I used this rom here, rebuilt both the script and the NBH with Atools.

Installed both sys and data in nand.

Every time I tried to configure the partitioner to use the SD I ended up with unusable device with errors about being unable to mount and/or find different folders. Haveing to restart install.

So ended up installing everything on nand, but now froyo says it can't find an sd.

From the settings menu it sees the SD fine (lets me mount/unmount it) but then both in astro and in the system it can't find it.

Anyone willing to help me?

Also I have a bunch of applications (were already in the rom) trying to auto-update (including super user) but they are stuck at the starting-download phase.

No matter how many resets or anything I do.
[Touch CDMA Android Development] l1q1d:
Try to reformat the sd