Running android from sd card

Использование карты памяти /sdcard/ приложениями в Android

Друзья, поклонники зеленых роботов, разработчики приложений, просто пользователи:
как Вы используете карту памяти /sdcard/ в Вашем Android-девайсе?

Рассмотрим, для начала данный вопрос на примере большинства рядовых пользователей устройства под управлением ОС Андроид:

Как и многие, я устанавливаю приложения на карту памяти — для экономии места в самом телефоне, но сами приложения, их кеши и т.д. — все это сохраняется прямо в корень карты памяти, в итоге я получаю на карте полную «кашу»:
огромное количество папок и т.д. среди которых достаточно неудобно (как через ФМ так и при подключении к ПК) искать нужные мне файлы, папки и т.д. Понятно, что можно обойтись костылями и, например, добавить мои папки в «избранное» в том же ФМ и т.д., но вопрос в другом.
Почему изначально большинство приложений устанавливаются на карту памяти так:

или, например, так:

или на худой конец — есть же скрытая системная
/sdcard/.android_secure
(понятно, что туда не всегда есть доступ и т.д., но все таки)

В итоге: что же получает юзер?
Среднестатистический юзер устанавливает достаточно много приложений и, зачастую, для экономии места, перемещает их на карту памяти. Все хорошо, но до того момента, когда нам вдруг понадобилось найти свой собственные документы на карте памяти, тут мы подключаем девайс с ПК в режиме карты памяти или же через ФМ самого смартфона заходим сюда: /sdcard/
И что же мы видим?
Да вот что:
habrastorage.org/storage1/e5deae9f/54a3c20b/8ba76329/55414a1a.jpg

Напрашивается, закономерный вопрос: почему так?
Насколько я понимаю, причины две:
1) это сама компания google, точнее ее политика в отношении это аспекта, то есть действия разработчиков программ никак тут не ограничены (тем же условием опубликования программы на market’e и т.д.)
2) разработчики программ, которые пишут софт, зачастую, создающий массу папок в корне /sdcard/

Ну и для любопытства ради воспользуемся любимым поиском:
habrahabr.ru/blogs/android_development/111868
Например тут указан некий Стандарт разработки приложений под Android
из которого четко следует:
Корневой каталог для всех файлов пользователя, кроме временных:
/sdcard/название проекта/, например /sdcard/TalentMania/

Каталог для музыки:
/sdcard/название проекта/sound/, например /sdcard/TalentMania/sound/
Каталог для MIDI:
/sdcard/название проекта/midi/, например /sdcard/TalentMania/midi/
Каталог для графики:
/sdcard/название проекта/img/, например /sdcard/TalentMania/img/

Подкаталоги для файлов различных активити:
/sdcard/название проекта/img/название активити/, например /sdcard/TalentMania/img/guitar/

И т.д.
Никаких претензий я разработчикам или вообще кому либо не предъявляю.
Просто хочу задать два вопроса:
1) Почему так? Почему все «сваливается» в корень карты памяти?
2) Одному мне это чертовски неудобно?

Спасибо за внимание!

PS: а пока юзеры выдают просто шедевральные методы облегчения использвания карты памяти:
открываешь карту памяти и создаешь
_Видео
_Документы
_Музыка
_Прочее
|-Карты
|-и т.д.
_Фото
как результат, то что мне нужно, хотя бы всегда сверху
как в телефоне
так и на ПК

Источник

Running Android or Linux from an SD card on a RK3288 device — An easy way to dual boo

Breadcrumb

Linuxium

Member

If you are interested in dual booting Android and Linux on your RK3288 device or you simply want to try a different Android ROM or Linux distro without flashing the device, then use this method of booting from an SD card.

You will need a PC running Linux and an SD card of 8 GB or more, at least class 10 speed.

Download the tools from ‘https://drive.google.com/file/d/0B99O3A0dDe67bGVqWkZMRGFCSjg’. After unzipping you will see two shell scripts called ‘create-android-sdcard’ and ‘create-linux-sdcard’, a directory called ‘Tools’, a file called ‘RK3288Loader_uboot_V2.17.02.bin’ and some ‘.img’ files together with a ‘parameter’ file.

To be able to dual boot (i.e. boot directly from the device or from an SD card), you will first need to update the bootloader on your device. Either use ‘AndroidTool v2.3’ on Windows or ‘upgrade_tool’ on Linux to flash just the ‘Loader’ with the ‘RK3288Loader_uboot_V2.17.02.bin’ file.

To create a bootable SD card first put it into your PC and use a command like ‘blkid’ or ‘lsblk’ to identify its device name (e.g. /dev/sdc).

