Related
{
"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"
}
This is new Android distribution based on Linux, Android and Archos stock os, using SDE from Archos.
Features:
Easy install method for external (SDcard) and Internal storage
EXT4 (much faster than ext3, can store files >4GB comparing to FAT32)
Full read/write access to every part of system
root (su + superuser.apk) out of the box
new services like: samba, sshd, vpnc, openvpn, dvbt, nfs4
3G/usb tether support
Possibility to remove some google/Archos apps
Swap memory in RAM (CompCache) or on disk by default or when you need it
No 300MB limit for apps (and no faulty app2sd required)
You can have SD card Class 8/10 - that can be much faster than internal flash (check this thread)
Many new new kernel modules (usbserial, ntfs, 3G modems, nfs4, cifs, hfs, iptables etc.)
DVB-T support for selected tuners
updated modules, firmware (like WiFi)
User friendly UrukConfig application
... and much, much more - to much to mention all here - please read changelog
Since 1.0 release main documentation source for UrukDroid is on it's WiKi. Please use it as a first and primary information source for UD.
Link to project (googlecode) page is: http://code.google.com/p/urukdroid
Update (10.09.2015)
Since code.google.com is no longer working (read only for limited time) - here are working links to latest (and final) release of UrukDroid: Dropbox,
I hope that new, much more detailed and complete documentation will help you use UrukDroid at it's full potential.
Changelog, proposed futures
Changelog:
UrukDroid 1.6 (02.01.2012) "DOV FUS LOS Wahl ko Daar Sivaas!"
[CHANGE] Incorporated changes from Archos firmware 2.4.19, 2.4.65, 2.4.80 and 2.4.81
[CHANGE] Updated superuser apk and binaries
[FIX] Fixed some library linking
[NEW] Changed top bar button size to 32px permanently
[NEW] New overclock module from milestone-overclock to change CPU voltage and max frequencies on the fly
[CHANGE] Added overclock support to CPUGovernor service
[FIX] Restored proper busybox binary
[NEW] New patches on kernel from December update from Archos git
[NEW] Full iptables support (with NAT, conntrack etc) - so everything is now possible (redirect, proxies etc)
[NEW] Full kernel timing for power consumption monitoring
[NEW] Recompiled WiFi? and HDMI drivers
[NEW] Added python 2.7, iotop (for watching i/o operations), PowerTOP (for power consumption monitoring - but it's not as useful as on x86)
[NEW] Added ntfs-3g support - full read/write support for NTFS file systems (need to be used manually, vold does not use it)
[CHANGE] Added UrukDroid? Rescue Menu - Repair submenu with disabling overclocking (for those who made their device unbootable with overclocking) and Dalvik cache cleaner
[NEW] New feature in cpugovernor script (genconf, current)
[CHANGE] New features in update subsystem
scripts now tries to keep /data/.tmp directory cleaner,
for those with disk shortage /data/.tmp can be now symlink to directory on sdcard
updater now checks if you have enough free space in /data/.tmp before it begin installation
update process now can be during bootup (better one) if you have enough free space on rootfs, or on running system (not so nice - this is default behavior until UD 1.6 release)
[CHANGE] restoring backup in Rescue Menu now erases partition before restore (until now it was just overwriting)
[FIX] added (again ) xbox pad kernel support (was missed out in new kernel compilation)
[FIX] fixes scp/sftp-server (on some configuration refused to start child processes)
UrukDroid 1.5 (16.0.2011) Manamana!
[CHANGE] Since UrukDroid? 1.1 (both beta1/2/3 and release candidate 1/2/3) had stability and compatibility issues - that I was unable to trace down (too many changes on changes etc.) - I've decided to implement all stuff from beginning on fresh OS. Since all "reverse engineering" stuff was already made and I already have required knowledge - It should be the fastest method. So entire system is cleaned up, updated to latest binaries - and so far looks good . That's why I've bumped version to 1.5 - just to make it a bit more visible it's not a straight continuation of 1.0/1.1.
[FIX] No more "soft reboots" (system reloaded it's graphics UI part)
[FIX] No more turning off WiFi issue (but it happens that WiFi can't pop in after full reboot - another reboot is required)
[FIX] CIFS startup on boot (Issue 57)
[CHANGE] Update process should be now more chatty and report more errors
[CHANGE] Reverted back WPA service (which enable UrukDroid? WPA supplicant with AdHoc? support) - since some people reported problems with adding new networks with Uruk version of WPA supplicant.
[CHANGE] Merged changes from Archos 2.3.28 OS
[NEW] New wpa_supplicant - hopefully with all features and without most of known problems (sometimes it still refuses to start)
[CHANGE] Updated modules and kernel
[FIX] Fix camera support for A43
[CHANGE] Merged changes from Archos 2.3.26 OS
[CHANGE] Redesigned services to output more reliable status
[FIX] Mediascanner fixes (did not rescan data sometimes)
[NEW] Introduced in 1.0 "Rescue Menu" now fully functional (RM)
[NEW] RescueMenu now have Alternative OS? boot feature
[NEW] RescueMenu now have "bare metal" backup/restore functionality
[NEW] Update process will now communicate with user with help of UrukConfig
[NEW] Enabled cgroups
[FIX] "Moved" boot image on A101
[FIX] 3Gmodem_init.sh fixes
[NEW] You can dissable boot from SDCard by naming any of it's partition "noboot" ('[email protected]:/root# e2label /dev/block/mmcblk2p1 noboot')
[NEW] patch (by Sibere) increasing USB current in Host mode
[NEW] New default apps in UrukDroid 1.5: WiFi Manager, FileExpert, QuickPic, Opera browser
UrukDroid 1.0 (30.04.2011)
[FIX] sshfs missing files fix
[FIX] EasyInstall: changed datafs max size from 2GB to 1.95GB (for market to work), fixed partition sizes for A101 16GB when doing internal install with resize, fixed installation for A70H devices
[NEW] small script to copy UrukDroid files from SDCard (external) to Internall (copy_from_sd_to_internal.sh)
[CHANGE] Changed behaviour of dvb service (device configuration)
[FIX] Added some missing modules for DVB support
[CHANGE] New kernel modules for more dvb devices (but it requires manual loading and testing)
[NEW] rsync tool
[CHANGE] swap service now can work on swap partition (or like before on swap file), also after mounting sdcard ext4 partition
[NEW] Ad-Hoc WiFi connection support by default (networks are visible with "*" on beginning of it's SSID)
[CHANGE] Some new progress indicators during install/upgrade
[NEW] Simple Animation during late phase of bootup
[NEW] New service: cifs (to load cifs modules)
[NEW] Added cgroups kernel setting
[NEW] Moved some modules dependencies (cifs,ntfs,dvb) to /etc/modprobe.d
UrukDroid 0.7 (28.02.2011) you're damn right it's a gift!!
[NEW] NFSv4 client support
[NEW] FS-Cache (cachefilesd) support for NFS (local disk cache for NFS files)
[NEW] sshfs support
[FIX] OpenVPN fix - thanks to nenadr
[FIX] PPtP fix - thanks to nenadr
[NEW] vpnc tool for using Cisco VPN connections
[NEW] vpnc UrukDroid service
[CHANGE] Updated to libc6 2.11 (and all binaries recompiled/changed because of it - big change)
[NEW] new gnu tools: nmap
[NEW] EasyInstall now allows installing UrukDroid on internal (mmcblk1) storage in A70 and A101
[NEW] Integrated 3G USB modem and RNDIS USB tethering service by nenadr
[CHANGE] New iobench.sh (with new bonnie++ test)
[CHANGE] Changed device fingerprint to work better with google market (enable download some missing apps)
[CHANGE] Merged Archos 2.1.8 firmware changes
[CHANGE] Changed DVB subsystem support and kernel/modules dependencies to work with new v4l2 modules (it will brake compatibility with most other kernels probably)
[FIX] Changes it UrukUpdate mechanism to work every time when file is moved to "/data/UrukUpdate"
[NEW] Added required modules and iptables service configuration for DroidWall (firewall) application
[NEW] sudo subsystem for launching properly some root tasks
UrukDroid 0.6 (11.02.2011) Eye of the Uruk... in new logo
[CHANGE] Merged changes from Archos firmware 2.1.2/2.1.3/2.1.4
[CHANGE] DVB support with LiveTV.apk from chulri (for selected cards, there are more modules then listed in /etc/uruk.conf/dvb - but it requires to do some experiment and report it back)
[CHANGE] Changed Uruk service to work better with new UrukConfig
[NEW] New services: openvpn, mediascanner
[NEW] IO Benchmark tool: iobench.sh
[NEW] Possibility to turn off mediascanner and use it on demand only
[FIX] Fixed mount_sdcard.sh script to work with 2.1.2 ext3 partitions
[NEW] Updated boot sequence with progress during upgrade/install
[NEW] You can hide soft buttons (Archos buttons) with UrukConfig
[NEW] Easy Install method - no need to know anything about Linux - just plug and wait...
[NEW] Kernel modules for 3g dongle
UrukDroid 0.5 (27.01.2011) Tom Bombadil... in red
[NEW] CompCache (aka ramzswap) support
[NEW] New CPU governor - interactive. Ported from XDA CyanogenMOD
[NEW] DVB: applied patches by chulri, Siano SMS1XXX USB support
[NEW] DVB: modules from outside kernel tree
[NEW] Some more GNU tools: gzip utils, zip utils, unzip utils, nc (NetCut for DVB streaming)
[CHANGE] New services model - so they can be easily run/configured with help of UI
[NEW] New kernel modules: usbnet, lzo
[NEW] Mediascanner modification - it should has much, much smaller impact on system performance
[NEW] sqlite3 (3.5.9) installed, for easy database file manipulation
[NEW] after restart of UrukDroid it will boot once again to Uruk without need of pressing any buttons, to boot on stock OS please use boot menu
[FIX] mount_sdcard.sh fixed so it will mount first ext4 partition on sdcard if exist, and will not interfere with Vold if its vfat
[CHANGE] New update/upgrade/flash model - everything done on UrukDroid - no boot menu required
[NEW] New application to configure UrukDroid - UrukConfig.apk. Installed with this release. Can be uninstalled in default way.
[FIX] Fixed corrupted logo in A101
[NEW] Unified kernel for UrukDroid on SDCard and internal storage (A70S/A101)
[CHANGE] Services ENABLED with this release: CpuGovernor, CompCache
UrukDroid 0.4.2 (21.01.2011)
Just extracted as a separate update file GoogleMarket
UrukDroid 0.4.1 (15.01.2011) Myyy preciousssss...
Some more tools like: bc, proc utils, vim, tcpdump, bzip2, tar etc.
Android apps (Market, Maps, Talk, Calendar, Contact, Feedback, Locator, Updater) by default
Samba (3.2.5) support for sharing /mnt/storage (internal and sdcard storage) from Archos
Dropbear SSH server
Backported modprobe, depmod etc. tools for modules management
WiFI driver recompiled, WiFi HW firmware update (from 6.1.0.0.335 to 6.1.5.44.7)
Initial DVB-T support (Afatech AF9005, Afatech AF9015, DiBcom DiB0700, Terratec CinergyT2/qanu)
Bootlogo with progress steps
Cleanups of initramfs and rootfs
EXT4 drivers backported from 2.6.30 - some mount changes (to prevent config files corruption)
Initial A70H support
SDCard/HD layout changed
Autoupgrade service and installation helper
ADB fixes
Removed two apps. TelephonyProvider.apk, Phone.apk
Since 0.4 all services are DISABLED by default, to enable it edit proper config file in /etc/uruk.conf/
UrukDroid 0.3 (9.01.2011) Rise my Uruk... not yet Hai
iptables, ntfs support
some more USB modules: usbserial, pl2303
fixed bluetooth problem (not working in Uruk 0.2)
automounting improvements (much more bulletproof)
new configuration files (/etc/uruk.conf/) to enable/disable features
new Uruk services (/etc/uruk.d/)
some more GNU utils openssh-client, coreutils
USB charging enabled (NOT tested!!!) - It would required much more power then standard USB in PC can give, use USB wall/car charges or double/triple USB cables
UrukDroid 0.2 (5.01.2011) Go GNU release
"smart" automounting script (that will mount ext4/vfat third partition from sdcard in RIGHT place, AFTER internal storage is mount)
plenty of useful GNU tools: whole e2fstools (mkfs, fsck for ext2/ext3/ext4), parted (for partition resize, format etc.), vfat tools, new toolbox, mtr, top, strace, bash - and much more (look in /usr/local/bin and /usr/local/sbin)
swap memory ON by default (50MIB file /swap01.file)
required compiled libraries libparted, libncurses, libe2fs... etc. (look in /usr/local/lib)
new text editor in text mode: nano (my favourite)
some init.rc cleanups
kernel changes (mostly toward console output)
fixed small (but problematic) misconfiguration in Archos (yep original one) Android in linking /etc/mtab
UrukDroid 0.1 (30.12.2010) Initial "release"
recompiled kernel with ext4, nfs4, fb console
added su and superuser.apk
bootup changes (to make it work)
Features planed in next releases:
backup scripts
proxy settings
CynanogenMOD parts backported
OC/UC kernel be default
FAQ or Tips & Tricks
More information you can find in seperate thread on this forum - FAQ + Question/Awnsers
How to upgrade from previous releases
To upgrade from 0.5 you should download special upgrade file (UrukDroid-0.6-upgrade.tbz2) from first post. You need to place this file in directory "/data/UrukUpdate".
First method:
Put it on your internal storage by any means - this is /mnt/storage (also visible as /sdcard/). Then use file manager (like Astro or RooteExplorer - not build in one) or do as follow in terminal (or over ssh)
Code:
su
cd /sdcard/
mv UrukDroid-0.6-upgrade.tbz2 /data/UrukUpdate/
Second method:
Use UrukConfig to enable SSHD (if you don't have it started already), and use any SCP/SSH client (like WinSCP, or plain scp on Linux) to copy file (default username is "root", password is "UrukDroid") to "/data/UrukUpdate".
In both cases upgrade will start automatically; alter kernel, initramfs and when finished, device will reboot itself.
How to enable/disable and configure UrukDroid services?
UrukDroid services are configured by text files, that can be found in /etc/uruk.conf/ directory. You can use file manager like RootExplorer or Terminal to edit them, but most convinient way is to use SSHD service and some ssh client (for example putty).
You can also use UrukConfig application - build in since 0.5 release. After you do some changes, restart service (/etc/uruk.d/service_name stop/start) or simply reboot Archos. Since 0.5, by default only CompCache and CPUGovernor are enabled.
Currently available services
samba - it's SMBD server allowing mounting your Archos storage directory on your PC. Default user is "storage" and password "UrukDroid"
sshd - SSH server allows you to connect to your Archos with any ssh client, work on terminal. It also allows to copy files with scp/sft. Default user is "root", password "UrukDroid"
swap - this service enable swap memory. It can make Archos a bit less responsive but memory manager won't kill application so quickly (co you can use WWW browser, email an communicator simultaneously - for example of course)
iptables - this pseudo service will load necessary modules to use iptables (firewall) features
ntfs - if you plan to connect NTFS formatted devices to your Archos - enable this service
dvb - this service load necessary modules to watch TV on your Archos. This service requires configuration from your side - it won't work "as is". Please read and edit config file (/etc/uruk.conf/dvb)
compcache - Start/stop CompCache swap memory service. Compcache is a compressed part of memory, where less used object reside. Usual compression ratio is 70%
cpugovernor - Changes default CPU governor and it's parameters. Governor decides how to scale CPU frequency. Since 0.5 there is new "interactive" governor.
openvpn - It's an implementation of popular free VPN service for Uruk. It will act like the one used in Archos stock config with difference it will work all the time - whenever you go, and you have full flexibility of configuration. Config file resides in /etc/openvpn/archos.conf.
VPNC - It's open implementation of Cisco VPN service. You should edit /etc/vpnc/archos.conf file.
NFS4 - NFS v4 client service allows you to mount remote file storage with use of NFS (much faster then SMB for example). You can also enable use of cachefilesd sub-service - that will cache locally, files transferred with NFS (for smooth playback of movies for example)
How to remove some default apps?
App started at the boot time are stored in /system/app, I've already removed some of them by moving it to /system/app.old/ - but you can do it by your own - but remember - some of them are actually required to run system
Some filesystems benchmarks (that's the reason why I wanted ext4 so badly)
Write tests (I've testes different filesystem and partition sizes)...
Tests on Archos:
internal 8GB
0,71Mb/s ext3,ordered,noatime
5,45Mb/s fat32
Lexar 16GB
2,63MB/s ext3,ordered
6,25MB/s ext4,ordered
Test on computer (the same lexar card)
2.93Mb/s 1GB,ext3,noatime
2.78Mb/s 1GB,ext3
3.04Mb/s 1GB,ext2
8.62Mb/s 1GB,vfat
7.61Mb/s 1GB,btrfs
7.87Mb/s 1GB,ext4
7.87Mb/s 16GB,ext4
Card is 16GB SDHC Lexar class 6 only - so this toshiba nand inside is not state of the art either :/
How to roughly check your filesystem write speed
Go to directory where you can write and were is more then 100MiB of free space and do the line. It will sync devices (flush all write caches), write 100MiB file filled with zeros, and fush caches once again to measure real write speed without buffers. Then easy math... and my laptop disk has write speed 16,66MiB/s
Code:
[email protected]:/tmp$ sync; date; dd if=/dev/zero of=test.file bs=1M count=100 2>/dev/null; sync; date
Wed Jan 5 19:02:28 CET 2011
Wed Jan 5 19:02:34 CET 2011
[email protected]:/tmp$ bc -q
scale=4
100/(34-28)
16.6666
quit
UrukDroid configuration system
I've created (or recreated, since Google threw away existing Sytem V and other solutions) something that works like rc/init.d system. It's old fashion, but for only few services will do it's job.
There are few location to remember:
/system/etc/uruk.d/ - directory with services
/system/etc/uruk.conf/ - directory with configuration files
/system/etc/init.d/ - symlinks Sxxserice/Kxxservice (like S01swap) to be run during startup process
Proper path is /system/etc/ but it's symlinked on every Archos to /etc - so you can also work on /etc/uruk.d, /etc/uruk.conf etc.
To enable iptables support (load proper module) it's enought to edit /system/etc/uruk.conf/iptables
To change swap memory settings edit /system/etc/uruk.conf/swap
How to mount ext4 under Windows?
There is project called "ext2read" that claims to work with ext4 also (I've only tested it with ext2 long time ago - it worked) http://sourceforge.net/projects/ext2read/ - please write some commends if you use it.
What is current directory/disk layout?
/ -> SDCard first partition (512M) - for root filesystem
/data -> SDCard second partition (1GB) - for installed apps
/mnt/storage -> internal 6GB partition - for data used by installed apps
/mnt/storage/sdcard -> SDCard third partition - anything you want, nothing by default
/mnt/sdcard2 - proposed mount point for other volumes, not used by default
And there is something called symbolic links (symlinks) - witch is kind of Win shortcut used on UN*X extensively.
/sdcard -> /mnt/storage
/storage -> /mnt/storage
/mnt/sdcard -> /mnt/storage
So you can enter /sdcard - and you are be using files from /mnt/storage. You can also create symblinks by yourself
Code:
ln -s /source destinations
How to gather data report from UrukDroid
Best way is to use SSH. For this, please start "sshd" service on UrukDroid by using UrukConfig application or by editing /etc/uruk.conf/sshd file.
First start will take one minute or so - since sshd has to generate unique encryption keys.
If you use Windows download putty.exe (ssh client) and run it. Write your Archos IP (it has to be visible in network) and connect.
Use
Login: root
Password: UrukDroid
Click to expand...
Click to collapse
Now you can write Linux commands and cut/paste results for help/debug purpose.
Thanks!
I think you talked me into it! I'll play with it tomorrow.
I've found this on Nook Color thread http://forum.xda-developers.com/showthread.php?t=888216
Can someone test is it worth to do on Archos? I think we don't need phone service running in background. Ill try this tomorrow when i get back to home but maybe someone can test earlier?
sorry for asking,but what is the point in doing step 3,i mean what does it actually do?
This is backup of install instruction, leaving more space for custom approach. Instruction in first post is now much simpler with less 'if/or'.
Material for this thread came from discussion here. So please be kind read also this thread before getting to work
This is mini how-to boot modified Archos Android from SD card, using SDE. It's base on 2.0.71.
Since this Android mod/distribution required some name - let it be Uruk-Droid
Why bother:
ext4 (much faster than ext3, can store files >4GB comparing to FAT32)
full r/w access to every part of system
root (su + superuser.apk) out of the box
possibility to remove some google/Archos apps (already done partly)
swap memory when you need it
no 300MB limit for apps (and no faulty app2sd required)
you can have SD card Class 8/10 - and that's much faster storage than internal flash (inside is something equal class 6 or 4)
Warning
Be aware that this modification requires SDE and probably some Linux knowledge.
By doing described below steps you probably can't brick your Archos - but do it on your own risk.
Root access on your devices makes it less secure form malicious software (user more head - less fingers )
Known problems:
Android automounter (vold) does not recognize EXT4 in stock firmware - so it will claim SD card is damaged (it's just a message) (FIXED)
Before you start:
Read about SDE on forum
Install some terminal emulator from Market (eg. "Android Terminal Emulator")
You should have 2.0.71 already installed (I'm not sure if it's required but only with that configuration tested)
All operations described here, done on Linux or Android should be done from root user (you can switch to that user in terminal by typing "su" or "sudo su" command)
If you don't have Linux - find any recent Rescue CD, Live CD or Virtual disk (VirtualBox or VMware) - distributions does not matter
SD card partition design
First of all, preferably buy card class 6+. So it won't be slower than internal storage
I'm currently using 3 partitions
0,5GB / (rootfs)
1GB /data
rest /mnt/storage/sdcard/
but You can create one big partition instead - I've made my configuration because of easiness to backup and upgrade (rootfs is easy to upgrade later on, /data has only runtime data and application, rest is for movies etc.) Size of /data partition determines how many apps you can install on your device.
Here it's how it looks on fdisk
Code:
linux-machine:~# fdisk -l /dev/sdb
Disk /dev/sdb: 16.0 GB, 16012804096 bytes
199 heads, 44 sectors/track, 3571 cylinders
Units = cylinders of 8756 * 512 = 4483072 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 1 121 529716 83 Linux
/dev/sdb2 122 362 1055098 83 Linux
/dev/sdb3 363 3571 14049002 83 Linux
Step one
Create at least one primary partition on SD card with fdisk, gparted, parted or any other partitioning tool. Assuming your SDCARD is visible as /dev/sdb (on Linux box - check "dmesg").
Code:
su (go root)
fdisk /dev/sdb
fdisk options (it's interactive):
p (print existing partitions)
d n (delete partition by it's number 1,2,3 etc)
n (create partition, you will be asked about type (primary, secondary - go primary), number (give first available), start sector (just enter will set first possible), size (you can give it as +1M, +2G etc)
w (write all changes, until you give this command no changes are made on disk physically)
Format partitions as EXT4 - but without huge_file option (it won't work with this feature since it requires special kernel option that brakes compatibility with existing modules).
Code:
su (go root)
mkfs.ext4 -O ^huge_file /dev/sdb1
If you created more partitions - do those steps for everyone.
Code:
mkfs.ext4 -O ^huge_file /dev/sdb2
mkfs.ext4 -O ^huge_file /dev/sdb3
Kind of "session log" for this steps you can find in this post.
Step two
Extract content of rootfs.tar.gz onto first partition on SD card (it HAS to be first one). Do it from root account on Linux/UNI*X box - or you won't transfer all permissions properly (mainly +s on su/superuser.apk).
assuming your SD Card is visible under Linux as /dev/sdb (you can check it by typing "dmesg" after you connect it)
open terminal/shell - go root: su, or sudo su
create mount point: mkdir /tmp/sdcard
mount it (if it's not mounted already) for example: mount /dev/sdb1 /tmp/sdcard
go to /tmp/sdcard directory: cd /tmp/sdcard
extract rootfs: tar -zxf /path_to_file/rootfs.tar.gz
exit directory: cd
umount your card: umount /tmp/sdcard
Flash initramfs.gz and zImage from SDE boot menu:
reboot Archos70, hold up or down volume key until you see Recovery menu,
choose "Recovery System"->"Developer Edition Menu"->"Flash Kernel and Initramfs",
connect Archos to PC and copy initramfs.gz and zImage to device
Reboot and hold up or down volume, choose "Developer Edition".
You should see all yours apps etc. - it should look like your Archos , but with su/superuser.apk etc. (check it on terminal emulator by typing "su" and enter).
Before go to next step make sure you have booted to SDE system AND it has root access! (check "su" in terminal, run root explorer or titanium backup)
Step three
It's kind of optional - since you have already working system - but it's not fun yet
Now you should copy /data files onto SD card. Use terminal emulator (from market can be "Android Terminal Emulator") or sshd (QuickSSHd and log into your tablet) and do:
If you have ONE partition
Code:
su
cp -rp /data/* /data.new/
If two or more
Code:
su
mount -t ext4 /dev/block/mmcblk2p2 /data.new
cp -rp /data/* /data.new/
umount /data.new/
Poweroff device.
Step four
Put card into computer and:
one partion
remove /data
rename /data.new to /data
On Linux it may look like this:
Code:
su (or sometimes "sudo su")
mkdir /tmp/sdcard
mount /dev/sdb1 /tmp/sdcard
cd /tmp/sdcard
rm -rf data
mv data.new data
edit /init.rc (it's /init.rc on Android - on Linux box it's going to be something like /tmp/sdcard/init.rc) - use any editor to modify file - do it as a root!
Code:
su
vi /tmp/sdcard/init.rc (edit the file)
umount /tmp/sdcard/
What to edit:
Code:
# Comment this
# mount ext3 /dev/block/mmcblk0p4 /data noatime nosuid
# Uncomment this
# mount ext4 /dev/block/mmcblk2p2 /data noatime
mount ext3 /dev/block/mmcblk0p4 /data.old noatime nosuid
two or more partitions
edit /init.rc (it's /init.rc on Android - on Linux box it's going to be something like /tmp/sdcard/init.rc) - use any editor to modify file - do it as a root!
Code:
su (or sometimes "sudo su")
mkdir /tmp/sdcard
mount /dev/sdb1 /tmp/sdcard
cd /tmp/sdcard
vi init.rc (edit file)
umount /tmp/sdcard
What to edit:
Code:
# Comment this
# mount ext3 /dev/block/mmcblk0p4 /data noatime nosuid
# Uncomment this
mount ext4 /dev/block/mmcblk2p2 /data noatime
mount ext3 /dev/block/mmcblk0p4 /data.old noatime nosuid
If you have third partition on SDCARD, whether it's EXT4 (recommended) or FAT32 it should by automounted since 0.2 version.
Reboot - it should work
End
Stuff you can do later:
Vold - automount daemon on android is quit.... crappy - to let go message about "sd card damaged" edit /etc/vold.fstab and hash the line "dev_mount_lun volume_sdcard /mnt/storage/sdcard...."
Other partitions - if, by any reason, you have more partition on SD card (more then 3) you can also mount it putting in init.rc (there are some potential issues with vold to be solved)
for ext4
Code:
mount ext4 /dev/block/mmcblk2p5 /mnt/sdcard2 noatime nosuid
For fat32 partition preferably tweak with Vold config (/etc/vold.fstab) - or add something like this (in init.rc)
Code:
mount vfat /dev/block/mmcblk2p3 /mnt/sdcard2 uid=1000 gid=1015 fmask=0000 dmask=0000
Files (UrukDroid-0.3):
Megaupload.com
initramfs.cpio.gz
zImage
rootfs.tar.gz
Dropbox.com (there can be server error because of download limit)
http://dl.dropbox.com/u/1017593/ArchosGEN8/UrukDroid-0.3/rootfs.tar.gz
http://dl.dropbox.com/u/1017593/ArchosGEN8/UrukDroid-0.3/initramfs.cpio.gz
http://dl.dropbox.com/u/1017593/ArchosGEN8/UrukDroid-0.3/zImage
Nm you said it's faster, interesting... I may test that out.
IMHO you should point out that it is a great security risk for having access to root without any password.
BTW this comment is not meant to insult you in anyway, but I think it is only fair to people that will use it and to cover your own ass.
Maurice
Does this require a clean system to do the SDE Root? what happens to everything already installed etc.
MoonPhantasm said:
Nm you said it's faster, interesting... I may test that out.
Click to expand...
Click to collapse
There was already link to my write speed tests (now I've pasted it to second post) - read speed is about the same. In quadrant I have something about ~2300 (one of quadrants test is I/O benchmark) - but that's not my goal - so I don't care much about that kind of speed.
divx118 said:
IMHO you should point out that it is a great security risk for having access to root without any password.
BTW this comment is not meant to insult you in anyway, but I think it is only fair to people that will use it and to cover your own ass.
Click to expand...
Click to collapse
Of course your are right - but that's kind of obvious, and that's the reason why superuser.apk requires to specify what process can gain root access (I know it's not strong security - but better something than nothing)
Is there any way to do this on the a32, or can will there be a solution for the 32.
I had SDE installed before, but I used the uninstall developer edition option in the boot menu. Now, regardless of if I use the .aos file from archos that has SDE, whenever I reboot holding a volume button, I get to a menu that says "Archos A101IT Recovery", and "Would you like to recover your system?" with the following options:
No
Update Firmware
Repair System
Format System
I select update firmware, and all I get is an update failed error.
I don't know what to do. I have a basic linux knowledge, so I have my sd card properly formatted, without the huge file option. I've extracted the contents of rootfs.tar.gz to the first partition.
Any ideas on what to do?
$aur0n said:
I don't have that problem since I use Linux everywhere
My mmcblk2p3 is also EXT4 partition (since fat 32 has 4/2gb file size limitation it's only place where I can put bigger files - mainly movies. It's one of ther reasons why ext4 is good for the task).
To mount (vfat or ext4) during but of Archos put in init.rc
Code:
mount ext4 /dev/block/mmcblk2p3 /mnt/storage/sdcard noatime nosuid
or
mount vfat /dev/block/mmcblk2p3 /mnt/storage/sdcard
just after mount of /data.old for example..
/mnt/storage/sdcard is the place where automounter would normally mount this device.
Click to expand...
Click to collapse
I did try to add it to init.rc, but it wouldn't mount.
Running "busybox mount -t vfat /dev/block/mmcblk2p3 /mnt/storage/sdcard" after boot seems to work however.
Is /mnt/storage mounted yet at that point? It seems to be separately mounted ("mount" shows /dev/block/vold/179:9 mounted on /mnt/storage, but I can't find any line related to that in init.rc)
Since "Preparing internal storage" appears after boot, I assume the SD card has to be mounted after that (unless I mount it somewhere else, which would break compatibility with some apps)
Actually, I'd prefer if the SD card was mounted on /mnt/storage, and the internal storage on /mnt/storage/internal, is there a way to do that?
Edit: Ah, I checked that /etc/vold.fstab file. It seems to be what I need to edit to auto mount the SD card, but I'm not sure what I need to edit.
The line currently reads:
dev_mount_lun volume_sdcard /mnt/storage/sdcard auto /devices/platform/usb_mass_storage/lun1 /class/block/mmcblk2
"auto" seems to be the partition number, I tried to change this to different values as well as changing mmcblk2 to mmcblk2p3, but they result in the same SD card damaged message. Is this a no-go and just won't work or am I doing something wrong? Either way, it seems like it's the only way to mount the SD card at boot if I want it mounted to /mnt/storage/sdcard.
Edit 2:
Adding these 2 lines to init.rc and commenting out the equivalent lines in /etc/vold.fstab seems to work:
mount vfat /dev/block/mmcblk2p3 /mnt/storage
mount vfat /dev/block/mmcblk1p1 /mnt/storage/internal
Now I have the SD card mounted on /sdcard
However, the settings won't show the space information now, so I have to connect it to the PC to check free space. Is there a better way to do it?
Jdbye said:
I did try to add it to init.rc, but it wouldn't mount.
Running "busybox mount -t vfat /dev/block/mmcblk2p3 /mnt/storage/sdcard" after boot seems to work however.
Is /mnt/storage mounted yet at that point? It seems to be separately mounted
Click to expand...
Click to collapse
No, this mount point (/mnt/storage/sdcard) is not ready yet at this point - that's why I've changed it to /mnt/sdcard2 in howto. It's not good solutions (since probably some tools won't find media - like movie player) - but the only one for now. Vold is crappy, and even so it should mount _first_ usable partition (with auto option) but it does not want to do that. I can't check it, since I don't have vfat on sdcard, but probably the only solution is to do separate script/service with delayed mount - that's what I'm going to do for now, later on (in next release).
Q: However, the settings won't show the space information now, so I have to connect it to the PC to check free space. Is there a better way to do it?
A: (kind of joke) - user "df -h" in terminal, probably some more smart tools with gui are also able to show space used by "other" devices.
hurrpancakes said:
Any ideas on what to do?
Click to expand...
Click to collapse
I guess it's some Archos SDE bug and you should report it (I thing that after uninstall of SDE and second install you should see developer menu back - if not,
it's error or faulty "watermarking" at work)
jab12 said:
Is there any way to do this on the a32, or can will there be a solution for the 32.
Click to expand...
Click to collapse
My guess - it may also work for you. All gen8 devices have the same kernel and system - so give it a try.
xShadoWxDrifTx said:
Does this require a clean system to do the SDE Root? what happens to everything already installed etc.
Click to expand...
Click to collapse
Everything that is installed on INTERNAL 8GB storage is untouch. So even when sde fails to boot, you can go back to original Archos Android and work on that.
When you follow my instr. you should see second Android with all yours application installed but on ext4 with root etc. etc.
$aur0n said:
I guess it's some Archos SDE bug and you should report it (I thing that after uninstall of SDE and second install you should see developer menu back - if not,
it's error or faulty "watermarking" at work)
Click to expand...
Click to collapse
I think the error may lie in the fact that I have to access my sd card by mounting it through my a101. Tomorrow (or later today, rather) I will get a sd card reader so I won't have to rely on using the tablet.
Hi, thanks for howto.
Can we keep the superuser mode explained in this topic http://forum.xda-developers.com/showthread.php?t=880321&page=13 And use your method (in case i forgot m'y sd card And need root access)
Hi all--
I'm sorry in advance for the confusion I might have. I'm an extreme noob when it comes to this platform, and I'm not that great when it comes to Windows either...
Basically I was surprised to see that the external SD Card is used so much by CGM7 and is required for so much. For instance, all downloads HAVE to go to the external card. In addition: I don't know if this has anything to do with operating system, but all saved documents from basically any productivity program seems to save here by default as well.
So here are my questions:
Is there anyway to alter where things are downloaded to by the built in browser? I'd prefer that internal memory (EMMC, right?) be used... Does the default location for app installation handle this?
What exactly uses the external card by default?
Using the built-in file browser, why does it not want me to move items from internal to external storage? Why can I only copy and paste them?
I thought CWM was suppose to look on the external SD card when I use "Install zip from SD card." Instead, it looks at whatever is marked as the internal SD card. Why's that?
Thanks for your help and suggestions. I am using a gTablet, and I couldn't find a more appropriate forum for this question...
scyld said:
So here are my questions:
1. Is there anyway to alter where things are downloaded to by the built in browser? I'd prefer that internal memory (EMMC, right?) be used.
Click to expand...
Click to collapse
There is a thread just for this at the forum.cyanogenmod.com and also here:
http://forum.xda-developers.com/showthread.php?t=1028305
The last link in the first post does what you want. However, read my warnings if you do switch SD cards using that method:
http://forum.xda-developers.com/showpost.php?p=13569415&postcount=26
2. What exactly uses the external card by default?
Click to expand...
Click to collapse
Is the question what will use the external SD card, or what is using the external SD card. If it is the latter, Settings > Applications > Manage applications & Storage use has that info.
3. Using the built-in file browser, why does it not want me to move items from internal to external storage? Why can I only copy and paste them?
Click to expand...
Click to collapse
You can move them in the default File Manager. Keep your finger on the filename until a menu pops up. There is a "Move" choice.
4. I thought CWM was suppose to look on the external SD card when I use "Install zip from SD card." Instead, it looks at whatever is marked as the internal SD card. Why's that?
Click to expand...
Click to collapse
I will have to look into this, but I guess what SD card it uses depends on whether you have an external SD card in the slot or not.
The version of CWM I use, which is Clockworkmod Recovery v2.5.1.3, will use the external SD card by default when installing stuff or when making backups and when restoring, if it detects an external SD card. If one is not detected, then it will use the internal SD card instead for all its actions. See the blog post on the front page of http://bekit.net
rajeevvp said:
There is a thread just for this at the forum.cyanogenmod.com and also here:
http://forum.xda-developers.com/showthread.php?t=1028305
The last link in the first post does what you want. However, read my warnings if you do switch SD cards using that method:
http://forum.xda-developers.com/showpost.php?p=13569415&postcount=26
Click to expand...
Click to collapse
Yep, that's exactly the file I flashed in order to switch what SD card was labelled as "EMMC." Hmm, I suppose I could just move all my apps from the phone to "the external SD card"...
Is the question what will use the external SD card, or what is using the external SD card. If it is the latter, Settings > Applications > Manage applications & Storage use has that info.
Click to expand...
Click to collapse
Thanks.
You can move them in the default File Manager. Keep your finger on the filename until a menu pops up. There is a "Move" choice.
Click to expand...
Click to collapse
Pardon, I should have explained: when I do use the default File Manager's "Move" command, I get the message "Could Not Move File" whenever I try to move the file from one storage to the other.
I just downloaded Root Explorer, and it allows me to do this. However, I'm a little worried that it has Super User status, making me worried that I might accidentally do something bad with my clumsy fingers. But I suppose that's why I have CWM backing up my tablet.
Speaking of CWM...
I will have to look into this, but I guess what SD card it uses depends on whether you have an external SD card in the slot or not.
The version of CWM I use, which is Clockworkmod Recovery v2.5.1.3, will use the external SD card by default when installing stuff or when making backups and when restoring, if it detects an external SD card. If one is not detected, then it will use the internal SD card instead for all its actions. See the blog post on the front page of http://bekit.net
Click to expand...
Click to collapse
Interesting, thanks. I unfortunately do not remember which version of CWM I use, but I think it is not this one. I should check it out.
scyld said:
Yep, that's exactly the file I flashed in order to switch what SD card was labelled as "EMMC." Hmm, I suppose I could just move all my apps from the phone to "the external SD card"...
Click to expand...
Click to collapse
Here's my /system/etc/vold.fstab in its entirely. With this, my tablet uses the internal SD card as the default for storage.
Code:
## Vold 2.0 NVIDIA Harmony fstab
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
#dev_mount sdcard /mnt/sdcard auto /devices/platform/tegra-sdhci.3/mmc_host/mmc0 /devices/platform/tegra-sdhci.3/mmc_host/mmc1
# dev_mount sdcard /mnt/sdcard auto /devices/platform/tegra-sdhci.2/mmc_host/mmc1
# dev_mount emmc /mnt/emmc auto /devices/platform/tegra-sdhci.3/mmc_host/mmc2
dev_mount sdcard /mnt/sdcard auto /devices/platform/tegra-sdhci.3/mmc_host/mmc2
dev_mount emmc /mnt/emmc auto /devices/platform/tegra-sdhci.2/mmc_host/mmc1
dev_mount usbdisk /mnt/usbdisk auto /devices/platform/tegra-ehci
Pardon, I should have explained: when I do use the default File Manager's "Move" command, I get the message "Could Not Move File" whenever I try to move the file from one storage to the other.
I just downloaded Root Explorer, and it allows me to do this.
Click to expand...
Click to collapse
Ah, OK. The reason for the difference is due to the way the move is actually implemented in File Manager and Root Explorer.
I had an idea about why File Manager couldn't move files across filesystems, and to confirm my suspicion I attached strace to a running File Manager:
Code:
$ su
# strace -e rename -p `pidof org.openintents.filemanager`
Process 28466 attached - interrupt to quit
[I]lots of irrelevant output omitted[/I]
rename("/mnt/sdcard/Kernel/Pershoot/lib-2632.40_gb.tar.gz", "/data/local/tmp/lib-2632.40_gb.tar.gz") = -1 EXDEV (Cross-device link)
[I]more irrelevant output omitted[/I]
File Manager calls the rename() system call to move the lib-2632.40_gb.tar.gz file, which, as the spec says, will fail in this case. The program is then supposed to do the move the old-fashioned way if rename() returns an EXDEV error: copy file1 to file2 by reading bytes from file1 and writing bytes into file2; then delete file1 if the copy is successful.
But, File Manager doesn't perform this very basic fallback step. It throws up its hands at the first error and spits out the error message you got. And, it's not just File Manager. The system mv command (if you have it) in /system/bin also exhibits the same dumb behaviour. The busybox mv is more robust. (You should actually report this as a bug to the File Manager people.)
Which brings us to Root Explorer. I got curious about it after the experiment with File Manager. RE handles cross-device moves just fine. What's more, it also moves entire directory trees across devices. Having written directory tree-moving programs before, I know that this is a non-trivial bit of programming. So, I ran strace on Root Explorer to see how it handled things, and the result made me laugh.
Code:
$ su
# strace -f -e execve `pidof com.speedsoftware.rootexplorer`
Process 3602 attached with 12 threads - interrupt to quit
[I]lots of irrelevant output omitted[/I]
10893 execve("/system/xbin/busybox", ["busybox"..., "cp"..., "-pr"..., "/sdcard/Kernel/Pershoot/lib-2632"..., "/data/local/tmp/lib-2632.40_gb.t"...], [/* 19 vars */] <unfinished ...>
10893 <... execve resumed> ) = 0
10914 execve("/system/xbin/rm", ["rm"..., "-r"..., "/sdcard/Kernel/Pershoot/lib-2632"...], [/* 19 vars */] <unfinished ...>
10914 <... execve resumed> ) = 0
[I]more irrelevant output omitted[/I]
Root Explorer is also taking the easy way out: It's actually using busybox to do (almost) all of its work.
I suspected this when I compiled a new version of busybox a few days ago to test out a new compiler toolchain. I moved the newly compiled busybox into /system/xbin without properly testing it first, and discovered that most of the commands died with segfault errors.
I re-uploaded the working version of busybox back onto the tablet in /mnt/sdcard/download, and then went into Root Explorer to move this busybox into /system/xbin, and RE started force closing on every action. Once I had managed to replace busybox through other means, RE started working fine again. At that time, I didn't look at the issue too closely--I thought it was just another example of the random lossage that Android exhibits from time to time. Now I know why.
Instead of moving all applications to SD card with app2sd, I want to move only selected applications.
Because I don't want to move my launcher, soft keyboard and dialer application to SD and make them unavaliable on boot if my SD card has problem or not inserted.
The idea behind is same, linking to SD card's second partition but differs in two ways.
One, instead of linking /data/app folder (that means moving all applications), you can select the applications that you want to move.
Two, it's an application which means has a user interface. You can manage your applications, create or remove links with just few clicks.
It also provides native apps2sd features on Android 2.2 and higher. Plus, it can move any non-protected user apps to SD card (force move), with batch moving capability.
That feature uses Android's standard SD-card installation feature and does not require a second partition. It can break some apps if they are not meant to be moved to the SD card (Such as Widgets).
Features:
- Create and remove link for apk, dex and lib files of the applications you select
- Automatically link newly installed apps
- Move any user apps to SD even though the app does not support moving to SD (for Android 2.2 and higher)
- Shows the apps that support moving to SD with native apps2sd (for Android 2.2 and higher)
- Set the default install location of the apps; auto, internal, or external (for Android 2.2 and higher)
- Batch link, unlink, reinstall, uninstall, "move to SD", "move to phone" functions (multi-select mode)
- Uninstall system applications
- Freeze and un-freeze system and users applications
- Convert system apps into user apps
- Convert user apps into system apps
- Integrate "Updated" system apps into system (ROM)
- Clear data and cache of the application
- Clear all apps cache at once (1-tap cache cleaner without being root)
- List applications, show detailed size information and link status
- Sort and filter applications
- Search applications by name
- Display available space information of internal storage, SD card and SD card 2nd partition
What you need for linking applications:
- root permission
- a second partition on your SD card. You should have two partitions on SD card and both should be primary
The first FAT partition is your standard SD card storage. The second partition is used for application files and can be ext2, ext3, ext4 or FAT32.
ext4 is the latest ext format but several ROMs have issues with it while fewer have issues with ext3 and ext2. FAT works on all ROMs.
I use free "MiniTool Partition Wizard Home Edition" (windows application) for this.
You can create the second partition without repartitioning, formatting or deleting your existing partition with this tool. Connect your SD card to PC with a card reader or phone itself and make it visible as a drive. Open Minitool select this drive and resize down FAT partition, you will see an unallocated area at the end of the card. Create ext2, ext3 or FAT32 partition in that area (create as primary, not logical), click apply. Unplug from the PC and reboot the phone. (To be on the safe side backup your SD card data before starting)[/LIST]- That's all. Just install Link2SD, it will do all necessary. No need to copy files or run scripts.*
* Some phones lack the ext2, ext3 or ext4 file system support and you may get mount errors like "no such device", "invalid argument". These phones need a matching ext2.ko or ext3.ko modules and even some additional modules to be able to mount.
Using FAT32 on the second partition will eleminate such problems, because FAT32 is supported on all phones.
How it works:
Link2SD mounts the second partition of your SD card as /data/sdext2 and makes OS mounts it at boot time.
When you select an application and press "Create Link" button you can select which files of the application will be linked and moved to SD card. Apk, dex and lib files can be moved and you can select all three or any two of three or even only one of them.
Depending on what you select, Link2SD moves apk file, dalvik-cache (.dex) file and lib files (.so) to SD card's second partition and creates symbolic links in original directories.
Note: On Android 1.6 and 2.1, shortcut and the widget of the app should be re-added to homescreen if you move the apk file.
Can I remove the links and put application files back to phone?
Yes, just click on application that is linked and press "Remove Link" button. You can select which files of the application will be unlinked and moved back to internal storage.
Then, Link2SD removes the symbolic links and moves the files you selected to original directories.
What happens if I uninstall or update a linked application?
If you uninstall a linked application apk, dex and lib files will be automatically deleted from the SD card by Link2SD.
If you update a linked application new apk, dex and lib files will be placed in the internal memory at first and then they will be automatically relinked by Link2SD in the background.
You don't have to manually relink after updating applications.
Note: Since the app is linked again, On Android 1.6 and 2.1, shortcut and the widget of the app should be re-added to homescreen if the apk file is linked
Some points
- System applications should not be linked to SD card. Link2SD does not allow these applications to be linked.
- When you connect your phone to PC as mass storage, Android unmounts FAT partition but the second partition remains mounted. Therefore linked applications are not affected and can be run without problems.
- Link2SD does not move application's private data directory; it moves apk, dex (dalvik-cache) and lib files
UPDATE:
2.1.2
- fixed crash if too many apps (400+) are installed on some devices
- improved app search (use "contains" instead of "start with" and higlight the matching characters)
- updated translations
2.1.1
- some fixes and tweaks
- added Croatian language
- updated translations
2.1
- added "relink all application files" feature to scan 2nd partition and relink all the files (can be used when changing or updating the ROM)
- added "relink dex files at boot" option
- changed multi-select UI
- added batch freeze/unfreeze
- added size info of /system and /cache partitions to "Storage info"
- fixed bug in converting system apps into user apps and vice versa
- added Persian language
- updated translations
- some fixes and UI tweaks
2.0.4
- fixed relink lib bug introduced in 2.0.3
- added Catalan and Macedonian translations
- updated some translations
2.0.3
- fixed force close at startup on some devices
- updated translations
2.0.2
- fixed bug in obtaining root access on some devices
- updated translations
2.0.1
- added the ability to convert system apps into user apps
- added the ability to convert user apps into system apps
- added "Updated" mark to show if the app has been install as an update to a system (built-in) app
- added "Updated" filter option
- added the ability to integrate "Updated" system apps into system
- fixed freeze/unfreeze bug on some ICS devices
- improved ICS compatibility
- optimized link/unlink/move operations and speed improvements
- some fixes and UI tweaks
1.9.13
- added an option to change language in application settings
- fixed bug in "Storage info" that displays incorrect values if the partition is >1GB on some devices
1.9.12
- changed a2sd checking
1.9.11
- fixed "Mount warning" issue on some devices that do not have operational init scripts to mount 2nd partition at boot, e.g. new Samsung Gingerbread roms
** if you have this problem run "Recreate mount scripts" from the menu after installing the new version of Link2SD
- added Basque translation
- some fixes and tweaks
1.9.10
- fixed some issues on Android 4.0 (Ice Cream Sandwich)
- added Greek and Slovenian translations
- updated some translations
- some minor fixes and tweaks
1.9.9
- fixed bug in recognizing the second partition on some devices
- updated some translations
1.9.8
- fixed bug in setting install location option
- updated some translations
1.9.7
- moved filter and sort functions from menu to title bar
- added an indicator icon which shows the apps that can be moved to SD with native apps2sd (a small icon in upper right corner, for Android 2.2 and higher)
- added "Movable" filter option which lists the apps that support moving to SD with native apps2sd (for Android 2.2 and higher)
- added "Clear data" to clear user data from the app
- added "Clear cache" to clear the app cache
- added "Cache size" sort option
- added ability to clear cache on all apps at once
- added "View in Market" for applications
- added an option to turn "auto link notification" off
- added Dutch, Serbian, Indonesian, Vietnamese translation
- fixed bug in recognizing the 2nd partition on some devices
- updated some translations
- some minor fixes and tweaks
1.9.6
- added Japanese, Chinese Simplified, French, Arabic, Bulgarian, Czech translation
- updated some translations
- added "Translation Credits" to the About page
1.9.5
- fixed freeze/unfreeze bug on some devices
- added Chinese Traditional, German, Hungarian, Italian, Polish, Portuguese, Portuguese Brazilian, Russian, Slovak, Spanish, Thai, Ukrainian translation
- added an option to use English language instead of system language
1.9.4
- added ability to freeze and unfreeze the user and system applications
- added "Frozen" filter option
- added ability to search applications by name, activated from the menu or search button
- some minor fixes and tweaks
1.9.3
- added "Recreate mount scripts" menu to recreate mount scripts manually when you change fs type or rom
- fixed bugs in "Quick reboot" and setting "Install location" on some devices
- some minor fixes and tweaks
1.9.2:
- added "Dex size" and "Total size" sort options
- some bugfixes
1.9.1:
- fixed FC on some devices
1.9.0:
- added native apps2sd function with batch capability (for Android 2.2 and higher)
** moves any user apps to SD even though the app does not support moving to SD
- added option to set the default install location of the apps; auto, internal, or external (for Android 2.2 and higher)
- added workaround for Roms that do not have install-recovery.sh and init.d scripts to mount 2nd partition at boot, e.g. new Samsung GB roms
** mounts after system finishes booting and you need to perform 'Quick reboot'
- new and safer 'Quick reboot' method
- added context menu to app list (activated on a long press)
- added option for automatic relinking of library files at boot
- added "on SD card" and "on internal" filter options
- added applications count to the title
- some UI changes
1.8.0
- changed the method for determining external storage to support devices that have more than one external storage (MMC and SD)
- added ability to uninstall system applications
- added batch (multi-select) reinstalling
- added batch (multi-select) uninstalling
- added "Relink library files" menu which relinks all the lib files that get unlinked after reboot
- removed "Market Fix" menu
- added "fast scroll thumb" option to quickly scroll through the app list
- added "Data size" to sort options
- some bugfixes
1.7.0
- added batch linking and unlinking (multi-select mode)
- some bugfixes
1.6.2
- fixed force close on application startup on some devices
1.6.1
- added horizontal screen orientation support
- added "Link dalvik-cache files" menu back
- improved loading and scrolling performance of the app list
- added cache size to app list
- fixed "Storage Info" bug on Android 2.3
- better CM7 support
Known issue:
* library files get unlinked after reboot on Android 2.3 and sometimes on 2.1 and 2.2. (PackageManager unpacks all native libraries from the apk files at boot)
1.6.0
- added option to link library (.so) files along with apk and dex files
- added automatic linking option for the new installed apps
- added ability to link/unlink apk, dex and lib files separately
- added '->' linked indicator to Apk, Dex and Lib labels
- added lib file size and link status information
- added lib size to sort options
- some bugfixes
1.5.5
- changed link creation, reboot is not required on Android 1.6 and 2.1 anymore
1.5.4
- added notification to status bar for automatic re-linking after app update
- added "reboot required" notification to status bar after linking app on Android 1.6 and 2.1
- some bugfixes
1.5.3
- changed menu name from "Quick Restart" to "Quick Reboot"
1.5.2
- added "Quick Restart" menu, cuts boot time
- added "Clean up the dalvik-cache" menu
- added "Clean up the 2nd partition" menu
- added ability to link updated system apps (that are located in /data/app)
- optimized refreshing of the app list after linking
- changed App2sd checking
- added support in detecting and mounting the second partition for some roms
- some bugfixes
1.5.1
- fixed background message
1.5.0
- added ext3, ext4 and FAT32 support for the second partition of SD card
- added refresh menu
- added "Not Linked" filter option
- changed App2sd checking
- added support in linking protected (/data/app-private) apps
- added support in detecting and mounting the second partition for some roms
- some bugfixes
1.4.2
- disabled automatic Market status fix after linking
1.4.1
- added option to link dalvik-cache (.dex) files along with apk files
- added automatic re-linking after app upgrade
- added automatic deleting from SD card after app uninstall
- added "Reinstall" button
- added "Link dalvik-cache files" menu which links dex files of all existing linked applications all at once
- added automatic Market status fix after linking
- better froyo support
- added dex file size and link status information
1.3.1
- added support in detecting and mounting ext2 partition for some roms
- some minor bugfixes
1.3.0
- added uninstall feature which deletes apk file also from ext2 for linked apps
- added launch and manage buttons
- added detailed size information of applications
- added support in detecting and mounting ext2 partition for some roms
- some minor bugfixes
1.2.1
- added info message to show which applications have been repaired after "Market Fix"
1.2.0
- added "Market Fix" feature to repair missing Market applications
- added support in detecting and mounting ext2 partition for some roms
- removed "ext2 found" info message at startup
- some minor bugfixes
1.0.5
- added support for some roms which install-recovery.sh is not operational
- added ext2.ko module installation on boot (if exists) for Motorola phones
1.0.4
- changed mount method at startup to be much safer
- some minor bugfixes
1.0.3
- initial release:good:
awesome app..very useful..!
what? are u the developer of link2sd? "BULENT AKPINAR" ??
this one https://play.google.com/store/apps/...?t=W251bGwsMSwxLDEsImNvbS5idWFrLkxpbmsyU0QiXQ.. ???
Never ever. Have you already looked at this?
http://forum.xda-developers.com/showthread.php?t=919326
Gesendet von meinem MT11i mit Tapatalk 2
motorazrv3 said:
Never ever. Have you already looked at this?
http://forum.xda-developers.com/showthread.php?t=919326
Gesendet von meinem MT11i mit Tapatalk 2
Click to expand...
Click to collapse
just another copycat . . what a shame! :/
eewwww i have been usin this app since ages with fat32 partition on my card..!!
Now who is this :|
Sent from my MT15i using xda app-developers app
Which is the best extension to use for an AOSP ROM? was using Sony stock ROM with ext4, now shifted to an AOSP ROM, and the partition doesnt seem to work
Abhilesh7 said:
Which is the best extension to use for an AOSP ROM? was using Sony stock ROM with ext4, now shifted to an AOSP ROM, and the partition doesnt seem to work
Click to expand...
Click to collapse
fat32 is usually supported by almost all roms .
I have a problem when the SD card is partitioned with more that one partition and if is enabled the MSC transfer mode (mass storage mode):
The latest files (e.g. camera pictures) and/or folders are not displayed on PC
This behavior is not visible when the MTP transfer mode is used for connectivity. I'm using the MSC mode for systems compatibilities (Windows / Linux / MAC OS) and my phone.
I tested with three cards (Silicon power, Kingmax and a non name one).
My phone is: MT15i, Android 4.0.4, firmware 4.1.B.0.587, kernel 2.6.32.9-pref
I partitioned:
- first partition - primary partition with fat32 format; (partition size = SD size - 1,5 GB for second partion)
- second partition - primary partition with ext2 (only this format is recognized by my kernel) also I tried and fat32, but I have same problem (maximum 1,5 GB)
I made partitions using:
- GParted - from a live CD and from an Ubuntu 12.04;
- MiniTool Partition Wizard Home Edition 7.6.1 - from my Windows 7 PC;
- DiskUtility from a MAC OS.
The results are the same: the latest files or folders from SD card don't appear on the PC.
Scenario:
1. open the phone;
2. take one picture: DSC_0001.jpg;
3. connect to PC, DSC_0001.jpg is visible on the attached card;
4. disconnect the phone from PC;
5. take another picture DSC_0002.jpg;
6. connect again the phone to PC, only DSC_0001.jpg is visible.
7. reboot the phone (shutdown then power on);
8. connect the phone to the PC: DSC_0001.jpg and DSC_0002.jpg are both visible.
9. take a third picture DSC_0003.jpg;
10. connect the phone to the PC, only first two images are vizible (DSC_0001.jpg and DSC_0002.jpg)
...
After each reboot all files / folders are showed correctly when the phone is connected for the first time.
All this time, the files are stored and displayed correctly on the phone using a file explorer or an album program.
Also, if I'm reading the SD card using an external card reader, all files and folders appear ok.
Anyone have any idea what could be wrong in my case?
What else informations could be helpful?
I attached some files from my phone (/ and /etc/)
Thank you for your time!
Later edit
A possible fix is to install a custom or an original rom. Actually this fixed my issue until I installed again Link2SD with partition mount script.
I installed: [ROM]=- Xperia Ultimate HD™ 2.0.3 -= [ Stable like a Rock ] & [ Best User Interface ] after that I was able to attach my phone using MSC mode multiple times and I can access latest files / folders.
ciubexx said:
I have a problem when the SD card is partitioned with more that one partition and if is enabled the MSC transfer mode (mass storage mode):
The latest files (e.g. camera pictures) and/or folders are not displayed on PC
This behavior is not visible when the MTP transfer mode is used for connectivity. I'm using the MSC mode for systems compatibilities (Windows / Linux / MAC OS) and my phone.
I tested with three cards (Silicon power, Kingmax and a non name one).
My phone is: MT15i, Android 4.0.4, firmware 4.1.B.0.587, kernel 2.6.32.9-pref
I partitioned:
- first partition - primary partition with fat32 format; (partition size = SD size - 1,5 GB for second partion)
- second partition - primary partition with ext2 (only this format is recognized by my kernel) also I tried and fat32, but I have same problem (maximum 1,5 GB)
I made partitions using:
- GParted - from a live CD and from an Ubuntu 12.04;
- MiniTool Partition Wizard Home Edition 7.6.1 - from my Windows 7 PC;
- DiskUtility from a MAC OS.
The results are the same: the latest files or folders from SD card don't appear on the PC.
Scenario:
1. open the phone;
2. take one picture: DSC_0001.jpg;
3. connect to PC, DSC_0001.jpg is visible on the attached card;
4. disconnect the phone from PC;
5. take another picture DSC_0002.jpg;
6. connect again the phone to PC, only DSC_0001.jpg is visible.
7. reboot the phone (shutdown then power on);
8. connect the phone to the PC: DSC_0001.jpg and DSC_0002.jpg are both visible.
9. take a third picture DSC_0003.jpg;
10. connect the phone to the PC, only first two images are vizible (DSC_0001.jpg and DSC_0002.jpg)
...
After each reboot all files / folders are showed correctly when the phone is connected for the first time.
All this time, the files are stored and displayed correctly on the phone using a file explorer or an album program.
Also, if I'm reading the SD card using an external card reader, all files and folders appear ok.
Anyone have any idea what could be wrong in my case?
What else informations could be helpful?
I attached some files from my phone (/ and /etc/)
Thank you for your time!
Click to expand...
Click to collapse
open your link2sd, on 1st time it will ask you to choose mount script which kind of partition you use
after that reboot your phone.. open link2sd if it show same dialogue like 1st time open link2sd reboot go to cwm and mount your sd-ext
hmm... did you link your galery?? if yes unlink it
sorry my bad english
motorazrv3 said:
Never ever. Have you already looked at this?
http://forum.xda-developers.com/showthread.php?t=919326
Gesendet von meinem MT11i mit Tapatalk 2
Click to expand...
Click to collapse
which file system(Fat 32,ext2 etc) should be proper to use with MT11i
Thank you for your answer.
Actually my problems is visible only when I attach my phone second time to PC, after a restart.
Opening the Link2SD I'm not asked to enable the mount script, because this script is already installed and running ok, I guess, because the second partition (/data/sdext2) appear on Link2SD -> Storage Info (see attached image).
Also I'm able to navigate through that linked folder (/data/sdext2/)
The behavior is like first time when I connect my phone to the PC, on the phone is created a 'cache' from where, on second / third / ... time are provided same informations (files and folders are same like on first connection).
I'm suspecting one of scripts: init.semc.rc or init.usbmode.sh (these files are recreated at start up / booting)
I'm not sure if I'm right.
Answering to aakash43
Try for first time to create two partitions with following formats:
- first partition: fat32
- second partition: ext2
More informations you can found here on the official page: Link2SD - Description - What you need for linking applications. ( link2sd.info/description)
If second partition is not mounted try to format to fat32. It is indicated to use a unix file format (ext4, ext3 or ext2) but depends by your phone kernel. In my case the phone (Neo - MT15i with latest firmware) was not able to recognize ext4 or ext3 format.
I want to know that Creating second partition in sd card will delete the data present in sdcard.
Answering to aakash43
Depends what program you use to make partitions.
For example I used, on Windows, the MiniTool Partition Wizard Home Edition 7.6.1
I resized first partition and I added on the remaining space a second partition. I did not lost any file from first partition, but to be sure copy all files to PC, be careful to get hidden files and folders also.
But for a safe partitioning process, back-up all files and folders (including hidden files and folders) to PC first.
And delete all existing partitions and recreate new partitions. Remember, all partitions should be primary and visible.
ciubexx said:
Answering to aakash43
Depends what program you use to make partitions.
For example I used, on Windows, the MiniTool Partition Wizard Home Edition 7.6.1
I resized first partition and I added on the remaining space a second partition. I did not lost any file from first partition, but to be sure copy all files to PC, be careful to get hidden files and folders also.
But for a safe partitioning process, back-up all files and folders (including hidden files and folders) to PC first.
And delete all existing partitions and recreate new partitions. Remember, all partitions should be primary and visible.
Click to expand...
Click to collapse
Great info! :good:
workaround for my MSC issue
I figured it out a workaround in my case, for the issue detailed on previous page at post #9.
It is important to have your phone rooted!
I flashed with a clean firmware (4.1.B.0.587) my phone (MT15i), I rooted my phone and I placed a customized rom: [ROM]=- Xperia Ultimate HD™ 2.0.3 -= [ Stable like a Rock ] & [ Best User Interface ]
I opened the phone and I let it to install and configure all applications.
I rebooted twice to be sure all configurations are made properly.
I turned off my phone, I removed the SD card and I partitioned the card using my laptop card reader.
I partitioned using the MiniTool Partition Wizard Home Edition 7.6.1 on mine Windows 7 machine:
1. I deleted all partitions from my card (previously I had some partitions);
2. I created at the end of the card one primary partition with ext2 file system format; (previously I tested others formats ext3 and ext4, but seems to not be recognized these formats)
3. on the remaining space I created another primary partition with FAT32 file system format.
Like on below image:
I placed formated card into the phone and I turned on.
I modified the file: /system/etc/vold.fstab
I replaced:
Code:
dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.4/mmc_host/mmc0 /devices/platform/msm_sdcc.4/mmc_host/mmc1
with:
Code:
dev_mount sdcard /mnt/sdcard 1 /devices/platform/msm_sdcc.4/mmc_host/mmc1
Format is:
Code:
Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
To found that solution I made some tests after each modification on /system/etc/vold.fstab I rebooted my phone. And I checked to see if the /mnt/sdcard is mounted properly.
I modified the file on PC and after each time I pushed modified file to the phone:
Code:
adb push vold.fstab /system/etc/vold.fstab
(you should have the terminal on the current folder where is your modified file)
Then, with my phone connected to PC I tried to mount the second partition to /data/sdext2/ folder.
Open a terminal and add below commands:
Code:
>adb shell
$su -
Your terminal should look like (this is in Windows):
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\ciubex>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ su -
su -
[email protected]:/ #
This folder was not on my phone, so I created: #mkdir /data/sdext2/
On PC terminal I tried to mount the partition using the command:
Code:
mount -t ext2 -o rw /dev/block/mmcblk0p2 /data/sdext2
After each mount attempt you can check if the partition is mounted by using df command, the terminal should show like:
Code:
[email protected]:/ $ df
df
Filesystem Size Used Free Blksize
/dev 169.9M 76.0K 169.9M 4096
/mnt/asec 169.9M 0.0K 169.9M 4096
/mnt/obb 169.9M 0.0K 169.9M 4096
/system 312.5M 310.7M 1.8M 4096
/data 380.0M 140.0M 240.0M 4096
/cache 101.5M 1.3M 100.2M 4096
/system/vendor 133.5M 92.1M 41.4M 4096
[b]/data/sdext2 1.4G 82.6M 1.3G 1024[/b]
[email protected]:/ $
If your second partition is mounted properly, you can proceed to install Link2SD.
I installed Link2SD, I let the software to generate mount script /system/etc/install-recovery.sh.
I don't rebooted, but I modified generated file by removing the line:
Code:
I let only the mounting:
Code:
mount -t ext2 -o rw /dev/block/mmcblk0p2 /data/sdext2 1>>$LOG 2>>$LOG
Be careful to have an empty last line.
To exit from terminal, use commad: exit
After that I rebooted my phone.
Now I do not have any more problems with my latest created files or folders on the phone, when I connect the phone to PC using MSC protocol.
I attached an archive with modified files (vold.fstab and install-recovery.sh).
i used cwm recovery of lupus kernel and it partitioned my mc into fat32,ext3 n its running flawlessly
when I try to create partition using mini tool partition wizard the unlocated space does not increase above 304 MB plz help
Steps to make partitions
I really don't know what's wrong in your case, is your card empty? It is your card full and remaining empty space is 304MB?
But let suppose you have inserted a formatted card into a card reader with a single partition and want to have two partitions.
Method 1:
resize existing partition and create a second one:
- right click on partition
- select 'Move/Resize'
- click on right side of the partition image from 'Size And Location'
- move the border on left side to desired partition size
- click on 'Ok'
- now on the disks images should appear resized partition and an unallocated space at the end of the card
- right click on the Unallocated space
- select 'Create'
- on the Warning message press 'Yes' (Warning message: The new created partition cannot be used in WIndows....)
- on the 'Create New Partition' dialog window chose:
--- Create As: Primary
--- File System: Ext2
--- Press 'OK' button
- Now, your card is ready for modifications: Press Apply.
Method 2:
in that case the entire card is erased and partition(s) is (are) deleted firstly and created from beginning
- right click on partition or on each partition from card and select 'Delete'
- when entire card appear as Unallocated
- let create second partition at the end
- right click on Unallocated space and select 'Create'
- resize the partition image from 'Size And Location' by clicking on the left side and moving the left border to the right until the new partition have desired size
- select:
--- Create As: Primary
--- File System: Ext2
--- Press 'OK'
- now will create first partition
- right click on the Unallocated space
- select 'Create'
- on the Warning message press 'Yes' (Warning message: The new created partition cannot be used in WIndows....)
- on the 'Create New Partition' dialog window chose:
--- Create As: Primary
--- File System: FAT32
--- Press 'OK' button
- Now, your card is ready for modifications: Press Apply.
That's all.
This is the one I used ^^
I created a ext3 partition on the sd card, I selected what I want to moved or not.
And now, all new apps are installed on the sd card automatically.
Works great , thanks.
Now that, our tablet S is now rooted finally .... thanks to all fellow users and developers for achieving this :highfive:
After rooting, i wanted to try Directory Bind developed by slig.. target to free up some space (internal sdcard). And result, this app is damn good guys! I have Maxpayne, GTA3, 9MM, Asphalt 6, Shadowgun. With all these games installed, i have 8.1gb from 8.9gb in internal storage (source: Sony's File Transfer) :laugh:
Requirement to make this work on sony tab, is ROOT, Enable write permission on sd patch from condi's S.ony Aio
Sounds cool? give it a try
Here's original thread [TOOL] DirectoryBind - move data to external_sd (GameLoft, Shadowgun etc.) ROOT req.
Hi all !
This is my application to bind directories located on external_sd to directories on internal memory (/sdcard/). This way You can transfer large application data directories to external_sd. Could be usefull with ex.: games from Gameloft, other like Shadowgun, applications like CamScanner.
Features:
* Requires ROOT !
* Aimed at specific functionality and features (not idiot-proof)
* You can create any number of Data -> Target directory pairs, mount them manually or choose to mount them on system boot (checkbox does that).
* On/Off switch controls whole mount-on-boot function.
* Diskette icon indicates if mount operation was successful, by taping it You can mount/umount entry.
* Icon changes if application is using mounted entry
* DirectoryBind can tell what application is using this entry (tap at entry in use)
* Long tap on entry (disabled) brings edit/delete window
* App auto umount all entries on USB connected and remount after USB disconnected (for now via BroadcardReceiver UMS_CONNECTED / UMS_DISCONNECTED)
* App shows notification and vibrates if auto umount on USB fails
* If mounting all checked entries (ex. on boot) app is waiting specified time (def. 60 sec) if data directory is not available (happens sometimes at boot)
* Tested sucessfully with Asphalt 6, Shadowgun, DeadSpace, CamScanner
Click to expand...
Click to collapse
Installation and usage is pretty simple. No format of card or extra partition required.
Just install the application and it will ask for root rights. Click allow and you are in the main screen. Now FIRST step, click menu and go for prog "preference" and there click bind on boot, 'alternate dbase mgmt"
and also check default data path, target path and assistant prefix dir- if reqd.
Now start adding games to move data, Add new entry -> click menu -> Data transfer assistant.
Click on the directory you want to transfer and select. -> and tick Transfer files from target to data. and finally click ADD
Now app will create similar path directory on your external sd card and will transfer all data files to same on your external sd card.
Once this transfer is completed, and click menu and click "Bind Checked" All done, data is now on your sd card and test your games.
Rest go through the original thread, after some tries you will succeed. Good luck guys :good:
edit:
Now added Asphault7, Brother in arm 2. Internal memory 7.8gb left
That's Cool！！！
Please feel free to post guides for
tweaks on how to root / unroot
device drivers
rom customizing
app 2 ext sdcard/sdcard2 default
here are some i found just want to share....
info link thanks to darkjf
TOOKY Beijing Kawasaki A981 + can also use this phone for some time
had the phone's internal phone storage space 2:00 4G ...
But with the passage of time a little bit
more slowly on its own is not enough to use a
mobile phone that supports SD cards
, but it is separate block
does not belong to the system default SD
and SD to determine the phone internal storage space is
to explain how the following Qian Kun Da Nuo
allow SD cards can become an internal storage space
of course ...
this part of the phone must have to gain root privileges
TOOKY A981 + install drivers get ROOT permissions:
SD card first using the original
files will all move to the inside of the computer
to this part of the main premise of this card clean and
replace the main reason is to avoid the
mess memory card files
have to pull out the SD card if I remember putting it back
, but this phone Most are using a USB
card first pull the battery because the pull ... (trouble)
Then back to the mobile operating
system to use can browse the program file browser
where I was using Total Commander
browse the file system / system / etc directory
down here looking for a vold.fstad file
(remember the figure below R switch to RW)
Click on the file and select Edit File
Here I use Total Commander built-in editor
Will see this screen and tap on the map
Looking down at the beginning of the previous two lines have no #
1
2
dev_mount sdcard / mnt / sdcard emmc @ fat / Devices / Platform / goldfish_mmc . 0 / Devices / Platform / MTK - SD . 0 / mmc_host
dev_mount sdcard / mnt / sdcard2 Auto / Devices / Platform / goldfish_mmc . 1 / Devices / Platform / MTK - SD . 1 / mmc_host
The figure has been modified is good
we will be the first line to / mnt/sdcard2
second line to / mnt / sdcard
1
2
dev_mount sdcard / mnt / sdcard2 emmc @ fat / Devices / Platform / goldfish_mmc . 0 / Devices / Platform / MTK - SD . 0 / mmc_host
dev_mount sdcard / mnt / sdcard Auto / Devices / Platform / goldfish_mmc . 1 / Devices / Platform / MTK - SD . 1 / mmc_host
After modification by the return
will be whether to save? choice
Then reboot the phone
into the Total Commander will see the SD card has already lost
this case your SD card and then (2) where the data
is moved to the SD card which can be covered
so that the completion USB storage space into the SD card Hello ~