Database Info

[KERNEL] CIFS + UTF8 NLS support for the official HTC Desire Froyo kernel

with the release of the source code for the bravo kernel this has become redundant
to be able to directly access my stuff on samba shares i made a _patch_ for the cifs code in 2.6.32.15 and built cifs.ko and nls_utf8.ko with arm-eabi-4.4.0
i thought i'd share them here in case it was of use to anyone else
this is how i installed them:
Code:
(boot into recovery mode)
$ adb shell mount /system
$ adb push cifs.ko /system/lib/modules
$ adb push nls_utf8.ko /system/lib/modules
$ adb shell chmod 644 /system/lib/modules/*.ko
$ adb shell "cd /system/lib/modules; ln -s . 2.6.32.15-gf9c0527"
$ adb shell umount /system
(reboot)
this is how i tested them:
Code:
sh-3.2$ su
sh-3.2# modprobe nls_utf8
sh-3.2# modprobe cifs
sh-3.2# busybox mount -t cifs -o user=<username>,password=<password>,uid=1000,gid=1015,file_mode=0775,dir_mode=0775,iocharset=utf8,nodfs //10.0.1.2/public2 /sdcard/smb/public2
(1015 is the gid of 'sdcard_rw')
--
cifs_bravo_2.6.32.15-gf9c0527.zip
cifs_bravo_2.6.32.15-gd96f2c0.zip

Hey cheers for this will try it out
Sent from my C64

just tried
init_module 'cifs.ko' failed (Exec format error)

epyon1873 said:
init_module 'cifs.ko' failed (Exec format error)
Click to expand...
Click to collapse
as stated above it works with the stock htc kernel, which is 2.6.32.15-gf9c0527
check the output of uname -r

snq- said:
as stated above it works with the stock htc kernel, which is 2.6.32.15-gf9c0527
check the output of uname -r
Click to expand...
Click to collapse
Thx find htc kernel is 2.6.32.15-g1fc4045 @ NexTSense Rom orz

epyon1873 said:
Thx find htc kernel is 2.6.32.15-g1fc4045 @ NexTSense Rom
Click to expand...
Click to collapse
afaik the current nextsense comes with Myshkinbob's cifs module (although not with the latest one) - it's module version id was simply patched to suppress the version mismatch error message you got
here is mine if still interested:
(be sure to type "ln -s . 2.6.32.15-g1fc4045" instead of "ln -s . 2.6.32.15-gf9c0527" when installing)
--
cifs_bravo_2.6.32.15-g1fc4045.zip

Thx~! go to try it.

Greetings,
I tried using your patch on the source for the supersonic (evo) and it went in and compiled perfectly, i was able to do an insmod and loaded the driver fine, but when i go to do a mount the phone crashes.
any ideas?
(i have tried both the arm-eabi-4.4.0 and the arm-2010q1 toolchains)
Thanks!!

adambot said:
I tried using your patch on the source for the supersonic (evo) and it went in and compiled perfectly, i was able to do an insmod and loaded the driver fine, but when i go to do a mount the phone crashes.
any ideas?
(i have tried both the arm-eabi-4.4.0 and the arm-2010q1 toolchains)
Click to expand...
Click to collapse
the patch does not cleanly apply to supersonic-2.6.32.15-g746f4f0, as it is for vanilla 2.6.32.15
please overwrite fs/cifs with the vanilla sources before you apply it
just tried and was able to build the very same .ko published in the first post (except for the buildstamp of course):
pulled the supersonic kernel source from developer.htc.com
overwrote fs/cifs/* with vanilla
pulled & applied the patch from pastebin
pulled .config from my phone
in menuconfig
set the localversion (general setup)
selected cifs + nls_utf8 to be built as module
did _not_ touch the debug options already set
did 'make modules'
stripped the modules with arm-eabi-strip --strip-debug
insmod worked, mount worked, browsing the share worked
if you get crashes, check /proc/last_kmsg after reboot

snq- said:
the patch does not cleanly apply to supersonic-2.6.32.15-g746f4f0, as it is for vanilla 2.6.32.15
please overwrite fs/cifs with the vanilla sources before you apply it
Click to expand...
Click to collapse
What is considered "vanilla sources"?
I used git and pulled the whole android repo but am not finding the vanilla sources there...
do you mean the vanilla linux sources??
[edit]
i tried the cifs files from the vanilla linux source (same version) but the phone still crashes (even after the debug strip)
Should i try to use a different config (rather than the one from the supersonic templates?)
Do you have an evo that you tested this on?
Thanks again!!!
[/edit]

adambot said:
do you mean the vanilla linux sources??
Click to expand...
Click to collapse
sorry if i wasn't clear enough. linux-2.6.32.15.tar.bz2 (kernel.org)
adambot said:
Should i try to use a different config
Click to expand...
Click to collapse
i pulled the config from the device ($adb shell zcat /proc/config.gz > .config)
i do not own an evo, the only reason for me to use evo/incredible sources is that htc haven't released bravo-froyo kernel sources yet

adambot, please let me know if this works for you
--
cifs_supersonic_2.6.32.15-g746f4f0.zip

snq- said:
adambot, please let me know if this works for you
Click to expand...
Click to collapse
WOW!!! That worked PERFECTLY!!!!!
Thanks SO MUCH!!!
(now i just have to figure out why mine wasn't working... I'll try again with your steps and compare the good one to mine with diff)
if you don't mind just to recap:
get linux vanilla kernel source
get supersonic kernel source
replace supersonic fs/cifs with vanilla
edit Makefile with extra EXTRAVERSION info
get .config from running device
make CROSS_COMPILE=CROSS_COMPILE=arm-eabi-4.4.0/bin/arm-eabi- oldconfig (accept defaults)
edit .config and make cifs and nls_utf8 modules
make CROSS_COMPILE=arm-eabi-4.4.0/bin/arm-eabi- modules
arm-eabi-4.4.0/bin/arm-eabi-strip fs/cifs/cifs.ko and fs/nls/nls_utf8.ko

adambot said:
WOW!!! That worked PERFECTLY!!!!! Thanks SO MUCH!!!
Click to expand...
Click to collapse
no problem, glad it worked out
adambot said:
if you don't mind just to recap: ...
Click to expand...
Click to collapse
- i don't see the step where you applied the patch
- i didn't edit the makefile per hand
- i didn't edit .config per hand
- as i don't own an evo, instead of pulling the config from the device i did a 'make supersonic_defconfig' before 'make menuconfig'

snq- said:
no problem, glad it worked out
- i don't see the step where you applied the patch
- i didn't edit the makefile per hand
- i didn't edit .config per hand
- as i don't own an evo, instead of pulling the config from the device i did a 'make supersonic_defconfig' before 'make menuconfig'
Click to expand...
Click to collapse
I got it to work FINALLY!!! I will be posting the step by step (copy/paste) directions in the evo section. Do you mind if i post the patch here as an attachment? also -- how do you want credit -- do snq- or do a different name?
thanks again!!
Adam

adambot said:
Do you mind if i post the patch here as an attachment?
Click to expand...
Click to collapse
feel free to use it for whatever you want
you might however want to post the patch directly applicable to the supersonic source (attached)
thanks for crediting me, using the nick is fine
--
supersonic-2.6.32.15-g746f4f0_cifs.patch

snq- said:
feel free to use it for whatever you want
you might however want to post the patch directly applicable to the supersonic source (attached)
thanks for crediting me, using the nick is fine
Click to expand...
Click to collapse
What did you do differently? (or what is the difference between cifs-supersonic and cifs-vanilla) -- I would look myself, but i'm not the best at coding... (that's what i get for being a sysadmin and not a dev -- but i can script until the cows come home )

Help me
I need nls_utf8.ko for 2.6.34 kernel

I would like cifs module for 2.6.32.15-g6a358a9 kernel, is it posible?
Thanks!

any for 2.6.32.15-ge2fb08e?

[MOD][CWM] Bash 4.1 Default Shell Env. and Custom Terminal Emulator BML/MTD 01/07

Android Shell Environment - Bash 4.1
Package Version 1.2b - 01/06/2012
DOWNLOAD MOD_CWM-UltimateAndroidShell-Bash4.1-20120107.zip
File size: 5.3 MB / MD5 84cb672cd11b7a3e9b21e29c3416da21
​
DETAILS
This package is an amalgamation from various sources including my own to create the perfect shell environment for Local and Remote administration.
All solutions so far have been incomplete or require more configuration to get working, so i thought i would share what i've been running.
This package installs Bash and the other listed features and sets bash as the default shell.
Hope it's useful!
INCLUDED BINARIES
- Bash 4.1
- BusyBox 1.19.0
- Htop
- 7z (p7zip v9.20)
- bc
- Nano
- Joe
- Vim
- SSH/Dropbear
- SCP
- Rsync
- Curl
Android Terminal v1.0.39 - /system/Term.apk - com.senseisimple.androidterm
Custom Built Terminal based on Terminal Emulator by Jackpal
[Source on Github]
INCLUDED SCRIPTS
[sudo] Pseudo sudo, run a command as Root
Usage: sudo [command]
[reboot] BML/MTD Compatible reboot wrapper with recovery boot
Usage: sudo reboot [recovery]
[adbwifi] Easily enable/disable ADB over Wifi (persistent until reboot or disable) without an app/widget (su required or use with sudo)
Usage: sudo adbwifi [on | off | status]
[remount] Remount the /system partition as ReadOnly or Read/Write (su required)
Usage: sudo remount [ro | rw | status]
[defaultshell] Change default shell on the fly from Bash to sh (this is a persistent change)
Usage: sudo defaultshell [sh | bash | current]
[sdcardstuck] Media Provider Fix
If your phone is running warm and laggy and eating battery after a clean install,
it's possible "android.process.media", the Media Scanner process,
is stuck on a file it's unable to read on the sdcard causing it to hang indefinitely.
The script tests for stuck files, and offers to delete them or generate a list,
also cleans the Media Provider database.
Usage: sudo sdcardstuck
CUSTOM BASH ENVIRONMENT
Home (~) at /data/local
$ prompt as User
# prompt as Root
Preset shopt options
histappend, histverify, histreedit, cdspell, expand_aliases, cmdhist
hostcomplete, no_empty_cmd_completion, nocaseglob, dotglob, autocd
Bash/Su files
- /etc/profile
- /etc/bash_bashrc
- /etc/terminfo
- /etc/passwd
- /system/etc/init.d/00bashinit - for kernel compatibility if using bash as default shell (sets up/fixes the bash environment on boot)
- /data/local/.inputrc
- /data/local/.profile
- /data/local/.bashrc
- /data/local/.bashrc_support
- /data/local/.bashrc_user <- Edit this file to add shell functionality (loads last)
- /data/local/.bash_history
- /data/local/tmp
- /data/local/bin
- /data/local/sbin
- /data/local/xbin
ENVIRONMENT VARIABLES
PATH = /data/local/xbin:/data/local/bin:/data/local/sbin:/system/bin:/system/xbin:/sbin:/data/local/tmp
EDITOR = nano - default editor (used by edit/e/suedit aliases, set with seteditor)
VISUAL = $EDITOR
TERMINFO = /system/etc/terminfo
TERM = Linux
HISTCONTROL = ignoredups:ignorespace
AVAILABLE FUNCTIONS
motd - clear the screen, display the MOTD
Usage: motd
hist - search command history
Usage: hist [part of command]
pg - search processes
Usage: pg [running process name]
pid - get process id
Usage: pid [running process name]
appuid - get uid of running process
Usage: appuid [running process name]
bg - run process in the background
Usage: bg [command]
quiet - run process quietly
Usage: quiet [command]
ip - get active ip address
Usage: ip
seteditor - set default text editor availability by order of preference
Usage: seteditor [space separated bins | default]
Example (defaults): seteditor nano vim vi
AVAILABLE ALIASES
bb - Busybox (/sbin/busybox)
su - Su (Bash compatible)
ls - ls w/ color
l - ls -CF w/ color
la - ls -a w/ color
li - ls -laniF w/ color
ll - ls -alF w/ color
lsn - ls -lanF w/ color
dir - ls -halF
edit or e - Shortcut to your favorite editor by order of preference/availability (default: nano vim vi)
suedit - run editor as Root
HUMBLE GRATITUDE
Nubecoder for the bash 4.1 bin that makes this possible http://http://forum.xda-developers.com/showthread.php?t=1225296
bc54 for additional ideas, remount/default shell scripts http://forum.xda-developers.com/showthread.php?t=1229211
Jocala for the pointer to nano and joe and info in his post http://forum.xda-developers.com/showthread.php?t=1349454
Toadlife MTD help
Bbelos MTD help

{
"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"
}
CHANGELOG
v1.2b - 01/06/2012
- bash env init script fixes (Thanks bbelos!)
- reorganized user bin directories
v1.2a - 01/06/2012
- ssh/dropbearmulti update [jocala]
- fix su link
v1.2 - 01/05/2012
- Added BusyBox 1.19.0
- Addtl. Permissions fixes
v1.1 - 01/02/2012
- BML/MTD Compatible
- Added BML/MTD Reboot wrapper [based on Toadlife]
- Permissions fixes
- other minor changes
v1.0 - 12/30/2011
Initial upload

and this one

nice.
but joe? haha I don't use it but one of my coworkers does...always leaves those damn ~files around lol.

Thanks, but no Emacs?
Just kidding. Good to have nano and joe there.

This looks so sick, thank you!!
Sent from my SPH-D700 using XDA Premium App

doesn't work for me on mtd. should just need to change the way it mounts /system, and it SHOULD work
sent from my touchwiz 4.5-ed epic

lost_ said:
Thanks, but no Emacs?
Click to expand...
Click to collapse
lol. There's only room for one operating system on the phone.

For some reason, this completely disables vibration on the phone running computerkid23's ROM. I'm about to do some digging lol, never had anything like this happen.

toadlife said:
lol. There's only room for one operating system on the phone.
Click to expand...
Click to collapse
Unless you chroot an Ubuntu image... but what does that have to do with the Emacs text editor?
Sent from my SPH-D700 using XDA App

ugothakd said:
doesn't work for me on mtd. should just need to change the way it mounts /system, and it SHOULD work
sent from my touchwiz 4.5-ed epic
Click to expand...
Click to collapse
FYI,
I believe, you can run these two command in a row and it will mount the system whether it's MTD or BML...
Code:
run_program("/sbin/mount","/system");
run_program("/sbin/mount","/dev/block/mtdblock2","/system");
EDIT: I know for a fact that both command work. I don't think one of them failing will cause any issues.

Using busybox mount instead of the semi-braindead one floating in /sbin should take care of it. That or a incantation of mount | grep | cut to put the dev name in automagically.
-- Starfox

UPDATE!
v1.1 - 01/02/2012
- BML/MTD Compatible
- Added BML/MTD Reboot wrapper [based on Toadlife's]
- Permissions fixes
- other minor changes
Happy New Year Everyone!​

thomasskull666 said:
For some reason, this completely disables vibration on the phone running computerkid23's ROM. I'm about to do some digging lol, never had anything like this happen.
Click to expand...
Click to collapse
This has to be a kernel issue, we experienced this with ShadowKernel early on as init.d scripts were running in the middle of the script instead of at the end. Other than that, i'm not sure why that would happen... The update might help you but im not sure, i'm not familiar with that ROM workings

SenseiSimple said:
This has to be a kernel issue, we experienced this with ShadowKernel early on as init.d scripts were running in the middle of the script instead of at the end. Other than that, i'm not sure why that would happen... The update might help you but im not sure, i'm not familiar with that ROM workings
Click to expand...
Click to collapse
Thanks for the reply, I figured it was something like that. I'll definitely be trying the update here shortly so I'll let you know if it changes anything. If not, I may be switching to a different ROM as bash is something I use on a day to day basis, and this mod has all the goodies too
EDIT: Yep, unfortunately it happens also on Legendary ROM. I'll see if I can find specifically what is causing it, I haven't been able to run a logcat yet although I suspect, like you said, it's something to do with the kernel.
Sent from my SPH-D700 using XDA Premium App

Thanks for the mtd fix something you might want to do though is set the updater-script to delete Androidterm.apk, which is the terminal emulater included with cm7. I had to do that manually
sent from my cm7 touchwiz 4.5-ed epic

thomasskull666 said:
Thanks for the reply, I figured it was something like that. I'll definitely be trying the update here shortly so I'll let you know if it changes anything. If not, I may be switching to a different ROM as bash is something I use on a day to day basis, and this mod has all the goodies too
EDIT: Yep, unfortunately it happens also on Legendary ROM. I'll see if I can find specifically what is causing it, I haven't been able to run a logcat yet although I suspect, like you said, it's something to do with the kernel.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
It is almost certainly to do with the kernel... you can try to unset bash as the default shell, try: sudo defaultshell sh and restart... since the custom android terminal is customized for bash, the default shell being bash is not strictly necessary but is more a matter of convenience in writing/running scripts... that MAY help.
ugothakd said:
Thanks for the mtd fix something you might want to do though is set the updater-script to delete Androidterm.apk, which is the terminal emulater included with cm7. I had to do that manually
sent from my cm7 touchwiz 4.5-ed epic
Click to expand...
Click to collapse
Thanks i added it! i already watch out for like 10 different names/locations to delete for the emulator, always helps to know more.

Bash Environment 1.2b 1/7
UPDATE
This update addresses some issues with the init script causing loss of vibrate functionality, as well as making sure busybox/su/bash/ssh all work together.
Changelog
v1.2b - 01/07/2012
- bash env init script fixes (Thanks bbelos!)
- reorganized user bin directories
v1.2a - 01/06/2012
- ssh/dropbearmulti update [jocala]
- fix su link
v1.2 - 01/05/2012
- Added BusyBox 1.19.0
- Addtl. Permissions fixes

SenseiSimple said:
UPDATE
This update addresses some issues with the init script causing loss of vibrate functionality, as well as making sure busybox/su/bash/ssh all work together.
Changelog
v1.2b - 01/07/2012
- bash env init script fixes (Thanks bbelos!)
- reorganized user bin directories
v1.2a - 01/06/2012
- ssh/dropbearmulti update [jocala]
- fix su link
v1.2 - 01/05/2012
- Added BusyBox 1.19.0
- Addtl. Permissions fixes
Click to expand...
Click to collapse
How did I miss this?! Definitely trying it out, I'll report back here soon.
EDIT: It works, no more vibration being killed! thank you, I appreciate the effort and will use this every day
Sent from my SPH-D700 using xda premium

This works great on my Galaxy Tab Plus. Thanks for this. Backtrack is running smooth.
UPDATE: I posted a link to this thread in the Galaxy Tab Plus Dev section.
Sent from my Samsung Galaxy Tab Plus with XDA Premium

Jhinta Kernel for Lilstevie Ubuntu

Dont have this tap anymore so cant support it anymore !!!
I do things manual as i want to know what has be done !
So every thing below is hardcore installation. This will give you the why and know how of things !!!
About bootimg.cfg
This file is need for creating boot.img
You can find it by unpacking a boot.img,but one is provided already.
The important part of this file is the first and last option.
The first one will say how big the image wil be, and the last is kernel cmdline.
This is also wehre you say loop= for a loop file
Pack or unpack blob files
Code:
cd /tmp
git clone git://github.com/AndroidRoot/BlobTools.git
cd BlobTools
make -j2
sudo cp blobpack /usr/bin/
sudo cp blobunpack /usr/bin/
cd ~
Unpack a boot.img
We create a folder and place a boot.img in it.
Code:
mkdir ~/test
cd ~/test
abootimg -x boot.img
Unpacking a initrd image
Code:
cd ~/test
mkdir ramdisk
cd ramdisk
gzip -dc ../initrd.img | cpio -i
Now you will have a directory with the ramdisk source files in ~/test/ramdisk
to repack it, run
Code:
cd ~/test/ramdisk
find . | cpio -o -H newc | gzip > ../new-initrd.img
for gzip
Code:
find . | cpio -H newc -o | lzma -c > ../initram.lzm
for lzma
This will give you a new-initrd.img file in ~/test/ for you to use............versions<
Go to the folder and select ALL file or folder BUT source and build !!!!
And compres it file wel be made in home.
modules are install in ubuntu in /lib/modules/
About kernel and initrd and boot.img and blob
Kernel = basic hardware installations and setup
initrd = like a ramdisk
boot.img = kernel + initrd
blob = boot.img + TF special header
Blob file you find in cwm.zip like a kernel update for android
boot.img you will find when using nvflash
kernel gets compiled from a git or source
initrd you can make your own or reuse
i will create cwm.zip to do the flashing
To do this i do.
Code:
mkdir ~/test
cd ~/test
cp ~/TF101-GNU-kernel/arch/arm/boot/zImage ~/test/zImage
abootimg --create ./ubuntu.img -f ./bootimg.cfg -k ./zImage -r ./initrd.img
This will give me a ubuntu.img ready for nvflash but i want cwm.
so i do
Code:
./blobpack kernelblob LNX ubuntu.img
(LNX is boot partition dont change this unless you know what your doing)
Now i got a new file kernelblob that i can add to a cmw.zip file
To do this , open !!!! the cmw.zip below and remove and add the file kernelblob.
Thats it, and ready for flashing.
Rootfs
You sould be able to use any rootfs that is for arm.
you can also build a rootfs with rootstock
keep in mind a rootfs kan have diffrent types of names like ( rootfs.img.ext234 or ubuntu,dabian,linux.img.ext234 or evrey name you want it to be its just a name+ext)
If you want to relock it for oem-config ( nice first setup like name location keyboard setup) do
Code:
touch /var/lib/oem-config/run
Ubuntu
Kbuntu
XBMX
So how do we even flash ?
I use nvflash directly or cwm
The easy why is just using Olife.
Keep in mind that i will never use uboot , only original bootloader of android.
So dualboot is what you need.
if you have dualboot flashed, do this.
Replaced (backup!) initrd-2.6.38.img and 2638-zImage in the kernel folder with my files,
and in Olife update your chromium kernel.
For those that want to use a loop file
Just flash this zip file
And copy the rootfs to sdcard (nand) /sdcard/linux/ubuntu.img (more will come, thats why linux/ubuntu.img)
Wifi setup
Wifi simply needs 2 files and you can get them from android space -> then copy them to Ubuntu space to /lib/firmware/
/data/misc/wifi/nvram.txt -> /lib/firmware
/data/misc/wifi/wpa_supplicant.conf -> /etc/wpa_supplicant.conf #optional
just use a root exploror to copy them to sdcard or usb ( this can alo be done when your in Ubuntu space (/system = mmcblk0p1, /data = mmcblk0p7))
and put them on the right place for Ubuntu.
Bluetooth setup
There are 3 file needed from android space, to get this,
Enable bluetooth
Rename you bluetooth name to what ever you want ( once in Ubuntu you cant change this !!!! )
Leave it on !! and boot to Ubuntu
/data/misc/bluetooth/{bcm4329.hcd,mac.txt} -> /lib/firmware
brcm_patchram_plus (lives on the net) -> /usr/sbin/brcm_patchram_plus (already in)
As last edit /etc/init.d/bsp-tf101 and correct your mac adress --bd_addr ***** (replac *** with mac !!!, mac is located in mac.txt)
.
Code:
#! /bin/sh
do_stop(){
#look if Board Support Package is already running
PS=$(ps -A | grep " brcm_patchram_plus\>")
if [ -n "$PS" ]; then
echo "* Stoping Bluetooth Support Package..."
killall brcm_patchram_plus
fi
}
do_start(){
#if already started then stop first
do_stop
#now start all board support binaries
echo "* Starting Bluetooth Support Deamon..."
rfkill unblock 0
modprobe bcm4329
/usr/sbin/brcm_patchram_plus --enable_hci --baudrate 921600 --bd_addr ***** --patchram /lib/firmware/bcm4329.hcd /dev/ttyHS2&
# making sure the nvtegra dev nodes have the correct permissions
echo "* Setting correct permissions on nvtegra device nodes..."
chmod 0666 /dev/nv* /dev/tegra_*
}
case $1 in
start | restart)
do_start
;;
stop)
do_stop
;;
esac
and reboot and your done.
Installing Tegra HEADER files ( needed when building things like XBMC )
Copy as root all folder to /usr/include/
Installing Opengl-ES
Download the Tegra drivers from Nvidia
Once downloaded unpack it and open a cmdline and go to that direction Where those files are and type,
Code:
sudo ./app*.sh --help
-r = your root directeroy whey you want to install this
--abi = witch version of abi your running, to get you version run in ubuntu on TF
Code:
aptitude show xserver-xorg-core | grep abi
So when running this directy on the TF in Ubuntu you wil get this
Code:
sudo ./app*.sh --abi 10 -r /
Get audio working
Code:
sudo usermod -a -G audio
sudo chmod -R 777 /dev/snd/*
Then open alsamixer and enable
playback
Left And Right speaker mixer DACL/R
Set DC input to DMIC
And sound sould work right away.
Install zram
Code:
sudo wget -O /etc/init/zramswap.conf 'https://wiki.ubuntu.com/ARM/TEGRA/AC100?action=AttachFile&do=get&target=zramswap.conf'
Installing XBMC
sudo apt-get install (try installing all dependencies you can in the readme.ubuntu in xbmc folder , some will fail so just remove them) )
Code:
cd ~
git clone git clone git://github.com/xbmc/xbmc.git
cd xbmc
./bootstrap
./configure --enable-tegra --enable-gles --disable-openmax --disable-vdpau --disable-hal --disable-joystick --disable-debug --disable-dvdcss
make -j2
sudo make install
sudo apt-get install libgl1-mesa-swrast
Loop or native parition
in your config (dualboot.cfg)
You kernel cmdline would be
( if you have native root=/dev/mmblk0p8 rw.........)
( for loop support you add loop= ( location of file !!! + root= (the partition where the file is located !!)
root=/dev/mmcblk0p7 rw loop=/xxx/xxx
Default Kernel
files
Support
hdmi ( audio ? )
USB ( full working )
jack ( mic ? )
Opengl-ES
zram ( needs script also a most have beacuse of low ram space )
-more to come
Sources
kernel
Khronos header package
Tegra Opengl-ES drivers
Blobtools
THANKS TO:

Jhinta said:
Supports..
Code:
OpenGL-ES
zram
Wifi
Bluetooth
FB -> half working no txt output
HDMI fully supported
Kexec enabled , dont know if its even working
Not working !!!
Sound
Touchpad
If you want to use this make sure the 3D driver are installed ( no FB !!! ), so install them first !!!!
And add the modules to you rootfs.
And keep in mind unity does not have gles support yet ( kde sould but didnt tryed it yet )
Download
Kernel
Modules
Source
make sound hardware pupup , still no sound
sudo usermod -a -G audio <your username here>
sudo chmod -R 777 /dev/snd/*
Click to expand...
Click to collapse
I will give this a shot tonight and let you know how it goes.
I'm sorry if this is a stupid question but what is FB? I tried searching on the forum and online but the only reference I could find was facebook.

could you use git, or post a .patch for the framebuffer patch because there is no way I am going to spend ages downloading the kernel source from 2shared then having to try and find WTF you did

Ke1evraTi: It just means the framebuffer which is the base graphics support under linux. Basically since it does not work, you won't see much until the X11 drivers kicks in.
lilstevie: Pulling the original kernel from Asus was way slower than 2shared. Also creating the patch was quick. Only a few hundred lines to skim. I have attached it for you or anyone else who is interested. If my diff options do not suit your fancy, kindly suggest different ones and I will re-post.

lilstevie said:
could you use git, or post a .patch for the framebuffer patch because there is no way I am going to spend ages downloading the kernel source from 2shared then having to try and find WTF you did
Click to expand...
Click to collapse
Sorry m8 i didnt had any sleep last two day's i was broke when i uploaded it , was easy for me fast upload thats why. but looking add the path above that sould do it if not ill will send a patch.
? any one tested already?

download link
I coldn't use the download link, the host gives error like "Gateway Timeout". Can you check it please, is it me or the host?

dismis said:
I coldn't use the download link, the host gives error like "Gateway Timeout". Can you check it please, is it me or the host?
Click to expand...
Click to collapse
The server is currently down for maintenance and will be back up in the next few hours
All done now

lilstevie said:
The server is currently down for maintenance and will be back up in the next few hours
All done now
Click to expand...
Click to collapse
lil , look on nvidia git , tty fix maby? i'm add work cant do anything.

Ok. I am running ubuntu on a sbk2 tf101 using the method posted by jozka.1 how do i apply the new kernels like the on posted here to that install? i know that this is a total noob question but i want to try it on my unit. I know that it says that the video acceleration does not work on unity but should work on kde. will it work on gnome?
Sent from my Transformer TF101 using XDA Premium HD app

Sorry, kernel isn't working for me. I installed the latest linux4tegra driver package, added the modules folder posted to /lib/modules and flashed the kernel through CWM, but the GUI fails to load and running startx from the command line does nothing. I'm not sure if this was my mistake, but the modules posted were for the 2.6.39.4 kernel and Jhinta posted a 2.6.36.4 kernel. Where did I mess up?

MrMuffin24 said:
Sorry, kernel isn't working for me. I installed the latest linux4tegra driver package, added the modules folder posted to /lib/modules and flashed the kernel through CWM, but the GUI fails to load and running startx from the command line does nothing. I'm not sure if this was my mistake, but the modules posted were for the 2.6.39.4 kernel and Jhinta posted a 2.6.36.4 kernel. Where did I mess up?
Click to expand...
Click to collapse
ore you flashed the wrong zip file ore the flashes didnt install make sure after cwm you see the blue line going meening its flashing the blob

Yep definitely the right kernel and I did see the blue line afterwards. Just to make sure that I've done this right, so I:
-download linux4tegra package, run: sudo <path-to>/apply_binaries.sh --root /
-run: sudo cp -r <path-to>/2.6.39.4/ /lib/modules/
-reboot to CWM, flash Ubuntu-3D.zip
-reboot.

MrMuffin24 said:
Yep definitely the right kernel and I did see the blue line afterwards. Just to make sure that I've done this right, so I:
-download linux4tegra package, run: sudo <path-to>/apply_binaries.sh --root /
-run: sudo cp -r <path-to>/2.6.39.4/ /lib/modules/
-reboot to CWM, flash Ubuntu-3D.zip
-reboot.
Click to expand...
Click to collapse
thats it, maby i did send a wrong one , any way here it is

Jhinta said:
thats it, maby i did send a wrong one , any way here it is
Click to expand...
Click to collapse
the latest t4l drivers use the 3.1 kernel, so which version of l4t did you use?

Still no luck with the new kernel posted by Jhinta, with the r12beta drivers installed on a sbkv2 device.
Heres the screen I originally get when I boot:
{
"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"
}
Here's what I get when I run startx:
I'll try it again from scratch, just in case. Let me know if there are any logs or anything you want me to post.

Have you tried maybe sudo depmod -a ? Might fix those module loading issues which could be your problem.

Running lsmod after boot shows that all the modules have loaded. I still get these errors on fully working installs for some reason.

Code:
uname -a
will reveal to you that you are in fact running 2.6.36.4 and not 2.6.39.4 which is jhintas kernel

Proof that I did install Jhinta's kernel:
Results of uname -a:

Look closer
Proof that you did not install Jhinta's kernel:
lilstevie said:
uname -a will reveal to you that you are in fact running ----> 2.6.36.4 <---- and not 2.6.39.4 which is jhintas kernel
Click to expand...
Click to collapse
Results of uname -a:

[App] [ 4.0+] [ROOT] Boot Shell - Execute Shell Commands and scripts at Boot [V 3.5]

Boot Shell allows you to save Linux Shell commands and execute them at boot. The Pro version allows to execute complete shell scripts at boot.
{
"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"
}
You can also save your favourite Linux commands and execute them at your will.
It can also eliminate the need of using init.d scripts for basic needs such as setting CPU parameters at boot such as, CPU Frequencies, governors, and also IO Governers,enable/disable Fastcharge, GPU Overclock etc.
REQUIREMENTS -
->ROOT
->BUSYBOX
Pro Version Extras -
-Ability to Execute Scripts at boot
-View outputs and errors after command execution
-Inbuilt Text/Script Editor
For any queries or problems please feel free to E-mail me at [email protected]mail.com
Try not to execute a resource intensive task or scripts at boot, it can slow down your device startup.
Explanation for Permissions -
-> Read/Write USB Storage - Allow the Shell commands to read/write on Device Storage
-> SuperUser Permission - To Execute Shell Commands
-> Run at Startup - To be able to execute Shell commands at Boot
Credits:
-> CMDProcessor Library, for making Root easy, and to @Androguide.fr for sharing it.
-> @nikwen - For being a very helpful and active contributor in the Java for Android App Development section, and for clearing my initial programming doubts.
Changelog-
8/2/14 -
Initial Release
10/2/14 -
Added notification to confirm execution of commands at boot.
Execution of commands at boot time should be faster now.
12/02/14 -
Added option to enable/disable execution of commands at boot.
Added link to XDA thread in settings.
21/02/14 -
Uploaded to play store
Added option to export saved commands as txt file to sdcard
Fixed a command delete bug
Added help documentation
25/02/14-
Fixed up some strings
Added more feedback options in settings
07/03/2014-
Fixed a bug with exporting of commands
Added a cancel option to command edit dialog
Minor code cleanup
21- Mar - 2014
-Major Overhaul
-Ability to Execute Scripts at boot [Pro Version]
-View outputs and errors after command execution [Pro Version]
-Inbuilt Text/Script Editor [Pro Version]
Click to expand...
Click to collapse
Please try to download from Google Play as it will help me to keep record of number of downloads, app crashes, etc.
For those who do not use Gapps download V3.0 from the attachments below.
P.S. - If you are coming from the Beta Version of the app, the signature for the app has changed so you will have to uninstall the old version to be able to install the new one. To backup your commands, please backup app data using titanium backup or helium, uninstall, reinstall from play store and restore app data. I am really sorry for this inconvenience.

Screenies !!!!

Some useful Shell Commands
USB FAST CHARGE Enable:
Code:
echo 1 > /sys/kernel/fast_charge/force_fast_charge
USB FAST CHARGE Disable:
Code:
echo 0 > /sys/kernel/fast_charge/force_fast_charge
SET GPU CLOCK:
Code:
echo x > /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc
where x is your desired GPU Frequency or frequency step
SET CPU GOVERNER
Code:
echo interactive > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
replace interactive with your desired governer
LOAD A KERNEL MODULE
Code:
insmod /system/lib/modules/module_name
TCP CONGESTION ALGORITHM
Code:
/system/xbin/sysctl -w net.ipv4.tcp_congestion_control=reno
replace reno with your desired value
SET CPU MIN FREQUENCY
Code:
echo 350000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
replace 350000 (350 MHz)with your desired frequency
SET CPU MAX FREQUENCY
Code:
echo 1500000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
replace 1500000(1.5 Ghz) with your desired frequency
SET READ AHEAD BUFFER
Code:
echo 1024 > /sys/block/mmcblk0/queue/read_ahead_kb
replace 1024 with your desired value(in KB)
SET I/O SCHEDULER
Code:
echo row > /sys/block/mmcblk0/queue/scheduler
replace row with your desired governer

gh0stslayer said:
mine
Click to expand...
Click to collapse
Boot Shell has stopped....
My system is 4.0.4
you one picture system UI is beautiful,can you sharing me?
:good:

Lumia997 said:
Boot Shell has stopped....
My system is 4.0.4
:good:
Click to expand...
Click to collapse
@Lumia997 :
Sorry about that, a new version has been uploaded , please try it. Thanks
you one picture system UI is beautiful,can you sharing me?
Click to expand...
Click to collapse
sorry I don't understand, what do you want me to share ?

OK, how does this baby work? That is, what executes the commands? When (linux boot, zygote startup, dalvik up and running)??
How does this relate to selinux?
I have scripts in /data/local/userinit.d/ which are supposed to be run by the init.d system. The only one I know that runs is link2sd's script if I move it to there. Others, apparently do not run, even in cm-10.2 with permissive selinux. I have tasker run them, successfully, when it begins its "listening."
The lead question here is critical! If the app must be present at boot (it is an apk, however!), then it needs be on internal storage or better, on system! If the app needs be present only for its UI, it can be on sdcard or linked (link2sd). It is a user app but maybe it needs place something on system or /etc/init.d/ to operate?

Dovidhalevi said:
OK, how does this baby work? That is, what executes the commands? When (linux boot, zygote startup, dalvik up and running)??
How does this relate to selinux?
I have scripts in /data/local/userinit.d/ which are supposed to be run by the init.d system. The only one I know that runs is link2sd's script if I move it to there. Others, apparently do not run, even in cm-10.2 with permissive selinux. I have tasker run them, successfully, when it begins its "listening."
The lead question here is critical! If the app must be present at boot (it is an apk, however!), then it needs be on internal storage or better, on system! If the app needs be present only for its UI, it can be on sdcard or linked (link2sd). It is a user app but maybe it needs place something on system or /etc/init.d/ to operate?
Click to expand...
Click to collapse
The commands saved on this app are executed in the same way they are executed by a Linux Shell Emulator, or a Terminal on a Native Linux system. The only difference is it save the commands you enter and executes them as soon as the device finishes booting. You can also save commands to a favourite list , which will not be executed at boot, but allows you to manually execute them as you wish.
Edit: - Info: - It uses busybox to execute shell commands
The app works fine when placed on the internal storage of the device, though I am not sure about if it will work if placed on SD Card but in theory it should work, no need to place it on the /system partition.
It cannot run whole shell scripts only single commands, but you can save as many commands as you like
Just make sure you enter a valid command and that you kernel or device supports it.

gh0stslayer said:
The commands saved on this app are executed in the same way they are executed by a Linux Shell Emulator, or a Terminal on a Native Linux system. The only difference is it save the commands you enter and executes them as soon as the device finishes booting. You can also save commands to a favourite list , which will not be executed at boot, but allows you to manually execute them as you wish.
Edit: - Info: - It uses busybox to execute shell commands
The app works fine when placed on the internal storage of the device, though I am not sure about if it will work if placed on SD Card but in theory it should work, no need to place it on the /system partition.
It cannot run whole shell scripts only single commands, but you can save as many commands as you like
Just make sure you enter a valid command and that you kernel or device supports it.
Click to expand...
Click to collapse
Thanks for the info. In other words, would work as I use tasker now but with a much easier UI for scripts entry. Not really a substitute for /etc/init.d functionality because would get run later but otherwise, quite nice. Note that current cm-11 ROMs (for my old LG P500 at any rate) are quite slow getting startup services going.

Dovidhalevi said:
Thanks for the info. In other words, would work as I use tasker now but with a much easier UI for scripts entry. Not really a substitute for /etc/init.d functionality because would get run later but otherwise, quite nice. Note that current cm-11 ROMs (for my old LG P500 at any rate) are quite slow getting startup services going.
Click to expand...
Click to collapse
Yup, not really a substitute for complex init.d scripts, and yes quite similar to the way tasker does shell commands at boot.
But it should be more than enough for some simple CPU, I/O and kernel tweaking etc.

gh0stslayer said:
Yup, not really a substitute for complex init.d scripts, and yes quite similar to the way tasker does shell commands at boot.
But it should be more than enough for some simple CPU, I/O and kernel tweaking etc.
Click to expand...
Click to collapse
... and maybe a tasker plugin to execute "favorites" entered to this app?

Dovidhalevi said:
... and maybe a tasker plugin to execute "favorites" entered to this app?
Click to expand...
Click to collapse
Hmmm, I will have to look into it. I have no knowledge about how to develop plugins for tasker :silly: but I can try, no promises though.
But can't you already add commands in tasker and schedule their execution ?

gh0stslayer said:
Hmmm, I will have to look into it. I have no knowledge about how to develop plugins for tasker :silly: but I can try, no promises though.
But can't you already add commands in tasker and schedule their execution ?
Click to expand...
Click to collapse
It is excruciatingly difficult to enter this stuff on the phone's keyboards. So if I have a "favorite"command in this app and later on decide to use it in tasker, I would not be to happy with struggling to enter it a second time
BTW, most of what I have entered as script are in bash script files. Can these be run by the app or only single line commands?

Dovidhalevi said:
It is excruciatingly difficult to enter this stuff on the phone's keyboards. So if I have a "favorite"command in this app and later on decide to use it in tasker, I would not be to happy with struggling to enter it a second time
BTW, most of what I have entered as script are in bash script files. Can these be run by the app or only single line commands?
Click to expand...
Click to collapse
Single line commands only, you can add the next line of bash script as another command .
Edit:
If you wanna use the same command else where , click on the command select edit and copy the command from the textbox. No need to enter it again.
Sent from my Galaxy Nexus using Tapatalk

gh0stslayer said:
Credits:
-> CMDProcessor Library, for making Root easy, and to @Androguide.fr for sharing it.
-> @nikwen - For being a very helpful and active contributor in the Java for Android App Development section, and for clearing my initial programming doubts.
Click to expand...
Click to collapse
Big thanks for that.
In my opinion it's great that you finished your app. Good job. :good:

nikwen said:
Big thanks for that.
In my opinion it's great that you finished your app. Good job. :good:
Click to expand...
Click to collapse
Thank you very much

Hello everyone, Boot Shell is now available on Play Store. Please find it here
https://play.google.com/store/apps/details?id=com.kislay.bootshellcommand
The signature for the app has changed so you will have to uninstall the old version to be able to install the new one. To backup your commands, please backup app data using titanium backup or helium, uninstall, reinstall from play store and restore app data. I am really sorry for this inconvenience.

New version is up-
Changes -
Fixed up strings
Added feedback options (E-mail and Play Store)
There is an easter egg somewhere too

Version 1.2 is now up-
Changes -
-Fixed a bug with exporting commands to SD Card
-Added a cancel option to command edit dialog
-Minor Code Cleanup
Please feel free to drop your feedback/ comments/ ratings
Email if you need any help, guidance or wanna report a bug.

New major update -
Changelog-
Version 2.0 -> 21- Mar - 2014
-Major Overhaul
-Ability to Execute Scripts at boot [Pro Version]
-View outputs and errors after command execution [Pro Version]
-Inbuilt Text/Script Editor [Pro Version]
Pro Version Link - Boot Shell Pro

help
I use that bootshell but need more time for executing ,its that normal because i already w8 for 4 hours

[12/13/14 finished][Android, iOS compatible][script][tool]check symlinks easily!

Article featured on XDA Portal:http://www.xda-developers.com/android/check-symlinks-chklnk/
use this script for checking symlinks fast and easy![requires busybox 1.19.4 and up]
how to install
STEP1) download the attachment posted below-->chklnk.sh.pdf
STEP2)remove the extension name(and you can change the file name to whatever you'd like)(mine's chklnk.)
STEP3)put it in /bin, /sbin or /xbin(any folder that contains posix applets)
Or... you can install the script like this-->
Code:
$ ./chklnk.sh --install
42 hits.
would you like to install it in /usr/local/bin? (y/n)
please wait...
copying files...
================================================================================
install complete!
type chklnk to run the program!
STEP4)open terminal
Click to expand...
Click to collapse
how to use
(if you have done the "how to install" correctly,) open the terminal, and do this:
Code:
chklnk [some file you want to check]
Click to expand...
Click to collapse
how to self-troubleshoot
if nothing shows up on terminal screen except "error code 1",
don't freak out and just do what i say:
Code:
chklnk --bbpass [your stuff]
if it still don't work, do:
Code:
chklnk --verbose [your stuff]
or do:
Code:
chklnk --verbose --bbpass [your stuff]
and paste the outcome right here.
Click to expand...
Click to collapse
for developers: good luck with your projects

changelogs
-improved script functions
-added help
-some bugfixes
-more bug fixes 11/10/14
-more bug fixes 11/11/14
-header function update 11/14/14
-more bug fixes(now fully working!) 12/13/14
-added compatibility for iOS(bash fix, mount fix, etc...) 1/6/15
-install() fix 2/13/15
-added ability to detect hard binds. 6/2/15
-API update #9 fixes install() issue
Click to expand...
Click to collapse

op updated

op updated

Looks very useful, keeping this in my xbin swiss army knife area , thanks!
Sent from my XT1068

Pizza_Dox said:
Looks very useful, keeping this in my xbin swiss army knife area , thanks!
Sent from my XT1068
Click to expand...
Click to collapse
you're welcome

updated tool.
new feature updated!
-detects hardlinked partitions and folders.

updated with API update #9
-fixes install() issue