Open GoogleCodeExporter opened 9 years ago
[deleted comment]
Get me:
# adb shell
# cat /proc/version
# cd /system/lib/modules
# modinfo cifs.ko
# lsmod
please.
Original comment by showp1984
on 16 May 2013 at 3:36
I had a little issue :
It seems that aroma installer didn't manage to correctly flash the new boot.img
(but told me that the install was successful). cat /proc/version was showing my
old kernel after I installed Bricked zip.
I get the newboot.img from /tmp during install and flashed it using fastboot.
cat /proc/version
Linux version 3.4.10-bricked-ville-master-gd153d42 (gitlab_ci@warmachine) (gcc
version 4.7.2 20120910 (prerelease) (Linaro GCC 4.7-2012.09) ) #1 SMP PREEMPT
Sun May 12 01:42:12 CEST 2013
root@android:/mnt # cd /system/lib/modules
cd /system/lib/modules
root@android:/system/lib/modules # modinfo cifs.ko
modinfo cifs.ko
modinfo: can't open
'/lib/modules/3.4.10-bricked-ville-master-gd153d42/modules.dep': No such file
or directory
1|root@android:/system/lib/modules # lsmod
lsmod
tun 15136 0 - Live 0x00000000
cifs 265604 0 - Live 0x00000000
kineto_gan 4636 0 - Live 0x00000000
And if I try to mount a cifs share (got the same error with the Cifs Manager
app) :
root@android:/system/lib/modules # mount -t cifs 192.168.x.xx/xxxx
/storage/sdcard0/cifs/xxx
.x.xx/xxxx /storage/sdcard0/cifs/xxx
mount: Invalid argument
255|root@android:/system/lib/modules #
Original comment by ghislain...@gmail.com
on 16 May 2013 at 7:06
This is an s-on problem. /boot is not writeable while you are in recovery.
Either s-off your device (which is quite easy, but as all things bears the risk
of bricking it) or always pull the newboot.img and flash it through the
bootloader.
The cifs module is loaded now and it should work.
Original comment by showp1984
on 16 May 2013 at 8:47
Hi,
I get the same error than ghislain...@gmail.com
Showp1984, Here a logcat from I start CifsManager.apk.
I'm on Viper Rom, and I use the stable version of your Kernel.
If you want some other information, say it to me.
Thanks
Original comment by mitch55...@gmail.com
on 20 May 2013 at 11:59
Attachments:
Original comment by showp1984
on 20 May 2013 at 12:24
I s-off my device today, flashed again the kernel and the problem is still here.
Original comment by ghislain...@gmail.com
on 13 Jun 2013 at 7:34
Original issue reported on code.google.com by
ghislain...@gmail.com
on 15 May 2013 at 1:55