For Android, run the script ‘create-android-sdcard’ and pass the name and location of the Android ROM you want to install onto the SD card, e.g.:

The program will prompt you to confirm the name of the device for the SD card. Once confirmed it will then unpack the Android ROM, create partitions on the SD card that mimic the ROM including a ‘user’ partition that will use the remaining space of the SD card. It will then install the Android ROM to the SD card and notify you when complete.

For Linux, as currently no standard approach to creating a Linux distro exists, to allow flexibility you will have to perform some initial set up steps. I’ve included example kernel and resource images which work fine on the Firefly, MK802V (et al) and Orion R28 (et al). I’ve also included download links for example root file systems (RFSs). Download either the Ubuntu 12.04 or Xubuntu/Lubuntu 14.10 RFS and unzip and rename as ‘linux-rfs.img’. If you want to try a different kernel/resource combo simply rename them as ‘kernel-linux.img’ and ‘resource-linux.img’. You can also use the tools in the ‘Tools’ directory to unpack Linux distros for those who want to experiment. Just don’t modify the ‘boot-linux.img’ or ‘parameter-linux’ files as these must be used rather than any supplied as part of a Linux distro for Linux to boot from SD card.

Once set up, simply run:

The program will initially prompt you to confirm the name the device for the SD card and then it will create a bootable Linux SD card from the images defined in the’*.img’ files.

Now just take the SD card and insert into your RK3288 device and power on to enjoy booting either Android or Linux.

The Android script will work with any Android ROM packed as an image with a separate ‘data’ and ‘user’ partition. I recently saw a ROM with the ‘user’ partition effectively combined with the ‘data’ partition. My sketchy knowledge of Android includes the memory of some requirement to have the ‘user’ partition as type ‘vfat’ as some programs expected or required that format. So until I can confirm this, or identify which Android version release it pertains to, I’ve not included it yet within the script.

Both scripts work for RK3288 and RK3188 devices. They utilize the excellent work from Fukaumi-san (naobsd) who provided the binary headers required to boot from SD card (see the ‘README.txt’ in the ‘Tools’ directory for further details and the required copyright notice, conditions and disclaimer).

The other key advantage of these scripts is that they allow you to boot a ‘bricked’ device. Some time ago I managed to break my Orion R28 Meta such that it would not boot and could not be flashed. I’ve included the required functionality in the scripts to boot even if no memory can be found on the device. So now I have a working Orion R28 again, albeit just from SD card.

Источник

Running android from sd card

Breadcrumb

fatsal

Senior Member

i want to share how to running android from sdcard, last time before i lose my X1 it’s already running well on my X1.

requirement :
1. linux (mine ubuntu 9.10)
2. for ubuntu do «sudo apt-get install squashfs-tools» for getting unsquashfs (for extract system.sqsh)

prepared equipment :
1. 8gb SDCard (for good starting but you can also using 2 gb or 4gb)
2. partition your sdcard like this (8gb configuration) you can using gparted :

1. 5.5 gb format using fat32 this called : mmcblk0p1
2. 1 gb format using ext2/ext3 for /system this called : mmcblk0p2
3. 1 gb format using ext2/ext3 for /data this called : mmcblk0p3
4. 512 mb format using linuxswap for /swap this called : mmcblk0p4

installation :
1. do execute on terminal : unsquashfs after extraction you will see directory called «squashfs-root»
2. copy all files from «squashfs-root» directory into your SD Card /system partition or mmcblk0p2.
3. copy startup.txt, haret.exe, modules .gz, zImage from vdelf build onto your root SDCARD fat32 or mmcblk0p1
4. download and copy/replace rootfs.img from here into your root SDCARD fat32 or mmcblk0p1.
5. execute haret.exe and then wait and pray.

@vdelf :
man. your the best, with this configuration you can easly changes or edit an android modules.

Источник

Unconfigured Ad Widget

Announcement

Running Android or Linux from an SD card on a RK3288 device — An easy way to dual boot

Running Android or Linux from an SD card on a RK3288 device — An easy way to dual boot

If you are interested in dual booting Android and Linux on your RK3288 device or you simply want to try a different Android ROM or Linux distro without flashing the device, then use this method of booting from an SD card.

You will need a PC running Linux and an SD card of 8 GB or more, at least class 10 speed.

Download the tools from ‘https://drive.google.com/file/d/0B99. GVqWkZMRGFCSjg’. After unzipping you will see two shell scripts called ‘create-android-sdcard’ and ‘create-linux-sdcard’, a directory called ‘Tools’, a file called ‘RK3288Loader_uboot_V2.17.02.bin’ and some ‘.img’ files together with a ‘parameter’ file.

