Database Develop

[GUIDE]Debian on the tattoo

Guide for debian on the Tattoo
this will NOT delete your android system
if it damage your android i am not responsible to that ... but actually it cant harm your loved phone
you must get the terminal emulator and androidvnc
first you should download the image file from here http://rapidshare.com/files/161776007/debian-armel-750.img.bz2then download the installer package from the attached zip file
this is only for the fyodor ROM or a rom with ext2 modules
extract the image and the package to anywhere or your desktop
copy the installer package to /sdcard/kit and the image to there too
then type
Code:
cd /sdcard/kit
su
sh firstrun.sh
now your debian is installed
to launch it you just write:
Code:
su
debian
to exit the shell type
Code:
exit
now you can make a desktop (icewm confirmed WORKING) with this:
http://www.androidfanatic.com/community-forums.html?func=view&catid=9&id=1620#1620
then you can help me make debian run at / from here ...
cant get the unionfs module into systemhttp://www.saurik.com/id/10

I'm interested, please write a guide.

Holy, it's very interesting
Post a guide please

I have been waiting for this for ages. I will love you long time if you share with us how.

What is debian?
Let me know please.

It is a linux distro. http://www.debian.org/

Thanks man.
Waiting.....

me 2 waiting...

okay i make the guide maybe tomorrow i but it will be in this week

Waiting.

Lets develop debian on Tattoo...
I am loving this..

Re: Debian on the tattoo
ohh..
I don't have mega skill, but maybe we all developers can made it.
-------------------------------------
Sent from my HTC Tattoo

rly looking forward

Great idea!
I have been using Debian for AVR and MIPS for ages, maybe I can help in some way.
I guess/hope the radio interface are open so that Debian application can use, as soon as we made a good Window Manager UI and can get rid of the google's dam binding business ;-)

Re: Debian on the tattoo
I can help with graphics.
-------------------------------------
Sent from my HTC Tattoo

Holyachmed said:
Guide for debian on the Tattoo
this will NOT delete your android system
if it damage your android i am not responsible to that ... but actually it cant harm your loved phone
you must get the terminal emulator and androidvnc
first you should download the image file from here http://rapidshare.com/files/161776007/debian-armel-750.img.bz2then download the installer package from the attached zip file
this is only for the fyodor ROM or a rom with ext2 modules
extract the image and the package to anywhere or your desktop
copy the installer package to /sdcard/kit and the image to there too
then type
Code:
cd /sdcard/kit
su
sh firstrun.sh
now your debian is installed
to launch it you just write:
Code:
su
debian
to exit the shell type
Code:
exit
now you can make a desktop (icewm confirmed WORKING) with this:
http://www.androidfanatic.com/community-forums.html?func=view&catid=9&id=1620#1620
then you can help me make debian run at / from here ...
cant get the unionfs module into systemhttp://www.saurik.com/id/10
Click to expand...
Click to collapse
we can have the list of the things that are missing? so that we can work on it one by one..
Cheers!!

I cannot install it.
I get this error:
modprobe: chdir</system/modules>: No such file or directory
mkdir: cannot create directory '/data/local/bin' : file exists
Any help?

