Related
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...
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.
Posts have been re-ordered, Look above.
cLK (source code)
Click to expand...
Click to collapse
Stable
Legacy
ppp wrappers (source code)
Click to expand...
Click to collapse
0.8b4
0.8b5
Drivers and Utilities
Click to expand...
Click to collapse
The following tools are provided here, for linux(ubuntu 64bit binaries), windows and mac:
adb
fastboot
mkbootimg (not windows)
unpackbootimg (not windows)
FAQ
Click to expand...
Click to collapse
Q: What is cLK?
A: cLK is a homebrew bootloader which will allow you to boot into android directly on your windows mobile phone.
Q: Is it better then magldr ?
A: This question is heavily dependent on the user and his needs however the following points might help you make a better choice:
magldr is capable of booting Windows Phone 7.x.
cLK boots a tad faster than magldr as it does not wait for radio processor on boot.
cLK is open source so you can give/take what you want and learn stuff while doing so.
cLK has Partitioning tools inbuilt, you'll never have to hook your phone to a computer ever again, just for flashing a rom!
cLK has recovery inbuilt for users with broken usb port.
cLK supports off-mode charging
Known issues
Click to expand...
Click to collapse
RMNET does not work.
Related projects
Click to expand...
Click to collapse
Multi-boot manager
Off-mode alarm
Custom Image Update Utility
cLK changelog
Click to expand...
Click to collapse
1.5.x (Experimental)
19/Jan/2012 - FIRST alternative suggestion
Link
25/Jan/2012 - UPDATE #1
Link
26/Jan/2012 - UPDATE #2
New format option leaves recovery partition untouched. So yeah, no pc needed after formatting !
Basically it erases all the other existing partitions one by one. At the end recovery partition is intact so we can enter recovery interface and flash our preferred rom.
Set userdata as 'auto-size' partition . So default partition table is:
"recovery:5"
"misc:1"
"boot:5"
"userdata:0"
"system:150"
"cache:5"
Click to expand...
Click to collapse
Revised the 'Enable/Disable ExtROM' option.
If enabled it will automatically be used for 'cache' partition .
If disabled 'cache' will automatically return to 5MB size .
28/Jan/2012 - UPDATE #3
Cleaned some code that was not used .
Added option to convert 'auto-size' partition to 'fixed-size' .
Added option to set a partition as 'auto-size' if one doesn't already exist (just decrease its size to zero).
Small fixes to some features I previously added.
29/Jan/2012 - UPDATE #4
Revised the 'rearrange partitions' menu.
We cannot move recovery , cause then we'll have to re-flash it via pc .
How it works:
Lets say we have this layout:
1."recovery"
2."misc"
3."boot"
4."userdata"
5."system"
6."cache"
Click to expand...
Click to collapse
And we want to change it to:
1."recovery"
2."misc"
3."boot"
4."cache"
5."system"
6."userdata"
Click to expand...
Click to collapse
Enter 'REARRANGE PARTITIONS'
Select 'userdata' -> Scroll DOWN to 6 -> Select it
(You should see the change in the order of the partitions immediately! Don't worry nothing is committed. If you exit and re-enter SETTINGS menu everything will be reset.)
Select 'COMMIT CHANGES' -> Select 'APPLY'
(Of course you still have the option to re-order and re-size the partitions via pc, if the default layout doesn't fit your needs)
WARNING ! If you change the order of the partitions then have in mind that the same /dev/block/mtdblock<n>, n=0,1,2,... point to different mount points.
Clean up some code
01/Feb/2012 - UPDATE #5
Added new info when booting
After the partition table you should see a list with the existing bad blocks IF ANY. (CONFIRMED)
IF there are any bad blocks inside recovery,misc,boot,sboot,cache THEN they will be auto-re-sized by adding 1MB to each one.
Changed some output messages
02/Feb/2012 - UPDATE #6
Changed the function regarding auto-resizing:
IF there are any bad blocks inside recovery,misc,boot,sboot,cache THEN 1MB per 1bad block will be added to each partition with bad block(s). (CONFIRMED)
Changed some output messages
Default partition table is:
"recovery:5"
"misc:1"
"boot:5"
"system:150"
"userdata:0"
"cache:5"
Click to expand...
Click to collapse
06/Feb/2012 - UPDATE #7
Minor fixes/changes
Changed some output messages
08/Feb/2012 - UPDATE #8
If you press&hold the middle [MENU] button during (re)booting you can immediately boot android from sdcard(emmc), assuming that you have flashed sboot partition with the appropriate image and you have the required folder in the root of your sdcard.
Process of having dual boot(without using pc):
Prerequisite: The folder(usually named 'Android' or 'ics') with the SD version of Android exists in the root of your sdcard
Boot the device in cLK pressing [BACK] button, having the sdcard inserted
Go to MAIN MENU/SETTINGS - Select ADD sBOOT
Select BOOT RECOVERY from MAIN MENU
Select 'install zip from sdcard' and use something like this(this is an example) flash_sboot.zip
Select 'reboot system now' and press&hold [MENU] button to directly boot Android (emmc)
After each change(resize/rearrange parts, add/remove sboot, enable/disable ExtROM) is committed there is no longer the need to reboot. clk will just auto return to main menu, and from there you can select your next action.
14/Feb/2012 - UPDATE #9
Changed cpu speed to 998MHz.
Added option to show/hide info(ptable and bbtable) at start-up under MAIN MENU/INFO.
If you invert screen colors, the change will remain after rebooting.
The speed of reading/writing or erasing is improved a bit.
Cleaned up some code.
22/Feb/2012 - UPDATE #10
Removed showing bad block info during startup. Bad blocks can be checked from SETTINGS/PRINT BAD BLOCK TABLE(if any bad blocks exist).
Added chipset info in header.
Cleaned up more unused code.
13/Apr/2012 - UPDATE #11
Ported Rick's latest commit.
Added ability to triple boot. It works like secondary boot 'sboot'; you can add a tertiary boot partition named 'tboot' and the rest work the same.
Added "USB" mark for usb detection; if your device is connected to the pc via usb you should see 'USB' at the bottom of the screen.
Cleaned up more unused code. (EXPERIMENTAL)
06/Jun/2012 - UPDATE #12
Code:
[U]Default partition table:[/U] recovery=5,misc=1,boot=5,system=150,userdata=0,cache=5
[U]Included recovery:[/U] CWM Recovery Touch Beta 8 Release Candidate 1
[U]ExtRom:[/U] Disabled
Added CID, IMEI , BT Mac Addr and WiFi Mac Addr under Device Info (Getting WiFi Mac doesn't work correctly ).
Revised the 'Enable/Disable ExtROM' option.
If enabled, a partition named "null" (which will be only 1 block in size) will be created after 'userdata' and the rest 191 blocks will automatically be used for 'cache' partition .
If disabled, 'cache' will automatically return to 5MB size .
Added ability to resize partitions by giving size in blocks too . NOT TESTED
Code:
fastboot oem part-resize name:size:b
where size is in blocks
i.e. fastboot oem part-resize misc:9:b => will resize 'misc' part to 9 blocks
Added ability to add partitions by giving size in blocks too . NOT TESTED
Code:
fastboot oem part-add name:size:b
where size is in blocks
i.e. fastboot oem part-add misc:8:b => will add 'misc' part with size 8 blocks (= 1MB)
Added option to enable/disable usb detection ("USB" mark at the bottom of the screen if device connected to pc) .
Changed version to LK_1.5black to avoid confusion regarding latest version of main cLK.
21/Jun/2012 - UPDATE #13
Code:
[U]Default partition table:[/U] recovery=5,misc=1,boot=5,system=150,userdata=0,cache=5
[U]Included recovery:[/U] CWM Recovery Touch Beta 8 Release Candidate 1
[U]ExtRom:[/U] Disabled
cLK can now be updated through fastboot* using a 'proper' image file**
*:In order to update use :
Code:
fastboot flash lk lk.img
**:In order to create the lk.img, use nbgen :
Code:
nbgen -b:lk.bin -o:lk.img
-Note that the partition table will not be overwitten.
-Also you can update clk from recovery or from android.
Bug fixes
20/Jul/2012 - UPDATE #14
Code:
[U]Default partition table:[/U] recovery=5,misc=1,boot=5,system=150,userdata=0,cache=5
[U]Included recovery:[/U] CWM Recovery Touch Beta 8 Release Candidate 1
[U]ExtRom:[/U] Disabled
Added option to reset ANY settings you have modified.
(RESET SETTINGS under SETTINGS MENU = 'fastboot oem reset' ,previously cmd was 'fastboot oem format_vptable')
Fixed errors caused by some partition changes, so it should be stable now!
26/Jul/2012 - UPDATE #15
Code:
[U]Default partition table:[/U] recovery=5,misc=1,boot=5,system=150,userdata=0,cache=5
[U]Included recovery:[/U] CWM Recovery Touch Beta 8 Release Candidate 1
[U]ExtRom:[/U] Disabled
Ported some commits from LK mainline.
(https://github.com/travisg/lk/commit/a95146ec5aef73b49e37045f96a26c10431d37d4,
https://github.com/travisg/lk/commit/6f28039866ddeb272e8660dd89a34208fc988896,
https://github.com/travisg/lk/commit/fc20e231dbabecb612343aa6784705086844052f,
https://github.com/travisg/lk/commit/ac8b88eefe9067fb0881e15435dce1bbc797d71b,
https://github.com/travisg/lk/commit/836375f779308d868515d43fbd7979f07874b6de,
https://github.com/travisg/lk/commit/c2a298970d74dca7c7d738b5e7e3ec04bee00984,
https://github.com/travisg/lk/commit/c32135b7e5972ec77f0883f55dd8b866b3c07c0d,
https://github.com/travisg/lk/commit/18559782b3335682310fdfd77b4ccb1563982d2a,
https://github.com/travisg/lk/commit/06d781f162ff3b35f806de59d7f0bf5bf87fdabd,
https://github.com/travisg/lk/commit/4bea031527e6d0153e61b7ffd4696df8a30f006c)
2nd attempt at fixing errors caused by some partition changes.
Edited nbgen so that it is possible to add recovery as a second partition.
11/Sep/2012 - UPDATE #16
Code:
[U]Default partition table:[/U] recovery=5,misc=1,boot=5,system=150,userdata=0,cache=5
[U]Included recovery:[/U] CWM Recovery Touch Beta 8 Release Candidate 1
[U]ExtRom:[/U] Disabled
Added option to set the default boot partition. At start default is 'boot', but you can change it.
Added option to show or not a MULTIBOOT MENU at startup. Default behavior is to be hidden.
The MULTIBOOT MENU will show any existing boot partitions
and will boot from the default selection in 10s if you don't select something else.
Code:
supported_boot_partitions[] =
{
{"boot",},
{"sboot"},
{"tboot"},
{"vboot"}, //no uboot :D
{"wboot"},
{"xboot"},
{"yboot"},
{"zboot"},
{""},
};
As you see we have the primary boot + 7 extra boot partitions.
However there is NO change to the MAX_NUM_PART (max number of the partitions) which is 12, so you can eventually add 5 (of the 7 extra) different boot partitions,
(unless you don't have a NAND installation and you have deleted 'system' and 'userdata' so you can use all 7 extra, but I think it will be a mess ).
Added ability to control menu navigation through fastboot:
Code:
'fastboot oem key 8' ==> KEY_VOLUMEUP
'fastboot oem key 2' ==> KEY_VOLUMEDOWN
'fastboot oem key 5' ==> KEY_SEND
'fastboot oem key 0' ==> KEY_BACK
Removed option to enable/disable usb detection ("USB" mark at the bottom of the screen if device connected to pc) . By default it will be disabled .
18/Sep/2012 - UPDATE #17
Code:
[U]Default partition table:[/U] recovery=5,misc=1,boot=5,system=150,userdata=0,cache=5
[U]Included recovery:[/U] CWM Recovery Touch Beta 8 Release Candidate 1
[U]ExtRom:[/U] Disabled
acpuclock that Rick wrote and I managed to break, works again. So you have a new option under SETTINGS: SET MAX/DEFAULT CPU FREQ.
Changed the menus. Rearranged SETTINGS and INFO and their entries.
Fixed the charging while off problem that the last version had. Plus you don't need to unplug the cable in order to turn your phone on. Just press once the [CALL] button.
Fixed errors regarding partition rearrangement.
Also from that menu you can remove 'system' and 'userdata' from the partition table, by setting their order to 0. This will give you the chance to add 2 more extra boot partitions. If you went crazy and did that, but something doesn't work well, and you want back 'system' and 'userdata' you just have to RESET SETTINGS and the partition will return to default.
Fixed some errors regarding add/remove %x%boot.
Changed how the countdown in multiboot menu works. If you interact then the countdown is canceled.
Added option whether to fill the bad block table at startup or not, FILL/SKIP FILLING BBT @ STARTUP under SETTINGS.
Remember the option PRINT BAD BLOCK TABLE? If you don't select to FILL BBT @ STARTUP, then you won't see a BAD BLOCK TABLE because it will not be created. In simple words this means a little faster boot into cLK menu.
At a (re)boot event the way LK is determining what to do is:
First checks if any key was pressed, then checks the boot reason.
For example, if you selected 'Reboot to bootloader' from android but in the process you want to boot to recovery, you can just press&hold the [HOME] button until the phone vibrates.
Removed the function regarding auto-resizing small partitions which have bad blocks.
Added a fading animation before booting any kernel or recovery.
18/Sep/2012 - UPDATE #18
Code:
[U]Default partition table:[/U] recovery=5,misc=1,boot=5,system=150,userdata=0,cache=5
[U]Included recovery:[/U] CWM Recovery Touch Beta 8 Release Candidate 1
[U]ExtRom:[/U] Disabled
Fixed messed up menus if more than one extra boot partition exists.
20/Sep/2012 - UPDATE #19
Code:
[U]Default partition table:[/U] recovery=5,misc=1,boot=5,system=150,userdata=0,cache=5
[U]Included recovery:[/U] CWM Recovery Touch Beta 8 Release Candidate 1
[U]ExtRom:[/U] Disabled
Fixed messed up menus if the order of the extra boot partitions is changed from default.
24/Oct/2012 - UPDATE #20
Code:
[U]Default partition table:[/U] recovery=6,boot=5,misc=1,system=150,userdata=0,cache=5
[U]Included recovery:[/U] CWM Recovery Touch Beta 8 Release Candidate 1
[U]ExtRom:[/U] Disabled
Increased default size of 'recovery' partition to 6MB and changed layout.
Removed fading effect.
Added back option to enable/disable usb detection ("USB" mark at the bottom of the screen if device connected to pc).
Some platform code changes.
29/Oct/2012 - UPDATE #21
Code:
[U]Default partition table:[/U] recovery=6,boot=5,misc=1,system=150,userdata=0,cache=5
[U]Included recovery:[/U] CWM Recovery Touch Beta 8 Release Candidate 1
[U]ExtRom:[/U] Disabled
Leds work. If you boot into cLK menu and your device is connected to a pc the led will go green. If not connected the led will stay turned off.
Screen brightness can be adjusted. Added option under SETTINGS. The selected level will be the default at each boot.
Entering cLK menu is slightly slower than before.
Added an option to change UDC settings at will. This is an attempt to solve any usb issues you might have (fastboot errors) without having to re-compile cLK's binary with different udc settings. 1st set is the default one. 2nd is the set that cLK used to have initially (1.5_rc1). 3rd is not working for me either, but left it for testing. So lets see how this goes...
When in cLK menu you can select items with the [MENU] button too(added this for those with broken [CALL] button).
11/Nov/2012 - UPDATE #22
Code:
[U]Default partition table:[/U] recovery=6,boot=5,misc=1,system=150,userdata=0,cache=5
[U]Included recovery:[/U] CWM Recovery Touch Beta 8 Release Candidate 1
[U]ExtRom:[/U] Disabled
Changed some options under SETTINGS.
Added option to use inbuilt off-mode charging under SETTINGS/SET DEFAULT OFF-MODE CHARGING. From that menu you can select it (option USE INBUILT OFF-MODE CHARGING) and try it out.
If using inbuilt off-mode charging the device wakes up if you press POWER [button].
This is an experimental feature! Only tested with original battery and charger.
High Voltage (as measurement) is set to 4.2 V. Use at your own risk! Otherwise stick to the default way of charging (option USE RECOVERY'S OFF-MODE CHARGING).
Usb detection function changed (option under SETTINGS/ENABLE USB DETECTION). "USB" mark at the bottom of the screen if device connected to pc is replaced by turning led on/off if connected/disconnected.
Added some code as an experiment for a potential off-mode alarm application.
More info in this thread.
Warning : I didn't know java or how to use eclipse and make an android app. Seriously, I still don't. But after some days I managed to write this application mostly because I wanted to know if this idea was possible. So consider it as an example. Any criticism accepted. I just hope that someone may find it useful and make the best out of it.
19/Nov/2012 - UPDATE #23
Code:
[U]Default partition table:[/U] recovery=6,boot=5,misc=1,system=150,userdata=0,cache=5
[U]Included recovery:[/U] CWM Recovery Touch Beta 8 Release Candidate 1
[U]ExtRom:[/U] Disabled
Added option to set the voltage threshold for inbuilt off-mode charging under SETTINGS. It can be set from 3.8 to 4.2 V.
Changed the code for the off-mode alarm application based on Rick's suggestions. In order to work you need to have a patched kernel like this one. More info on off-mode alarm in this thread.
Added some code for another project, a multiboot android app. More info here.
Small fixes.
23/Nov/2012 - UPDATE #24
Code:
[U]Default partition table:[/U] recovery=6,boot=5,misc=1,system=150,userdata=0,cache=5
[U]Included recovery:[/U] (a)CWM Recovery Touch Beta 8 Release Candidate 1 Or (b)TWRP 2.2.2.0 with new zImage (patched tytung's latest GB-kernel)
[U]ExtRom:[/U] Disabled
Voltage threshold for inbuilt off-mode charging can be set from 3.7 to 4.2 V.
First attempt to fix problem with suspend mode.
Each included recovery is edited to fix the problem with the limitation of total mtd partitions(before edit the max was 11 - now I've set it to 20)
1.5.0 (Stable)
Added GUI (Graphical User Interface)
Added Flashlight support
Added partitioning support
Added on device paritioning support
Added support for device poweroff from device itself
Added support for "Use Last 24MB NAND"
Added stable CWM recovery in the NBH for those with broken USB port
Added support for Linux kernel fonts in lk framebuffer driver.
Added Power Down support in bootloader.
Few cherry picks from mainline lk at newos.org and codeaurora.org
Few bug fixes
This is not an exhaustive list of changelog, it will be updated in the coming days.
1.4.0.1 (Legacy)
Added clk=xxx as part of the /proc/cmdline
1.4
nbgen for making .nb file
1.3.3
small fix on get_boot_reason
cwm off charge fully implemented, inspired by dan1j3l's code
1.3.2
ROMHDR base addr is spl virtual 0x80000000 = 11800000 physical, LK will relocate to correct address (MEMBASE)
save reboot reason at 0x2FFB0000 (ramconsole - 0x1000 (PAGE_SIZE)) and @0x2FFB0004 XOR 0x004b4c63 (cLK signature)
added oem cmd to fastboot and oemcmd.bat for PC. supported commands are:
dmesg - kernel debug messages
smesg - spl messages
pwf addr len - dump memory
set[c,w,s] addr value - set char(1byte), word(4 byes), or string
Linux Kernel Patches
Click to expand...
Click to collapse
17.03.2011
small fix on get_boot_reason
cwm off charge fully implemented, inspired by dan1j3l's code (http://gitorious.org/htc-hd2-android.../master/cmon.c)
15.03.2011
kernel patch to save reboot reason so is available on bootloader
old patched in zip as pushed in most branches
25.02.2011
CWM patch for charging, unpatched CWM code is not properly reading kernel cmdline because /proc/cmdline file size is always 0 resulting in a always empty cmd line. I also changed the code to wait for key press then reboot phone to normal android.
20.02.2011
cLK_power_clllapse patch adds detection of cLK to kernel and puts the reset vector at 0x11800000 where cLK will jump (+4) at power_collapse_exit
off_mode_charging just prevents the kernel from BUG() if off mode charging and panel is off ( and not detectable )
both of this patches are compatibile with current SD and magldr builds, please push them to your git trees
Credits
Click to expand...
Click to collapse
- Cedesmith
- Martijn Stolk
- Cotulla
- seadersn
- stirkac
- Dan1j3l
- xdmcdmc
- arif-ali
- kokotas
[07 Jun 2011][BOOTLOADER]+[RECOVERY]cLK v1.4.0.1
Contents
Post 6: cLK compile HowTO (Linux)
Post 7: cLK compile HowTO (Windows)
Post 8: ROMs, HowTOs, Utilities (created by others)
Post 9: convert magldr ROM to cLK HowTO
Source code
cLK GIT
wrapper GIT
Drivers and Utilities
The following tools are provided in here, for linux(ubuntu 64bit binaries), windows and mac; thanks to Segnale007, who compiled them for mac.
adb
fastboot
mkbootimg (not windows)
unpackbootimg (not windows)
Changelog
blah blah blah
cLK compile Howto (Linux)
You need to install some packages to get things working, and the commands below will install the dependencies
Ubuntu:
Code:
sudo apt-get update
sudo apt-get install gcc make git wget unzip zip libc6-dev-amd64 libc6-dev
Fedora:
Code:
yum install gcc make git wget unzip zip
Open a terminal session, and create a directory called clk, change directory to clk, and run the following command to get the cLK git repository
Code:
git clone git://github.com/cedesmith/cLK.git
then run the following commands to download the codesourcery toolchain, and set-up environment
Code:
wget http://www.codesourcery.com/sgpp/lite/arm/portal/package5353/public/arm-none-eabi/arm-2009q3-68-arm-none-eabi-i686-pc-linux-gnu.tar.bz2
tar xvfj arm-2009q3-68-arm-none-eabi-i686-pc-linux-gnu.tar.bz2
export PATH=$HOME/clk/arm-2009q3/bin:$PATH
To change your values for cache, system, boot etc... you need to change the following files in the the $HOME/clk/cLK directory
lk/target/htcleo/rules.mk
line 8 - system
lk/target/htcleo/init.c
line 28 - misc
line 32 - recovery
line 36 - boot
line 43 - cache
Now you can compile by running the following command
Code:
cd cLK
./compile clean
Now your RUU_signed.nbh will be located in the following folder
Code:
bin/RUU_signed.nbh
Hopefully that should work.
Anyone have any issues, let me know, I will amend the howto
cLK compile Howto (Windows)
OK, two ways, first way is to do everything yourself, so follow the steps below, i.e. start from Step 1.
If you want the easy way, then download the following zip file from the llink, then unzip it, and then double click "setup.bat". This automatically do all the steps listed below in bullet points
cLK_win.zip
* install cygwin, and all dependancies
* download cLK from git
* download codesourcery toolchain
* download yang
and now skip to Step 2
Step 1: Prepare environment
Download, the following file, and execute it
http://www.cygwin.com/setup.exe
Click Next
Click "Install from internet" and click Next
Click Next (to accept the default directory to install)
Click Next (to accept the default directory for local Package directory)
Click "Direct Connection", and click Next
Select a "local mirror", and click Next
Now in the search bar, you need to search for the following things to install
gcc
make
git
wget
zip
unzip
Once selected click Next to continue, and Finish
Now you will have an icon for Cygwin on the desktop, double-click this
now in the window that appears, run the following command
Code:
git clone git://github.com/cedesmith/cLK.git
then run the following commands to download the codesourcery toolchain
Code:
wget http://www.codesourcery.com/sgpp/lite/arm/portal/package5354/public/arm-none-eabi/arm-2009q3-68-arm-none-eabi-i686-mingw32.tar.bz2
tar xvfj arm-2009q3-68-arm-none-eabi-i686-mingw32.tar.bz2
wget http://htc-flasher.googlecode.com/files/yang-1.1_win32.zip
cd cLK/bin
rm -rf yang
mkdir yang
unzip ../../yang-1.1_win32.zip yang/yang.exe
mv yang/yang.exe .
cd ..
sed -i s/yang/yang.exe/g compile
Step 2: Change partition sizes
To change your values for cache, system, boot etc... you need to change the following files
lk/target/htcleo/rules.mk
line 8 - system
lk/target/htcleo/init.c
line 28 - misc
line 32 - recovery
line 36 - boot
line 43 - cache
These will be located in c:\cygwin\home\<username>\cLK on your windows machine
Step 3: Compile cLK
Now you can compile by running the following command
Code:
export PATH=$HOME/arm-2009q3/bin:$PATH
cd cLK
./compile clean
Now your RUU_signed.nbh will be located in the following folder
Code:
bin/RUU_signed.nbh
Hopefully that should work, I have just tested this on my machine.
Anyone have any issues, let me know, I will amend the howto
ROMS, HowTOs and Utilities
ROMs
Click to expand...
Click to collapse
HyperDroid-CM7 by pongster
Froyo Sense revolution 2.5 by arif-ali
UD 3.1 by crawlingcity
Revolution HD v2.6 & SL v1.4 by arif-ali
HowTOs
Click to expand...
Click to collapse
cLK for Dummies by stirkac
Utilities
Click to expand...
Click to collapse
CWR with yes/no menu by seadersn
HD2 NAND Toolkit by ksubedi
Convert magldr ROM to cLK HowTO
another one for howto for rom chefs
Coming Soon!!!
Awsome new clk bootloader! It will be interesting to see how stable internet is!
if you find a way to install with clk and recovery at once from sd card method (leoimg.nbh) it would be awesome to be able to change on the road between wm and nand android
It's a shame you're not going to support RMNET. The data stability with PPP seems to a minus. I know cedesmith (at one time) was deving for RMNET support, but I doubt it'll get there now. Still though, cLK is a great bootloader. Keep up the great work (if there is any left).
-Bryan
Can't cotulla provide the source script of RMNET ?
white-energy said:
Can't cotulla provide the source script of RMNET ?
Click to expand...
Click to collapse
This has been already been mentioned in the other thread, He will not provide it, and it was taken apparently by hacking out the radio code.
I think a few people have asked the question, and there is no chance that he will provide his code, this is a similar issue that people are having where Cotulla is developing magldr on other devices, it is all closed-source.
FYI, cedesmith may have said that he was going to do it in the early days when he was doing cLK, but when he had discussions with cotulla, and him not providing the code, and how it was working, he decided not to try to implement even if he could.
arif-ali said:
This has been already been mentioned in the other thread, He will not provide it, and it was taken apparently by hacking out the radio code.
I think a few people have asked the question, and there is no chance that he will provide his code, this is a similar issue that people are having where Cotulla is developing magldr on other devices, it is all closed-source.
FYI, cedesmith may have said that he was going to do it in the early days when he was doing cLK, but when he had discussions with cotulla, and him not providing the code, and how it was working, he decided not to try to implement even if he could.
Click to expand...
Click to collapse
Oh no! alright i have an idea! (shinny lamp =P) lets hijack Cotulla's computer and get everything he has closed-sourced and make it open-sourced =P
HELP
this is the first time I have ever tried to compile a kernel. I know sdk pretty well but compiling this kernel and the directions that have been provided are confusing to me.
Step 3: Compile cLK
Now you can compile by running the following command
Code:
export PATH=$HOME/arm-2009q3/bin:$PATH
cd cLK
./compile clean
I have entered these in Cygwin the first line I am a little lost on? I entered export c:/cygwin/home/HD2/cLK=$HOME/arm-2009q3/bin:$c:/cygwin/home/HD2/cLK
i get bash: export: c:/cygwin/home/HD2/cLK=$HOME/arm-2009q3/bin:$c:/cygwin/home/HD2/cLK
/cLK' not a valid identifier
I have no idea what that means can anyone help?
jhr5474 said:
this is the first time I have ever tried to compile a kernel. I know sdk pretty well but compiling this kernel and the directions that have been provided are confusing to me.
Step 3: Compile cLK
Now you can compile by running the following command
Code:
export PATH=$HOME/arm-2009q3/bin:$PATH
cd cLK
./compile clean
I have entered these in Cygwin the first line I am a little lost on? I entered export c:/cygwin/home/HD2/cLK=$HOME/arm-2009q3/bin:$c:/cygwin/home/HD2/cLK
i get bash: export: c:/cygwin/home/HD2/cLK=$HOME/arm-2009q3/bin:$c:/cygwin/home/HD2/cLK
/cLK' not a valid identifier
I have no idea what that means can anyone help?
Click to expand...
Click to collapse
you need the actual word "PATH", don't replace it
Sent from my HTC HD2 using XDA Premium App
CLK over MAGLDR
I was having problem with my NAND Android phone with MAGLDR bootloader. The problem was my phone is unreachable while it is screen off/sleep mode. There is no problem when the screen is on. I tried different versions of Android with all the recommended settings. There is an exemption for Windows 7 mobile, it was OK even when in sleep mode. Two days ago I started using CLK boot loader, and I never had this problem again. To confirm I tried various versions of android including doubleshot and kingdom with sense 3. The only problem I think is the unstable PPP internet connection. MAGLDR was good with its RMNET connection.
Anybody else observed this? Any comments or advise?
alexkutty said:
I was having problem with my NAND Android phone with MAGLDR bootloader. The problem was my phone is unreachable while it is screen off/sleep mode. There is no problem when the screen is on. I tried different versions of Android with all the recommended settings. There is an exemption for Windows 7 mobile, it was OK even when in sleep mode. Two days ago I started using CLK boot loader, and I never had this problem again. To confirm I tried various versions of android including doubleshot and kingdom with sense 3. The only problem I think is the unstable PPP internet connection. MAGLDR was good with its RMNET connection.
Anybody else observed this? Any comments or advise?
Click to expand...
Click to collapse
Already tested the two ril wrappers? beta4 seems to be the best for most of the people.
Using the beta4 wrapper since its out (end of april) and my data connection didn't drop one time.
so it's arif taking over the wheel now? i hope to c somethin' going on in here...
maybe clk with recovery preinstalled?
i was thinking yesterday, what if we would do a check of partitions on cLK start:
1.so if /recovery is empty, we fire up fastboot and give a hint in last line what to do-after fastboot: processing commands
if it just goes to -suspend- than write a line to say "please connect to usb or install fastboot drivers"
2.and when /system is empty, it drops you to recovery.
i thnk that would be possible in couple of lines (but don't take me 100% because i'm yet to see cLK source..i hate VM's + i don't have much space on regular drive to spare)
*** ABOUT ***
This is an attempt to build a completely clean installation of xubuntu for the tf300tg (and probably tf300t). Most notably it does not reuse the ac100 ubuntu package.
I also want it to be as completely documented as possible starting from an official ubuntu repository and kernel source, until everything is working. Which does not mean it is for a complete beginner to reproduce...
It's not (yet) packaged : you at least need to be able to install a blob for the kernel, and a rootfs to a dedicated partition.
It's also not yet as cleaned up and documented as I would for the kernel side of things.
Everything is done on device on (and for) a tf300tg but as been reported to work on tf300t.
Most of the hard work was done by others. I mostly started from rabit's tf700 ubuntu, and added some insight from cb22 work on arch to get something working.
*** STATUS ***
What works :
- it boots into a clean xubuntu dm/desktop, with wifi (improved), 3g
- it also boots into android (stock, didn't try cm)
- 3g also works under android (new)
- touchpad / touchscreen
- 3d acceleration (version 16.3 of nvidia drivers)
- cpu and gpu overclock (respectively to 1,5 GHz and 446 MHz)
What I know doesn't work, isn't there yet :
- sound
- bluetooth
- some key remapping (esc, alt, ...)
Many other things I didn't check (sensors ?).
*** HOWTO install ***
0. of course you can break many things doing that ; you should have access to nvflash (never had to use it though) and with a recovery installed (I'm on twrp 2.4.3.0)
1. unpack xubuntu_tf300tg_rootfs-0.1.2.img.lzma to the internal storage and move / rename to linux/rootfs.img (/data/media/linux/rootfs.img)
1bis. you can change your keyboard layout in /etc/default/keyboard (replace "us" by whatever is your locale)
2. install the kernel blob using fastboot or "dd if=xubuntu_tf300tg_kernel-0.1.2oc.blob of=/dev/block/mmcblk0p4"
You should be able to reboot into xubunfu (or android).
3. log in as guest, from "user and groups" in the "settings manager", add one user, set password, change account type to administrator, add to sudo group (root password wil be asked : root)
4. logout, then login into your newly created user
5. open "language support" from the settings manager, and when it says missing locales, either choose install if you want "en" or "ask me later" if you want something else (in which case you can chose to install your own language, and configure them on the "regional format" page ; don't forget to apply system wide on both pages
6. change root password
Your second reboot should be more satisfying
*** HOWTO improve ***
1. find out what does not work and tell in the thread
2. understand what is documented bellow and propose correction / evolutions in the thread
3. don't hope for frequent updates : I do that alongside a more than full time job and tending to a two years old child. Still I will update.
*** DOWNLOAD ***
rootfs : http://d-h.st/vYf
kernel : http://d-h.st/UAy
misc config files : http://d-h.st/TEZ
nvidia drivers : http://d-h.st/pwQ
md5sum :
4f572c110c3f06f54699c826fed692f4 src-0.1.2.tar.lzma
249826271f4fadff4352217467e4ed2e xubuntu_tf300tg_kernel-0.1.2oc.blob
3263de707c2586d1e2177367f067361a xubuntu_tf300tg_rootfs-0.1.2.img.lzma
cf20b01281be3ef4b6d4631ae5cea67b R16.3.tar.lzma
*** HOW is it done / rootfs ***
I did it from ubuntu (rabits') on my tf300tg. Should be doable from another platform. Definitly doable from self.
As root.
# unset languages / locales
export LANG=C
unset LC_ADDRESS
unset LC_IDENTIFICATION
unset LC_MEASUREMENT
unset LC_MONETARY
unset LC_NAME
unset LC_NUMERIC
unset LC_PAPER
unset LC_TELEPHONE
unset LC_TIME
# mount a cleanly ext4 formated partition (futur root partition)
mount /dev/mmcblk1p2 /media/p1
# install initial minimal system
apt-get install debootstrap
debootstrap quantal /media/p1 http://ports.ubuntu.com/
# prepare to chroot
mv /media/p1/etc/apt/sources.list /media/p1/etc/apt/sources.list.orig
cp src/sources.list /media/p1/etc/apt/sources.list
mv /media/p1/etc/fstab /media/p1/etc/fstab.orig
cp src/fstab_chroot /media/p1/etc/fstab
mkdir /media/p1/run/user
# chroot into the new system and mount all special filesystems
chroot /media/p1
mount -a
# download xubuntu (avoiding unity which is recommended by lightdm)
apt-get update
apt-get upgrade
apt-get install xserver-xorg
apt-get --no-install-recommends install lightdm
apt-get install lightdm-gtk-greeter
apt-get install xubuntu-desktop
# install nvidia drivers and tuned nv.conf
tar xf R16.3.tar
update-alternatives --force \
--install /etc/ld.so.conf.d/arm-linux-gnueabihf_EGL.conf arm-linux-gnueabihf_egl_conf /usr/lib/nvidia-tegra/ld.so.conf 9000 \
--slave /usr/lib/xorg/modules/drivers/tegra_drv.so nvidia_drv /usr/lib/nvidia-tegra/xorg/modules/drivers/tegra_drv.abi13.so
ldconfig -v
update-rc.d ondemand disable
# change root password to something of your chosing and exit chroot
passwd root
# configure touchscreen and touchpad
apt-get install xserver-xorg-input-multitouch
exit
cp src/mtev.so /media/p1/usr/lib/xorg/modules/input
mkdir /media/p1/etc/X11/xorg.conf.d
cp src/50-elan* /media/p1/etc/X11/xorg.conf.d
# change hostname
# edit /media/p1/etc/hostname and replace tf300tg with your chosen hostname
# edit /media/p1/etc/hosts and insert a line (second one) with "127.0.0.1 yourhostname"
# hide the partitions from mmcblk0 (thanks cb22)
echo 'ENV{ID_PATH}=="platform-sdhci-tegra.3", ENV{UDISKS_IGNORE}="1"' > /media/p1/etc/udev/rules.d/80-hide_tf300tg_partitions.rules
# change keyboard defaults
# edit /media/p1/etc/default/keyboard ; replace "pc105" by "asus_laptop" ; you can also change "us" to your locale
# create mountpoints for system and data
mkdir /media/p1/system /media/p1/data
# configure for loading wifi module
echo bcm4329 >> /media/p1/etc/modules
#
cp /media/p1/etc/fstab.orig /media/p1/etc/fstab
*** HOW is it done / kernel ***
The kernel source is default asus 10.4.3.9 from asus' website download section. Patched to add cpu overclock from faux's kernel and gpu overclock from motley's kernel (diff file in src.tar.lzma).
Initial kernel config file is taken from stock 10.4.3.9 android, with options added to support ubuntu and oc. path to the nvram for bcm4329 modified.
Ramdisk is mostly that from rabbits 0.8.0, with some modificaitons to enable modem support under android.
*** Todo ****
- modify config / kernel to use nvidia's R16.3 tool to patch wifi ;
- build initramfs anew from tf300t/tg stock android initramfs (currently rabbits modified tf700) ;
- bluetooth and sound ;
- key remapping.
reserved 2
Sounds promising! Keep it up, hopefully other devs see this and help you out :good:
Re: [DEV][WIP] xubuntu on tf300tg 0.1.0
Good job, I will tray luck to night when I back from work.
P.S. I heave no dock - that means no keabord and mouse
Sent from my GT-I9100 using xda app-developers app
Keshukas said:
Good job, I will tray luck to night when I back from work.
P.S. I heave no dock - that means no keabord and mouse
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your interest.
Although I would be happy to have some feedback, it may be a bit early if you don't have a dock : it's completely functionnal with a dock and mouse (I've been using it for work - and build - for a few days), without a keyboard and mouse, you will not go farther than xubuntu' login screen.
Anyway if you still wan't to try it, tell me if you reach xubuntu blue login screen.
Re: [DEV][WIP] xubuntu on tf300tg 0.1.0
On the rabbit Ubuntu for tf700 are virtual keabord (beside clock switch ) witch I use to login to Ubuntu
Sent from my GT-I9100 using xda app-developers app
Assuming this is a dual boot kernel, how does the kernel know where ubuntu is installed if not installed on internal sdcard? Also what's the minimum size partition that can be used?
Moved the thread for ya...
Yes!!! ) Thanks I wait for it )) Xubuntu is my lovely linux, I have it on PC, Notebook, installed on fathers PC and now for tablet!! :good::good::good:
Keshukas said:
On the rabbit Ubuntu for tf700 are virtual keabord (beside clock switch ) witch I use to login to Ubuntu
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
I know that and it can be reproduced (look at rabits' /etc/X11/xorg.conf ; and needs packages xserver-xorg-input-multitouch and mtev).
But I have not yet abandonned all hope of doing it the ubuntu way (ie. with evdev).
TechyNut said:
Assuming this is a dual boot kernel, how does the kernel know where ubuntu is installed if not installed on internal sdcard? Also what's the minimum size partition that can be used?
Click to expand...
Click to collapse
Rabits modified the boot image so that it checks /dev/sda*, then /dev/mmcblk1p*, then an img file on /dev/mmcblk0p8. The first which looks to be an ubuntu partition is used as root. He also activated vt (having a console during boot) in is kernel configuration. I reproduced both.
NRGZ28 said:
Moved the thread for ya...
Click to expand...
Click to collapse
Thanks. Induced some noise on other threads
Ramdisk initrd.img in your kernel blob file is not a gzip !!!
Ok starting test
1. Yours kernel most start android if no Linux in /dev/sda1 or /dev/mmcblk1p* or on /dev/mmcblk0p8. Some I understand ?
Now making backup of me tablet ( TF300t ) and flashing kernel to test it.
2. I planing Make Linux on me ExtSDcard (MiniSD 8 gb) and plug sdcard in tablet and then reboot tablet. i hope to start Xubuntu
akurpiel said:
Ramdisk initrd.img in your kernel blob file is not a gzip !!!
Click to expand...
Click to collapse
No. It's lzma.
You can check rabits' git for details : https://github.com/rabits/tf700
Keshukas said:
Ok starting test
...
i hope to start Xubuntu
Click to expand...
Click to collapse
I hope too. Thanks for testing.
Can't mount linux
So I thought I'd give this a try. These are the steps I took to install this:
1. Formated 8gig SD card as ext4
2. Extracted rootfs to SD card.
3. Inserted SD in base
4. copy /system/vendor and /system/etc from your tf into /system on that partition ; copy /data/misc from your tf into /data on that partition
5. fastboot -i 0x0b05 flash staging xubuntu_tf300tg_kernel-0.1.0.blob
6. reboot
6. Kernel boots prompting option, select 1 (linux) and fails to mount partition and boots into android with no other problem.
What am I missing?
ColMustard said:
So I thought I'd give this a try. These are the steps I took to install this:
1. Formated 8gig SD card as ext4
2. Extracted rootfs to SD card.
3. Inserted SD in base
4. copy /system/vendor and /system/etc from your tf into /system on that partition ; copy /data/misc from your tf into /data on that partition
5. fastboot -i 0x0b05 flash staging xubuntu_tf300tg_kernel-0.1.0.blob
6. reboot
6. Kernel boots prompting option, select 1 (linux) and fails to mount partition and boots into android with no other problem.
What am I missing?
Click to expand...
Click to collapse
I have had some occurences of hitting return to fast at the prompt and init not detecting correctly the SD card. So maybe let it timeout into trying to boot linux.
If that does not work, you can choose "s" at the prompt, then from there check into /dev/ which disks / partitions are recognized. Provided that your linux partition is the first and only one on the SD card, you should have a /dev/sda and /dev/sda1. What do you see ?
Also remove any usb drive, which could appear as /dev/sda (and make the sd card appear as /dev/sdb).
Some RABIT write "In-device microSD really bad works." :crying:
I heave problems to boot from sd now i think extract xubuntu in /data/media/linux/rootfs.img
-- Update --
MicroSD - /dev/block/mmcblk1p1
schrdlu said:
I have had some occurences of hitting return to fast at the prompt and init not detecting correctly the SD card. So maybe let it timeout into trying to boot linux.
If that does not work, you can choose "s" at the prompt, then from there check into /dev/ which disks / partitions are recognized. Provided that your linux partition is the first and only one on the SD card, you should have a /dev/sda and /dev/sda1. What do you see ?
Also remove any usb drive, which could appear as /dev/sda (and make the sd card appear as /dev/sdb).
Click to expand...
Click to collapse
Well it looks like it's a no go for me. it could be that I used Minitool Partition Wizard to format because I could not get to my linux machine at the time.
I also tried flashing the kernel over 3 different ROM:
1. CROMI 3.4.4 - Keep failing with Encryption error after boot animation prompting me to reset the device.
2. Hydro 7 - Keep failing with Encryption error after boot animation prompting me to reset the device.
3. CM 10.1 - Failed to get pass boot animation.
I'll have to re-flash Asus stock ROM (10.4.2.20) in order to fully test this, I might have to reformat the sd on linux also.
ColMustard said:
Well it looks like it's a no go for me. it could be that I used Minitool Partition Wizard to format because I could not get to my linux machine at the time.
I also tried flashing the kernel over 3 different ROM:
1. CROMI 3.4.4 - Keep failing with Encryption error after boot animation prompting me to reset the device.
2. Hydro 7 - Keep failing with Encryption error after boot animation prompting me to reset the device.
3. CM 10.1 - Failed to get pass boot animation.
I'll have to re-flash Asus stock ROM (10.4.2.20) in order to fully test this, I might have to reformat the sd on linux also.
Click to expand...
Click to collapse
Me to. I can't boot to android at all
I still tray boot to xubuntu with this kernel and I make img on the internal card
Keshukas said:
Me to. I can't boot to android at all
I still tray boot to xubuntu with this kernel and I make img on the internal card
Click to expand...
Click to collapse
Yeah, I did notice that the kernel looks for the /data/media/linux/.img for a last effort. I was thinking on doing the same.
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"