Kernel Modules for Xperia 2011 ICS v4.1.B.0.587: fuse.ko,usb-storage,cifs,ntfs,ext4.. - Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A

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

Related

Dual-boot your favourite custom ROM with stock firmware

To encourage developers and users to switch to the new xRecovery, I prepared a package that allows dual-booting between custom ROM and stock firmware. This is just a proof of concept, I am not going to develop it further nor support it as usual project release. Instead, I hope that developers will find many useful things inside to use in their own pojects
It also may be useful for people using 2.3 ROMs without camera/camcorder.
Tested with: FreeX10 beta4, Woflbreak's CM, AOSP 2.3
PLEASE READ CAREFULLY:
- it works from NAND rather than SD Card - should not suffer fom performance issues
- it will work with any custom 2.2/2.3 ROM of reasonable size
- it WON'T work with custom 2.1 ROMs - not enough storage space
- it uses 200MB of your /system and 256MB of your /data partition - make sure you've got enough free space
- it requires xRecovery 1.0.0 (the old one doesn't allow custom boot)
- it cannot be accessed via recovery, but it's possible to mod it to do so (devs/adv.users)
- it works with baseband 49/52!
- if you back up your system with nandroid backup, the 2.1 ROM will be included in this backup
Click to expand...
Click to collapse
Install:
Flash the dualboot 2.0.A.0.504.zip via xRecovery 1.0.0.
Uninstall:
Remove the following folders using Root Explorer:
Code:
/data/dualboot
/system/dualboot
Boot into stock 2.1 firmware:
Boot into xRecovery, select "Boot custom ROM/kernel"
Download:
dualboot 2.0.A.0.504.zip
Cheers,
z
You genius you've done another amazing things for our phone thank you
Sent from my SEX10 using XDA App
Nice work mate!
What kind of genies do we have hear :O?!
I told everyone so, updating recovery has an advantage.
U really rock man
zdzihu said:
To encourage developers and users to switch to the new xRecovery, I prepared a package that allows dual-booting between custom ROM and stock firmware. This is just a proof of concept, I am not going to develop it further nor support it as usual project release. Instead, I hope that developers will find many useful things inside to use in their own pojects
It also may be useful for people using 2.3 ROMs without camera/camcorder.
Tested with: FreeX10 beta4, Woflbreak's CM, AOSP 2.3
Install:
Flash the dualboot 2.0.A.0.504.zip via xRecovery 1.0.0.
Uninstall:
Remove the following folders using Root Explorer:
Code:
/data/dualboot
/system/dualboot
Boot into stock 2.1 firmware:
Boot into xRecovery, select "Boot custom ROM/kernel"
Download:
dualboot 2.0.A.0.504.zip
Cheers,
z
Click to expand...
Click to collapse
Thanks for the work buddy..... I don't have access to mediafire from workplace will check once i reach home....
As you said its for developer's so i assume all source code's are included in it.
How to revert back to the first rom?
Thanks Z..u r the best
astrall said:
How to revert back to the first rom?
Click to expand...
Click to collapse
Remove this:
/data/dualboot
/system/dualboot
FINALLY
something awesome to play with!!!
downloading now...
will test it out this weeked for dual booting using FreeX10/CM7
also i think we can integrate custom kernel booting into this... for those roms which require it...
finished d/ling:
@anantshri:
Code:
#!/sbin/sh
# zdzihu: let's get some Ubuntu fun!
insmod /system/kernel/splboot.ko
sync
cat /system/kernel/miniloader > /proc/splboot/image
cat /system/kernel/boot-stock.img > /proc/splboot/boot_img
sleep 3
echo > /proc/splboot/boot
interesting eh???
guess i will heave to search for that splitbootimg binary/app again...
Genius @work
Thank you Z without you there would be no fun using the X10...
DooMLoRD said:
Code:
#!/sbin/sh
# zdzihu: [b]let's get some [size=4]Ubuntu[/size] fun[/b]!
insmod /system/kernel/splboot.ko
sync
cat /system/kernel/miniloader > /proc/splboot/image
cat /system/kernel/boot-stock.img > /proc/splboot/boot_img
sleep 3
echo > /proc/splboot/boot
Click to expand...
Click to collapse
Lawl, I forgot to rename my script Damn Ubuntu never booted fine anyway...
Cheers,
z
oh i see...
so basically we are flashing 2.1 ROM on top of custom rom....
so the 2.1 rom is actually in the .ext2 files!!!
zdzihu said:
Lawl, I forgot to rename my script Damn Ubuntu never booted fine anyway...
Cheers,
z
Click to expand...
Click to collapse
so for multibooting we can actually jsut store the img files on sdcard check flags set by users... copy those img files to /data & /system and then jsut continue booting with the modded kernel u posted...
hu i think that should work...
DooMLoRD said:
so for multibooting we can actually jsut store the img files on sdcard check flags set by users... copy those img files to /data & /system and then jsut continue booting
Click to expand...
Click to collapse
It does work. But it's not pretty. I played with both /system and /data being stored on SD Card, but the system suffered from terrible freezes/"x stopped responding" (like FreeX10 alpha). Also, first boot took around 7-8min.
DooMLoRD said:
with the modded kernel u posted...
Click to expand...
Click to collapse
With any kernel really. It's ramdisk that's important (mounting images).
Cheers,
z
V/Nice!
Q: Is this using CM7_Passion sources? cm_passion_full-xx - would be nice to compile and maybe add some extra's in.. possible?
{
"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"
}
zdzihu said:
It does work. But it's not pretty. I played with both /system and /data being stored on SD Card, but the system suffered from terrible freezes/"x stopped responding" (like FreeX10 alpha). Also, first boot took around 7-8min.
With any kernel really. It's ramdisk that's important (mounting images).
Cheers,
z
Click to expand...
Click to collapse
ya i got that... i actually ment the ramdisk which doesnt remount NAND MTDs
Great works !!
Please teach me how to make system.ext2 & data.ext2 files ??

[modules][play??][fw:4.0.a.2.368] usb-otg {doesnt work... Sorry...}

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?

[ Tutotrial ] Install either Ubuntu or Debian in any Android Phone without any app

This is a Tutorial to install either Ubuntu or Debian in any Android mobile without using any app ​
* Installing Ubuntu or Debian Linux does not format your Android OS or change anything to your phone.
The Operating Systems run over the underlying Android OS which continues to function as normal
Choosing your Linux OS:
There are few things you must be aware of before installing Ubuntu/Debian on youe Android Phone
Ubuntu does not support earlier ARM CPUs like the ones used in the Motorola Cliq. Samsung Galaxy Fit (ARMv6), Samsung Galaxy Y, etc.
( Reason behind this is , Your Android OS Kernel must support loop devices. Most newer Android smartphones/tablets come with this support so we can mount our Ubuntu image as a loop device. If not, you will either have to build your own kernel with support for loop devices or you can try an aftermarket ROM for your phone as most aftermarket ROMs come with support for it. )
You need at least an ARMv7 CPU like the kind found in the Motorola Droid, Samsung Galaxy S,HTC EVO 3D, Sony Experia Play, etc. most newer phones (Hummingbird, Snapdragon, Tegra2, etc.).So you can Install Ubuntu if you have ARMv7 or newer Processor.
If you have ARMV6 or any other moderate Processor don't be sad, because Debian supports the CPU on practically all Android devices, so if you prefer Debian, or you can't run Ubuntu, choose the Debian download link.
* If you're not sure what CPU your device has, look up your device on http://pdadb.net/, click the link under CPU, and read the line for "Supported Instruction Set(s)".
e.g. : My Phone which is a " Samsung Galaxy Fit" uses ARMV6 Instruction Sets.
{
"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"
}
Click to expand...
Click to collapse
Pre-Requirements:
Hardware Required:
an Android Phone
SD Card with more than 2GB of free Space
Android root environment:
Most important! Your Android device should be “rooted” because you need root access to run Ubuntu/Debian off your Android. If your device is not rooted you have to root your device.
Linux Operating System:
Download suitable OS from the following Link:
Ubuntu 11.04 (Natty Narwhal)
linux.ubuntu-natty.tar.bz2 Ubuntu 11.04 (Natty)
Ubuntu 11.10 Oneiric Ocelot
linux.ubuntu-oneiric.tar.bz2 Ubuntu 11.10 (Oneiric)
Debian 6.0 Squeeze
linux.debian-squeeze.tar.bz2 Debian 6.0 (Squeeze)
Click to expand...
Click to collapse
Applications Required:
BusyBox Installer
A terminal emulator like Better Terminal Emulator ( Recommended ) or Terminal Emulator.
Optional Apllications:
androidVNC
Or
ConnectBot
Click to expand...
Click to collapse
Procedure ----------------------------------------------->
Step 1:
(Mount the SD card on your computer.)
Extract the .tar.bz2 file you downloaded to your SD card. You should now have a folder named "linux" on the root of your card.
(Unmount the SD card.)
Open Busybox Installer, and install Busybox.
Open Better Terminal Emulator, and install Better Terminal Emulator.
Click to expand...
Click to collapse
Step 2:
Open your terminal emulator. (If using ConnectBot, connect to 'local', not 'ssh'.)
Run the following commands:
Code:
[B]su[/B]
( If Prompt for Superuser Request then allow )
Code:
cd /sdcard/linux
sh install.sh
If you don't see any errors, Linux is now installed.
Click to expand...
Click to collapse
Step 3:
Open your terminal emulator.
To start a chroot session
Code:
su
linux
To start the SSH server
Code:
su
linux ssh
You can then use ConnectBot (SSH: [email protected]) on your device, or any SSH client to connect to your device. See Login Information, below.
Click to expand...
Click to collapse
To start a VNC session
( Firest you need androidVNC to be installed , then type the following in terminal )
Click to expand...
Click to collapse
Code:
su
linux vnc
The first time you run VNC, it will prompt you to create a VNC password.
You can then use androidVNC (host: localhost port: 5901), or any VNC client to connect to your device.
Configure The VNC App as follows:
Note: The default desktop environment is icewm. If you wish to replace it, for example, with LXDE:
Run the following as root in Linux:
Code:
apt-get autoremove icewm- lxde+
Secure your Log in Password:
Please remember to change these passwords if you are planning on using the SSH server. Malicious people can do Very Bad things to your device if you don't.
There are two accounts included in the images:
root
Password:cheesecake
user
Password:dessert
Click to expand...
Click to collapse
After a successful connection to host you will be able to use Ubuntu / Debian in graphical interface just like in your PC ! It will keep your Android OS as it is and just run in the upper layer over it
These are some of the screen shots taken from my Samsung Galaxy Fit!
Click to expand...
Click to collapse
Linux vs Linux Terminal Emulator :
Terminal Emulator only Emulates Linux terminal, but after Linux Installation you can get full features; more than just the limited commands which runs on Android shell rather than Linux Shell.
Please Leave your Feedback and Queries below. Thank You
​
Click to expand...
Click to collapse
riddz17 said:
This is a Tutorial to install either Ubuntu or Debian in any Android mobile without using any app ​
Click to expand...
Click to collapse
Nice, i have tried for my Galaxy Ace so with ARM V6 too, but the terminal emulator gave me error in the step 3 and 4
error not working
I'm getting about a dozen errors in the install process, all of which seem to relate to file permissions.
G.Galante said:
Nice, i have tried for my Galaxy Ace so with ARM V6 too, but the terminal emulator gave me error in the step 3 and 4
Click to expand...
Click to collapse
what kind of error could you please specify??
First of all check is your phone rooted?
when I type su
sh install.sh
there are many error like dir.. not found help me...
Sent from my HTC Explorer A310e using xda app-developers app
sateesh907 said:
when I type su
sh install.sh
there are many error like dir.. not found help me...
Sent from my HTC Explorer A310e using xda app-developers app
Click to expand...
Click to collapse
worked for me. I tried to install from the microsd card (sdcard-ext) but i got errors. Once i moved the files to the phones memory (sdcard) it worked like a charm.
note: I am using Debian 6.0 Squeeze
Sent from my GT-I9000 using Tapatalk 2
ivke101 said:
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
I get the same error. Anyone know how to fix it?
hey guys
Thanx to the author of this forum on debian on android. I had the same problem you see in the error logs above. the problem is between regular "mount" command and busybox "mount". you need to use the busybox mount. so I added the word busybox infront of every mount word in the script. eg. busybox mount -o , rw /system remount. the alternative is to delete the mount found on /system/bin so that the terminal will use the busybox one automatically on /system/xbin.
Thanks, I found that the version of busybox I had didn't install the mount comand. I had to use the smart installer and manually check the box to overwrite the mount command then it worked.
Sent from my SPH-L710 using xda app-developers app
Nice work. I've been experimenting with Ubuntu some so I can run side by side w/windows.
Does anyone know if You can connect to the the ubuntu instance on your phone from a computer through vnc? I would like to be able to use a bigger keyboard and mouse to control it.
Edit: If I make changes to the Linux.img on my phone and just copy the whole folder to my tablet will it still keep all of the changes? (I will try it tonight if know one knows).
---------- Post added at 10:52 AM ---------- Previous post was at 10:36 AM ----------
Ok you can connect to the phone from a computer. I used wifi tether and then just put the phones ip and the port into tightvnc and it connected. It took a minute to recognized the phone the first time though.
Sent from my SPH-L710 using xda app-developers app
riddz17 said:
This is a Tutorial to install either Ubuntu or Debian in any Android mobile without using any app ​
Click to expand...
Click to collapse
HI , THANKS
for your work..i have galaxy ace plus [armv7] ,i tired installing linux on my phone, when i type "sh install.sh "then ,,,such dir not found like error
appears, i am new for linux command [ my dir . /sdcard/external_sd/linux ].what can i do for this? plz help me .
patilsb said:
HI , THANKS
for your work..i have galaxy ace plus [armv7] ,i tired installing linux on my phone, when i type "sh install.sh "then ,,,such dir not found like error
appears, i am new for linux command [ my dir . /sdcard/external_sd/linux ].what can i do for this? plz help me .
Click to expand...
Click to collapse
- try to install "busybox installer" first..
- when you open the app, it will ask to install busybox..
pay attention to "Advanced install" checkbox.. be sure to have it checked..
- you will found so many applets.. try to find named "MOUNT"..
- when you found them, see the triangle sign on the right-side.. click it..
- there are 3 options: symlink applet / remove symlink / skip symlink
pick symlink applet..
- press install
- after it's done, get ou of busy box
- back to terminal, repeat the step "sh install.sh"
i got stuck @ step 2 " please wait while booting ubuntu.img.. this may take some time ,,. "
i installed busy box , i got my device root
sent from my Arc S
itzwood said:
i got stuck @ step 2 " please wait while booting ubuntu.img.. this may take some time ,,. "
i installed busy box , i got my device root
sent from my Arc S
Click to expand...
Click to collapse
How long did you wait? Mine took about 15 minutes the first time after the first its just is there.
i left it before i go to sleep .. waked up nothing "ABOUT 8hours "
scientist343 said:
How long did you wait? Mine took about 15 minutes the first time after the first its just is there.
Click to expand...
Click to collapse
itzwood said:
i left it before i go to sleep .. waked up nothing "ABOUT 8hours "
Click to expand...
Click to collapse
Try redownloading it to make sure it isn't corrupt.
You can also try a reboot, then try starting at the top again. I had it do that on my old phone and after a reboot it worked.
Also which version of ubuntu did you download 11.04 or 11.10?
no such file or directory errors
Hi I'm getting "no such file or directory" errors when I try the step "sh install.sh"
can't post pictures yet so I'll type up the short version
# sh install.sh
remounting /system rw ...
mount: no such file or directory
installing scripts in /system/bin ...
mounting the linux image ...
mounting prepwork...
mounting: loopback mount ...
mknod /dev/block/loop254: file exists
mount: invalid argument
mounting: setting up chroot environment ...
mount: no such file or directory
mkdir failed for /data/local/mnt/media/sdcard, no such file....
[done]
then the rest is no such file or directory
I'm on an Epic 4g touch rooted obviously
I tried putting busybox in front of mount in the script as suggested before
I moved all the files from /mnt/sdcard/external_sd to /sdcard
made sure mount is installed in busybox
Not sure what to try next. Guess I could make the folders manually and see what happens.

Stock bootimg 6.1.B.0.544 + root + CWM Recovery v5.5.0.4

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?

[Ubuntu] T3buntu

{
"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"
}
Please OP remove my old post about Ubuntu on Tab 3...
T3buntu (Had to call it something...)
Disclaimer:
What you do with this information is up to you. If your device breaks while trying anything in here you do that at your own risc.
I cant be held responsible for anything that happens to your device.
Everything in here was tested on a Samsung Galaxy Tab3 10.1(5210) if you try anything in here on any other device thats up to you.
Most of the work is made by the Linux on Android team i have just tested and fixed some stuff.
The image is ext2, x86 but im working on a ext4, AMD64 image.
”Changelog”
1. Replaced lxde with KDE Plasma
2. Added entryś in etc/fstab for int/ext SdCards
3. Edited bootscript from the Linux on Android team so that the SdCards in the Tab is correcly mounted and works with fstab.
4. Installed "missing" packages to minimize errors.
Works:
Wifi
Battery indicator
Int/Ext SdCard
Most of the stuff in Ubuntu.
Issues:
Leftpanel is black
Slow startup, but can be fixed. I will add that later.
Some apps dont work if you start them as root.
Couldnt make jpg work as wallpaper so using png at the moment.
Rotation isnt setup since we cant use xrandr to rotate the screen..
Not tested:
GPS
ToDo
Streamline startup
Add init.d support on the Tab
Tweaking were ever possible.
Fix sound
Now for the fun stuff.
Installation:
1. Root your device. I used this Guide.
2. Install Busybox.
3. Install Linux on Android.
4. Install a VNC client of your shoice, i preferr Jump Desktop free.
5. Copy bootscript.sh to /data/data/com.zpwebsites.linuxonandroid/files/ overwrite the old file.
6. Unpack and Copy the t3buntuv1.2_20131216.img to a place of your choosing on either internal or external sdcard.
7. Make a Linux on Android widget and point it to the img file you copied in 6.
OBS !! This image is preconfigured with the user ubuntu and psw t3buntu..
8. Now click on the LOA widget you made in 7 and let linux ”bootup”
9. In your VNC client connect to localhost.
DONE ! Your now in Ubuntu..
If you want more screenspace you can uncomment
# service call activity 42 s16 com.android.systemui
In bootscript.sh this will remove the android panel. The problem with this at the moment is that to
get it back you have to restart the Tab becourse the ´am´ command to get it back ”Seg faults” on
my tab and i havnt figured out why yet.
Consider this image as alpha...
OBS !! The image file is BIG 1.4GB compressed and 4GB decompressed. Will try and make it smaller not sure how the Linux on Android team made there images so small...
LINK to imagefile
LINK to bootscript
Credits
Linux on Android team
The one that made the scripts from the start. Not sure who made them...
How about a link to get 3. Linux on Android.
I know I'm top lazy to Google.
Sent from my GT-P5210 using XDA Premium HD app
Awesome! Glad to see something! And having Ubuntu is a very cool os to have! Good work and thank you!
Sent from my SCH-I605 using xda app-developers app
Added links to Linux on Android and Busybox in first post.
Nice, but there are a few things...
The bootscript.sh contains one little, but crucial error.
At line 172, character 44, you forgot one space, which makes the mount procedure unusable:
Code:
$bbox mount -o bind /storage/extSdCard $mnt/extSdCard
Which should be:
Code:
$bbox mount -o bind /storage/extSdCard $mnt/extSdCard
Without this (for me) it failes while it's starting up.
And, another thing, my tablet reboots at the moment I have to run VNC to start the X server, even though I'm not doing or touching anything.
After reboot it doesn't start up t3buntu either.
But, very good work !!
And yes, I do have Samsung Galaxy Tab 3 10.1 GT-P5210...
RubenStauttener;48606882]Nice, but there are a few things...
The bootscript.sh contains one little, but crucial error.
At line 172, character 44, you forgot one space, which makes the mount procedure unusable:
Code:
$bbox mount -o bind /storage/extSdCard $mnt/extSdCard
Which should be:
Code:
$bbox mount -o bind /storage/extSdCard $mnt/extSdCard
Without this (for me) it failes while it's starting up.
Havnt noticed any problems here but i have added the space and updated the script since both versions works for me.
And, another thing, my tablet reboots at the moment I have to run VNC to start the X server, even though I'm not doing or touching anything.
After reboot it doesn't start up t3buntu either.
Does it reboot during script execution ? It do sound like a mem issue. Do you have widgets and such running in android ?
You can try with enabling the swapfile in bootscript.sh .
But, very good work !!
And yes, I do have Samsung Galaxy Tab 3 10.1 GT-P5210...
I've got the terminal up and running fine. But I can't VNC into it. What settings are you using for you VNC viewer?
How about native graphic support using libhybris? Or since this device use PowerVR SGX 544, is native X11 possible? Reference: https://wiki.archlinux.org/index.php/Intel_GMA3600
EDIT: https://github.com/trevd/android_kernel_samsung_santos10/tree/cm-10.2/drivers/staging/mrst/pvr and https://github.com/thomas001/cedarview-drm/tree/master/staging/cdv/pvr looks similar
Thanks for sharing but it's not working
VNC: autentification failed !
Jump Desktop: It ask a password, and I don't have this password !
Sent from Gallifrey using TARDIS
Nonta72 said:
Thanks for sharing but it's not working
VNC: autentification failed !
Jump Desktop: It ask a password, and I don't have this password !
Sent from Gallifrey using TARDIS
Click to expand...
Click to collapse
Test password: ubuntu
When run script say mnt error =/
zorrigas said:
Test password: ubuntu
When run script say mnt error =/
Click to expand...
Click to collapse
Thanks, but I already solved it :good:
Sent from my GT-5210 powered by AmatROM HD
Hi, I posted a question in the Q&A forum (them 10 posts), but I guess it really belongs here.
Tried this on my TWRP rooted UANB4 stock rom P5210, stock kernel. And I get the following with your script and image:
Code:
[email protected]:/ $
[email protected]:/ $ cd /storage/extSdCard/Img
[email protected]:/storage/extSdCard/Img $ su
[email protected]:/storage/extSdCard/Img # sh /data/data/com.zpwebsites.linuxonandroid/files/bootscript.sh /storage/extSdCard/Img/t3buntuv1.2_20131216.img
Checking loop device... FOUND
mount: mounting /dev/block/loop255 on /data/local/mnt failed: Invalid argument
Error: Unable to mount the loop device!
1|[email protected]:/storage/extSdCard/Img #
Line : $bbox mount -t ext2 /dev/block/loop255 $mnt
Do I tell busybox to overwrite the mount command?
Otherwise, excellent work, cant wait till I have it running.
*EDIT*
Turns out I just had to copy the image again, I guess my first transfer got cut off.
Totally works, thx
hey. i noticed that the last update was in April of 2014. i was wondering if there was any updates on this.
getting linux on my tablit was the #1 reason i chose to root my GT-P5210 in the first place.
Homage said:
hey. i noticed that the last update was in April of 2014. i was wondering if there was any updates on this.
getting linux on my tablit was the #1 reason i chose to root my GT-P5210 in the first place.
Click to expand...
Click to collapse
I did not try this one. I bet itworks in VNC as it tell us. Instead i did
http://forum.xda-developers.com/showpost.php?p=58175673&postcount=54
I guess I can say it work aceptable in VNC mode, definitly work nice in comand mode. I been working in a native solution but it is a hard bone for my teeth. Look in the general area.
Download link is down
I would like to run Ubuntu on my Tab 3 but the link doesn't work. Could some upload a working link please?
Hi Guys,
Anyona has this .sh script and the t3buntuv1.2_20131216.img file? if you send me im hosting and distributing free as i live i want to use for my home automatization.
THX
G
jorgen_gustavsson said:
Please OP remove my old post about Ubuntu on Tab 3...
T3buntu (Had to call it something...)
Disclaimer:
What you do with this information is up to you. If your device breaks while trying anything in here you do that at your own risc.
I cant be held responsible for anything that happens to your device.
Everything in here was tested on a Samsung Galaxy Tab3 10.1(5210) if you try anything in here on any other device thats up to you.
Most of the work is made by the Linux on Android team i have just tested and fixed some stuff.
The image is ext2, x86 but im working on a ext4, AMD64 image.
”Changelog”
1. Replaced lxde with KDE Plasma
2. Added entryś in etc/fstab for int/ext SdCards
3. Edited bootscript from the Linux on Android team so that the SdCards in the Tab is correcly mounted and works with fstab.
4. Installed "missing" packages to minimize errors.
Works:
Wifi
Battery indicator
Int/Ext SdCard
Most of the stuff in Ubuntu.
Issues:
Leftpanel is black
Slow startup, but can be fixed. I will add that later.
Some apps dont work if you start them as root.
Couldnt make jpg work as wallpaper so using png at the moment.
Rotation isnt setup since we cant use xrandr to rotate the screen..
Not tested:
GPS
ToDo
Streamline startup
Add init.d support on the Tab
Tweaking were ever possible.
Fix sound
Now for the fun stuff.
Installation:
1. Root your device. I used this Guide.
2. Install Busybox.
3. Install Linux on Android.
4. Install a VNC client of your choice, i preferr Jump Desktop free.
5. Copy bootscript.sh to /data/data/com.zpwebsites.linuxonandroid/files/ overwrite the old file.
6. Unpack and Copy the t3buntuv1.2_20131216.img to a place of your choosing on either internal or external sdcard.
7. Make a Linux on Android widget and point it to the img file you copied in 6.
OBS !! This image is preconfigured with the user ubuntu and psw t3buntu..
8. Now click on the LOA widget you made in 7 and let linux ”bootup”
9. In your VNC client connect to localhost.
DONE ! Your now in Ubuntu..
If you want more screenspace you can uncomment
# service call activity 42 s16 com.android.systemui
In bootscript.sh this will remove the android panel. The problem with this at the moment is that to
get it back you have to restart the Tab becourse the ´am´ command to get it back ”Seg faults” on
my tab and i havnt figured out why yet.
Consider this image as alpha...
OBS !! The image file is BIG 1.4GB compressed and 4GB decompressed. Will try and make it smaller not sure how the Linux on Android team made there images so small...
LINK to imagefile <===== this URL broken
LINK to bootscript <===== this URL broken
Credits
Linux on Android team
The one that made the scripts from the start. Not sure who made them...
Click to expand...
Click to collapse

Categories

Resources