dancer_69 said:
I cannot install it.
I get this error:
modprobe: chdir</system/modules>: No such file or directory
mkdir: cannot create directory '/data/local/bin' : file exists
Any help?
Click to expand...
Click to collapse
try to:
adb shell
su (if u aren't root)
mkdir /system/modules
chmod 775 /system/modules
rm -rf /data/local/bin ( check the content of folder before delete..)

Cannot create /system/modules file exists, so I just chmod it.
I remove folder bin and the scipt run, but very fast print "on" and "#"(root symbol)
After that I tried to run the debian command and I get these errors:
mknod: /dev/loop2:file exists
mount: mounting /sdcard/kit/debian.img on /data/local/mnt failed: No such file or directory (but mnt folder exists)
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
rm failed for -f, No such file or directory
link failed File exists
EDIT:
After fresh installation of fyodor rom 5.31 version, happens again the above error.
Only this time I didn't get any messages when the firstrun.sh script ran.

Another reason why I shouldn't sell my HTC Tattoo...
Nice guide!

[Q] dsifix.ko applied to stock milestome froyo rom

hello, basically my question is that, how to apply the fix to a stock froyo rom...i think that it must be done trougth open recovery but i wanted to be sure. thankss

it can be done through the console of open recovery, or through a terminal editor if you have root.
edit: simpler way for stock roms
copy the dsifix.ko to your sdcard
mount the /system partition as read/write
run these commands:
Code:
cp /sdcard/dsifix.ko /system/lib/modules/dsifix.ko
chmod 644 /system/lib/modules/dsifix.ko
echo "insmod /system/lib/modules/dsifix.ko" >> /system/etc/rootfs/init.mapphone_umts.rc

correct me if im wrong, but the second directory, system/rootfs/, isnt that only for cyano based roms?? because in stock roms it doesnt exist. thanks for the reply.

ah you're right, sorry
hmm you could try using the 'install mods autostarts - not needed in many roms' script thats in androidiani openrecovery, and then running these commands:
Code:
cp /sdcard/dsifix.ko /system/lib/modules/dsifix.ko
chmod 644 /system/lib/modules/dsifix.ko
cd /system/etc/init.d
touch 1dsifix
echo "insmod /system/lib/modules/dsifix.ko" > 1dsifix
chmod 750 1dsifix
I'm not entirely sure this will work, but try it and see.

Hi,
to sum it up:
To use additional kernel modules (e.g. dsifix.ko) you need to tweak the startup scripts (e.g. init.mapphone_umts.rc)
To use tweaked startup scritps like modified init.mapphone_umts.rc you'll need a ROM that makes use of 2nd init process.
Stock ROMs do not use 2nd init, because it's a hacked feature and stock ROMs are usually not hacked
On stock ROM there's also no /system/etc/init.d nor /system/etc/rootfs directory, because they are no used there.
Hope this helps
P.S.: Don't know about this androidiani stuff ...
EDIT: Search button is so nice... http://forum.xda-developers.com/showthread.php?t=1003338
Regards,
scholbert

great i will try this evening, thanks for the repliess.
Sent from my Milestone using XDA App

the androidiani mod enables 2nd-init, which means it checks for scripts in the init.d folder
that link is only for the display update fix, which causes tearing, not for the kernel module fix thats popped up recently. However, we can modify coldsphinx's instructions to suit our purposes.
as usual, you'll need to move the dsifix to /system/lib/modules
Code:
cp /sdcard/dsifix.ko /system/lib/modules/dsifix.ko
chmod 644 /system/lib/modules/dsifix.ko
then rename the mot_boot_mode file to mot_boot_mode.bin
Code:
mv /system/bin/mot_boot_mode /system/bin/mot_boot_mode.bin
then create the file /system/bin/mot_boot_mode
and add this to the file:
Code:
#!/system/bin/sh
export PATH=/system/bin:$PATH
mot_boot_mode.bin
insmod /system/lib/modules/dsifix.ko
and then finally set the permissions
Code:
chmod 755 /system/bin/mot_boot_mode
it will work.

GReat! thanks!

[Q] Compiling kernel modules

Hi
I'm a new owner to a Galaxy tab 8.9 and trying to make it able to mount NFS exports.
So I've rooted the device, installed SuperUser and terminal emulator. Then I downloaded the kernel source tree from Samsung, I compiled the NFS module on my desktop computer moved it to /system/lib/modules on the tab. But it doesn't work, when I do 'insmod nfs.ko' it gives back 'insmod: init_module nfs.ko failed (No such file or directory)'
Is it possible at all to add modules to the standard kernel that comes with the device?
Is my device completely rooted because when I try 'adb root' I get 'adbd cannot run as root in production builds'

me too...
I just encountered the exact same problem on my LG Revolution, except I'm trying to load nfsd.ko for server support.
I know I built it correctly because I've already succeeded in getting tun.ko working properly...
Code:
root # /system/bin/insmod /system/lib/modules/nfsd.ko
insmod: init_module '/system/lib/modules/nfsd.ko' failed (No such file or directory)
root # ls /system/lib/modules
... nfsd.ko
Very odd...

When you do the insmod are you actually in the /system/lib/modules directory? If not, you have to use the full path to the module.
The message with "adb root" is normal even on a rooted device. If you can do "adb shell" followed by "su" you should be ok.
edit...
Now that I think of it...that message usually means the module file was found but a dependency wasn't.

gtj0 said:
Now that I think of it...that message usually means the module file was found but a dependency wasn't.
Click to expand...
Click to collapse
Yep that was my problem. My nfsd.ko needed dependencies that didn't exist...
To the OP: try to insmod the nfs.ko module again and then look at the output of dmesg. You should see messages complaining about the dependencies required by the nfs module.
Then you ought to be able to either remove the requirement for them from your module (my nfsd.ko wanted posix_acl support so I just got rid of that option and rebuilt the module) or if it's something you need/want you might be able to add support for whatever it is as another module...
Good luck and I hope I didn't intrude upon your thread too much

Thanks, I had indeed a dependency problem. Now I managed to load nfs.ko and sunrpc.ko and lockd.ko that were needed because of dependency.
Although I'm still having problems at mounting an nfs export. Previously, before kernel module problem was solved, I got the error message 'No such device' when I tried to mount, now I get 'Invalid argument' instead.
I've tried commands like
busybox mount -t nfs 192.168.1.100:/mnt/raid/media /sdcard/nfs
and
busybox mount -o nolock,ro,hard,intr,vers=3 -t nfs 192.168.1.100:/mnt/raid/media /sdcard/nfs
Any thoughts?

NFS Share - Invalid Argument
Marlin79 said:
........... now I get 'Invalid argument' instead.
I've tried commands like
busybox mount -t nfs 192.168.1.100:/mnt/raid/media /sdcard/nfs
and
busybox mount -o nolock,ro,hard,intr,vers=3 -t nfs 192.168.1.100:/mnt/raid/media /sdcard/nfs
Any thoughts?
Click to expand...
Click to collapse
Seems like an Old thread, and I would assume you've gotten this fixed already, but in case it ISN'T fixed...
>Double check your NFS config (/etc/exports file) and confirm that you are sharing:
* /exports/mnt/raid/media *
If you specified something else in your /etc/exports file, check to make sure your Hard drive (I assume /mnt/raid/media) is soft-linked to the share name you wanted to give it, or that at least the subfolders/files you want shared are softlinked to the /exports/share directory.
**e.g.**
# ln -s /exports/media/ /mnt/raid/media
-OR-
# ln -s /exports/media/shared_media_1.mp4 /mnt/raid/media/actual_file.mp4

Can't install apk from sdcard on CM 10.1

Hi guys, İ just flashed the cm10 mod on stock kernel everything seems to work properly but can't install apks from sdcard. Is this a bug? Or did I do something wrong?

AlexZooL said:
Code:
mount -o remount,rw /
chmod 755 /mnt/shell
chmod 555 /storage
Decision "problem parsing package"
Drew script to automatically run, throw in the system / etc / init.d (unpacked from the archive)
set permissions to 755-rwxr-xr-x (the letter П)
If all of a sudden does not start at boot - install Script Manager, open the script in it and put SU and BOOT
Click to expand...
Click to collapse
Download this file
forum.xda-developers.com/attachment.php?attachmentid=1897898&d=1366473855

[Q] Init.d under Cocore 6.2 dont working [SOLVED]

Hi
Im using Galaxy S Advance with:
JB 4.1.2 and stock ROM
rooted
kernel Cocore 6.2
I tried to use script on boot from init.d directory, unfortunately not working.
To see if it works fine, I created /etc/init.d folder
with permissions 777, owner root
Inside init.d folder, I created simple script: testinit.sh also testinit
Code:
#!/system/bin/sh
echo init.d script is working > /storage/sdcard0/init.txt
file permissions 777, owner root
But after restart, file init.txt on sdcard0 isnt created,
so I suppose that script isnt running.
I created also another script follow Cocore thread
Code:
#!/system/bin/sh
insmod /lib/modules/logger.ko
for start logger. Logger didnt start also.
Both scripts started in console or adb works fine.
Tnx in advance

darcik said:
Hi
Im using Galaxy S Advance with:
JB 4.1.2 and stock ROM
rooted
kernel Cocore 6.2
I tried to use script on boot from init.d directory, unfortunately not working.
To see if it works fine, I created /etc/init.d folder
with permissions 777, owner root
Inside init.d folder, I created simple script: testinit.sh also testinit
Code:
#!/system/bin/sh
echo init.d script is working > /storage/sdcard0/init.txt
file permissions 777, owner root
But after restart, file init.txt on sdcard0 isnt created,
so I suppose that script isnt running.
I created also another script follow Cocore thread
Code:
#!/system/bin/sh
insmod /lib/modules/logger.ko
for start logger. Logger didnt start also.
Both scripts started in console or adb works fine.
Tnx in advance
Click to expand...
Click to collapse
Try this way: LINK.

Tnx for answer, atm I abandoned testinit script, this isnt important
and focused on start of logger .
I changed it to
Code:
#!/system/bin/sh
busybox mount -o remount,rw -t auto /system;
busybox insmod /lib/modules/logger.ko
but logger didnt start.
Does the system log, what happens when boot, I mean errors?
I have a habit of "big" Linux system

darcik said:
Tnx for answer, atm I abandoned testinit script, this isnt important
and focused on start of logger .
I changed it to
Code:
#!/system/bin/sh
busybox mount -o remount,rw -t auto /system;
busybox insmod /lib/modules/logger.ko
but logger didnt start.
Does the system log, what happens when boot, I mean errors?
I have a habit of "big" Linux system
Click to expand...
Click to collapse
I think log starts after script is executed, and it can't be executed during pre-boot. So maybe it only works when you get in system (booted). And then there is not much to show, try doing some thing while logcat is triggered. Like change governor, IO etc.
I am just gessing this, maybe I am wrong about that, but seams logical to me. :fingers-crossed:

Lol
Incidentally, I found the answer to my problem in this topic.
Save the script without any extensions (Yes, not even .sh extension).
Click to expand...
Click to collapse
So I renamed my script to logcat without sh extension and all works.
Anyway tnx for help.

Cocore 8.0 init.d not working
I make this init.d file for cocore 8.0:
#!/system/bin/sh
busybox mount -o remount,rw -t auto /system;
echo 12 > /sys/module/mxt224e/parameters/threshold_batt
echo init.d script is working > /storage/sdcard0/init.txt
echo "pegasusq" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo "sio" > /sys/block/mmcblk0/queue/scheduler
echo 100663296 > /sys/block/zram0/disksize
mkswap /dev/block/zram0
swapon /dev/block/zram0
echo 700 > /sys/kernel/abb-charger/max_ac_c
echo 0 > /sys/module/mali/parameters/mali_debug_level
Click to expand...
Click to collapse
placed in /system/etc/init.d with "logcat" name. This scirpt don't make the txt file. Why?

Permission 755 for script file. No .sh at the end - just filename.
That should help
Sent from my SGS Adv. using xda-developers app.

th3cr0w said:
Permission 755 for script file. No .sh at the end - just filename.
That should help
Sent from my SGS Adv. using xda-developers app.
Click to expand...
Click to collapse
The solution was i left some space after the command. Thank you!