Related
Hi all,
Forgive the noobishness.
I rooted my device using the "One-Click" method found here: http://forum.xda-developers.com/showthread.php?t=1011196. It appears to have flashed the 1.3.0 Tiamat kernel in the process.
I am trying to follow the instructions here to flash the latest 1.4.0 Tiamat kernel: http://forum.xda-developers.com/showthread.php?t=978013
When I went to Mounts & Storage --> Mount USB Storage, I received a pop-up in Windows informing me that I had to format the drive before first use. I tried cancelling that to avoid it, but there was no way around it. I ended up formatting some 3MB drive (although I'm not sure where/what this is.)
I then proceed with the instructions "Drop kernel onto SD card". The problem is, the ZIP is larger than 3MB and won't fit onto the drive that shows up on my PC when I mount the storage as instructed.
Confused as to what I actually "formatted for first use", I actually put an SD Card in the Xoom's reader (even though I don't think it was working yet, which is part of why I want the new kernel), and repeated the 'mount' process. This didn't seem to help at all.
So - where did I go awry? Any advice on where to go from here and how to flash 1.4.0? Thanks in advance.
The easiest way to flash tiamat is to download kernal manager for the market and flash that way.
Jthom203 said:
The easiest way to flash tiamat is to download kernal manager for the market and flash that way.
Click to expand...
Click to collapse
Had no clue such a thing existed. I had to also install Busybox but it seems to have done the trick. Thanks once again for your help!
no worries
I may have spoken too soon. It seems that the method didn't work properly. Kernel Manager says I installed the kernel, but when I go to Settings --> About Tablet, it still shows version 1.3.0 Tiamat kernel.
It also seems to have broken my Wifi Radio, which now says "Error" since the reboot.
Any ideas?
run it one more time. Make sure you hit the more info button to verify the version
How do I run it again? I had verified before that it was the 1.4.0 Kernel in the Info.
When I go back, all it says is "Install" but the button is greyed out.
When I installed BusyBox through the market, I unloaded it to /system/xbin.
Would this explain why WiFi isn't working?
The wifi isn't working because something wasn't pushed right. I would try to flash to 1.3.2 then back up to 1.4.0 if that doesn't work we'll have to manually push the wifi drivers.
Edit :
If you open busybox are you running 1.18.4?
Hey again -
I did as you suggested, flashed down to 1.3.2 then back up to 1.4.0 via Kernel Manager. I should note that each time I flashed, to whichever version, I had to activate the device for the 3G radio to work.
After doing this, Wifi still isn't working. In About Tablet, Kernel Version is showing up as "2.6.36.3Tiamat_Xoom-v1.3.0-g5019ece-dirty [email protected] #3".
I am going to have to call it a night but any/all info you can post, I will read in the AM. Thanks again for answering these questions.
Ok this is what i would try next. Go here and down load the 1.3.1 kernel: http://forum.xda-developers.com/showpost.php?p=11798679&postcount=2 copy and paste these commands:
Code:
1. Reboot into the bootloader by running:
adb reboot bootloader
2. Flash the boot image to your boot partition, then boot back into Android by running:
fastboot flash boot boot.img
fastboot reboot
3. Push the bcm4329.ko, scsi_wait_scan.ko, and any other modules to your /system/lib/modules folder and reboot.
adb remount
adb push bcm4329.ko /system/lib/modules/bcm4329.ko
adb push tun.ko /system/lib/modules/tun.ko
adb push scsi_wait_scan.ko /system/lib/modules/scsi_wait_scan.ko
adb push cifs.ko /system/lib/modules/cifs.ko
adb push vold.fstab /system/etc/vold.fstab
adb reboot
NOTE: Special Instructions for 1.3.1
You have to manually make a new directory called "sdcard2" inside "sdcard" prior to flashing. Either use your file explorer of choice or...
Code:
adb shell
mkdir /data/media/sdcard2
exit
CREDIT FOR Flashing Instructions Template goes to coolbho3000
This will enable your sdcard slot. Then you can download the zip 1.4.0 and put it onto you sdcard and flash through clock work recovery
I wonder what exactly you formatted? I don't think the actual SD card will pop up in windows explorer unless you run a script that enables it for USB.
Make sure the sdcard2 folder is in the root xoom folder in windows explorer (or the sd folder in the Xoom explorer), flash down to 1.31, push the five files then flash CWM. If done correctly CWM can mount the actual sd card on its own and you can install 1.40 there.
I reverted to 1.3.1 and the Wifi radio is now fixed. Thanks!
I created the sdcard2 folder, and now have to go scrounge up a microSD.
So, where ought I place the Tiamat_Xoom-v1.4.0.zip? I'm assuming it goes on the sdcard2 folder when I mount the USB storage via CWM? Or do I need to push it to /data/media/sdcard2 via ADB?
EDIT: all figured out now. Thanks to all for your help!
Please note: the 1.4.0 kernel through Kernel Manager is bunk! At least as of last night! Flashing through CWM did the trick, but I had to flash 1.3.1 first...
volta said:
Please note: the 1.4.0 kernel through Kernel Manager is bunk! At least as of last night! Flashing through CWM did the trick, but I had to flash 1.3.1 first...
Click to expand...
Click to collapse
It might have to do with the fact that the sdcard was not yet functional on your xoom. I started flashing at 1.3.0 and flashed as BRD was releasing stable kernels. So by the time 1.4.0 was released i was all ready on 1.3.2 and Kernal manager worked great for me. But i am glad you were able to get everything working, and enjoy 1.4.0 BRD is doing some excellent work.
Here is what I've tried:
1. Settings -> about tablet to get kernel version: 2.6.32.39-cyanogenmod [email protected] #1
2. Go to http://droidbasement.com/db-blog/ and find the kernel for gTab. There are several one, I just picked one with Gingerbread and downloaded
lib-2632.39_gb.tar.gz
Unpack on put cifs.ko under /system/lib/modules
3. Install CIFS Manger
4. Run CIFS Manager, add the share
5. If there is problem mount it in rw mode, use option "rw,noperm" (thanks, rajeevvp)
The share is successfully mounted.
Thanks!
redhonker said:
Here is what I've tried:
1. Settings -> about tablet to get kernel version: 2.6.32.39-cyanogenmod [email protected] #1
2. Go to http://droidbasement.com/db-blog/ and find the kernel for gTab. There are several one, I just picked one with Gingerbread and downloaded
lib-2632.39_gb.tar.gz
Unpack on put cifs.ko under /system/lib/modules
3. Install CIFS Manger
4. Run CIFS Manager, add the share
The share is successfully mounted.
The only issue I have is that it can't seem to mount a share in read-write mode even though it's shared with write permission. Does anyone know how to fix it?
Thanks!
Click to expand...
Click to collapse
After pushing the cifs module to the tablet you need to add an chmod and then you also need a insmod line every time you want to use it (at least after following a reboot).
Go back and read the instructions on droid basement. He has the details of the steps following loading the cifs.ko.
Good luck.
Sent from my ADR6300 using Tapatalk
CIFS manager already loads the module fine. Are you saying in order to mount in rw mode, it needs permission on cifs.ko file?
redhonker said:
CIFS manager already loads the module fine. Are you saying in order to mount in rw mode, it needs permission on cifs.ko file?
Click to expand...
Click to collapse
No, you don't.
CIFS Manager should have an option to do a read-write mount.
Otherwise, you can try changing the mounting back into read-write mode:
Code:
$ su
# /system/xbin/mount -w -o remount /CIFS/PATH
Replace, /CIFS/PATH with the directory you provided to CIFS Manager.
Also, understand my cautions, as mentioned in the other thread, about mixing and matching kernels and kernel modules. I would suggest that you also install the kernel that goes with the module file you downloaded--ie. get the one in the same blog post.
Appreciate your advice on not mixing kernel and modules. I could not tell which exact build CM 7 uses so I had to pick one. When I get more experienced with Android, I may start changing kernels.
Doesn't CIFS uses rw mount by default? If not, what's the option? rw? I've tried that as well.
If I change the system file to mount it by default, I'd have to save the password on the command line, right? Will wireless be ready at that time? And if server or wireless is not ready at the time, I'd need to manually remount with some tool, do I?
Thanks!
redhonker said:
Appreciate your advice on not mixing kernel and modules. I could not tell which exact build CM 7 uses so I had to pick one. When I get more experienced with Android, I may start changing kernels.
Doesn't CIFS uses rw mount by default? If not, what's the option? rw? I've tried that as well.
If I change the system file to mount it by default, I'd have to save the password on the command line, right? Will wireless be ready at that time? And if server or wireless is not ready at the time, I'd need to manually remount with some tool, do I?
Thanks!
Click to expand...
Click to collapse
Cm7 includes pershoots kernel. The gb one.
Sent from my ADR6300 using Tapatalk
not to confuse issue with whatop is having but I wonder if anyone has run into a problem with cifs in which it doesn't include all of the folders from your windows shares.
redhonker said:
Here is what I've tried:
1. Settings -> about tablet to get kernel version: 2.6.32.39-cyanogenmod [email protected] #1
2. Go to http://droidbasement.com/db-blog/ and find the kernel for gTab. There are several one, I just picked one with Gingerbread and downloaded
lib-2632.39_gb.tar.gz
Unpack on put cifs.ko under /system/lib/modules
3. Install CIFS Manger
4. Run CIFS Manager, add the share
The share is successfully mounted.
The only issue I have is that it can't seem to mount a share in read-write mode even though it's shared with write permission. Does anyone know how to fix it?
Thanks!
Click to expand...
Click to collapse
OP,
See modified instructions from your first post. This should get you up and running.
1. Settings -> about tablet to get kernel version: 2.6.32.39-cyanogenmod [email protected] #1
2. Go to http://droidbasement.com/db-blog/ and find the kernel for gTab. There are several one, I just picked one with Gingerbread and downloaded
lib-2632.39_gb.tar.gz
Unpack on put cifs.ko under /system/lib/modules/2.6.32.39-cyanogenmod/
From ADB or terminal emulator (enable SU and do not need the adb part)
adb remount
adb shell chmod 644 /system/lib/modules/2.6.32.39-cyanogenmod/MODULE.ko
adb shell insmod /system/lib/modules/2.6.32.39-cyanogenmod/MODULE.ko
3. Install CIFS Manger
4. Run CIFS Manager, add the share
I wanted to help you with this earlier but been sidetracked. I hope this helps
redhonker said:
Doesn't CIFS uses rw mount by default? If not, what's the option? rw?
Click to expand...
Click to collapse
Yes, by default it should be mounted read-write. If, for some reason, it gets mounted read-only, you can use the remount command I gave earlier to make the mount read-write again.
But, there could be other reasons for you not being able to write to the share directory. Permission and UID/GID mismatches could be one reason. Try adding the "noperm" flag to tell Linux not to check permissions locally ie. do the permission checking only on Windows:
Code:
/system/xbin/mount -t cifs //SERVER-IP-ADDRESS/SHARENAME /some/path -o rw,noperm,domain=DOMAIN,username=USER.NAME,password=PASSWORD
If I change the system file to mount it by default, I'd have to save the password on the command line, right? Will wireless be ready at that time? And if server or wireless is not ready at the time, I'd need to manually remount with some tool, do I?
Click to expand...
Click to collapse
Which system file? If you mean /etc/fstab, then that file does not exist on Android.
CIFS Manager (I haven't used it) should have an option to let you store the password securely. On normal Unix systems, the mount command accepts a "credentials=/some/file.txt" option which can be used in place of the "domain=XXX,username=YYY" options when mounting. Unfortunately, the mount command on the gTablet does not understand that option--I checked: you have to do it the old-fashioned way. You can't even skip the "password=" bit. On Unix, if you skip that, the mount command will prompt you for the password.
The solution, if you don't use CIFS Manager, is to place all the commands--the insmod and the mount--into a shell-script and give it 700 permissions. That way only the owner can see what's inside it and you can run the script after the wireless has come up.
noperm does the trick. Will update first post.
Oozura said:
From ADB or terminal emulator (enable SU and do not need the adb part)
adb remount
adb shell chmod 644 /system/lib/modules/2.6.32.39-cyanogenmod/MODULE.ko
adb shell insmod /system/lib/modules/2.6.32.39-cyanogenmod/MODULE.ko
[/B]
Click to expand...
Click to collapse
Could you explain the exact process for doing this from a terminal emulator. My main hold up is the /system directory being read only, so I can't copy the module (CIFS.KO in this case) to that directory.
h3llphyre said:
Could you explain the exact process for doing this from a terminal emulator. My main hold up is the /system directory being read only, so I can't copy the module (CIFS.KO in this case) to that directory.
Click to expand...
Click to collapse
You don't need to put cifs.ko into /system. If CIFS Manager asks for the path to a cifs.ko file, then you can put the file anywhere you want.
I have a new problem. There seems to be a limit on the file size. I have a 3 GB file shows up as 28 KB. Does anyone have success with large file? Thanks
I tried your instruction... there are two problems...(my rom is also cm7.0.3)
1. I can't put the cifs.ko into /system/lib/modules~ it seems that it is forbid to copy some files into system folder...
2. so I tried to put the cifs.ko in the /mnt/cifs.ko, and made the related setting in cifs manager(path to cifs.ko), then i mounted, but it showed that:"no route to host"
but i am sure that my ip and password is correct... so is there anyone know how to solve this problem?
I used Root Explorer. I am sure there are other means to put it under /system. I am not sure if that's necessary
savage0 said:
I tried your instruction... there are two problems...(my rom is also cm7.0.3)
1. I can't put the cifs.ko into /system/lib/modules~ it seems that it is forbid to copy some files into system folder...
2. so I tried to put the cifs.ko in the /mnt/cifs.ko, and made the related setting in cifs manager(path to cifs.ko), then i mounted, but it showed that:"no route to host"
but i am sure that my ip and password is correct... so is there anyone know how to solve this problem?
Click to expand...
Click to collapse
I literally just went through this today. Download Terminal Emulator (free on the market).
PS: Don't type the '#' sign below.
#su
#/system/xbin/mount -w -o remount /system
#cp /SDCARD/cifs.ko /system/lib/modules/2.6.32.41-cyanogenmod/
#/system/xbin/mount -r -o remount /system
Then, just add the path /system/lib/modules/2.6.32.41-cyanogenmod/ into CIFS Manager. Should be all set.
redhonker said:
I have a new problem. There seems to be a limit on the file size. I have a 3 GB file shows up as 28 KB. Does anyone have success with large file? Thanks
Click to expand...
Click to collapse
File size limits depend on the underlying filesystem.
I tried the following command on an external NTFS formatted USB HDD connected to a Linux desktop mounted on the gTablet at /mnt/usbdisk via CIFS, and had no problems.
Code:
# ls -l /mnt/usbdisk/rvp/bak/hda3.img
-rw-rw-rw- 1 root root 8011422720 Apr 17 2010 /mnt/usbdisk/rvp/bak/hda3.img
# dd if=/mnt/usbdisk/rvp/bak/hda3.img of=/dev/null bs=1M skip=7500
140+1 records in
140+1 records out
147102720 bytes (140.3MB) copied, 150.135761 seconds, 956.8KB/s
The command skips the initial 7.5 GB of a 8,011,422,720 byte file and reads the rest (~140 MB).
rob_z11 said:
not to confuse issue with whatop is having but I wonder if anyone has run into a problem with cifs in which it doesn't include all of the folders from your windows shares.
Click to expand...
Click to collapse
I had the same issue, but I found the guide on abettergeek which helped me fix it. Turns out the problem is that the mount point created by Cifs Manager doesn't have execute permissions.
I don't have enough seniority to post the link, but it's a recent post on abettergeek.com. If someone with enough seniority wants to paste it, some others may find it extremely helpful.
archmcd said:
I had the same issue, but I found the guide on abettergeek which helped me fix it. Turns out the problem is that the mount point created by Cifs Manager doesn't have execute permissions.
I don't have enough seniority to post the link, but it's a recent post on abettergeek.com. If someone with enough seniority wants to paste it, some others may find it extremely helpful.
Click to expand...
Click to collapse
The link I believe you are refering to is here: http://blog.abettergeek.com/hardwar...n-cyanogenmod-7-0-3-on-the-viewsonic-gtablet/
I have the same issue. I haven't tried this fix yet, but I will give it a go.
ByteWrencher
Pls, where I can put "rw,noperm" in cifs manager? I tried in module path as:
/system/lib/modules/slow-work.ko:/system/lib/modules/cifs.ko rw,noperm
And:
/system/lib/modules/slow-work.ko:/system/lib/modules/cifs.ko:rw,noperm
But still don't working as rw.
Ty.
I spent entirely too much time on this, so I'll post my boot.img and my findings here in case it's useful to anyone else in the future.
Paladin ROMs:
This page and this thread have working links to CWM and Superuser zips.
This page has a link to an ICS 4.0.3 ROM running Linux 3.0.8. I installed this ROM, but was disappointed with the kernel's feature set. Important options like CONFIG_IP_NF_TARGET_REJECT and CONFIG_IP_NF_TARGET_LOG were disabled.
This page has a custom ROM by "pinkflozd". I wasn't able to find this image in the wild. It may have a newer kernel (3.0.23?) but AFAICT it doesn't have the Netfilter changes I needed either.
Custom kernel build:
I stumbled across this kernel and used it as a baseline. Then I enabled:
Various missing Netfilter features (e.g. LOG and REJECT targets)
CONFIG_TUN
CONFIG_CIFS
The process looks like:
Install CWM
Find the .zip file for the ROM you want to use, e.g. the ICS 4.0.3 link above
Install that ROM and make sure the stock kernel works
Create a new boot.img with the desired options enabled
Flash the new boot.img with CWM
Basic steps to create the new boot.img:
Code:
git clone -b paladin-3.0.8 git://github.com/cernekee/linux
cd linux
git submodule init
git submodule update
cd paladin
cp /path/to/boot.img orig.img
make NDK=/opt/android-ndk-r9b
# if desired, edit kernel code or .config, and rerun "make"
The scripts under linux/paladin/ will extract the ramdisk from orig.img, then create a new boot.img based on your kernel source tree. For more details on the kernel build, see paladin/README .
Kernel installation:
To flash the new image, reboot into CWM, then:
Code:
adb push boot.img /tmp/
adb shell "dd if=/tmp/boot.img bs=1048576 seek=3 count=8 of=/dev/block/mmcblk0 ; sync"
# hit the reset button again
Other random findings:
I did not have any luck with the "z4root" app, although ro.secure=0 on this ROM so "adb shell" always gives you a root shell. It did take some work to find Superuser/su binaries that worked on MIPS.
Enabling Netfilter's conntrack option seemed to cause dhd.ko to become unstable, possibly because it affected binary compatibility with existing kernel modules. So I left it alone.
This ROM is missing native iptables/ip6tables binaries, so AFWall needs to be set to use the builtin copies. The latest AFWall betas do ship with MIPS binaries now (the purpose of this exercise was to test them).
Checking the box to enable IPv6 crashes AFWall instantly. Need to investigate this.
AFWall's inbound connection option probably will not work, due to the lack of conntrack in the kernel.
This ROM appears to be missing some Java libraries needed for ICS+ VpnService apps to work.
NDK r9b is the first NDK release with support for the "MXU" SIMD instructions supported by the Ingenic JZ4770 chip. Prior to this, most people used Ingenic's special toolchain to build the kernel.
To forcibly boot into CWM, hold down VOL+ while pressing the reset button.
I cannot figure out how to install kexec boot. I have the latest crombi-kk and twrp 2.6.3-that3. I tried running the latest 2.5.6 script as root in android terminal emulator, but I keep running into problems. I can successfully install Kexec blob, however when I try to install Android kexec Kernel I keep getting the same error "You are not running this script from the correct directory. Exiting" (I a have it located on my external sd card in a folder named "TF700t-AKBI-v2.5.6"). I cannot for the life of me figure out how to get passed this. And yes I have experience with linux and I have tons of experience with android and roms and flashing things.
Hi
I updated my Phone via CyanogenMod Updater .
So i get the "official" CyanogenMod 11-20140104-SNAPSHOT-M2-xt897 with
3.0.101-gbfa6ebb ([email protected] #1) Kernel.
Is a NFS/CIFS module available or
would someone be so kind to compile one =) ?
thx
Fr4nz84 said:
Hi
I updated my Phone via CyanogenMod Updater .
So i get the "official" CyanogenMod 11-20140104-SNAPSHOT-M2-xt897 with
3.0.101-gbfa6ebb ([email protected] #1) Kernel.
Is a NFS/CIFS module available or
would someone be so kind to compile one =) ?
thx
Click to expand...
Click to collapse
Why the quotes around "official"?
Cifs and nfs support is built-in, there's no need for additional loadable kernel modules (you can check https://github.com/CyanogenMod/andr.../arch/arm/configs/msm8960_mmi_defconfig#L3091 )
If mount fails for you, try busybox mount.
Btw., after CM11 M2, Motorola msm8960 2012 devices were unified under moto_msm8960 moniker in CM11.
Later, after the release of the official KitKat update for only a subset of the devices being part of the moto 2012 family, xt897 builds went under moto_msm8960_jbbl (jellybean bootloader) unified builds.
So the latest CM11 builds for xt897 can be found here: http://download.cyanogenmod.org/?device=moto_msm8960_jbbl
For CM12, the builds were separated again, so CM12 builds for xt897 can be found again under http://download.cyanogenmod.org/?device=xt897
A other problem?
Thanks kabaldan.
So then I hava a other problem.
What have I done:
I installed SuperSU v2.46 via OpenRecovery-
I installed BusyBox Free after reboot
In terminal I execute:
su -c setenforce 0 && su --mount-master -c mount -o username=franz,password=XXX,rw,noperm,file_mode=0777,dir_mode=0777 -t cifs //192.168.100.150/daten0 /sdcard/cifs/daten0
I see SuperSU granting access for setenforce and mount.
But the directory is still empty with or without root.
So I was assuming cifs was missing.
What else could be the problem?
It shouldn't a problem on the sever side. I can access it via Windows 7, n900 (maemo) and a cheap Q29 (Android 4.0.4).
P.S.:
Sorry, the quotes was a stupid idea. I was trying to say it’s not the original installed OS.
But it’s simply the stable CyanogenMod 11 via updater. No ROM or whatever.
I've always accessed CIFS shares thru an app like ES File Explorer. Works fine.
Fr4nz84 said:
Thanks kabaldan.
So then I hava a other problem.
What have I done:
I installed SuperSU v2.46 via OpenRecovery-
I installed BusyBox Free after reboot
In terminal I execute:
su -c setenforce 0 && su --mount-master -c mount -o username=franz,password=XXX,rw,noperm,file_mode=0777,dir_mode=0777 -t cifs //192.168.100.150/daten0 /sdcard/cifs/daten0
I see SuperSU granting access for setenforce and mount.
But the directory is still empty with or without root.
So I was assuming cifs was missing.
What else could be the problem?
It shouldn't a problem on the sever side. I can access it via Windows 7, n900 (maemo) and a cheap Q29 (Android 4.0.4).
P.S.:
Sorry, the quotes was a stupid idea. I was trying to say it’s not the original installed OS.
But it’s simply the stable CyanogenMod 11 via updater. No ROM or whatever.
Click to expand...
Click to collapse
CM11 M2 is quite old, so I can't be 100% sure it worked there, but I'm convinced that it worked fine even on such old build.
I mount cifs shares quite regularly on my xt897, so I guess I would have noticed if it was not working anymore in any milestone build.
Regarding SuperSU and BusyBox Free - there's no need to install anything like that, CM has built-in su and also busybox.
I'm on CM12 and I don't plan to restore CM11 any time soon (and certainly not M2, if anything it would be moto_msm8960_jbbl M12 or a recent moto_msm8960_jbbl nightly), but something like this has always worked for me:
Code:
su
mount -o username=franz,password=XXX,rw,noperm,file_mode=0777,dir_mode=0777 -t cifs //192.168.100.150/daten0 /sdcard/cifs/daten0
I've just tested it (indeed with my own server path and user credentials) and it works fine.
To use busybox for mount, just replace "mount -o..." with "busybox mount -o..."
The stock CM busybox resides in /system/xbin , btw.
@arrrghhh good tip! Compared to AndSMB I can at least look at pictures without downloading with hand.
@kabaldan
You are totally right with cat /proc/filesystems I can see the Kernel supports cifs.
I had to install SuperSu because there was no su in terminal available.
After playing around, I was able to mount with:
mount -o username=franz,password=XXX,rw,nodev,relatime,default_permissions,allow_other -t cifs //192.168.100.150/daten0 /sdcard/cifs/daten0
But it’s only available to the terminal where I executed the command. Do I have multiple root users?
I don’t know something in my system feels wrong.
Could there some other security policy I am not aware of?
It works now. It seems it was a update problem.
I wipe/clean the system with Open Recovery
removed all Files and Folders in /system (To remove old apps especially SuperSu)
And installed cm-11-20140104-SNAPSHOT-M2-xt897.zip again with Open Recovery
Now su is there on start and root is managed by the System. And I can mount cifs normally.
Whatever, now the shell seams not proper configured so I get this ^[[A^[[D^[[C for arrow keys, in su.
Also I can't get Link2Sd to work because mount give me constantly "invalid argument"( not more) even when I try it on console. Fells like it don’t want me to mount my second partition.
OK is a problem with the SD Card mount works normally. I tested it with another sd card.