I've been trying for thee past couple of hours to get Haret to work, to no avail.
Whenever I click on Haret, it will go into the process:
Haret: Booting Linux...
And load through that screen. Once it finishes that though, it just freezes. Notification LED still works if I had something beforehand. It won't vibrate twice like it normally does when normally booting Linux. To my knowledge I haven't changed anything at all. I'll post my startup.txt incase that might be the problem
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=2,1,3 rel_path=andboot north_am_dialing=0 force_cdma=0 hw3d.force=0 physkeyboard=tilt2"
boot
Do you have all of the files in the andboot folder at the root of your SD card?
You have some strange options in there, but nothing that would prevent booting.
I have highlighted the commands you should remove in red/bold (deprecated).
I have also highlighted some in blue/bold - no reason to have 'em if they're set to 0. Plus, hw3d is on whether you turn it on or off in the startup.txt IIRC.
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 [color=red][B]msmts_calib=0x9f.0x39a.0x35c.0x78 [/B][/color]msmvkeyb_toggle=off [B][color=red]pmem.extra=1[/color] [/B]gsensor_axis=2,1,3 rel_path=andboot [B][color=blue]north_am_dialing=0 force_cdma=0 hw3d.force=0[/color][/B] physkeyboard=tilt2"
boot
What build are you using? You should post in that build's thread instead of creating a new thread - thanks!
arrrghhh said:
You have some strange options in there, but nothing that would prevent booting.
I have highlighted the commands you should remove in red/bold (deprecated).
I have also highlighted some in blue/bold - no reason to have 'em if they're set to 0. Plus, hw3d is on whether you turn it on or off in the startup.txt IIRC.
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 [color=red][B]msmts_calib=0x9f.0x39a.0x35c.0x78 [/B][/color]msmvkeyb_toggle=off [B][color=red]pmem.extra=1[/color] [/B]gsensor_axis=2,1,3 rel_path=andboot [B][color=blue]north_am_dialing=0 force_cdma=0 hw3d.force=0[/color][/B] physkeyboard=tilt2"
boot
What build are you using? You should post in that build's thread instead of creating a new thread - thanks!
Click to expand...
Click to collapse
I always forget to mention that XD
I am using FRX05 if that helps in any way.
QuentinX5 said:
I always forget to mention that XD
I am using FRX05 if that helps in any way.
Click to expand...
Click to collapse
Try what I have suggested.
Post in the build thread please .
I had this same problem before but I think it was due to a corrupted build . . . . . I forget exactly how I fixed the problem but first id recopy Haret to the sd as if had it corrupt before.
Next make sure you have the right kernal where it should be, pay particular attention to the 'zimage' file.
Do you use an Overclock on Win-Mo?
Having the same problem with the march 11 kernal.
Files are on the root folder. Simple startup file. No overclock in win-mo or android.
I'll try reformating with HP format tool again and re-load the files.
Related
If you are familiar with Android already, but are not satisfied with the speed of your system, you might want to try a smaller release, without senseui, etc.
In this case, I recommend you to go to the Google Code: Android for Vogue website.
On this site, you will always find the latest kernels, rootfs's, etc..
The file list of a working Android (on the root of your formatted card):
default.txt
haret.exe
initrd.gz
rootfs.img
system.img
zImage
The default.txt of your Android on a Nike should look like this:
set RAMSIZE 0x07000000
set RAMADDR 0x10000000
set FBDURINGBOOT 0
set MTYPE 1724
set KERNEL zImage
set initrd initrd.gz
set cmdline "board-htckaiser.panel_type=1 ppp.apn=wnw ppp.username= ppp.password= board-kaiser-battery.battery_capacity=1800 mddi.width=320 mddi.height=480 msm_sdcc.msmsdcc_fmax=20000000 pm.sleep_mode=1 no_console_suspend board-kaiser-keypad.atttilt=1 board-htcnike-keypad.keypadlayout=1"
boot
With these settings, you have keyboard working, power button ends the call, start button is Home, camera button is menu.
Feel free to combine the files, test zImage's, system.img's.
Remember, for a clean start, the only files that should be on the card are listed above. If you leave the previous data.img created at the first start of Android when trying out a new kernel, or system.img, there can be issues, maybe system fail.
Regards, Hope i could help some.
Questions are welcome, i may make a FAQ from them.
Simple, short...
Thank you
Is it possible to get my windows mobile contacts working on android?
Good question, I have the same...
I think it possible through Outlook, exporting to Gmail, but I didn't try this...
Another question; you speak about "board-htckaiser[...]" and the wiki speak about "board-htcnike[...]" is the same options for the two commands ? I'have tested board-htcnike-keypad.keypadlayout=2 for my AZERTY 20keys nike and it work fine...
wm contacts
Yep, you have to copy your contacts to the SIM card, and then in Android, you can access, and copy them to the local storage, and you can also sync them with your Google account, and also, you can link your contacts with Facebook or Twitter users. It will display their picture, news, and birthdays automatically.
Big Up
Can you let us know the details:
1- Which android version you used
2- Which zImage version you used
3- What is you startup.txt like
4- Did you manage to solve it? and how?
This is a survey after finding out alot of people are having this problem and so far it is hard to pinpoint what the exact problem is.
If we can share our info together I am sure we can get to the bottom of it.
Thanks
1- I've tried Froyostone (sense and clean) latest builds from 7 Aug 2010
2- zImage from 14 Aug 2010
3- Startup as follows:
set mtype 2524
set ramaddr 0x18000000
set ramsize 0x0fc00000
set initrd_offset 0x00a00000
set KERNEL zImage
set initrd initrd.gz
set cmdline ""
boot
also tried
set mtype 2524
set ramaddr 0x11800000
set ramsize 0x1E400000
set initrd_offset 0x00a00000
set KERNEL zImage
set initrd initrd.gz
set cmdline ""
boot
also tried to replace cmdline by adding "rel_path=Android" and changing boot to bootlinux
Formatting SD always before re-trying
4- Still no solution, after Jumping to Kernel i get black screen or just freeze and nothing happens. Have to remove battery to reboot.
the details:
1- All latest built version with fullram zImage
2- kernel: darkstone 2.6.32.9 #35 (freeze)
Kernel: huanyu 2.6.32.9 #4 (sometime can work on first time after format SD)
Kernel: manusfreedom 2.6.32.9 #74 (shown rebooting in 5 second)
Kernel: ElBartoME 2.6.32.9#11 (freeze)
3- I am sure all version has correct startup.txt and add "rel_path=Android" in cmdline such as below:
set mtype 2524
set ramaddr 0x11800000
set ramsize 0x1e400000
set initrd_offset 0x00a00000
set KERNEL zImage
set initrd initrd.gz
set cmdline "rel_path=Android"
boot
4- I have tried difference radio / rom but still no solution for me, but I only can use back old build version with Kernel: Cotulla 2.6.32.9 #103 (mattc Leo 1.4 / shubCRAFT 1.1)
I can only run these perfectly
PB81100 HX-BC
Radio 2.12.50.02
Laterest EnergyROM 23129
Hope someone can help me
Thanks
I only have this problem, when a .51 (European Radio) is installed (Non-TMO-US Version). With a .50 (U.S. Radio), booting the Kernel just works fine.
Solved
The rom update solved my issues too. Just used the latesd one and no more problems starting!
Thanx for your help!
Yep seems the ROM update to .50 solves this issue that most of the people are having!
Here you find all info on how to change your ROM version: http://forum.xda-developers.com/showthread.php?t=609477
i have .50 but i still get jumping to kernel. but just with the new coredroid build...
Jumping to Kernel
Dear All,
Still No Solution about this problem.
Trying all solution nothing success.
Any suggestion ?
Thanks.
Regards,
Arifin
what works for me
Always delete cache and data folder not the data file when switching Kernel, Rom or anything else. Android should run after this.
cw-data said:
I only have this problem, when a .51 (European Radio) is installed (Non-TMO-US Version). With a .50 (U.S. Radio), booting the Kernel just works fine.
Click to expand...
Click to collapse
this made the fix for me. updated radio to .50
Gentlemen, with these settings below I can not succeed in installing android on my HTC topaz where I'm wrong because the settings of the Haret defaul.txt enters the boot to put it on display with this information
Haret boot
Shutting down hardware
Turning off MMU ...
PSR = 600000
AND LATCH.
I'LL SHOW THEM HOW THIS SET THE SD CARD AND THE FILES THEREIN.
THE ROOT OF THE FOLLOWING FILES ARE SDCARD:
/ CONF
/ MEDIA
CALIBRATION.TXT
DEFAULT.TXT
EncFiltLog.menc
HARET.EXE
Initrd.gz
modules-2.6.27-00706-g4da65fd-dirty.tar.gz
ROOTFS.IMG
system.sqsh
zImage
REMEMBERING THAT THIS CARD SD formatted in FAT32.
SETUP FILE IS THIS DEFAULT.TXT.
MTYPE September 2293
September KERNEL zImage
# Set FBDURINGBOOT 0
September initrd initrd.gz
September ramsize 0x10000000
September ramaddr 0x10000000
PWF # dm.txt 0x8e0000 0x20000
PWF # smem.txt 0x01f00000 0x100000
# = Msmts_calib 0x376.0x3c1.0x6a.0x8a
September cmdline "= msmts_calib 0x395.0x3d5.0x79.0xa0 msmvkeyb_toggle = off lcd.density mddi.width = 240 = 320 = 480 mddi.height no_console_suspend pmem.extra gsensor_axis = 1 =- 1, -2.3 sensor topaz force_cdma = = htc_battery_smem.fake 0 = 1 "
# Mddi.width mddi.height = 320 = 480
boot
WHAT IS WRONG OR BETTER WHERE I'M wrong?
GRATEFUL FOR THE HELP
pauloedusp said:
Gentlemen, with these settings below I can not succeed in installing android on my HTC topaz where I'm wrong because the settings of the Haret defaul.txt enters the boot to put it on display with this information
Haret boot
Shutting down hardware
Turning off MMU ...
PSR = 600000
AND LATCH.
I'LL SHOW THEM HOW THIS SET THE SD CARD AND THE FILES THEREIN.
THE ROOT OF THE FOLLOWING FILES ARE SDCARD:
/ CONF
/ MEDIA
CALIBRATION.TXT
DEFAULT.TXT
EncFiltLog.menc
HARET.EXE
Initrd.gz
modules-2.6.27-00706-g4da65fd-dirty.tar.gz
ROOTFS.IMG
system.sqsh
zImage
REMEMBERING THAT THIS CARD SD formatted in FAT32.
SETUP FILE IS THIS DEFAULT.TXT.
MTYPE September 2293
September KERNEL zImage
# Set FBDURINGBOOT 0
September initrd initrd.gz
September ramsize 0x10000000
September ramaddr 0x10000000
PWF # dm.txt 0x8e0000 0x20000
PWF # smem.txt 0x01f00000 0x100000
# = Msmts_calib 0x376.0x3c1.0x6a.0x8a
September cmdline "= msmts_calib 0x395.0x3d5.0x79.0xa0 msmvkeyb_toggle = off lcd.density mddi.width = 240 = 320 = 480 mddi.height no_console_suspend pmem.extra gsensor_axis = 1 =- 1, -2.3 sensor topaz force_cdma = = htc_battery_smem.fake 0 = 1 "
# Mddi.width mddi.height = 320 = 480
boot
WHAT IS WRONG OR BETTER WHERE I'M wrong?
GRATEFUL FOR THE HELP
Click to expand...
Click to collapse
1st off.. post in the correct forum: http://forum.xda-developers.com/forumdisplay.php?f=623
2nd try change the name of the startup file from "default" to "startup.txt"
3rd: you should have this layout in your sd card:
/AndroidApps/
/conf/
/media/
/STARTUP CONFIG/
/STARTUP.TXT
/haret.exe
/initrd.gz
/rootfs.img
/system.ex2
/zImage
4th: try using latest bundle package (XDAndroid is working for me). find some more info here: http://forum.xda-developers.com/showthread.php?t=509493
hope this helps, good luck!
I'm sorry for this post I will put it in the forum thanks for the warning stated.
I did just download the knack that you told me.
only one question should be how startup.ext settings?
AND A QUESTION FILE modules-2.6.27.46-01165-gfc1639f.tar.gz Unzip WHERE DO I HAVE?
the system that I downloaded was XDANDROID.2.2.AOSP.FRX01.17.09.10.UPDATE_PACKAGE
grateful
pauloedusp said:
I'm sorry for this post I will put it in the forum thanks for the warning stated.
I did just download the knack that you told me.
only one question should be how startup.ext settings?
AND A QUESTION FILE modules-2.6.27.46-01165-gfc1639f.tar.gz Unzip WHERE DO I HAVE?
the system that I downloaded was XDANDROID.2.2.AOSP.FRX01.17.09.10.UPDATE_PACKAGE
grateful
Click to expand...
Click to collapse
if you just extract the package and copy the whole 'Andboot' folder to the root of your SD, then go into the STARTUP CONFIG\TOPAZ and copy the startup.txt file to into the Andboot folder and launch haret it should work.
keep in mind that you should have at least 250mb-300mb free in your storage card.
the modules can stay gzipped, no problem.
I'm afraid that for advanced setting i cannot be of any help. If you have question, try posting them in the XDAndroid thread...
good luck
thanks for the help but I have not had success ...
I tried all forms with multiple files at last unable to exit the screen when having to boot the Haret.
Haret boot
Shutting down hardware
Turning off MMU ...
In preloader
PSR = 600000df
I'm forgetting to do something so I do not know what it is yet but thanks for the help.
nobody answered me in the post.
good keep searching and counting on your help
I'm already almost one month trying and nothing ...
but thanks
I downloaded the cab xdandroid from here http://forum.xda-developers.com/showthread.php?t=627997 and use this as STARTUP:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 clock_7x00.grp=0xa99 hw3d.force=1 board-htcrhodium.is_cdma=1 msmvkeyb_toggle=off pmem.extra=1 rel_path=andboot force_cdma=1 gsensor_axis=2,1,3 pm.sleep_mode=2 acpuclock.oc_freq_khz=716800 physkeyboard=rhod400"
boot
Now it starts and gets stuck at the internet browser saying to update "Launcher Pro" but it has no wifi or internet. How can I solve this? What do I have to do?
Should we guess at the model of phone/rhodium you have? Is it GSM CMDA?
Davidtjuh said:
Now it starts and gets stuck at the internet browser saying to update "Launcher Pro" but it has no wifi or internet. How can I solve this? What do I have to do?
Click to expand...
Click to collapse
Based on your startup.txt, I'd guess RHOD400, CDMA.
But that's not the problem - I'd hazard a guess that you downloaded the BLAZN version from Sept.28... that version is very oudated, I would recommend using FRX04 AKA "Reference". Don't get the CAB either, just extract the RAR (or ZIP, can't remember... the compressed file ) to the root of your SD and go. No CAB mess.
Sorry for the unclear explanation.
I have this HTC TP2: http://regmedia.co.uk/2009/06/22/htc_touch_pro2_3.jpg
on the Android Startup Menu it is the Rhod100 UK, but I doubt it's that version.
I have the Energy Blue Glass Rom something 6.5, I will look it up asap..
I just can't get out of the webbrowser to setup my wifi, it stays on "No Service", it's the Blazn indeed. Ill try the reference.
Yea for some reason the version of launcher pro is out of date so you cant return to home they should add another home or include the stock one just in-case but the OC makes its really fast.
you could always update launcher pro too, thats what i did
noodles21o2 said:
you could always update launcher pro too, thats what i did
Click to expand...
Click to collapse
I don't have any wifi or mobile internet my phone won't connect
DroidFreek said:
I don't have any wifi or mobile internet my phone won't connect
Click to expand...
Click to collapse
Use reference build, as I mentioned above...
By the picture you posted of your phone, it is a rhod100.
If so (you can see it underneath your battery), you need to change the board line to =0 and force_cdma to 0. Also you need to change keyboard to rhod100_uk. If your wifi still doesn't work, try to find the wifi fix.
Greetz,
Steyn
Here is the altered startup:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 clock_7x00.grp=0xa99 hw3d.force=1 board-htcrhodium.is_cdma=0 msmvkeyb_toggle=off pmem.extra=1 rel_path=andboot force_cdma=0 gsensor_axis=2,1,3 pm.sleep_mode=2 acpuclock.oc_freq_khz=716800 physkeyboard=rhod100_uk"
boot
Hope this helps you
Also, wifi fix:
This will fix your problem. Find your MAC ADDRESS on your phone and write it in the WIFI-NVRAM.TXT then place the WIFI-NVRAM.TXT in the root of your storage card. Now replace your FROYO.USER.CONF with the one in this zip. The FROYO.USER.CONF is in this folder ANDBOOT/CONF. Now boot android and you'll have wifi working.
www.4shared.com/file/UXS_y76U/WIFI-NVRAM.html
Greetz (again)
Steyn
i cant get my startup.txt right idk why i followed what it said in F22's rootfs thread but idk..
so can someone post theirs that i can use as a reference for mine it would really help me ALOT
btw im using a rhod 400
thanks
afgomar said:
i cant get my startup.txt right idk why i followed what it said in F22's rootfs thread but idk..
so can someone post theirs that i can use as a reference for mine it would really help me ALOT
btw im using a rhod 400
thanks
Click to expand...
Click to collapse
Check the link in my signature for more detail and a guide
Alternatively you can use this as a base, if your phone is not CDMA:
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=1 hw3d.force=1 physkeyboard=rhod400"
boot
Remember to hit 'Thanks' if I helped
I have also subscribed so if you need any more help after you have checked my guide, let me know.
ryannathans said:
Check the link in my signature for more detail and a guide
Alternatively you can use this as a base, if your phone is not CDMA:
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=1 hw3d.force=1 physkeyboard=rhod400"
boot
Remember to hit 'Thanks' if I helped
I have also subscribed so if you need any more help after you have checked my guide, let me know.
Click to expand...
Click to collapse
Only option that's not needed is hw3d.force=1 - enabled by default now .
ryannathans said:
Check the link in my signature for more detail and a guide
Alternatively you can use this as a base, if your phone is not CDMA:
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=1 hw3d.force=1 physkeyboard=rhod400"
boot
Remember to hit 'Thanks' if I helped
I have also subscribed so if you need any more help after you have checked my guide, let me know.
Click to expand...
Click to collapse
so i went to the guide that you posted and i got the code you posted for cdma devices and changed it for my specific device which is a rhod 400
and i put in the root of my sd card and when i booted up (im on frx06 if thats important) and still the power button on the top of the tp2 does not act as a home button. can you tell me how i can make the top power button the home button?
thanks
Adding "gpiokeyopts=b4POWER-powerHOME" to startup.txt will enable you to do this.
See startup.txt below for example.
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 rel_path=frx05 board-htcrhodium.is_cdma=1 force_cdma=1 pm.sleep_mode=1 hw3d.force=1 physkeyboard=rhod110"