To be able to dual boot (i.e. boot directly from the device or from an SD card), you will first need to update the bootloader on your device. Either use ‘AndroidTool v2.3’ on Windows or ‘upgrade_tool’ on Linux to flash just the ‘Loader’ with the ‘RK3288Loader_uboot_V2.17.02.bin’ file.

To create a bootable SD card first put it into your PC and use a command like ‘blkid’ or ‘lsblk’ to identify its device name (e.g. /dev/sdc).

For Android, run the script ‘create-android-sdcard’ and pass the name and location of the Android ROM you want to install onto the SD card, e.g.:

The program will prompt you to confirm the name of the device for the SD card. Once confirmed it will then unpack the Android ROM, create partitions on the SD card that mimic the ROM including a ‘user’ partition that will use the remaining space of the SD card. It will then install the Android ROM to the SD card and notify you when complete.

For Linux, as currently no standard approach to creating a Linux distro exists, to allow flexibility you will have to perform some initial set up steps. I’ve included example kernel and resource images which work fine on the Firefly, MK802V (et al) and Orion R28 (et al). I’ve also included download links for example root file systems (RFSs). Download either the Ubuntu 12.04 or Xubuntu/Lubuntu 14.10 RFS and unzip and rename as ‘linux-rfs.img’. If you want to try a different kernel/resource combo simply rename them as ‘kernel-linux.img’ and ‘resource-linux.img’. You can also use the tools in the ‘Tools’ directory to unpack Linux distros for those who want to experiment. Just don’t modify the ‘boot-linux.img’ or ‘parameter-linux’ files as these must be used rather than any supplied as part of a Linux distro for Linux to boot from SD card.

Once set up, simply run:

The program will initially prompt you to confirm the name the device for the SD card and then it will create a bootable Linux SD card from the images defined in the’*.img’ files.

Now just take the SD card and insert into your RK3288 device and power on to enjoy booting either Android or Linux.

The Android script will work with any Android ROM packed as an image with a separate ‘data’ and ‘user’ partition. I recently saw a ROM with the ‘user’ partition effectively combined with the ‘data’ partition. My sketchy knowledge of Android includes the memory of some requirement to have the ‘user’ partition as type ‘vfat’ as some programs expected or required that format. So until I can confirm this, or identify which Android version release it pertains to, I’ve not included it yet within the script.

Both scripts work for RK3288 and RK3188 devices. They utilize the excellent work from Fukaumi-san (naobsd) who provided the binary headers required to boot from SD card (see the ‘README.txt’ in the ‘Tools’ directory for further details and the required copyright notice, conditions and disclaimer).

The other key advantage of these scripts is that they allow you to boot a ‘bricked’ device. Some time ago I managed to break my Orion R28 Meta such that it would not boot and could not be flashed. I’ve included the required functionality in the scripts to boot even if no memory can be found on the device. So now I have a working Orion R28 again, albeit just from SD card.

Источник

[HOW TO] BOOT FROM SD CARD [SUCCESSFULLY] on QMobile Z8 with BRICKED/DEAD eMMC

Breadcrumb

mirfatif

Senior Member

I’m a mechanical engineer, not an IT guy. I can fix machines, perhaps, but not bricked phones. So try anything at your own extreme risk. This is NOT a step by step guide.

DEVICE:
QMobile Z8, same as Wikio Ridge 4G, (MSM8916).
Running Android 5.0.2, SuperSU rooted.
Kernel v 3.10.49
Thanks to @ASAZING for TWRP 3.0.2-0

PROBLEM:
So the screen started blinking and locking / unlocking automatically like UI resetting. And there was no SIM. At first I thought it’s launcher or SuperSU causing problem. But it got worse over days. So I decided a factory flash since I didn’t have untouched flashable zip.
Flashed firmware using QFIL but no success. Rebooted to recovery and TWRP was still there.
/data partition was locked and TWRP doesn’t support decryption. So I did a factory reset and the message came: /data not mounted. Invalid Argument
Formatted /data from «Repair or Change Filesystem» option in TWRP and as a result /data and /cache both couldn’t be mounted.
Formatted /cache, and /system too not mounted.
Manually formatted using ‘make_ext4‘ and tried ‘fastboot format:ext4 userdata‘ as well. Both succeeded apparently but mount still failed.
Run ‘e2fsck‘ and that showed: » Bad magic number in super block » and » The superblock could not be read. »
Run ‘mke2fs -n‘ for alternate super blocks, run again ‘e2fsck‘ but no success. Images are attached.
‘sgdisk —verify‘ gives this error log:

