for now it seems this will not be possible for Xperia Play... SE kernel sources are incomplete/broken for Xperia Play to support FULL USB-OTG...
since i dont have this device i will not be working on fixing the SE sources for this...
may be someone with the device can get it working with lots of fixes & testing...
sorry to disappoint u guys... i tried...
[ screenshots ]
{
"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"
}
[ requirements ]
Xperia Arc (Neo?/Play?) on FW: 4.0.A.2.368
preferably rooted + busybox installed
USB-OTG hardware cable
Terminal Emulator app
[OPTIONAL] adb Wireless app
[ tested on ]
Xperia Arc Stock FW: 4.0.A.2.368 with DooMKernel v08
[ how to ] (general instructions for modules)
download the modules and push the modules to /system/lib/modules/
use adb shell or terminal emulator to enter following code/commands
Code:
su
cd/system/lib/modules/
busybox insmod usbhid.ko
busybox insmod usbmouse.ko
busybox insmod usbkbd.ko
busybox insmod usb-storage.ko
check if all modules are live are not:
Code:
lsmod
done the modules are LIVE!
[IMP] u will have to manually reload the modules on EVERY boot... unless u use start-up scripts which will take care of this!
[ how to ] (instructions for usb-storage) [simpler way]
download app: http://android.gval.biz/download/Q5_USB_Memory_Manager.apk
follow instructions: http://android.gval.biz/Q5_USB_Menory_Manager.php
the usb storage device should now be mounted to /usb_storage/
u will need to use RootExplorer for this to work
[ how to ] (instructions for usb-storage) [manual way]
before u begin/connect device there are few things which need to be done
creating necessary directory structure
Code:
su
cd /sdcard/
mkdir usbStorage
now connect the usb storage device via usb-otg cable to phone
now enter the following command:
Code:
dmesg
at the last part u will see some info of connected device (an if it was rejected due to power issues)
now enter
Code:
ls -l /dev/block/sd*
u will get output similar to the one posted below
note if the last part: /dev/block/sda1
finally mount this device
Code:
mount /dev/block/sda1 /sdcard/usbStorage
if u get no error then enjoy usb storage is now mounted
to unmount usbstorage
Code:
umount /dev/block/sda1
[ donations ]
if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc
PAYPAL DONATION LINK
[ download links ]
USB-STORAGE
USB-HID
USB-KEYBOARD
USB-MOUSE
[ known issues ]
usb mouse works but there is no cursor... but u can move around and select (left click on stuff)
when using usb-storage mode some devices will not be mountable if:
they require more power (u can check this in dmesg)
they have filesystem not supported by ur current kernel
sometimes the mounted usb-storage files wont appear using some apps... i have tested it to be wrking using RootExplorer... though it will work in adb shell/terminal emulator also...
[ troubleshooting ]
when u post any error/issue please include the full output of dmesg command (adb shell dmesg > dmesg_log.txt) OR (dmesg > /sdcard/dmesg_log.txt)
P.S.: all these features will be included in next version of DooMKernel for all supported Xperia 2011 devices
enjoy!
reserved reserved
Woow!! very nice.
Thank you very much for your work doom. I ll test this when I get a cable
I have downloaded the files on my phone by long pressing and the save link. It downloaded as txt files. Then I simply renamed the files to .ko is that the correct way? I moved the files with rootexplorer and set permissions as the bcm4329.ko. But when using terminal emu it won't insmod it says:
export PATH=/data/local/bin:$PATH
$ export PATH=/data/local/bin:$PATH
$su
# cd /system/lib/modules
# ls
usbmouse.ko
usbkbd.ko
usbhid.ko
usb-storage.ko
bcm4329.ko
# busybox insmod usbhid.ko
insmod: can't insert '/system/lib/modules/usbhid.ko': unknown symbol in module or invalid parameter
#
Regards Dousan...
e: re-downloaded the files on my laptop and they downloaded as .ko files. Then pushed them with adb but i still get the same error?
I have busybox installed in /system/xbin and it's 1.18.4. The newest fw .368 and your kernel.
Dousan said:
I have downloaded the files on my phone by long pressing and the save link. It downloaded as txt files. Then I simply renamed the files to .ko is that the correct way? I moved the files with rootexplorer and set permissions as the bcm4329.ko. But when using terminal emu it won't insmod it says:
export PATH=/data/local/bin:$PATH
$ export PATH=/data/local/bin:$PATH
$su
# cd /system/lib/modules
# ls
usbmouse.ko
usbkbd.ko
usbhid.ko
usb-storage.ko
bcm4329.ko
# busybox insmod usbhid.ko
insmod: can't insert '/system/lib/modules/usbhid.ko': unknown symbol in module or invalid parameter
#
Regards Dousan...
Click to expand...
Click to collapse
try all the others too... if all give same error i will compile again...
DooMLoRD said:
try all the others too... if all give same error i will compile again...
Click to expand...
Click to collapse
The same error on all 4.
Regards Dousan...
Dousan said:
The same error on all 4.
Regards Dousan...
Click to expand...
Click to collapse
ok... i will reupload all those specifically compiled for Play...
Great
Will you post, when at some point, they're re-uploaded?
Regards Dousan.
Dousan said:
Great
Will you post, when at some point, they're re-uploaded?
Regards Dousan.
Click to expand...
Click to collapse
i am at work mate
will try to compile it here and see if i can upload it
DooMLoRD said:
i am at work mate
will try to compile it here and see if i can upload it
Click to expand...
Click to collapse
No hurry mate, if you can that's great but no sweat if you can't
Regards Dousan...
Dousan said:
No hurry mate, if you can that's great but no sweat if you can't
Regards Dousan...
Click to expand...
Click to collapse
in anycase i will re-compile & upload it once i get back home...
Another great work Doom
seems SE kernel sources are incomplete for Xperia Play to support FULL USB-OTG...
since i dont have this device i will not be working on fixing the SE sources for this...
may be someone with the device can get it working with lots of fixes & testing...
sorry to disappoint u guys... i tried...
No worries. you've done a great job anyways, and hopefully you've learnt things. that is what counts
I'm sure Blagus will benefit from this, too.
Logseman said:
No worries. you've done a great job anyways, and hopefully you've learnt things. that is what counts
I'm sure Blagus will benefit from this, too.
Click to expand...
Click to collapse
ya i have talked to him about this... so may be he can get it working...
thanks for the support!
No worries mate You did try and it's fully understandable you won't develop any further. Thanks for the effort and it might be that blagus can carry on, would be great
Regards Dousan...
DooMLoRD said:
seems SE kernel sources are incomplete for Xperia Play to support FULL USB-OTG...
since i dont have this device i will not be working on fixing the SE sources for this...
may be someone with the device can get it working with lots of fixes & testing...
sorry to disappoint u guys... i tried...
Click to expand...
Click to collapse
Don't worry Doom,you're great
apparently Xperia Play is not supported by official SE dock
http://www.sonyericsson.com/cws/pro...w/livedock?cc=gb&lc=en#view=compatible_phones
The Play has its own dock, the DK300. I have one, if you want I can use the Play plugged in if you need any data.
Any chance of a retry on this Doom, now you have the device?
Related
All credits go to pulpoff2 for this! This is not by me, I am merely the messenger. Only thing I did was to ask pulpoff for the files and a tutorial With his permission I will share it with you.
This will provide you with a fresh and unmodified 2.1-system, exactly like you would do the official update - only exception is that it is rooted. So all the apps and games of the official firmware are available and nothing else. You can remove the crap (like the games or timescape for example) by yourself after doing the steps below.
UPDATE:
There is a newer ROM by propc you can use instead of this one. Look here:
http://forum.xda-developers.com/showthread.php?t=888427
-- NEW --
propc kindly provides us with a shellscript to automate the steps below. See here for the script and a short manual:
http://forum.xda-developers.com/showpost.php?p=10067921&postcount=120
If the script doesn't work for you or you prefer to do things the manual way, you may use the steps below.
Download these files:
x8-2.1rooted.img.yaffs.rar
and
ISO-8859-1__unyaffs-arm.rar
Also download the 2.1-firmware from here or here. Unpack it on your computer and delete the "system.sin".
Unpack "x8rooted.img", "busybox" and "unyaffs" to SDcard.
You need 1.6 with root on your phone. By the way, all the data on your phone will be lost after doing the following steps, so making a backup is advised.
Use "adb shell" to connect to your phone and become su:
Code:
su
Copy "busybox" and "unyaffs" to /data/local/tmp. (Pulpoff says you should copy to /sbin, but this requires remounting with busybox. I copied to /sbin, but I think /data/local/tmp should work just fine)
Code:
cd /data/local/tmp
cat /sdcard/busybox > busybox
cat /sdcard/unyaffs > unyaffs
chmod the files to make them executable:
Code:
chmod 755 busybox
chmod 755 unyaffs
EDIT: If you want to copy the files to /sbin (like pulpoff2 advises), you can do this OPTIONAL step:
EDIT2: It was confirmed that this is indeed not necessary!
Remount the root directory to make /sbin writable. Then copy the files over and change the working directory to /sbin:
Code:
[strike]
./busybox mount -o remount,rw /
./busybox cp -prf busybox /sbin/
./busybox cp -prf unyaffs /sbin/
cd /sbin[/strike]
Remount /system as writable:
Code:
mount -o remount,rw /dev/block/mtdblock0 /system
Switch to busybox shell:
Code:
./busybox sh
Remove /system (yes, really!). It's normal to get errors because of the "lost+found"-folders. Ignore the errors.
Code:
./busybox rm -r /system
Unpack pre-rooted image to system. It should output "end of image" if it finishes correctly.
Code:
./unyaffs /sdcard/x8rooted.img /system
Your phone won't boot anymore now and it will crash as soon as you try to use it - that's normal! Go to next step.
Just remove the battery and the usb-cable from the phone, then re-attach the battery. Flash 2.1-kernel (without system.sin !!) using the flasher-tool by Bin4ry. If the flasher gives you an error because of a missing "loader.sin" you can take this file from the 1.6-firmware. Refer to Bin4ry's thread to learn how to use his flasher and how to enter flash-mode on your phone.
The phone should now boot, although the first boot can take a little while. If you get into a boot-loop or you just see the white sony ericsson logo (not the green one after the animation) for several minutes, it probably didn't work and you have to start over again by flashing 1.6.
This was written as I remember how I did it by myself. It worked for me at first try! If it works for you, please click the thanks-button. It will make me feel better
After you have your nice rooted 2.1 you probably want to enable JIT for a nice performance boost.
But does it have root? Bad reading.
{
"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"
}
a-k-t-w said:
But does it have root?
Click to expand...
Click to collapse
Absolutely. But no busybox. So if you plan to enable JIT, you have to copy busybox to /system/bin by yourself.
a-k-t-w said:
But does it have root? Bad reading.
Click to expand...
Click to collapse
of course it is rooted.
now we know what to do with unyaffs.
2 things:
1. I've bought the phone with 1.6 android, but I was unable to root it with any method, then I've upgraded to 2.1 update 1. Is there any way to root it?
2. I have Hungarian language. Does it contain Hungarian language?
csengoi said:
2 things:
1. I've bought the phone with 1.6 android, but I was unable to root it with any method, then I've upgraded to 2.1 update 1. Is there any way to root it?
2. I have Hungarian language. Does it contain Hungarian language?
Click to expand...
Click to collapse
1: There is no way to directly root a phone with 2.1. You need to go back to 1.6, root it and then follow the above steps.
2: I guess so. As far as I know the firmware is the same for all countries.
Works like a charm! I removed the /system folder contents one by one though, using the method from the previous thread. Anyway, the first time I tried, unyaffs exited before extracting all the files (maybe the phone ran out of memory?). I didn't notice it and went on to flash the phone, ending up stuck at the Sony Ericsson logo. So, make sure that unyaffs reports that it has reached the "end of image" before moving on to the next step!
Thanks!!
cat /sdcard/busybox > busybox invalid lenght
cat /sdcard/unyaffs > unyaffs invalid lenght
how to proceed?
isaac12 said:
cat /sdcard/busybox > busybox invalid lenght
cat /sdcard/unyaffs > unyaffs invalid lenght
how to proceed?
Click to expand...
Click to collapse
in adb shell:
enter su and you have to look your mobile screen because it will ask you to allow su. (if you rooted well your phone)
i had this problem when i didn't press the allow button in superuser confirmation.
---dobule post--- sorry
trapacska said:
in adb shell:
enter su and you have to look your mobile screen because it will ask you to allow su. (if you rooted well your phone)
i had this problem when i didn't press the allow button in superuser confirmation.
Click to expand...
Click to collapse
rooted phone yes
su confirmed
cd /data/local/tmp
cat /sdcard/busybox > busybox invalid lenght
cat /sdcard/unyaffs > unyaffs invalid lenght
does it mount data.img on sdcard???
or i'll need to use chargemon from previous way?
WARR10r said:
does it mount data.img on sdcard???
or i'll need to use chargemon from previous way?
Click to expand...
Click to collapse
This has nothing to do with App2SD. Also the ROM gets loaded from internal flash, not from sdcard. The result is the same as with the official update, but with root.
If you want to have /data on sdcard, use the modified chargemon or neptun2's method.
I'm totally new to android but somehow i managed to get to number 8, and I have no idea how to switch to busybox shell, can somebody explain this bit in lamens terms please.
gully666uk said:
I'm totally new to android but somehow i managed to get to number 8, and I have no idea how to switch to busybox shell, can somebody explain this bit in lamens terms please.
Click to expand...
Click to collapse
try adding ./ before
gully666uk said:
I'm totally new to android but somehow i managed to get to number 8, and I have no idea how to switch to busybox shell, can somebody explain this bit in lamens terms please.
Click to expand...
Click to collapse
You should still be in "/data/local/tmp" as the working directory (check with "pwd"-command). If you followed the steps correctly, you should have a working busybox-file in there. So just type "busybox sh". If it looks like it does nothing, it's all right
isaac12 said:
rooted phone yes
su confirmed
cd /data/local/tmp
cat /sdcard/busybox > busybox invalid lenght
cat /sdcard/unyaffs > unyaffs invalid lenght
Click to expand...
Click to collapse
try to use another su. i rooted my x8 with superoneclick 1.5.0
I got stuck at SE logo for at least 10mins, it doesnt re-boot cycle although..
Sectoras said:
I got stuck at SE logo for at least 10mins, it doesnt re-boot cycle although..
Click to expand...
Click to collapse
That's way too long, something isn't right there. To start over again you have to flash back to 1.6.
Ok I had not realised the superuser permissions was not popping up on my phone that's sorted now. I get to number 8 again and it said permission denied
DooMLoRD & MrHassell proudly present to u...
xCharge Reboot Options [a.k.a. Xperia Reboot Options]
firstly i would like to thank Bin4ry & Androxyde for the FlashTool and the option to "reboot into xrecovery from flashtool" as this APP is based on that..
and to my good friend MrHassell for doing the xcharge base coding, teaching & guiding me to develop android apps....
thanks to everyone who has done the testing and provided invaluable feedback/comments
we are finally ready with a new version and its directly released to market!!!
get it here:
xCharge Reboot Options
{
"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"
}
its a paid app for 2$
new features include:
cleaner layout
new UI
working themes!
and u will be entitled to future upgrades
Screenshots:
On X10:
On Xperia 2011 / Other Androids:
if u like the app please buy the paid app to support our work
P.S.: Older versions are available in 2nd post and will be kept for XDA users...
Requirements:
Any of the following supported devices
Phone needs to be rooted with Busybox installed
Any Working Version of Recovery
[Xperia Arc/Play/Neo ONLY] For "Reboot into FASTBOOT mode" u need to connect device (via USB) to PC and have fastboot drivers installed
Supported Devices:
Xperia X10
Xperia X8
Xperia X10 Mini
Xperia X10 Mini Pro
Xperia Arc
Xperia Play
Xperia Neo
Lots of other non Xperia devices too!!! check this post for all supported devices
I'm in )
me too
i am from pune too
It works for me in stock SE rom with xrec installed through flastool 0.2.9.1
Sent from my E10i using XDA Premium App
Me too.
Hi, DooMLoRD
I successfully tested it in my Xperia mini(E10i) running on miniCM Beta2(2.2.1) by nobodyatall.It works great. The day of pressing back key for xrecovery is over.
Many Thanks to you and all devs involved in this great project.
+1 to DooMLoRD.
@daemon-rj and @tufadorin
I think u guys got the wrong idea. DooMLoRD is taking about reboot into xecovery from your phone not from Flash tool
Sorry for my bad English.
No i did without flashtool.I installed universal v1.zip.Them i changed permisions in chargemon and then typed script in GScript. And then you can reboot in recovery mode without press back button.
I did in stock SE rom with new baseband and kernel.
I was rooted and installed xrecovery in my phone with flashtool 0.2.9.1
Sorry for my english.
Sent from my E10i using XDA Premium App
where is the file for downloading?and what i must do?
please dont rush to download those files...
clepto1995 said:
where is the file for downloading?and what i must do?
Click to expand...
Click to collapse
please dont rush to download those files...
U can use the manual way for editing files for ur own device...
i will be uploading a newer universal update.zip file which should be useful for those who have used FlashTool v0.2.9.1 to install recovery...
what is flash tool?i install xrecovery with copy&paste 3 files (xrecovery, busybox, chargemon) into /system/bin (i think) and change their permission...
clepto1995 said:
what is flash tool?i install xrecovery with copy&paste 3 files (xrecovery, busybox, chargemon) into /system/bin (i think) and change their permission...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=986690
i haven't installed xrecovery with that...so can i reboot into xrecovery without pressing the back button with this script of yours?
clepto1995 said:
i haven't installed xrecovery with that...
...
Click to expand...
Click to collapse
oh ok....
clepto1995 said:
...
so can i reboot into xrecovery without pressing the back button with this script of yours?
Click to expand...
Click to collapse
ya thats the idea
but i recommend u try the manual way...
here's mine chargemon https://dl-web.dropbox.com/get/chargemon?w=6564280f
i am using nobodyatall's rom...minicm beta 2!
clepto1995 said:
here's mine chargemon https://dl-web.dropbox.com/get/chargemon?w=6564280f
i am using nobodyatall's rom...minicm beta 2!
Click to expand...
Click to collapse
cant access forbidden...
just post it here...
sorry
Code:
#!/system/bin/busybox sh
/system/bin/charger
cat /dev/input/event1 > /dev/keycheck&
sleep 3
kill -9 $!
if [ -s /dev/keycheck ]
then
# remount rootfs rw
mount -o remount,rw rootfs /
# Umount MTDs
umount -l /dev/block/mtdblock1
umount -l /dev/block/mtdblock2
umount -l /dev/block/mtdblock3
# Mount recovery partition
cd /
rm -r /sbin
rm -f etc
tar -xf /system/bin/xrecovery.tar
# Umount /system
umount -l /dev/block/mtdblock0
# chroot
chroot / /init
fi
# remount rootfs rw
mount -o remount,rw rootfs /
chmod 0777 /dev -R
chown 0.2000 /dev/oncrpc -R
cd /
rm init*
rm logo.rle
rm default.prop
tar -xf /system/bin/ramdisk.tar
sync
chroot / /init
tufadorin said:
No i did without flashtool.I installed universal v1.zip.Them i changed permisions in chargemon and then typed script in GScript. And then you can reboot in recovery mode without press back button.
I did in stock SE rom with new baseband and kernel.
I was rooted and installed xrecovery in my phone with flashtool 0.2.9.1
Sorry for my english.
Sent from my E10i using XDA Premium App
Click to expand...
Click to collapse
Could you please let me know where you got flashtool 0.2.9.1 from and send me the file itself if possible?I haven't seen anything beyond 0.2.8.By the way,I have an E10i.
Thanks in advance.
sathkartha said:
Could you please let me know where you got flashtool 0.2.9.1 from and send me the file itself if possible?I haven't seen anything beyond 0.2.8.By the way,I have an E10i.
Thanks in advance.
Click to expand...
Click to collapse
Here your go Flash Tool 0.2.9.1
nishan432 said:
Here your go Flash Tool 0.2.9.1
Click to expand...
Click to collapse
Thanks Nishan,can we use this with the mini E10i?
sathkartha said:
Thanks Nishan,can we use this with the mini E10i?
Click to expand...
Click to collapse
Yes we can. I used it for installing xrecovery.
[ info ]
the reason i created this thread is that many custom kernels for our X10 are having the feature of running init.d scripts at startup, BUT the problem is that some ROMS dont have the necessary/correct files in place for executing those scripts...
so i am attaching a easy to flash update.zip which contains these missing files required for full functionality of executing startup scripts...
use the following files only if u are not able to execute init.d startup scripts on ur current ROM
[ requirements ]
rooted device with recovery installed
kernel/other modifications which support init.d script execution (via sysinit) [exec /system/bin/sysinit]
[ download link ]
update.zip flashable via xRecovery-0.3-GBready (amend syntax)
init.d-autorunner-v01.zip
[ additional info ]
i have added the following things in the update.zip:
corrected /system/bin/sysint file
run-parts binary in /system/xbin/run-parts (which is basically busybox 1.16.2 binary)
test/example script /system/etc/init.d/99test
CM7-FreeXperia ROM already supports this execution so no need to flash it on that ROM
if ur startup script is not correctly working then u need to make sure that u have the correct permissions on the script (just tick all 9 boxes using RootExplorer permissions pop-up)
let me know how it goes!
{
"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"
}
ENJOY!
reserved reserved
Hey Doom, Is this already implemented in Z's CM7 2.3.5 rom?
Aphex33 said:
Hey Doom, Is this already implemented in Z's CM7 2.3.5 rom?
Click to expand...
Click to collapse
i dont remember...
test it out...
if init.d scripts are getting executed w/o using this FIX then its already implemented
This solves the issues with wolf v4.0.4 with Doomkernel??
So i will retain back my init.d files...
Hey doom and other devs
How many copies of busybox we will have in roms
I mean why not just add special folder rtm ( run-time module ) and place our busybox there...
That would ensure that it is not overwritten and replaced by market or some external thing...
If you take look now we have devs placing busybox in /recovery/sh /xbin/sh /bin/busybox etc, etc ...
Let's not forget busybox has size 700 kB that is like almost 1 MB of wasted space per copy...
And all sh scripts can run using #!/path_to/busybox sh and let's not forget that run-parts are created by update-script in xbin or bin folder so making new copy of busybox as run-parts not needed
And sysinit can be as service in init file
service sysinit /path_to/busybox run-parts /system/etc/init.d
Hi Doom,
Thank you
aZuZu said:
Hey doom and other devs
How many copies of busybox we will have in roms
I mean why not just add special folder rtm ( run-time module ) and place our busybox there...
That would ensure that it is not overwritten and replaced by market or some external thing...
If you take look now we have devs placing busybox in /recovery/sh /xbin/sh /bin/busybox etc, etc ...
Let's not forget busybox has size 700 kB that is like almost 1 MB of wasted space per copy...
And all sh scripts can run using #!/path_to/busybox sh and let's not forget that run-parts are created by update-script in xbin or bin folder so making new copy of busybox as run-parts not needed
And sysinit can be as service in init file
service sysinit /path_to/busybox run-parts /system/etc/init.d
Click to expand...
Click to collapse
aZuZu u will have to check all busybox binaries... wht i found was NOT ALL busybox binaries support run-parts (u can check it ur self)...
there are symlinks created using update-script which are wrong... u should be using busybox --s -install command always...
anyways the problem is that some devs use busybox in /system/bin /system/xbin
some include busybox in ramdisk (/sbin)...
so simplest solution for run-parts is to use a small "<400kb" binary which handles this well...
BTW i already use the sysinit service for my other kernels (Arc/Play/etc...) [which is much more advanced]
the solution posted here is a generic one which should work for MOST kernels...
P.S.: having a small 400Kb file is not going to waste 350MB+ space of ur /system partition
DooMLoRD said:
aZuZu u will have to check all busybox binaries... wht i found was NOT ALL busybox binaries support run-parts (u can check it ur self)...
there are symlinks created using update-script which are wrong... u should be using busybox --s -install command always...
anyways the problem is that some devs use busybox in /system/bin /system/xbin
some include busybox in ramdisk (/sbin)...
so simplest solution for run-parts is to use a small "<400kb" binary which handles this well...
BTW i already use the sysinit service for my other kernels (Arc/Play/etc...) [which is much more advanced]
the solution posted here is a generic one which should work for MOST kernels...
P.S.: having a small 400Kb file is not going to waste 350MB+ space of ur /system partition
Click to expand...
Click to collapse
Hi my friend,
I think your idea is also based
so I want to try this script
Cheers,
tkymgr
thanks for your such nice information sharing with us in this forum so keep it up
@DooMLoRD: This does not seem to work on ICS.. any suggestions?
is sysinit 0755 or 0777 (chmod) ?
Is this supported for fera lab v20?
Sent from my Xperia X10 using xda premium
Works on any android device ?
Enviado desde mi GT-I9300 mediante Tapatalk
Hallo, this is boot image for stock ICS firmware 6.1.B.0.544 unsecured and in SIN format + my version of the CWM recovery! I allways prefering manually installation of the root tools so here is tutorial how to propertly root your Xperia P!
Before you going to install this "pack" you need to unlock your bootloader!
After unlocking bootloader procedure for installing boot image and root tools is:
install boot image:
fastboot flash boot kernel.sin
install root tools:
adb remount
adb push su /system/xbin/
adb push busybox /system/xbin/
adb install Superuser.apk
adb shell
cd /system/xbin
chmod 6755 su
chmod 6755 busybox
/system/xbin/busybox --install -s /system/xbin/
Than you are done! Just last step you need to do:
establish internet connection on your phone
go to aplications
run superuser
under superuser menu click to "tap to ckeck for updates" (see picture http://img52.imageshack.us/img52/2097/screenshot201209151603.png) and update your super user... make sure to give and "remember" permision for superuser app!
Done!
Note: I have no Xperia P so this is untested version! Please test and let me know if something is missing or strange please let me know... I am sure everything will be ok! Enjoy!
Kernel source:
Its stock ICS kernel used from this post -> http://forum.xda-developers.com/showthread.php?t=1838457
Thanks to Jozinek for giving link to stock rom !
Changelog is here
Warning:
You can play with this recovery but on your own risk... I am not responsible if you lose your data!
{
"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"
}
24.Sep.2012:
Changelog:
backported my own modified version of the Clockwork Recovery from Xperia GO to Xperia P
rooted boot image
Recovery:
battery indicator (icon) in real time
leds indicator in real time
button backlight enabled
you can mount internal sd card
you can backup/restore from/to internal sd card
new menu and tool (Big thanks Letama for great tool!!!) -> my modification to his tool is: backported to arm, backported to recovery, created easy sin to tar packer. This recovery tool is for easilly "in one click" repacking upcoming ICS firmwares! Just place your system.sin into internal sd card, reboot to recovery, under menu click to sony tools, and you will get your system.sin unpacked to system.tar... enjoy!
adbd is auto enabled on boot... (you just need to wait ~30 seconds until adb and mass storage mode is inited!)
Upcoming tools soon!
Next plan is tool for converting sin format to recovery-compatible flashable zip !
Working Recovery that can mount System and therefore enables to flash zips?
Sent from my LT22i using xda app-developers app
Wow! Hi munjeni
You also buying is Xperia p?
dimon2242 said:
Wow! Hi munjeni
You also buying is Xperia p?
Click to expand...
Click to collapse
Hi mate, we here again :laugh: ...I have Xperia Go
Wolfbreak said:
Working Recovery that can mount System and therefore enables to flash zips?
Sent from my LT22i using xda app-developers app
Click to expand...
Click to collapse
Will see. I done full working recovery on Sola and Go so it must working too on P
munjeni said:
Hi mate, we here again :laugh: ...I have Xperia Go
Will see. I done full working recovery on Sola and Go so it must working too on P
Click to expand...
Click to collapse
Congratulations on your purchase of one!
Wolfbreak said:
Working Recovery that can mount System and therefore enables to flash zips?
Sent from my LT22i using xda app-developers app
Click to expand...
Click to collapse
Hi Wolf, I loved your works with the X10, it's nice to see you here Any chance of you developing some ROMS for the P?
When this is with working CWM then yes
Sent from my LT22i using xda app-developers app
Wolfbreak said:
Working Recovery that can mount System and therefore enables to flash zips?
Sent from my LT22i using xda app-developers app
Click to expand...
Click to collapse
Yes, I tested allready on X-Go, just repacked an sin system image to recovery compatible zip format and sucesfully reflashed my system partition ...see this -> http://forum.xda-developers.com/showpost.php?p=31922215&postcount=13 ...need some help there!!!
Did Xperia P have external micro sd card slot ?
Xperia P doesn't have any sd card slot
Hey guys, I need help to finish recovery... please give me output from:
adb shell find /sys | grep capacity
adb shell find /sys | grep lun
adb shell find /sys | grep usb_connected
adb shell find /sys | grep power_supply
munjeni said:
Hey guys, I need help to finish recovery... please give me output from:
adb shell find /sys | grep capacity
adb shell find /sys | grep lun
adb shell find /sys | grep usb_connected
adb shell find /sys | grep power_supply
Click to expand...
Click to collapse
how can i send you that i really want to help you
C:\android-sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # find /sys | grep capacity
find /sys | grep capacity
/sys/devices/platform/ab8500-i2c.0/ab8500-fg.0/power_supply/ab8500_fg/capacity_l
evel
/sys/devices/platform/ab8500-i2c.0/ab8500-fg.0/power_supply/ab8500_fg/capacity
[email protected]:/ # find /sys | grep lun
find /sys | grep lun
/sys/devices/platform/musb-ux500.0/musb-hdrc/gadget/lun0
/sys/devices/platform/musb-ux500.0/musb-hdrc/gadget/lun0/uevent
/sys/devices/platform/musb-ux500.0/musb-hdrc/gadget/lun0/power
/sys/devices/platform/musb-ux500.0/musb-hdrc/gadget/lun0/power/runtime_status
/sys/devices/platform/musb-ux500.0/musb-hdrc/gadget/lun0/power/control
/sys/devices/platform/musb-ux500.0/musb-hdrc/gadget/lun0/power/runtime_suspended
_time
/sys/devices/platform/musb-ux500.0/musb-hdrc/gadget/lun0/power/runtime_active_ti
me
/sys/devices/platform/musb-ux500.0/musb-hdrc/gadget/lun0/power/autosuspend_delay
_ms
/sys/devices/platform/musb-ux500.0/musb-hdrc/gadget/lun0/ro
/sys/devices/platform/musb-ux500.0/musb-hdrc/gadget/lun0/file
/sys/devices/platform/musb-ux500.0/musb-hdrc/gadget/lun0/nofua
/sys/devices/platform/musb-ux500.0/musb-hdrc/gadget/lun1
/sys/devices/platform/musb-ux500.0/musb-hdrc/gadget/lun1/uevent
/sys/devices/platform/musb-ux500.0/musb-hdrc/gadget/lun1/power
/sys/devices/platform/musb-ux500.0/musb-hdrc/gadget/lun1/power/runtime_status
/sys/devices/platform/musb-ux500.0/musb-hdrc/gadget/lun1/power/control
/sys/devices/platform/musb-ux500.0/musb-hdrc/gadget/lun1/power/runtime_suspended
_time
/sys/devices/platform/musb-ux500.0/musb-hdrc/gadget/lun1/power/runtime_active_ti
me
/sys/devices/platform/musb-ux500.0/musb-hdrc/gadget/lun1/power/autosuspend_delay
_ms
/sys/devices/platform/musb-ux500.0/musb-hdrc/gadget/lun1/ro
/sys/devices/platform/musb-ux500.0/musb-hdrc/gadget/lun1/file
/sys/devices/platform/musb-ux500.0/musb-hdrc/gadget/lun1/nofua
/sys/devices/virtual/android_usb/android0/f_mass_storage/lun
/sys/module/scsi_mod/parameters/max_report_luns
/sys/module/scsi_mod/parameters/max_luns
[email protected]:/ # find /sys | grep usb_connected
find /sys | grep usb_connected
1|[email protected]:/ # find /sys | grep power_supply
find /sys | grep power_supply
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_ac
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_ac/ueven
t
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_ac/subsy
stem
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_ac/devic
e
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_ac/healt
h
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_ac/prese
nt
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_ac/onlin
e
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_ac/volta
ge_now
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_ac/volta
ge_avg
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_ac/curre
nt_now
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_ac/curre
nt_avg
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_ac/type
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_ac/power
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_ac/power
/runtime_status
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_ac/power
/control
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_ac/power
/runtime_suspended_time
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_ac/power
/runtime_active_time
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_ac/power
/autosuspend_delay_ms
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_usb
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_usb/ueve
nt
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_usb/subs
ystem
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_usb/devi
ce
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_usb/heal
th
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_usb/pres
ent
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_usb/onli
ne
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_usb/volt
age_now
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_usb/volt
age_avg
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_usb/curr
ent_now
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_usb/curr
ent_avg
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_usb/type
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_usb/powe
r
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_usb/powe
r/runtime_status
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_usb/powe
r/control
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_usb/powe
r/runtime_suspended_time
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_usb/powe
r/runtime_active_time
/sys/devices/platform/ab8500-i2c.0/ab8500-charger.0/power_supply/ab8500_usb/powe
r/autosuspend_delay_ms
/sys/devices/platform/ab8500-i2c.0/ab8500-btemp.0/power_supply
/sys/devices/platform/ab8500-i2c.0/ab8500-btemp.0/power_supply/ab8500_btemp
/sys/devices/platform/ab8500-i2c.0/ab8500-btemp.0/power_supply/ab8500_btemp/ueve
nt
/sys/devices/platform/ab8500-i2c.0/ab8500-btemp.0/power_supply/ab8500_btemp/subs
ystem
/sys/devices/platform/ab8500-i2c.0/ab8500-btemp.0/power_supply/ab8500_btemp/devi
ce
/sys/devices/platform/ab8500-i2c.0/ab8500-btemp.0/power_supply/ab8500_btemp/pres
ent
/sys/devices/platform/ab8500-i2c.0/ab8500-btemp.0/power_supply/ab8500_btemp/onli
ne
/sys/devices/platform/ab8500-i2c.0/ab8500-btemp.0/power_supply/ab8500_btemp/tech
nology
/sys/devices/platform/ab8500-i2c.0/ab8500-btemp.0/power_supply/ab8500_btemp/temp
/sys/devices/platform/ab8500-i2c.0/ab8500-btemp.0/power_supply/ab8500_btemp/type
/sys/devices/platform/ab8500-i2c.0/ab8500-btemp.0/power_supply/ab8500_btemp/powe
r
/sys/devices/platform/ab8500-i2c.0/ab8500-btemp.0/power_supply/ab8500_btemp/powe
r/runtime_status
/sys/devices/platform/ab8500-i2c.0/ab8500-btemp.0/power_supply/ab8500_btemp/powe
r/control
/sys/devices/platform/ab8500-i2c.0/ab8500-btemp.0/power_supply/ab8500_btemp/powe
r/runtime_suspended_time
/sys/devices/platform/ab8500-i2c.0/ab8500-btemp.0/power_supply/ab8500_btemp/powe
r/runtime_active_time
/sys/devices/platform/ab8500-i2c.0/ab8500-btemp.0/power_supply/ab8500_btemp/powe
r/autosuspend_delay_ms
/sys/devices/platform/ab8500-i2c.0/ab8500-fg.0/power_supply
/sys/devices/platform/ab8500-i2c.0/ab8500-fg.0/power_supply/ab8500_fg
/sys/devices/platform/ab8500-i2c.0/ab8500-fg.0/power_supply/ab8500_fg/uevent
/sys/devices/platform/ab8500-i2c.0/ab8500-fg.0/power_supply/ab8500_fg/subsystem
/sys/devices/platform/ab8500-i2c.0/ab8500-fg.0/power_supply/ab8500_fg/device
/sys/devices/platform/ab8500-i2c.0/ab8500-fg.0/power_supply/ab8500_fg/voltage_no
w
/sys/devices/platform/ab8500-i2c.0/ab8500-fg.0/power_supply/ab8500_fg/current_no
w
/sys/devices/platform/ab8500-i2c.0/ab8500-fg.0/power_supply/ab8500_fg/current_av
g
/sys/devices/platform/ab8500-i2c.0/ab8500-fg.0/power_supply/ab8500_fg/charge_ful
l_design
/sys/devices/platform/ab8500-i2c.0/ab8500-fg.0/power_supply/ab8500_fg/charge_ful
l
/sys/devices/platform/ab8500-i2c.0/ab8500-fg.0/power_supply/ab8500_fg/charge_now
/sys/devices/platform/ab8500-i2c.0/ab8500-fg.0/power_supply/ab8500_fg/energy_ful
l_design
/sys/devices/platform/ab8500-i2c.0/ab8500-fg.0/power_supply/ab8500_fg/energy_ful
l
/sys/devices/platform/ab8500-i2c.0/ab8500-fg.0/power_supply/ab8500_fg/energy_now
/sys/devices/platform/ab8500-i2c.0/ab8500-fg.0/power_supply/ab8500_fg/capacity_l
evel
/sys/devices/platform/ab8500-i2c.0/ab8500-fg.0/power_supply/ab8500_fg/type
/sys/devices/platform/ab8500-i2c.0/ab8500-fg.0/power_supply/ab8500_fg/power
/sys/devices/platform/ab8500-i2c.0/ab8500-fg.0/power_supply/ab8500_fg/power/runt
ime_status
/sys/devices/platform/ab8500-i2c.0/ab8500-fg.0/power_supply/ab8500_fg/power/cont
rol
/sys/devices/platform/ab8500-i2c.0/ab8500-fg.0/power_supply/ab8500_fg/power/runt
ime_suspended_time
/sys/devices/platform/ab8500-i2c.0/ab8500-fg.0/power_supply/ab8500_fg/power/runt
ime_active_time
/sys/devices/platform/ab8500-i2c.0/ab8500-fg.0/power_supply/ab8500_fg/power/auto
suspend_delay_ms
/sys/devices/platform/ab8500-i2c.0/ab8500-fg.0/power_supply/ab8500_fg/capacity
/sys/devices/platform/ab8500-i2c.0/ab8500-chargalg.0/power_supply
/sys/devices/platform/ab8500-i2c.0/ab8500-chargalg.0/power_supply/ab8500_chargal
g
/sys/devices/platform/ab8500-i2c.0/ab8500-chargalg.0/power_supply/ab8500_chargal
g/uevent
/sys/devices/platform/ab8500-i2c.0/ab8500-chargalg.0/power_supply/ab8500_chargal
g/subsystem
/sys/devices/platform/ab8500-i2c.0/ab8500-chargalg.0/power_supply/ab8500_chargal
g/device
/sys/devices/platform/ab8500-i2c.0/ab8500-chargalg.0/power_supply/ab8500_chargal
g/status
/sys/devices/platform/ab8500-i2c.0/ab8500-chargalg.0/power_supply/ab8500_chargal
g/health
/sys/devices/platform/ab8500-i2c.0/ab8500-chargalg.0/power_supply/ab8500_chargal
g/type
/sys/devices/platform/ab8500-i2c.0/ab8500-chargalg.0/power_supply/ab8500_chargal
g/power
/sys/devices/platform/ab8500-i2c.0/ab8500-chargalg.0/power_supply/ab8500_chargal
g/power/runtime_status
/sys/devices/platform/ab8500-i2c.0/ab8500-chargalg.0/power_supply/ab8500_chargal
g/power/control
/sys/devices/platform/ab8500-i2c.0/ab8500-chargalg.0/power_supply/ab8500_chargal
g/power/runtime_suspended_time
/sys/devices/platform/ab8500-i2c.0/ab8500-chargalg.0/power_supply/ab8500_chargal
g/power/runtime_active_time
/sys/devices/platform/ab8500-i2c.0/ab8500-chargalg.0/power_supply/ab8500_chargal
g/power/autosuspend_delay_ms
/sys/class/power_supply
/sys/class/power_supply/ab8500_ac
/sys/class/power_supply/ab8500_usb
/sys/class/power_supply/ab8500_fg
/sys/class/power_supply/ab8500_btemp
/sys/class/power_supply/ab8500_chargalg
[email protected]:/ #
Click to expand...
Click to collapse
Can it be?
Thank you!
Beta version done... please test and let me know... if something missing I will fix... "how to" is on first post
Man i thought it would work for locked BL too becouse its stock Kernel with SE Certificate
Sent from my LT22i using xda app-developers app
Wolfbreak said:
Man i thought it would work for locked BL too becouse its stock Kernel with SE Certificate
Sent from my LT22i using xda app-developers app
Click to expand...
Click to collapse
SE certificate? Please let me know more about these certificate, I am new to Sony, whats use of these certificate and where is stored these certiificate? I found stock boot image have 4 parts inside (kernel, unknown_elf.3 ???, ramdisk, command line)... I reverted everything back and right to sin format including these elf.3 !
This working on relocked bootloader after unlocking... allready tested on X-Go ! But maybe elf.3 is in conjuction with these certificate?
No i mean if its original only with a slight modify it might work to flash becouse its original but if you change more it wont. Like example a stock Kernel you can flash becouse its from SE but custom you cant with locked becouse its modified more and adds things and all so its no original anymore. With certificate i mean like permission so stock Kernel works to flash becouse it has SE certificate and others dont with locked becouse its not SE its example DoomKernel... On X10 it was like this if i remember correctly its been a long time
Sent from my LT22i using xda app-developers app
Ok, I not understand how it is secured on Sony but on HTC these images is signature checked by bootloader so if some one modify one bute inside signed image installation mision fail when bootloader is locked...
Any one tested my version of the CWM recovery?
Information and Modules description
I was in the need to add some missing kernel modules to my Xperia Mini Pro sk17i with v4.1.B.0.587, and I couldn't find modules compiled for that ICS kernel version, so I decided to build them myself.
All modules have been compiled from official sony Xperia v4.1.B.0.587 kernel sources, using Android NDK r5, and they should be fine with any ICS based Xperia 2011 device (with that kernel version).
This is the list of modules, with some interesting programs using them:
fuse.ko: Cryptonite (used to create encrypted EncFS or Truecrypt volumes, adds support to mount drives so that are visibile to the whole Android system. Note: Cryptonite is not currently able to load the module automatically, you need to load it from Terminal Emulator..se more below)
usb-storage.ko, nls_utf8.ko, ntfs.ko (compiled with write support, currently untested): USB OTG Helper (used to mount external USB drives with USB On The Go cables).
cifs.ko, slow-work.ko, md4.ko: CifsManager (used to mount network shares)
ext4.ko, jbd2.ko: if you wish to use the EXT4 filesystem
Installation Instructions
Attached to this post you will find a ZIP that can be used along with CWM Recovery to install the modules in system.
Download the module, put it inside you SD card, reboot your phone in CWM (which you can install with the Xperia CWM Auto-Installer) and select install zip from sdcard, and browsed to the ZIP. Reboot your phone when install finishes.
Loading Modules
No module is automatically loaded at system startup: this saves your memory and battery (some of those modules are known to drain your battery if always loaded).
To manually load a module you have to open the Android Terminal Emulator and tap:
Code:
su
insmod /system/lib/modules/MODULENAME.ko
where MODULENAME is the name of the module you want to load.
Other useful commands:
Code:
lsmod
to see currently running commands
Code:
rmmod MODULENAME.ko
to unload a module.
If you wish to manually load a module at phone startup you should use init.rd or any other method (?) to run custom scripts at startup.
Load Order
Some modules need to be loaded in a specific order:
slow-work.ko must be loaded before cisf.ko
jbd2.ko must be loaded before ext4.ko
Other Firmware Versions
I've released the same package for other firmware versions, click on the firmware version to go to the specific thread:
GB v4.0.2.A.0.58 Kernel Modules package by zxp
Changes
v1 - 2012.10.04
============
- First release
Terminal emulator says cannot allocate memory.
Oh god, why??
Sent from my Nokia 3310 using Tapatalk 2
chepoz said:
Terminal emulator says cannot allocate memory.
Oh god, why??
Sent from my Nokia 3310 using Tapatalk 2
Click to expand...
Click to collapse
Terminal emulator doesn't start? Or is the "insmod" command output telling you that it cannot allocate memory? Either way it seems like your RAM is full and there is not enough space to load the module(s) you want to load.
zxp said:
Terminal emulator doesn't start? Or is the "insmod" command output telling you that it cannot allocate memory? Either way it seems like your RAM is full and there is not enough space to load the module(s) you want to load.
Click to expand...
Click to collapse
No, it says like that after I install some modules. Some of them running well, n some says like that.
So maybe my ram not much left to run those modules. Thanx for answering. :thumbup:
Sent from my Nokia 3310 using Tapatalk 2
Works on Sony wt19i
Thank you,,,
I've successfully accessed the usb pendrive using this simple method. It worked for Sandisk Cruzer Blade pendrives.....
But I can not access my transcend jetflash 700 16 GB pendrive...
If there any solution for this....then reply...
is the slow-work.ko still needed for ICS? from what I searcher it was needed for froyo (2.2)
Warl0rd said:
is the slow-work.ko still needed for ICS? from what I searcher it was needed for froyo (2.2)
Click to expand...
Click to collapse
It's a while since I compiled those modules and I may recall wrong, but...as far as I can remember it was related to the Linux Kernel version on which our Android OS ROM is based. That is, the Xperia 2011 lineup uses Kernel 2.6 (both on Android 2.3 and 4.0), which requires slow-work to be compiled; if it was based on Linux Kernel v3.x then slow-work.ko wouldn't be needed.
i have an error
when im going to load modules,this is what's happening
export PATH=/data/local/bin:$PATH
a/local/bin:$PATH <
[email protected]:/ $ su
ib/modules/usb-storage.ko <
insmod: init_module '/system/lib/modules/usb-storage.ko' failed (File exists)
/lib/modules/ntfs.ko <
insmod: init_module '/system/lib/modules/ntfs.ko' failed (File exists)
255|[email protected]:/ #
please help me
i'm getting the same error
i'm on .587 stock kernel & rom. cant load modules
fixed!
sorry for disturbing u guys. I figured it. that message appears because the module is running. its my fault that I didn't check whether its running or not.
tharu_roxx said:
when im going to load modules,this is what's happening
export PATH=/data/local/bin:$PATH
a/local/bin:$PATH <
[email protected]:/ $ su
ib/modules/usb-storage.ko <
insmod: init_module '/system/lib/modules/usb-storage.ko' failed (File exists)
/lib/modules/ntfs.ko <
insmod: init_module '/system/lib/modules/ntfs.ko' failed (File exists)
255|[email protected]:/ #
please help me
Click to expand...
Click to collapse
It seems like those modules are already loaded in memory, as it happened to RavinduSha.
Try lsmod: if usb-storage.ko and ntfs.ko are listed by lsmod, they are already loaded, and that's why you get those errors.
Can anyone compile modules for dvb-t dongle rtl2832u like those available here?
http://forum.xda-developers.com/showthread.php?t=1841759
Or at least point me in the right direction
btw modules are working fine
Problem Solved!!!
{
"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"
}
Yep...these modules work fine!!!! But i couldn't mount usb storage device using the OTG Helper app.so I tried stick mount pro(with above modules,no need to load them) It worked!!!! [this happened when I'm using the stock rom & the kernel,but now my kernel supports them by default ,so no worries!! ]
Current Device : MT11i Xperia Neo V
ROM : Xperia Ultimate HD ™
Build Number : 2.0.3
Kernel : Suave Kernel
Root Status : Rooted
Bootloader : Unlocked
Previous Devices : Samsung Galaxy Y
GT-5360(Sold)
Sent from my MT11i using XDA Premium HD app
Hello zxp,
I want to learn to build some modules by myself because I want to try to build some drivers for cameras, scanner, etc... Can you tell me about where you've got the source code to build or the way to build it?
I've downloaded source code of my android on developer.sonymobile.com. When I extracted it I saw the folder structure like "kernel/drivers/usb". Did you build the modules from source code of that folder?
When i type insmod in the terminal
It said invaild file format can anyone help,please??
Sent from my SK17i using xda premium
zack871024 said:
When i type insmod in the terminal
It said invaild file format can anyone help,please??
Sent from my SK17i using xda premium
Click to expand...
Click to collapse
What?? It's impossible,:-o
Sent from my MT11i using Tapatalk 2
I dont know why either
Anyone help?? Thanks
postimage.org/image/x33tabkc5
Sent from my SK17i using xda app-developers app
zack871024 said:
I dont know why either
Anyone help?? Thanks
postimage.org/image/x33tabkc5
Sent from my SK17i using xda app-developers app
Click to expand...
Click to collapse
Have you rooted ur phone?
Sent from my MT11i using Tapatalk 2
tharu_roxx said:
Have you rooted ur phone?
Sent from my MT11i using Tapatalk 2
Click to expand...
Click to collapse
Are you kidding??I'm not that stupid=) Of courseHelp me!! By the way,i got my bravia engine 2 working again cheers!!
Sent from my SK17i using xda app-developers app