hi all,
I'm actually trying many times to install Andoird on my Touch Pro. but I just got stuck whenever I run Haret then it freezes.
I try to read through many posts here but it seems there's no similar situation. and I even did exact same thing like the Youtube Tutorial did. But I still got it failed.
Mine is:
RAPH100
OS Version: 5.2.23016
ROM: 5.00.000.00 CHT
Radio: 1.13.25.55
Could anyone help me please?? thanks a million.
Cheers
What does your startup.txt say?
I've got a 110 and I had to enter the following lines at the beginning of it:
set ramsize 0x10000000
set ramaddr 0x10000000
ragingclue said:
What does your startup.txt say?
I've got a 110 and I had to enter the following lines at the beginning of it:
set ramsize 0x10000000
set ramaddr 0x10000000
Click to expand...
Click to collapse
+1, post your startup.txt if adding those lines don't fix it. There was an issue with the latest startup's, missing those lines across the board as far as I'm aware. I just reverted to an old startup.txt.
.
superal1980 said:
hi all,
I'm actually trying many times to install Andoird on my Touch Pro. but I just got stuck whenever I run Haret then it freezes.
I try to read through many posts here but it seems there's no similar situation. and I even did exact same thing like the Youtube Tutorial did. But I still got it failed.
Mine is:
RAPH100
OS Version: 5.2.23016
ROM: 5.00.000.00 CHT
Radio: 1.13.25.55
Could anyone help me please?? thanks a million.
Cheers
Click to expand...
Click to collapse
some thing happened to me the problem was i was using the CMDA touch pro start up text and not the gsm
this is my start up text for a fuze with a touch pro kyebord
PHP:
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
Hello.
I have a problem when i install android on my htc touch pro.
I manage to install it but when to start it he remains at the wellcome movie.
What i need to do ? I've used search on this forum but didn't find any answer or question on this.
Thanks
Try blasting out your data.img and booting again.
If this doesn't work, run a build from 3.31 or older, and drop your data.img from that build in to the folder for the new build.
ragingclue said:
What does your startup.txt say?
I've got a 110 and I had to enter the following lines at the beginning of it:
set ramsize 0x10000000
set ramaddr 0x10000000
Click to expand...
Click to collapse
The 110 that's the one with the blue keys on the keyboard right?
Do you know what the rest of the start up code is? I've been searching and the only one i've found is the one posted above.
Try using the CAB installer mentioned in the original post. Had simular issues installing on my WM 6.5 modded ATT Fuze. CAB version works everytime.
Time
How long should it take to install android?
How long to install...? It's just copying files to your SD card so a few minutes maybe?
Now how long to boot is another story. If you're getting a boot loop, try updating your rootfs. If that doesn't help, delete your data.img and try haret.exe. If you're still stuck, post back here what is hanging you up.
I am stuck at the set up. It is as though my screen does not work. It keeps saying to touch droid to begin and everytime I try to touch it it goes into emergency call or language (the two bottom options). What should I do?
Sounds like you have a bad calibration. Delete the ts-calibration file at the root of SD (or wherever you launch haret.exe from) and try to boot again. Watch the boot process! There's a calibration section that if you don't do it, the touchscreen won't work properly.
Sorry for my English.
I tried all the rom, all, and no work for me either. Use two ext2 partitions for data and system. Using the latest zimage, haret and initrd 2.6.32, tested all options with default.txt
When I install, the first time, everything is right, but the second time I boot android, everything goes wrong. After installing, wait 15 minutes before touching anything.
What else I can try?
WM 6.1
radio 1.70.19.09
SD 8GB class6 with fat32, ext2, ext2, linuxswap
Thanks.
Go to NAND ?
vellowax said:
Go to NAND ?
Click to expand...
Click to collapse
Now prefer haret.
My bootlog.txt
** /dev/block/mmcblk0p1
** Phase 1 - Read FAT (compare skipped)
Attempting to allocate 7032 KB for FAT
** Phase 2 - Check Cluster Chains
** Phase 3 - Checking Directories
** Phase 4 - Checking for Lost Files
Free space in FSInfo block (1093801) not correct (1078495)
Fix? yes
Next free cluster in FSInfo block (640022) not free
Fix? yes
1961 files, 119676 free (1078495 clusters)
sh: 2: unknown operand
e2fsck 1.38 (30-Jun-2005)
e2fsck: while determining whether /dev/block/loop1 is mounted
/dev/block/loop1: clean, 710/65536 files, 97021/262144 blocks
e2fsck 1.38 (30-Jun-2005)
e2fsck: while determining whether /dev/block/loop0 is mounted
/dev/block/loop0 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
/dev/block/loop0: 625/65536 files (12.8% non-contiguous), 19711/262144 blocks
My default.txt
#alloctest 0x2000
set RAMSIZE 0x08000000
set RAMADDR 0x10000000
set FBDURINGBOOT 0
set MTYPE 1553
set KERNEL zImage
set initrd initrd.lzma
#
# The following kernel parameters are useful
# ppp.nostart - Set ppp.nostart=1 to disable starting the ppp connection on boot
# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller
# pm.sleep_mode - The mode used when the phone is off
# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,
# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt
# Default is 1, use 1 for best power savings
# board-htckaiser.panel_type - Panel type used to power the panel off and on
# 0=Don't power off the panel (Default)
# 1=Sony 2=Topoly 3=Topoly (probably just the same as 2)
# lcd.density - Defaults to 160, 128 shows more on screen
#
set cmdline "ppp.nostart=0 pm.sleep_mode=0 lcd.density=120 mddi.width=240 mddi.height=320 no_console_suspend board-kaiser-keypad.atttilt=0 board-htckaiser.panel_type=2 hw3d.version=1 board-kaiser-battery.battery_capacity=2160 board-kaiser-battery.haret_divisor=2200 board_htckaiser.pmem_size=4 board_htckaiser.pmem_adsp_size=1 clock-7x00.a11=400"
boot
Please explain what goes wrong on the second boot.
What is showing on the screen at the end?
Everything you posted looks right, as far as I can see.
n2rjt said:
Please explain what goes wrong on the second boot.
What is showing on the screen at the end?
Everything you posted looks right, as far as I can see.
Click to expand...
Click to collapse
Thanks for your help.
On the second boot every few minutes installation screen appears (the rays forming X) and finally the screen turns white and kaiser does not respond and I have to go back to WM.
Can be the problem have installed this WM rom?
I can install android in NAND if that solve my problems, I like it android.
Sorry for my English.
Maybe when you turned off after the first boot, the filesystem was not cleanly dismounted. It might help to clear the dalvik cache during the boot, using the boot menu. To open the boot menu, push the middle of the screen when Linux starts to boot. Choose the option to clear the dalvik cache. When that finishes, choose the "Exit" option. I don't know, but it might help.
NAND will give fewer problems, but still has problems dismounting the filesystem cleanly when shutting down.
n2rjt said:
Maybe when you turned off after the first boot, the filesystem was not cleanly dismounted. It might help to clear the dalvik cache during the boot, using the boot menu. To open the boot menu, push the middle of the screen when Linux starts to boot. Choose the option to clear the dalvik cache. When that finishes, choose the "Exit" option. I don't know, but it might help.
NAND will give fewer problems, but still has problems dismounting the filesystem cleanly when shutting down.
Click to expand...
Click to collapse
Thanks, I'll do it again (clear dalvik cache), I tried it once after reading a lot, but did not help.
Clear dalvik cache but problems persist, now the kaiser after working a few hours, as before, the screen stays black and does not respond, back to WM.
At least now do not see the X and white screen. If everything is like most people, why do not I have the same results?
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.
trying to boot custom kernel (tried android and LK)
want to boot into native debian (irregular-expression.com/?p=30 - cant find his xda post)
-have changed cmdline in menuconfig
-have changed 'type' of cmdline (override, append, static)
-have used fastboot in combo with above to try to change
-changed root=/dev/block/mmc***, root=/dev/mmc***
-tried to boot to system (mmcblk0p10) and sdcard (mmcblk0p12)
fastboot -c 'root=/dev/mmcblk0p12 rw rootfs=ext4 init=/sbin/init rootwait noinitrd' boot zImage
i either get a hang at the google logo
or
the fone vibrates and reboots to the boot partition
can't find anything, don't know what that would be called, or how to tell what i'm doing wrong
i know rootfs doesn't mount because i don't have so much as a dmesg log in /var/log - or any other logs for that matter
edit : noticed...clearly boots LK to cyan fine...so...unless someone wants to help, can prolly close this
aug 17 edit:
well...it still follows the same title so...?
got fb console output...but i don't know enough about android and can't find anything to make sense of the init
basically edited stock initrd and changed init.rc to 'chroot /newroot /sbin/init' into my mounted debian...
get an error "Unable to open persistent property directory /data/property errno: 2 - Failed to bind socket 'property_service': No such file or directory" ... "Kernel panic - not syncing: attempting to kill init" ..."reboot in 5 seconds"
is there a better/easier way to boot into debian? as far as I can tell kernel cmdline init= doesnt do anything. can't get output and i'm assuming no /dev gets messed with at all when i don't use a modified android init with ueventd and its setup
thanks for any help
read something that says questions like these belong in dev-forum...but not having 10 post i cannot do that...
so...bump
been looking up different devices and their chrooting tricks and w/e i can find...i really don't understand. my chromebook boots gentoo fine, swapped the kernel and some modules/firmware around - works...can't get anything except initrd to print anything & make /dev.
edit:
phew...ok...some BT5(backtrack) img/initrd i found will mount my internal sdcard for root...mkdir zzz gives me a directory on /data.
so i have /dev...but no fb or display
W00T
so i found
http://forum.xda-developers.com/showthread.php?t=1075054
got the bt5kern img and extracted its initramfs
had static udev and other boot progz
made sure to compile devtmpfs in kernel (drivers > generic drivers)
waited longer than i usually would
got to gdm
now i just need to get the touchscreen working...every time i touch it goes back to tty and then gdm
bl00dy said:
W00T
so i found
http://forum.xda-developers.com/showthread.php?t=1075054
got the bt5kern img and extracted its initramfs
had static udev and other boot progz
made sure to compile devtmpfs in kernel (drivers > generic drivers)
waited longer than i usually would
got to gdm
now i just need to get the touchscreen working...every time i touch it goes back to tty and then gdm
Click to expand...
Click to collapse
Look at the xorg log, you should be able to see it now. What xorg version is that?
a manta sent this.
beekay201 said:
Look at the xorg log, you should be able to see it now. What xorg version is that?
a manta sent this.
Click to expand...
Click to collapse
i don't remember what version. i just copied my chromebook rootfs to my fone, so i gotta add evtouch or something. haven't had nix on a touchscreen before now that i think about it.
good idea, i'll look at the log and see if it's some other reason it's respawning.
edit:
Code:
(EE)
(EE) Backtrace:
(EE)
(II) evdev: barometer: Close
(II) UnloadModule: "evdev"
(EE) BUG: triggered 'if (inSignalContext)'
(EE) BUG: /var/tmp/portage/x11-base/xorg-server-1.13.1/work/xorg-server-1.13.1/os/log.c:588 in LogVHdrMessageVerb()
(EE) Warning: attempting to log data in a signal unsafe manner while in signal context.
Please update to check inSignalContext and/or use LogMessageVerbSigSafe().
The offending header and log message formats are:
%s: %s: Close
(EE)
(EE) Backtrace:
(EE)
(WW) Warned 3 times about sigsafe logging. Will be quiet now.
(II) evdev: tuna-gpio-keypad: Close
(II) UnloadModule: "evdev"
(II) evdev: proximity: Close
(II) UnloadModule: "evdev"
(II) evdev: lightsensor-level: Close
(II) UnloadModule: "evdev"