‘parted rm‘ and ‘fastboot erase‘ didn’t work either. Partition was still there.
Then I tried to flash stock recovery through TWRP. And recovery too gone.
Now, device boots directly to bootloader (fastboot mode) and is halted there. Have to ‘fastboot boot recovery.img‘ or ‘fastboot boot boot.img‘ each time.
Download Mode (QDLoader 9008) is also accessible.

FLASHING FACTORY FIRMWARE:
Now left only with fastboot and EDL, tried once again QFIL flasher, Wiko official flasher, QDownloader. Log says: » Read back verify failed at sector . » for partitions misc, system, cache, persist, recovery, userdata (6 partitions) and 2 partition table *.bins
Hence proved, eMMC is malfunctioning and device now can’t boot on its own due to no partition table.
Tried ‘sgdisk —backup‘ and ‘sgdisk —load-backup’ options for partition table. It gives error: » Warning! Current disk size doesn’t match that of backup. » and » Problem: Partition 28 ends before it begins. » etc.
‘fastboot flash partition *.bin‘ also failed with error: » remote: failed to write partition «.
‘dd if=gpt_main0.bin of=/dev/block/mmcblk0‘ apparently succeeded but comparing octal dump (‘od‘) files of 34 sectors at start shows no difference, means file is not written to eMMC.

SOLUTION SUMMARY:

• Partition SD card according to already existing partition table on internal eMMC.
• Flash partition images from factory firmware to newly created partitions.
• Modify kernel (boot.img) and recovery to boot from sd card instead of internal memory.
• Boot kernel or recovery through fastboot.

SECTION 1
PARTITION SD CARD:
Here comes Google. Following the footsteps of @lexelby at this, I created gpt (parted command) on 16GB C-10 sd card using Ubuntu virtual machine.
Created first partition for external_sd card and 6 more of same size as original ones (size checked by parted and from rawprogram_unsparse.xml). Filesystems: system, userdata, cache & persist of ext4 while misc, recovery of linux-swap (though ‘dd’ will overwrite them).
Then I unsparsed userdata, system and cache images from factory firmware (on Windows used packsparseimg.exe binary). Sparsed images can only be flashed through fastboot?
Copied 5 prtitions images: userdata, system, cache, persist and misc using dd command to /dev/block/mmcblk1p*.

MODIFYING BOOT & RECOVERY:
Now coming to the changes in mount paths of boot and recovery (fstab and init.*.rc).
Extracted boot.img and then ramdisk using «Image Studio for Android». ‘unpackbootimg‘ and ‘abootimg‘ don’t extract all files on Ubuntu. ‘mkbootimg‘ makes smaller boot.img file without boot.img-dtb. Perhaps I’m doing it wrong.
Anyway, then did ‘grep dev/block‘ on all extracted files. Results are attached for reference.
Made changes in «fstab.qcom» and «init.target.rc». For details on changes made, please read on RE-MODIFYING BOOT & RECOVERY.
Repacked boot.img

Similarly extracted recovery.img, did ‘grep dev/block‘ on all extracted files. And made changes in «recovery.fstab».
Repacked recovery.img

COPYING IMAGES TO PARTITIONS AND BOOTING:
‘fastboot flash boot boot.img‘ and ‘dd if=recovery.img of=dev/block/mmcblk1p*‘ (though useless, have to boot from fastboot)
Rebooted to recovery by ‘fastboot boot recovery.img‘
userdata, persist and cache couldn’t be mounted in TWRP. Tried ‘mount -t ext4 -o loop *.img‘ on Ubuntu but there too not mounted. Googled and using commands ‘file‘, ‘fdisk‘, ‘sfdisk‘, ‘e2fsck‘ and finally ‘resize2fs -f /*.img‘ resolved the problem » bad geometry: block count xxx exceeds size of device. «.
Also unsparsed userdata too large to handle and only a few MBs data inside, that too useless. Therefore, did ‘make_ext4fs‘ on cache & userdata.

Now booted kernel by ‘fastboot boot boot.img‘
And. it boots. But very very slow (due to slow write speed of sd card obviously). Took almost half an hour at first boot.

UNRESOLVED PROBLEMS:
There is no sound. Because of /persist not mounted? And still no SIM, means radio firmware isn’t readable from eMMC or this too due to /persist absent? After all that contains drivers. And also Wi-Fi and bluetooth not working.

SECTION 2
RE-PARTITION SD CARD:
So re-created gpt on sd card (using parted and fdisk) and in a hope to utilize all necessary partitions, 100% replicated all partitions (except larger userdata) including space required at start and end of eMMC for partition table. Partition tables of both mmcblk0 and mmvblk1 are attached.

Источник