Develop Bugs

I can't boot Linux

Hello,
I followed this manual:
http://handhelds.org/moin/moin.cgi/BlueAngelHowtoInstallLinux
I partitioned my SD card (FAT; ext3 but even tried it with ext2) and copied these files to FAT:
http://htc.gnulinux.biz/files/blueangel/sd/linux/
and this OPIE image to ext3/s:
http://hands.com/~lkcl/blueangel/
Haret starts, but when the penguin gets the "big eyes" it freezes and I have to take out the battery.
I have an MDA III with Windows Mobile 6 (perhaps that's the problem?)
Thank you,
Alex

No that's not your problem. Try with a GPE image.
And, you have to tell us what's on the screen when it freezes.

There's only the penguin and a red-filled thermometer column on the screen.
I'll try it with the GPE image, thanks.

I tried it again with the GPE image, but still no luck.

Oh excuse me. I thought you had a problem with the linux image.
Your problem I think is the startup.txt. You should modify it to match the files you imported in the FAT partition.
Follow the link I give you bellow to download the newest files.
http://htc.gnulinux.biz/files/blueangel/sd/linux/
That worked for me.

I took exactly these files, and the files in startup.txt are correct. Now I did this: I changed one file in startup.txt to a non-existant file. Now I could get into the Haret application (otherwise it tries to boot correctly) and made it listen to port 9999. On my computer I started HyperTrm on 9999 (and got a console). Then I corrected startup.txt again. Using the command "bootlinux", it started the bootprocess. This is what I got:
-----------------
Welcome, this is HaRET running on WindowsCE v5.2
Minimal virtual address: 00010000, maximal virtual address: 7fffffff
CPU is Intel XScale ARM arch 5TE revision 3 product 16 stepping 6 running in sys
tem mode
Enter 'HELP' for a short command summary.
HaRET(1)# set KERNEL "zImage-2.6.12"
HaRET(2)# set MTYPE 766
HaRET(3)# set INITRD "initrd-2.6.12-hh2.gz"
HaRET(4)# set CMDLINE "root=/dev/ram0 init=/linuxrc ramdisk_size=14336 keepinitr
d console=tty0 boot_mmc=y"
HaRET(5)# bootlinux
Physical kernel address: a0008000
Preloader physical/virtual address: a55ad000
Physical initrd address: a0408000
Goodbye cruel world ...

have you put initrd-*wh.atev.er*-hh2.gz on the sd card in the same directory as HaREt? that was my problem.

and, as a tip, once you get it going, use the GPE image from here:
http://htc.gnulinux.biz/files/blueangel/sd/linux/
GPE will not be your booting problem, this is an inintialisation issue before it ven starts to boot GPE. but it will help if you use that image.

I was wondering how to start gpe from the command line, when I boot up linux, I get the login, but don't know how to start GPE. Does anyone here know?
Thanks,
Tim

GPE should start automatically. If not, it seems as if it doesn't find the image.
Perhaps you have no configuration file / a wrong file name of the GPE image is written in there?

My MDA III not booting with linux, i use:
haret-20071216.exe
startup.txt:
set KERNEL "zImage-2.6.12-hh2"
set MTYPE 766
set INITRD "initrd-2.6.12-hh2"
set CMDLINE "root=/dev/ram0 init=/linuxrc ramdisk_size=14336 keepinitrd console=ttyS2,115200 console=tty0"
bootlinux
initrd-2.6.12-hh2 (without GZ )
zImage-2.6.12-hh2
My MDA III booting, and stoping on :
Starting portmap daemon: portmap
where use board-id? In instruction write:
5. get your board id
dmesg | grep -i "board id"
6. write it down.
I'm waiting long time, my mda is freeze
i not use crandel...
use gpe image on linux partition...
me help, only hard reset
OS: WM6.0
Radio:1.15
help please... i love linux...

Problems with dualboot

hy i have a Htc Raphael 100 (t7272)
i use the newest GenY rom with bootloader.
yesterday i downloaded the XDandroid 2.1 and was following the instructions
i formatet my 16 GB Kingston MicroSDHC2 card with the formater from sdcards.com
on the card are only XDandroid with the startup.txt in root with following text inside
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 1910
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmts_calib=0x7a.0x5e.0x35a.0x37f clock-7x00.a11=500 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=-1,-2,3 board-htcraphael-navi.wake=0 physkeyboard=fuze"
boot
if i start the haret.exe it boots. but it hangover when the Graphic X (the moving thing) and it wanna go nothing more? i waitet for 15 min but nothing.
du you have any idea what i did wrong?
sory for the "perfect" english...
by sunny

I believe if you grab the newest zImage/rootfs you'll be good

sunny2010 said:
hy i have a Htc Raphael 100 (t7272)
i use the newest GenY rom with bootloader.
yesterday i downloaded the XDandroid 2.1 and was following the instructions
i formatet my 16 GB Kingston MicroSDHC2 card with the formater from sdcards.com
on the card are only XDandroid with the startup.txt in root with following text inside
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 1910
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmts_calib=0x7a.0x5e.0x35a.0x37f clock-7x00.a11=500 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=-1,-2,3 board-htcraphael-navi.wake=0 physkeyboard=fuze"
boot
if i start the haret.exe it boots. but it hangover when the Graphic X (the moving thing) and it wanna go nothing more? i waitet for 15 min but nothing.
du you have any idea what i did wrong?
sory for the "perfect" english...
by sunny
Click to expand...
Click to collapse
r u Indonesian ?

Make sure you do have the latest zImage and rootfs. If you do recopy all the files over to the card and start it up. When it gets stuck boot into WM and delete data.img. After that it should run fine, I wrestled with it for hours and that was the suggestion I was given.

sunny2010 said:
hy i have a Htc Raphael 100 (t7272)
i use the newest GenY rom with bootloader.
yesterday i downloaded the XDandroid 2.1 and was following the instructions
i formatet my 16 GB Kingston MicroSDHC2 card with the formater from sdcards.com
on the card are only XDandroid with the startup.txt in root with following text inside
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 1910
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmts_calib=0x7a.0x5e.0x35a.0x37f clock-7x00.a11=500 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=-1,-2,3 board-htcraphael-navi.wake=0 physkeyboard=fuze"
boot
if i start the haret.exe it boots. but it hangover when the Graphic X (the moving thing) and it wanna go nothing more? i waitet for 15 min but nothing.
du you have any idea what i did wrong?
sory for the "perfect" english...
by sunny
Click to expand...
Click to collapse
I have the same problem with you,so I back to the andriod 2.0.1.

I had the same issue with the latest version. Downgrading didnt help me either. i literally spent all day trying to boot it. kept deleting, trying again, etc... Finally after a few hours of doing 2.1 over and over, it booted. Looks like the 1st boot is a killer. it takes a while and sometimes gets stuck.
Sent from my AOSP on XDANDROID MSM using the XDA mobile application powered by Tapatalk

enTRAPAG said:
I had the same issue with the latest version. Downgrading didnt help me either. i literally spent all day trying to boot it. kept deleting, trying again, etc... Finally after a few hours of doing 2.1 over and over, it booted. Looks like the 1st boot is a killer. it takes a while and sometimes gets stuck.
Sent from my AOSP on XDANDROID MSM using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
Yep, I had the same issues, was able to boot after updating to latest rootfs and zimage and deleting data.img after the first boot.

android wont boot

hi there i got the new [9/28 build] for htc touch pro2. i installed 2 times right now because when i want to boot it...it says andboot/ doesnt exist.
i got riddin of all the android files before i installed it.
btw cant find the default of start file...
greetings

double check where your haret.exe is

Also, don't use the startup utility. I've found it's still not right... a few times it corrupted my startup.txt, and the update portion is still very broken.

screenshot
or maybe its the system.ext2 that i have to rename?
look i dont have it..in the attachment

you rename the "startup.txt" to "default text". so when it gets to that haret screen, just press run and itll work.
you mite have to do it after a fresh install if your startup.txt if its size is at a 0.

am i a noob
mmm k but like ive shown on the attachment screenshot...i dont have a "startup.txt" i got system.ext2 file
cheers

peruwan said:
mmm k but like ive shown on the attachment screenshot...i dont have a "startup.txt" i got system.ext2 file
cheers
Click to expand...
Click to collapse
That's you're problem then. You need a startup.txt... it kinda tells haret where everything is & how to set the system up basically...
There should be a STARTUPS folder. Grab the startup for your device, put it where you run haret from.

arrrghhh said:
That's you're problem then. You need a startup.txt... it kinda tells haret where everything is & how to set the system up basically...
There should be a STARTUPS folder. Grab the startup for your device, put it where you run haret from.
Click to expand...
Click to collapse
have you seen the screenshot on my last message i dont have such thing...i still got the backup from the older build is that a problem to copy paste?

peruwan said:
have you seen the screenshot on my last message i dont have such thing...i still got the backup from the older build is that a problem to copy paste?
Click to expand...
Click to collapse
I've seen your magical screenshot dude. I can't really see if that's the root of the SD or what, so that's why I mentioned a STARTUPS folder. Babijoee's builds used to have 'em, I think reef removed it so it wouldn't confuse people... You can reuse an old startup, just make sure that it's setup correctly. If it's not, it could cause issues. Which is why you may want to start over, why the heck do you not have a startup.txt?!?

theres no STARTUP file nor STARTUP folder in the root thats why ive shown the andboot/ ... ye there was a STARTUP file before i installed this build...
what kinda setup information should i put i got this one from the old
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 7x00.a11=500 msmvkeyb_toggle=off pmem.extra=1 force_cdma=0 gsensor_axis=2,1,3 pm.sleep_mode=2 acpuclock.oc_freq_khz=716800 rel_path=andboot hw3d.force=1 physkeyboard=rhod100_uk htc_hw.force_cdma=0 "
boot

peruwan said:
theres no STARTUP file nor STARTUP folder in the root thats why ive shown the andboot/ ... ye there was a STARTUP file before i installed this build...
what kinda setup information should i put i got this one from the old
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 7x00.a11=500 msmvkeyb_toggle=off pmem.extra=1 force_cdma=0 gsensor_axis=2,1,3 pm.sleep_mode=2 acpuclock.oc_freq_khz=716800 rel_path=andboot hw3d.force=1 physkeyboard=rhod100_uk htc_hw.force_cdma=0 "
boot
Click to expand...
Click to collapse
So you didn't want to go with a clean new build huh...? It looks OK, you've got the force_cdma command in there 2x for some reason... but I assume since they're both set to 0 that'll be fine. Make sure physkeyboard is set correctly. Other than that, it looks OK.

arrrghhh said:
So you didn't want to go with a clean new build huh...? It looks OK, you've got the force_cdma command in there 2x for some reason... but I assume since they're both set to 0 that'll be fine. Make sure physkeyboard is set correctly. Other than that, it looks OK.
Click to expand...
Click to collapse
i did a clean start i got ridding of everything. ye its ok thats in uk...i live in holland tho but its the same thing i guess

peruwan said:
i did a clean start i got ridding of everything. ye its ok thats in uk...i live in holland tho but its the same thing i guess
Click to expand...
Click to collapse
Alright... is it working now?

arrrghhh said:
Alright... is it working now?
Click to expand...
Click to collapse
nope still sayin the same message...i copy and paste it weird tho

peruwan said:
nope still sayin the same message...i copy and paste it weird tho
Click to expand...
Click to collapse
That may be your problem.
Just start completely over at square one. Format your SD and start with a clean new build - don't reuse anything. Something's obviously been buggered, and this is just a much easier method to fix it than actually trying to troubleshoot what you broke

arrrghhh said:
That may be your problem.
Just start completely over at square one. Format your SD and start with a clean new build - don't reuse anything. Something's obviously been buggered, and this is just a much easier method to fix it than actually trying to troubleshoot what you broke
Click to expand...
Click to collapse
Listen to arrrghhh,dude. Like he said you've obviously fudged it somewhere. Just uninstall it, delete all folders and start over from scratch. Maybe you should hard reset your device back to factory standards also. This might solve all you whoas

right..
dude it wasnt that obviously....now it wont even start the android project after clickin it it says a error.NET COMPACT FRAMEWORK IS INSTALLING ON YOUR SD CARD(which isnt?) IF THAT DOENST HELP? INSTALL IT AGAIN.
well what now? error code is: 2147479552 (80001000).
probably i need to install again the .net framework...but in cab version and the good version
cheers

peruwan said:
dude it wasnt that obviously....now it wont even start the android project after clickin it it says a error.NET COMPACT FRAMEWORK IS INSTALLING ON YOUR SD CARD(which isnt?) IF THAT DOENST HELP? INSTALL IT AGAIN.
well what now? error code is: 2147479552 (80001000).
probably i need to install again the .net framework...but in cab version and the good version
cheers
Click to expand...
Click to collapse
Don't use the cab bro... make it unnecessarily complicated IMHO. Plus, it's slow and fosters ignorance!!

ok which one should i download?? can you give me the link 2 download the framework for my device before ill destroy it
btw i downloaded the [10/4] update now i got 2 of those apps which i cant open
dont know why it created 2 android after the update cab.

peruwan said:
ok which one should i download?? can you give me the link 2 download the framework for my device before ill destroy it
btw i downloaded the [10/4] update now i got 2 of those apps which i cant open
dont know why it created 2 android after the update cab.
Click to expand...
Click to collapse
Well you can try to use the cab, but you seem to be having issues with it. So just download the rar... it's in the same location as the cab dude. Reef's site offers both the cab and rar installers on the same page..

How to FIX freezing on boot[RIL + ROOTFS]

THIS POST IS OUTDATED, FOLLOW THE GUIDE IN THE STICKY INTRODUCTION TO ANDROID - THIS BUG HAS BEEN FIXED
DISREGARD THE POSTS UNTIL PAGE 5, THEY WERE POSTED BEFORE THIS ORIGINAL POST WAS EDITED WITH THIS FIX.
The problem some users are experiencing is that their phones freeze soon after their first boot until APN (access point name) is changed, this is somewhat difficult to do due to the freezes.
Note: this is for GSM users. I have no idea if this will work with CDMA, or even if they receive freezes.
Highlandsun and I have stumbled upon a fix that worked for me RHOD110 - this has been tested on GSM only (Froyo).
Using this fix, there should no longer be a need to manually select APN.
There are two files you need:
Highlandsun's RIL
and
Customized ROOTFS (F22's keymap rootfs (Mar 1st) edited - it WILL work with all his custom key bindings)
You will probably want to use this kernel if you are not already, it has great battery life and most failed wakes and SoDs are fixed. It is also what I used when testing this fix.
Firstly, extract put the downloaded RIL onto your SD card, I put mine in a folder named Android in the root of my SD, I recommend you do this also.
now edit conf/froyo.user.conf contained wherever you keep your HaRET.exe on your SD. If you are using Linux or a UNIX based operating system, use any editor you wish. If you are running windows, use notepad ++ to edit this file.
Add the following within the { } after custom_shells at the bottom of this file.
Code:
mount --bind /sdcard/Android/libhtcgeneric-ril.so /lib/froyo/libhtcgeneric-ril.so
so that your file should look something like this, I have highlighted the added line. You could even copy and paste the below to replace your whole file.
Code:
# General parameters
general{
renice=1 # Run the renice script to inprove call answering
}
#compcache related parameters
compcache{
compcache_en=1 # enable(1) or disable(0)20 compcache
cc_disksize=100 # Ram swap disksize - any number between 1 to 98 should work; default is 1/4 of the RAM (24)
cc_memlimit=64 # Limit the memory usage for backing swap (cc .5x known issue-defaults to 15% of total RAM)
cc_backingswap_en=0 # enable(1) or disable(0) backing swap
cc_backingswap=/dev/block/mmcblk0p4 # pointing to the backingswap partition device, swap
}
#create swap file for compcache or linux swap
swap_file{
swap_file_en=0 # set to 1 to create swap file
# set to 0 to del the swap file
linux_swap_file_size=32 # swap file size in MB
linux_swap_file=/sdcard/swapfile # pointing to the swap file location ( must be /system/sd/)
}
#Linux swap parameters
#
# linux swap can only be enabled if cc_backingswap_en is set to "0"
#
linux_swap{
linux_swap_en=0 # enable(1) or disable(0) linux swap
linux_swap_partition=/dev/block/mmcblk0p4 # swap partition device
}
#virtual memory
sys_vm{
sys_vm_en=1 # enable(1) or disable(0) virtual memory configurations
swappiness=0 # default 60
page_cluster=0 # default 3, (0 since CM3.9.6+)
laptop_mode=5 # default 0
dirty_expire_centisecs=3000 # default 3000
dirty_writeback_centisecs=1500 # default 500
dirty_background_ratio=3 # default 5
dirty_ratio=5 # default 10
vfs_cache_pressure=200 # default 100 (tendency of the kernel to reclaim cache memory)
overcommit_memory=1 # default 0 (0=Heuristic 1=Always overcommit 2=Don't overcommit)
overcommit_ratio=80 # default 50 (% of Physical+Virtual memory to allow allocation)
}
# custom shell commands, these commands run last
custom_shells{
chmod 777 /etc/dbus.conf
echo 2 > /sys/devices/platform/msm_hsusb/usb_function_switch
rm -f /sdcard/*.rec
mount --bind /sdcard/Android/libhtcgeneric-ril.so /lib/froyo/libhtcgeneric-ril.so
modprobe ipv6
#echo "Hello!!!" # example
#echo "You can create your own commands here" # example
}
Once you have done that, save it and make sure it is saved. You may have to copy it to your pc, edit it, delete the one on your sd, copy it back across - if using droidexplorer to manage files. You could also edit this file from within Android using ASTRO to browse to it.
Now extract that rootfs.img mentioned above and replace your current one.
You will now have improved reliably and hopefully no freezes on boot. The device may also seem faster now.
This fix was suggested to me by Highlandsun (hyc) on #xdandroid irc. He deserves all the credit.
---------For Developers-----------
The modified rootfs has /init.etc/ppp/options.smd edited to the following with changes bolded:
Code:
debug
defaultroute
updetach
[B]#persist[/B]
local
usepeerdns
noipdefault
unit 0
linkname gprs
novj
novjccomp
[B]lcp-restart 1
lcp-max-configure 3
ipcp-restart 1
ipcp-max-configure 3[/B]
highlandsun said:
The hang is because the ril is stuck, it launches pppd and waits for a success status from it. But in this particular case, the connection used the wrong APN so pppd cannot succeed. With the "persist" setting in the ppp options file, pppd also never returns on failure, so ril waits forever, and everything grinds to a halt.
Commenting out the persist setting is the main fix for this. The additional ipcp/lcp lines are to decrease the time pppd spends retrying the connection setup, so that it will quit in less than 60 seconds, which allows ril to recover from the error sooner. I have some more patches for ril which will hopefully make the recovery even faster, coming up.
Click to expand...
Click to collapse

Well you really need to break it down better.
What kernel/modules combo have you tried? How far back did you go? What rootfs have you tried? What builds? System images? Have you looked at your startup.txt? What is in it?
I don't have a 110, but on my 400 most everything "works" flawlessly - assuming you have it configured correctly, yours should be the same.

arrrghhh said:
Well you really need to break it down better.
What kernel/modules combo have you tried? How far back did you go? What rootfs have you tried? What builds? System images? Have you looked at your startup.txt? What is in it?
I don't have a 110, but on my 400 most everything "works" flawlessly - assuming you have it configured correctly, yours should be the same.
Click to expand...
Click to collapse
Okay, firstly my startup.txt
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 clock_7x00.grp=0xa99 hw3d.force=1 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=2,1,3 pm.sleep_mode=1 physkeyboard=rhod110"
boot
Full Packages I have tried:
FROYO X RED 2011.02.06
ProjectAndroid2.2Froyo.012311
RhodiumXDAndroid23.01.10
XDAndroid2.2Froyo.012211
SENSE x 2011.02.10
Along with these Modules:
htc-msm-linux-20101204_010857-package
htc-msm-linux-20110210_213850-package
modules-2.6.27.46-01253-gd53ddf6-dirty
initrd:
initrd-20100813-b11116a
Rootfs:
rootfs-20110210-2cb7ec0
(and many others i have just deleted)

ryannathans said:
Okay, firstly my startup.txt
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 clock_7x00.grp=0xa99[/B][/color] hw3d.force=1 msmvkeyb_toggle=off [color=red][b]pmem.extra=1[/color][/b] gsensor_axis=2,1,3 pm.sleep_mode=1 physkeyboard=rhod110"
boot
Full Packages I have tried:
FROYO X RED 2011.02.06
ProjectAndroid2.2Froyo.012311
RhodiumXDAndroid23.01.10
XDAndroid2.2Froyo.012211
SENSE x 2011.02.10
[ 175.542358] hw3d: current 1343 ppid 1 file d5bb27c0 count 2
[ 175.580810] binder: 1329:1342 transaction failed 29189, size 564-0
[ 175.730926] hw3d: closing
[ 175.730987] hw3d_release: in release for pid=1338 tid=1343
[ 175.731018] hw3d: releasing 1338
Along with these Modules:
htc-msm-linux-20101204_010857-package
htc-msm-linux-20110210_213850-package
modules-2.6.27.46-01253-gd53ddf6-dirty
initrd:
initrd-20100813-b11116a
Rootfs:
rootfs-20110210-2cb7ec0
(and many others i have just deleted)
Click to expand...
Click to collapse
Ok, first the rhod110 physkeyboard option only exists in F22's rootfs.
Have you tried with FRX04?
Have you tried with a "regular" rootfs from the autobuild service?
You also have deprecated commands in your startup.txt, I highlighted them in red.
I'm assuming when you try different kernel/modules you're removing the old zImage/modules-xxx.tar.gz and replace with the new zImage/modules-xxx.tar.gz...
I don't see any other issues. You might need to go way back in the kernel archives, start around the beginning of November and work your way backwards.
If you can get any logs that would be helpful, as I'm just grabbing at straws since I don't actually know what the problem is. Could be your SD card, have you tried a different SD?

arrrghhh said:
Ok, first the rhod110 physkeyboard option only exists in F22's rootfs.
Have you tried with FRX04?
Have you tried with a "regular" rootfs from the autobuild service?
You also have deprecated commands in your startup.txt, I highlighted them in red.
I'm assuming when you try different kernel/modules you're removing the old zImage/modules-xxx.tar.gz and replace with the new zImage/modules-xxx.tar.gz...
I don't see any other issues. You might need to go way back in the kernel archives, start around the beginning of November and work your way backwards.
If you can get any logs that would be helpful, as I'm just grabbing at straws since I don't actually know what the problem is. Could be your SD card, have you tried a different SD?
Click to expand...
Click to collapse
Tried multiple SD cards, my current card is 16GB (could there be a problem here?)
where could I grab logs from?
Tried FRX04 too.
Just making sure im doing it right
Dowloaded RAR - Android v2.2.1 Froyo: Reference
unrar to 'andboot' on sd card.
edit startup.txt
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 rel_path=andboot"
boot
Downloaded and put modules-2.6.27.46-01212-ge59fdaf.tar and its zImage in andboot
(deleted old ones first)
replaced rootfs with rootfs-20110210-2cb7ec0 (renamed of couse to rootfs.img)
.....
run haret.exe
past all the booting
past the xdandroid logo loop
screen is horizontal
slow and laggy android
screen flips to verticle
seems to be more stable
set up my wifi, connected.
so looks like the modules-2.6.27.46-01212-ge59fdaf has stopped it freezing seconds after booting into android.
what do you need now? Am I forever stuck with this old module?

ryannathans said:
Tried multiple SD cards, my current card is 16GB (could there be a problem here?)
where could I grab logs from?
so looks like the modules-2.6.27.46-01212-ge59fdaf has stopped it freezing seconds after booting into android.
what do you need now? Am I forever stuck with this old module?
Click to expand...
Click to collapse
Well at least an old kernel/modules boots. You sound like you're doing it correctly - just to be clear the modules ends in .tar.gz - you shouldn't be uncompressing this file whatsoever.
Now, on to logs. Since you never really boot adb is the only option. If you have Windows, Droid Explorer does most of the hard work for you. Once you get it setup, do a pull
Code:
adb pull /data/system/dropbox/ /path/to/folder/on/your/pc
It will dump all the files in that folder on your phone, onto that folder on your PC. Look at the last SYSTEM_LAST_KMSG file, attach it here.
Hell, attach a few of them.

arrrghhh said:
Well at least an old kernel/modules boots. You sound like you're doing it correctly - just to be clear the modules ends in .tar.gz - you shouldn't be uncompressing this file whatsoever.
Now, on to logs. Since you never really boot adb is the only option. If you have Windows, Droid Explorer does most of the hard work for you. Once you get it setup, do a pull
Code:
adb pull /data/system/dropbox/ /path/to/folder/on/your/pc
It will dump all the files in that folder on your phone, onto that folder on your PC. Look at the last SYSTEM_LAST_KMSG file, attach it here.
Hell, attach a few of them.
Click to expand...
Click to collapse
Just to clear it up, logs from module that dont boot or the one that does?

ryannathans said:
Just to clear it up, logs from module that dont boot or the one that does?
Click to expand...
Click to collapse
The dropbox will have logs from failed boots hopefully.
If you can get a log when it's failing to boot, that would be ideal. Might want to rename your data.img, grab the newest 1253 kernel from GIT and boot. See if you can grab a dmesg from adb,
Code:
adb shell dmesg > dmesg.txt
Will dump the dmesg.txt file to where ever you're running that command from. You can change the path on the right side of that command if you want to direct the output to a different folder.

i cant get droid explorer to find me device =/
scratch that, it picked up a "00000" that seems to be it.

new data.img, kernel and module from 1253. loads home screen with the google search bar and the android and it just froze up, performing soft reset, putting on the working modules and retrieving the logs for you.

done!
see attachment

is that all you need?
What should I do next?

ryannathans said:
is that all you need?
What should I do next?
Click to expand...
Click to collapse
The only log in there is from Sat Oct 23 02:21:48 CEST 2010. Can you get any adb interface running while it's booting...? Have you traced it down to which kernel is the one that fails to boot?

arrrghhh said:
The only log in there is from Sat Oct 23 02:21:48 CEST 2010. Can you get any adb interface running while it's booting...? Have you traced it down to which kernel is the one that fails to boot?
Click to expand...
Click to collapse
any kernel after november 2010 just freezes after booting (something to do with the panel?)
Trying a different 'package' and hopefully I can get the logs.
this time im using: http://forum.xda-developers.com/showthread.php?t=933177
okay is seems to be working -.- its modules-2.6.27.46-01232-gb7033df
ill try and load 1253

Ok, so start at 1232 and work your way towards 1253 - which kernel stops booting? I can't troubleshoot this as 1253 works fine on mine and most devices .

arrrghhh said:
The only log in there is from Sat Oct 23 02:21:48 CEST 2010. Can you get any adb interface running while it's booting...? Have you traced it down to which kernel is the one that fails to boot?
Click to expand...
Click to collapse
arrrghhh said:
Ok, so start at 1232 and work your way towards 1253 - which kernel stops booting? I can't troubleshoot this as 1253 works fine on mine and most devices .
Click to expand...
Click to collapse
can you point me to where I can download 1232 - 1253? appreciate the help so far
EDIT: I think i found them.
Trying now.
EDIT:
01245 - PASS
01246 - PASS
01250 - PASS

perhaps it was my 'noobiness' previously causing it to crash, I cant seem to reproduce it anymore -.-' I think i was using a different zImage to the Modules version
using FRX04, latest rootfs, my FN button on the keyboard is an @ and there is no other button that works as FN.
keyboard layout in startup.txt is set to rhod110
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ryannathans said:
perhaps it was my 'noobiness' previously causing it to crash, I cant seem to reproduce it anymore -.-' I think i was using a different zImage to the Modules version
using FRX04, latest rootfs, my FN button on the keyboard is an @ and there is no other button that works as FN.
keyboard layout in startup.txt is set to rhod110
Click to expand...
Click to collapse
Heh, it happens.
Have you tried F22's new rootfs? Adds all sorts of interesting keys, read thru his thread. I don't think the RHOD110 layout is in any other rootfs TBH...

arrrghhh said:
Heh, it happens.
Have you tried F22's new rootfs? Adds all sorts of interesting keys, read thru his thread. I don't think the RHOD110 layout is in any other rootfs TBH...
Click to expand...
Click to collapse
ahh noo. still same problem with it
thanks anyway
EDIT: everything's working sweet now that I had a chat with F22 and we got rhod110 support now

I faced same issue, it froze while installing, or so it seems. then one fine day, i accidently clicked on screen for 2-3 secs with stylus and then ... the screen moved one line up showing some message related to 'point 2' or in other words caliberation. My guess was it was waiting for caliberation and i thought it froze. Not sure of this is the same case with yours, but you can try it once. I clicked for 2-3 seconds on top-left corner first, then top-right, bottom-left, bottom-right, and lastly center of screen. After that everything worked properly.

[Q] Can't overclock?

Anytime I try to put the acpuclock.oc_freq_khz=672400 command line in my startup.txt I get an error message along the lines of "acpuclock is not a recognized command" or something similar. Haret still runs and Android still boots but the phone is still locked at the default clock speed.
Any ideas? I'm running FRX07 with the latest zImage and whatever rootfs came with FRX07.

benutne said:
Anytime I try to put the acpuclock.oc_freq_khz=672400 command line in my startup.txt I get an error message along the lines of "acpuclock is not a recognized command" or something similar. Haret still runs and Android still boots but the phone is still locked at the default clock speed.
Any ideas? I'm running FRX07 with the latest zImage and whatever rootfs came with FRX07.
Click to expand...
Click to collapse
Are you putting that acpuclock command in the cmdline section (between the quotes)? I doubt it, it does not go on its own line. It goes in the cmdline...
Paste your startup.txt if you want me to show you.

arrrghhh said:
Are you putting that acpuclock command in the cmdline section (between the quotes)? I doubt it, it does not go on its own line. It goes in the cmdline...
Paste your startup.txt if you want me to show you.
Click to expand...
Click to collapse
Herp derp. I was putting it on my own line. Thanks for the help.