Database Develop

[L3] [MOD] [CM/MIUI] Data2ext

Hi to all again! I've done another little mod to make our low-end device with too low internal memory (10 apps and is full!) a little bit larger.
This script is a modded d2ext wrote originally by cronmod. This init.d script mounts the /sd-ext partition as /data moving the entire partition in the sd-ext (previously created by the recovery!!).
I have to advise you that the partition MUST be more than 1GB (it moves the entire partition, so if you have it very small it's useless!!).
If you want to install/backup/restore it, you must have this recovery made by me:
http://forum.xda-developers.com/showthread.php?t=2283641
That's because the updater-script mounts the /sd-ext and moves everything from /data leaving it totally empty.
So if you don't want to make a factory reset you have to use my recovery, sorry.
Istructions:
1) Flash the new recovery from the link above
2) Download the attachment and put it into your phone's sdcard
3) Boot into recovery
4) Wipe cache/dalvik-cache
5) Install the zip
6) Reboot into system
EDIT: The .zip provided is in test because I've already put the script in the CM zip before installing it on my phone. Tell me if it works or not and I'll make modifications.
Here's the screenshot of my phone with a "/data" partition of 2GB!!:victory:

when i partitioned my sd card in 2 GB, the 2 GB partition just disappeared, only the 12 GB was left...what to do?
and also tell me how to un-partition it.

Whoa awesome works thanks

Sorry but I made an error in the updater-script. It didn't set the right permission . Now it's correct here: www.4shared.com/zip/SkBxf9FB/Data2ext_signed.html

Aggror said:
when i partitioned my sd card in 2 GB, the 2 GB partition just disappeared, only the 12 GB was left...what to do?
and also tell me how to un-partition it.
Click to expand...
Click to collapse
How did you partiton the sd?

Thanks 4 sharing
TouchWiz-e400 v1 (coming nxt month)

[ROM][4.4.4] LineageOS 11.0 for LG Optimus One [OS2SD][19.03.13]

LineageOS 11.0
{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 4.4 KitKat, which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
This is LineageOS 11.0 for LG Optimus One OS2SD edition based on androidarmv6 jenkins builds. I made this edition to solve lack of space in our P500 and and improve phone performance because many todays MicroSD cards are faster then this phone internal storage. What it does, it mounts /system and /data on SD card ext4 partitions, so this way you can have as many space as you want to install apps and flash untrimmed gapps without using any a2sd mods, link2sd, manual symlinking or dalvik2cache.
What's working:
Supports all android 4.4 (KitKat) features
Fully functional camera (preview, taking photo, recording video, panorama)
Full H/W acceleration with new adreno drivers, 3D modelling (yamato)
Hardware decoding of videos, Youtube HQ videos
Internet sharing (Bluetooth tethering, USB tethering, Wi-Fi hotspot)
Calls, SMS, MMS, 3G/2G, Mobile data, Data limit
Loudspeaker in call, Manual network search
Usb mass storage, Usb debugging
Wi-Fi, Bluetooth, Bluetooth headset, A2DP (Bluetooth Music), Car dock w/BT
GPS, Sensors, Lights, Touch screen
Funny SIM (128k USIMs)
Browser, GMail, GPlay
Youtube LQ/MQ/HQ
Offmode charging
Known issues
Wi-Fi wakelock because of the old bcm4325 wireless driver
Swipe in stock keyboard because of missing armv6 libs
FM Radio (bcm4325 FM chip is depends on bluez-hcitool)
After Wi-Fi hotspot reboot is required to use Wi-Fi
Installation instructions:
I am not responsible for lost data or dead SD card, do this at your own risk.
Backup all you data with Titanium Backup or alternatively use "Migrating to new file system without loosing data" method
Backup all SD card contents to PC
Flash TWRP recovery (20161230 or later)
While in TWRP go to Advanced>Partition SD Card and use default partition sizes or adjust it depending on your needs.
Also you can do partitioning on computer.
Use exact order and recommended partitions sizes as listed below
FAT32 primary for /sdcard
ext4 primary for /system (448 MB or more)
linux swap primary for /swap (64MB or more)
ext4 primary for /data (1024 MB or more)
Partitioning guides:
MiniTool Partition Wizard (Windows):
You need to start with one partition formatted with fat32 (or unallocated space to create fat32 partition and skip 2 step):
Right click the fat32 partition and use Move/Resize tool to shrink that partition:
Right click on unallocated space and select Create. Following this create ext4, swap and again ext4 partitions:
After that you should end with this configuration (partitions sizes may differ) then hit Apply:
GParted (Linux)
You need to start with one partition formatted with fat32 (or unallocated space to create fat32 partition and skip 2 step):
Click the fat32 partition and resize it to shrink partition:
On unallocated space create create ext4, swap and again ext4 partitions:
After that you should end with this configuration (partitions sizes may differ) then hit Apply:
Copy all SD content from PC back
Flash latest Rom and Gapps
After system booted restore your data with Titianium Backup or alternatively use "Migrating to new file system without loosing data" method
Important! For f2fs rom make sure you have /data partition formatted with f2fs.
Instructions:
Note /data will be formated! Follow method above to backup data.
In TWRP Go to Wipe>Advanced Wipe select Data. Then Repair or Change File System>Change File System>F2FS.
Note: To reverse /data back to EXT4 do the same as above except select EXT4 in last step.
Migrating to new file system without loosing data:
What do I need to migrate without loosing data?
ADB installed on your PC (somehow adb in recovery working only on linux for me) or use Terminal emuliator on TWRP
sdcard with enough memory to backup whole your /data partition
How to perform a migration?
Reboot to recovery.
Go to Mount menu and make sure that /data and /MicroSD are selected.
Open Command Line (Windows) or Terminal (Linux/OS X) on your PC or Terminal emuliator on TWRP
Type: adb shell and press ENTER (skip this if you are using Terminal emuliator on TWRP).
Type: tar -cvpzf /sdcard/data.tar.gz /data
Wait until operation will finish. If you see any error, it means you don’t have enough free space on your SDcard.
Perform steps to format /data to new file system.
Go to Mount menu and make sure that /data and /MicroSD are selected.
Now type: tar -xvpzf /sdcard/data.tar.gz -C /
If previous step didn’t produce any error, reboot your phone and check if it’s boot succesfully. If yes, you can safely remove data.tar.gz file from your SD card.
Done. You have migrated to new file system without loosing your data!
Recommendations:
Use Class 6 or even Class 10 SD card for best performance
CPU settings: SmartassV2 480-748 MHz
I/O Scheduler: I've read that for emmc devices (sd card) best choice is SIO, but Deadline is also very good, please leave your feedback
Screenshots:
DOWNLOADS
Thanks to:
LineageOS for sources
AndroidMeda, Conn O'Griofa and other members of androidarmv6 for bringing KitKat to P500
skinbark, bigsupersquid for help on OS2SD mod
XDA:DevDB Information
LineageOS 11.0 OS2SD, ROM for the LG Optimus One P500
Contributors
HardLight
Source Code: https://github.com/os2sd
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: LineageOS
Version Information
Status: Stable
Created 2014-10-17
Last Updated 2019-03-14

Reserved

Looks promising

Does not boot!
Strange! I flashed couple of days back Androidmeda's "partitionsdcard"built from Jenkins, but failed to boot this ROM. I did a clean install in both cases!:crying:

sumansur2008 said:
Strange! I flashed couple of days back Androidmeda's "partitionsdcard"built from Jenkins, but failed to boot this ROM. I did a clean install in both cases!:crying:
Click to expand...
Click to collapse
Read the instructions carefully. You need to repartition you sd I said and use TWRP-OS2SD, not any other recovery.

Base ROM
On which ROM is this ROM based?

[ROM] [4.4.4] CyanogenMod 11.0 for LG Optimus One [OS2SD] [14/07/25]
Flashed the rom and it works perfectly well. ROM is smooth and fast as always.Thanks androidmeda.
Here is what I did:
1. Partitioned my 16GB Class 10 SD card as per instructions
2. Flashed the new recovery TWRP-OS2SD
3. Flashed the rom.
4. Rebooted and again flashed the Gapps-minimal(36MB!)
All fine. Playstore works, No FCs.
Partition info after Gapps:
/system 240MB / 394MB
/data 129MB / 1.68GB
/cache 1.15MB / 64.00MB

As mns123 posted, cm-11 (20140725) OS2SD has succesfully been installed on my obsolete device P500. It's amazing. Even using SDCard Class 6, it's running smooth like butter (or silk) and fast (and furious) :victory: Be patient, the initial reboot take a quite time, circa 7 minutes.
I think @HardLight fooled the recovery that /system and /data in SDCard pretended as /system and /data partitions in the internal memory, apparently. Very clever :good: The question is, where's 412 MB memory device, anyway?
Configuration:
SDcard: 2GB, Class 6
Processor:
Min CPU Freq: 320 MHz; Max: 600 MHz; Governor: SmartassV2
Memory management: Swap on
Dev Option: Window animation scale: 0.5X; Transition animation scale: 0.5X; Animator duration scale: 0.5X
Pros:
Space running out is no longer a problem. You can install apps as many as you want. The limit is just the SDCard capacity
Cons:
Out of known issues, none. Except I have to buy a new 16 GB SDCard Class 10. Duh! No, just kidding!

xu3sno said:
The question is, where's 412 MB memory device, anyway?
Click to expand...
Click to collapse
It is still there, probably with your last regular rom, just not mounted.
Sent from my LG-P500 using xda premium

Sarisfied till now
I have used this ROM for a day now, and this ROM has worked better for me than mukulson's CM11-v12 because, there was no insane battery drain in wifi standby.

14/07/27
Changelog:
Updated to last nightly
Increased read_ahead_kb to 2048 for better sd card read speeds

HardLight said:
Changelog:
Updated to last nightly
Increased read_ahead_kb to 2048 for better sd card read speeds
Click to expand...
Click to collapse
Firstly, thanks for the update. So it's based on 20140727 where ARMv6 enable and switch to ART runtime, isn't?
Suggestions:
1. Since OTA doesn't work, you may provide just the incremental.zip, whenever last nightly build is available. No need to download full size rom.
2. It will be helpful, if TWRP is capable "one fit for all" , one TWRP for all ROM!
Hey, you push me to buy a new Class 10 SDCard (16 GB maybe). Just kidding. The old one reserved for backup

I tried partitioning SD card using minitool partition, installed TWRP, ROM and GAPPs.
Try to do a dalvik/cache partition but I had failed, TWRP doesn't mount data partition.
I tried more time without success.
Minitool doesn't accept / before name in the labeling and then I try using data e system (instead /data and /system).
Tri to boot mobile, but It doesn't boot (I wait 20 minutes).
Any idea?

xu3sno said:
Firstly, thanks for the update. So it's based on 20140727 where ARMv6 enable and switch to ART runtime, isn't?
Suggestions:
1. Since OTA doesn't work, you may provide just the incremental.zip, whenever last nightly build is available. No need to download full size rom.
2. It will be helpful, if TWRP is capable "one fit for all" , one TWRP for all ROM! (
Click to expand...
Click to collapse
+1

casaprocida said:
I tried partitioning SD card using minitool partition, installed TWRP, ROM and GAPPs.
Try to do a dalvik/cache partition but I had failed, TWRP doesn't mount data partition.
I tried more time without success.
Minitool doesn't accept / before name in the labeling and then I try using data e system (instead /data and /system).
Tri to boot mobile, but It doesn't boot (I wait 20 minutes).
Any idea?
Click to expand...
Click to collapse
Have no experience with Windows Mini Tool. Re-partition SDCard by using Linux (assuming you have a Linux box).
Here what I did as I posted previously.
Execute Terminal as root:
# fdisk -l will show sdcard, /dev/sdx
# fdisk /dev/sdx, follow the instruction to make partition in primary (p): vfat, ext4, swap, ext4.
formatting partitions
# mkfs.vfat /dev/sdx1 (for vfat file system)
# mkfs.ext4 /dev/sdx2 (for ext4 fs)
# mkswap /dev/sdx3 (for swap)
# mkfs.ext4 /dev/sdx4
Since Android based on Linux, making partition using Linux command is more accurate than Windows, IMHO.

xu3sno said:
Firstly, thanks for the update. So it's based on 20140727 where ARMv6 enable and switch to ART runtime, isn't?
Suggestions:
1. Since OTA doesn't work, you may provide just the incremental.zip, whenever last nightly build is available. No need to download full size rom.
2. It will be helpful, if TWRP is capable "one fit for all" , one TWRP for all ROM!
Hey, you push me to buy a new Class 10 SDCard (16 GB maybe). Just kidding. The old one reserved for backup
Click to expand...
Click to collapse
Yes it's based on 20140727, but speculations about ART is wrong. Conn O'Griofa just switched to local androidarmv6 repo of art, not enabled it.
Also here is the commit message: I'm merging this now, but only because it's needed to test changes. I don't intend for ART to be included in builds.
About ota and incremental, I don't use them so probably all upcoming updates will be full zips.
You mean TWRP capable of flashing to internal and external? If yes, it would complicate some things but I will try
casaprocida said:
I tried partitioning SD card using minitool partition, installed TWRP, ROM and GAPPs.
Try to do a dalvik/cache partition but I had failed, TWRP doesn't mount data partition.
I tried more time without success.
Minitool doesn't accept / before name in the labeling and then I try using data e system (instead /data and /system).
Tri to boot mobile, but It doesn't boot (I wait 20 minutes).
Any idea?
Click to expand...
Click to collapse
Then partitioning you don't need to change partitions names, leave it blank. So after partitioning fat32 will have Removable Disk and other * names by default.

HardLight said:
Yes it's based on 20140727, but speculations about ART is wrong. Conn O'Griofa just switched to local androidarmv6 repo of art, not enabled it.
Also here is the commit message: I'm merging this now, but only because it's needed to test changes. I don't intend for ART to be included in builds.
About ota and incremental, I don't use them so probably all upcoming updates will be full zips.
You mean TWRP capable of flashing to internal and external? If yes, it would complicate some things but I will try
Click to expand...
Click to collapse
Thanks for the enlightenment. I did flash 20140727 in internal (have not yet a new 16 GB Class 10 SDCard) using @Notonlyeyes CWM 6.0.5.3 TLS compatible. Go to Settings > Developer option > Select run time to ART > Warning OK > reboot successfully, without error notifications. Don't know if the ART enable or not, feel no different with previous system set to traditional Dalvik :silly:
TWRP, yes just one TWRP capable to flash any ROM (internal or external as yours) and restore nandroid backup. No need to swap between different version of TWRP, or between TWRP and CWM. Apology for so demanding
Wish you luck!

@HardLight: Can you make a TWRP support TLS flash all ROMs?
Because my sccard have class 4, not best for performance.
And I want use Link2SD to install many apps.
How is to increase /system not use OS2SD?

New version
Uploaded latest nightly (20140729)
Made TWRP-MULTI version for flashing ROMs to internal and external memory.
Regular roms flashes normaly to /system and OS2SD roms to /sd-system. Also there is /data for internal and /sd-data for external memory.
Please note that /sd-ext and /sd-system are same partions.
For the people who don't want experimenting flashing to external and internal with same recovery: TWRP-OS2SD version will still work on new roms.
Uploaded new gapps package for new recovery (also compatible with TWRP-OS2SD)
@anhsmile
I've already made it.
Download

HardLight said:
Uploaded latest nightly (20140729)
Made TWRP-MULTI version for flashing ROMs to internal and external memory.
Regular roms flashes normaly to /system and OS2SD roms to /sd-system. Also there is /data for internal and /sd-data for external memory.
Please note that /sd-ext and /sd-system are same partions.
For the people who don't want experimenting flashing to external and internal with same recovery: TWRP-OS2SD version will still work on new roms.
Uploaded new gapps package for new recovery (also compatible with TWRP-OS2SD)
@anhsmile
I've already made it.
Download
Click to expand...
Click to collapse
You're the man :good: You save my day, bro!

[Q] Which CWM version for ext4 fomat, for Cooper?

I am currently using CWM 5.0.2.6 as it is universally suggested the appropriate for Galaxy Cooper.
The problem is that this version can only format the sd card up to ext3, and not ext4.
I want to try the Ulimatum rom with all its goodies and I need ext4 format in partition for Swapall. My sd card is super fast class 10 u3.
I have read that in many cases 6.x.x.x versions end up in blue screens or fail to reboot.
Although I use minitool for partions, when installing a new rom at some point devs ask to format memory before installation, so even if it was originally in ext4 it reverts back to ext3 after the CWM format with the 5.0.2.6 version.
Which version I can safely use for ext4?

tommycr7 said:
I am currently using CWM 5.0.2.6 as it is universally suggested the appropriate for Galaxy Cooper.
The problem is that this version can only format the sd card up to ext3, and not ext4.
I want to try the Ulimatum rom with all its goodies and I need ext4 format in partition for Swapall. My sd card is super fast class 10 u3.
I have read that in many cases 6.x.x.x versions end up in blue screens or fail to reboot.
Although I use minitool for partions, when installing a new rom at some point devs ask to format memory before installation, so even if it was originally in ext4 it reverts back to ext3 after the CWM format with the 5.0.2.6 version.
Which I can safely use for ext4?
Click to expand...
Click to collapse
You can use the ext4 format with CWM without problems, CWM's version is NOT important, but it can't create this typ of partitions, so you need ypur PC to create an ext4 partition (Gparted, Minitool partiton magic...)
If you want to flash The Ultimatum Rom or another CM7 based ROM you must use a CWM 5.x based recovery.
Use CWM 6.x just for CM11
To use ext4 format >>> all versions are safe
To flash the Ultimatum ROM >>> CWM 5.x

[Q&A] MultiSystem for Android

MultiSystem is a powerful tool for locked- and unlocked-bootloader Android devices with many features that at least includes the following:
Keeps stock system partition safe/rooted
Permenant root survival with proper use
MultiROM support via virtual ROMs
Unlimited number of virtual ROMs
Booting options to choose stock, primary, or secondary virtual ROM
Any of the virtual ROMs can work as a recovery replacement
Flashing multiple ROMs at the same time without a reboot
Ability to create/install ROMs on Linux to microSD card
Great performance & battery life on virtual ROMs
Recovery solution to install ROMs or Mods
Easy upgrade to newer versions of Android
Ability to safely apply OTA updates to virtual system
Permissive SELinux and other kernel tweaks
Safe flashing that doesn't trip KNOX flag on Samsung devices
Wrapper script runs via ADB or a Terminal Emulator on device
APK to manage all MultiSystem functions with a nice UI and extra options
Management for the best performance & user experience
Support for all Android devices with microSD card
Portability to almost all devices
Compatibility with all Android versions
Click to expand...
Click to collapse
Q&A​
What is the concept behind MultiSystem?
It runs virtual Android ROMs on microSD, like booting multiple systems on a PC from different partitions/disks. So, your stock system partition is kept safe/rooted. It won't affect performance or anything (might even be better on the virtual system if you've high quality microSD & the device supports its speed). Also, you can freely modify any of the virtual systems & in the worst case, reboot the safe stock system or another working virtual system to recover. So, no root loss or potential damage to the original device partitions.
Click to expand...
Click to collapse
Is it a recovery or an APK tool?
It's a shell script that hijacks system at early boot & force Android to boot from the stock system partition or a virtual system IMG & an APK that manages all booting options, virtual ROMs, and works as a recovery replacement + extra features...
Click to expand...
Click to collapse
Does it work as a recovery replacement?
It IS a POWERFUL recovery replacement. You can do whatever you do in recovery with the APK. HOW? recovery does its magic b/c it doesn't depend on the system & has its own kernel/ramdisk. In MultiSystem, you can boot a virtual ROM from extSD that sure doesn't depend on stock system partition or any of the other virtual ROMs (it does depend on the kernel, which you can't flash on locked devcies anyway). Hence, install, backup, restore, ... & all recovery functions are all possible +++ more features since you're running a full ROM not just a recovery ramdisk like Safestrap.
Bottom Line: I think it's the best & most convenient recovery replacement ever for locked devices & it can also attract unlocked devices for the powerful features, MultiROM, and recovery from within ROM.
Click to expand...
Click to collapse
Can I use FlashFire along with MultiSystem?
Yes. MultiSystem is compatible with FlashFire & fully supports it on stock & virtual ROMs. So, you can use both/any of them for flashing to either a stock or virtual ROM. However, it's recommended to use MultiSystem when flashing to the stock system partition (shouldn't be needed anyway since you can always be safe & flash to your old/new virtual ROMs).
Click to expand...
Click to collapse
Does MultiSystem require FlashFire?
No, MultiSystem doesn't require FlashFire. They're fully combatible though.
Click to expand...
Click to collapse
Would the virtual ROM we install be exactly the one in the stock slot?
In MultiSystem APK, you can create a virtual ROM from stock system, a copy from other virtual ROM, a new IMG, a dev-provided ROM, a flashable .ZIP, ... etc. Literally, your virtual ROMs can be any stock or custom ROM that's compatible with your firmware/kernel.
Click to expand...
Click to collapse
How can it run virtual ROMs from external microSD card?
External MicroSD will be formated into 2 partitions:
exFAT or FAT32 for the 1st partition (your new external storage)
EXT4 for the 2nd partition (your MultiSystem partition)
It'll hijack the system & boot a virtual system from the 2nd partition. The 1st partition will be automatically detected as your extSD.
Click to expand...
Click to collapse
Can I run unrooted virtual ROM for work apps or any other reason?
Yes. You can add unrooted virtual ROM & reboot to it via MultiSystem APK.
Click to expand...
Click to collapse
How do you boot back into a different ROM?
MultiSystem APK manages all functions including ROM activation & reboot to current system, another stock/virtual system, download mode, recovery, ... etc.
Click to expand...
Click to collapse
Will it be OK to still store media like movies/photos/music to extSD?
100% OK; That's my setup a few months ago. 2 virtual ROMs in the SECOND extSD partition in EXT4 format while all personal data are stored on the FIRST extSD partition in exFAT or FAT32 format... TWO COMPLETELY DIFFERET PARTITIONS.
Click to expand...
Click to collapse
How much space are we going to have for virtual ROMs?
The size of the 2nd partition is optional (> 4GB) for your ROMs, but here is an estimated sizes:
1 Virtual ROM Uncompressed = ~2.7 GB ---> ready for running
1 Virtual ROM Compressed = ~1.5 GB ---> for full ROM backups
I'd say better allocate 4 GB for each ROM you plan to run. If you just need one virtual ROM to keep stock system safe, 4 GB 2nd extSD partition is enough; The remaining space is allocated for the 1st extSD partition as your external storage.
For me, I run Linux too from extSD via MultiSystem. So, I've 64 GB extSD card with two partitions 32 GB each.
Click to expand...
Click to collapse
Can I clear up space on an existing SD card and partition it while full or will the entire card need to be wiped and partitioned from scratch?
You need to backup all your files; it'll be wiped & repartitioned.
Click to expand...
Click to collapse
How can I swap microSD cards & be able to run virtual ROMs?
You can swap microSD cards as you wish provided that the device is powered off; don't remove the microSD card when running a virtual ROM. If the new microSD card doesn't include a 2nd parition of available virtual ROMs, the device will boot directly to the stock system.
Click to expand...
Click to collapse
Is there a specific sd card you recommended for this?
I personally have two microSD cards:
SanDisk Extreme Plus 64GB (Up to 80MB/s read speed)
Samsung 64GB PRO (Up to 90MB/s read speed)
You don't have to change your microSD card for MultiSystem; any card you use on your device should work just fine. The need for more speed is relevant when the device supports that speed & if you're going to buy a new card anyway that you may use with a newer device later.
Click to expand...
Click to collapse
Can I copy virtual ROMs to a new microSD card?
Yes. I'll add a feature for swapping microSD cards so that you can backup/restore virtual ROMs from/to the current extSD to/from internal storage as follows:
power off device
use MultiSystem APK to backup your virtual ROMs
insert the new properly formatted microSD,
power on device (it'll boot to stock system)
use MultiSystem APK to restore your virtual ROMs
use MultiSystem APK to activate one of your virtual ROMs
use MultiSystem APK to reboot to any of your ROMs
Click to expand...
Click to collapse
What about other data/cache partitions and internal storage?
Only system img's are in the extSD. All ROMs share all other partitions. This substantially improves the performance & you won't notice any difference between your stock & virtual ROMs. The reason for performance improvement is that EXT4 loop devices are very fast in reading but not in writing. Your system partition is read-only while data (for example) is read write & cache IMGs cause problems like Safestrap issues on ROM slots. Also, you don't have to worry about switching data/settings between ROMs (they're shared), but you just need to regularly backup your important data (which is healthy anyway).
Click to expand...
Click to collapse
Can your elaborate where data is stored?
The userdata partition is also shared; so, you'll have access to all your FULL storage partitions & all apps/data similarly on either stock or virtual ROMs. This also solves the Safestrap issue of having less storage on ROM slots...
Click to expand...
Click to collapse
Will mSDcard incur a significant performance penalty on some devices?
there's no diffrerence between virtual & stock ROMs in terms of performance & battery life. The reason is simple: loop devices associated with the READ-ONLY system IMG mounted from EXT4 partition using a high-quality microSD card IS very fast more than enough.
The read speed is faster than the device can operate anyway + the exact same device should perform on the lowest speed when reading/writing from/to the FAT/FAT32/ExFAT extSD card (where you store your files or even move apps!!!) anyway, which is much slower than the read speed of a loop device mounted from EXT4 partition.
That's why data partition is shared for many reasons, including the poor READ/WRITE performance.
Click to expand...
Click to collapse
If virtual systems are read only, how do we modify them? Do we have to boot to another multisystem rom to modify a virtual rom?
The stock system partition is mounted by default read only & so are the virtual systems. To modify a stock/virtual system, the MultiSystem APK remounts them read/write. You can modify the currently running virtual system, copy it & modify the copy, modify another stock/virtual system.
Click to expand...
Click to collapse
How is a corrupted virtual rom handled? Does it see it's bad and default to stock system?
At early boot, MultiSystem checks for the microSD & active virtual ROM to boot it. There's a boot menu that gives you options to select a stock/virtual system, but it crashes on LP. I'm debugging it, but all functions won't be affected if I removed it. To fail safe, you can remove the microSD card to boot to stock system & restore/repair your virtual ROMs.
UPDATE1: MultiSystem v1.0.1 now allows you to also switch to stock system on boot to repair corrupted virtual IMGs or any other reasons. More options will be added during boot to ultimately select another virtual system if the active IMG is not booting normally (e.g., bootloop after applying a mod or flashing a bad .ZIP).
UPDATE2: Now, on boot, you can choose from two primary/secondary virtual ROM or stock ROM. Flashing multiple ROMs at the same time without a reboot is now possible.
Click to expand...
Click to collapse
How to check if an IMG is corrupted using MultiSystem status?
Code:
Current System IMG: Test_Rom.img
Current System DEV: [B][COLOR="Red"]/dev/block/mmcblk0p23[/COLOR][/B]
When you see "/dev/block/mmcblk0p23"; it's the original system partition; so MultiSystem failed to boot Test_Rom.img, but it should be your current system.
So, the check is simple based on "Current System Device":
/dev/block/mmcblk0p23 = Stock System Partition
/dev/block/loop0 = Virtual System IMG
Note: The block device number (mmcblk0p23) may vary per device & per variant !
Click to expand...
Click to collapse
Does android do any maintenance whatsoever on stored data within /data or external sd? So if I have an app installed on 1 system and not on another system will android see it and clear the data?
No, all storage partitions are shared between ROMs. If you installed an app, it'll be availabe for all of them. Since on locked devcies we're limited to stock manufacturer-based ROMs, this makes the switch between ROMs very convinient (you don't have to worry about your changes/data/setup & storage space on the another ROM; all ROMs share everything except system). However, you should make regular backups in case a virtual ROM (probably with unsafe mods) results in bootloop due to your user data. In this case, it's safe to wipe data & selectively restore apps/data from backup(s). Another advantage of sharing all storage partitions is that your messages/emails/etc received on a virtual ROM are immediated synced (actually shared) to the other ROMs.
Click to expand...
Click to collapse
Will anything like Xposed modify the virtual ROM system IMG as opposed to the stock system IMG?
When you run a Virtual System, everything incldung kernel & apps are hijacked to speak to it as the original system.
Click to expand...
Click to collapse
Can we install AOSP ROMs on locked devices?
You can only install stock/manufacturer-based ROMs on locked devices while unlocked devices can use kexec or flash the required kernel to boot any AOSP/Stock ROMs. I've got a Note 4 Developer Edition & a lot of development is planned to go there (thanks to the unlocked bootloader!) More devices will get supported including unlocked TMO & international variants after adding more features untilizing the unlocked bootloader with kexec'd kernels.
Click to expand...
Click to collapse
Are there limitations to the combinations of ROMs that can be loaded on the "stock" and "virtual" slots? Can you mix KK and LP?
Yes, if they can run on the same kernel. LP won't run on KK kernels & so, you'd have to upgrade the firmware anyway. As for running mixed compatible Android versions, this is possible but your'd have to backup your data before switching ROMs; if it cause no issues, enjoy smooth switch & if it doesn't, do factory reset in recovery & restore your data backup. Backups via MultiSystem are painless.
Click to expand...
Click to collapse
Are applications installed once for each ROM slot that has that applicaiton installed, or can I share a game across ROMs (for instance?)
Everything is shared between ROMs, which is very good for storage & for easy switching. Just make regular backups of your sensitive data.
Click to expand...
Click to collapse
How there are no performance hits while internal storage memory was much faster than any microSD technology?
Read speeds from microSD is very fast compared to write speeds & since virtual ROMs are actually a virtual read-only systems (hence, MultiSystem), they provide a high performance. Moreover, again, read speeds from EXT4 loop devices are higher compared to physical partitions. They're very bad in writing, which we don't need for the read-only "system".
Click to expand...
Click to collapse
Is there a preferred "daily driver" ROM that should be installed in the stock slot?
Uses a stock ODEXED ROM on stock slot for better stability!
Click to expand...
Click to collapse
Is it based off of Safestrap?
Short answer NO. I've been working on MultiSystem & Safestrap for ~7 months. Earlier versions of MultiSystem (called, JasmineREC) was based on Safestrap, but it failed to support newer versions of Android mainly due to TWRP changes in the graphics/UI libraries that cause segmentation fault & the stock kernel framebuffer issues. Then, I decided to find another solution. However, the basic idea of system hijack is powered by Safestrap (or 2nd-init recoveries in general) & all the work done by @Hashcode is GREATLY appreciated.
Click to expand...
Click to collapse
How can it overwrite system files while running?
MultiSystem allows you to install safe mod's or a ROM in full or OTA-like update. It's strongly recommended to install .ZIP files NOT to the current system, b/c some files can not be overwritten while running. So, you can use backup function to copy the current system & install to the new img or any of your other virtual systems. You'll have several options to activate a virtual img & reboot directly to stock system, any virtual img you've activated, quick reboot, Download/bootloader, recovery,... etc.
Click to expand...
Click to collapse
How would I benefit from it if I'm only running Stock ROM or would there be no point for me to install it?
If you run a ROM on stock system, you're vulnerable to root loss unless/untill a new rooting method for LP comes out. MultiSystem gives you the option to run safe-to-mod virtual ROMs + recovery replacement + extra features.
Click to expand...
Click to collapse
Is there a way to convert a normal ROM .ZIP into MultiSystem .IMG?
Create or copy any of your IMGs, activate it & reboot to the active IMG! Then, use FlashFire to flash the ZIP file. However, the updater-script should be safe/compatible. Some devs mount the phyical partition, which will redirect everything to it!!
For example:
Code:
mount(“ext4″, “EMMC”, “/dev/block/mmcblk0p23″, “/system”);
will mount the original system partition; while
Code:
run_program("/sbin/mount", "-t", "auto", "/system");
will mount the current system (stock or virtual). This is recommended/safe.
Click to expand...
Click to collapse
Would a KitKat ROM work with multisystem even though my stock is Lollipop?
Any ROM requires a compatible kernel & modem. So, running KK ROMs requires flashing KK firmware (namely, kernel & modem). This may work with MultiSystem on other devices, especially if the bootlpoader is unlocked. For example, I plan to add features for Note 4 DevED to allow different Android versions (including AOSP, manufacturer-based, & probably Linux systems) by utilizing kernel swapping or execution.
Click to expand...
Click to collapse
When MultiSystem comes out will it be open sourced?
Most probably, haven't decided yet!
Anyway, here's the repository on GitHub: https://github.com/hsbadr/MultiSystem
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Video Tutorials
A quick preview of MultiSystem v1.0 tested on Lollipop for VZW Note 3. The video has been captured on a stable virtual ROM of JasmineROM v5.0.1. It's FULLY compatible with FlashFire on virtual/stock systems. More devices will get supported as well, after required testing.
Facebook: https://www.facebook.com/hsbadr/videos/vb.331488823689599/428178174020663

How to check if you are running a Stock/Virtual System?
There're many ways to check whether you're running a Stock or Virtual system. MultiSystem app should include this simple check at some point. That's important to avoint ruining the Stock system & keep it safe. To make it clear to NOOBZ & anyone who's requesting "another" proof even though I owe hime nothing. Very weird!
Anyway, BusyBox mountpoint applet can print the current block/device mounted to /system mountpoint by running the following command:
Code:
busybox mountpoint -n /system
The stock system is mounts the original system partition:
Code:
[B][COLOR="Red"]/dev/block/mmcblk0p23[/COLOR][/B]
while the virtual system mounts a loop device associated with a system IMG:
Code:
[B][COLOR="Blue"]/dev/block/loop0[/COLOR][/B]
Here're two videos for both stock & virtual systems...
UPDATE:
Now, you could run the following command to print the current system (stock or virtual) and the system device (physical partition or loop device):
Code:
MultiSystem status
Note: The block device number (mmcblk0p23) may vary per device & per variant !

How to repartition microSD card for MultiSystem?
You can use any tool/program for partitioning on Android, Linux, Mac, or Windows. For example, MiniTool Partition Wizard is a good partitioning tool for Windows. So, let's use it for this task. Simply, you need to follow this PDF tutorial (thanks to @carl1961). In sum:
Step 1: delete old partitions on SD card
Step 2: create FAT32 PRIMARY partition
Step 3: create EXT4 PRIMARY partition
Then, apply changes (note that the program UI may get changed in newer versions).
Notes:
This partitioning tutorial doesn't create PRIMARY partitions (it creates logical partitions). So, you need to change "Create As" from "Logical" to "Primary" when creatig a partition.
The sizes of the two partitions are arbitrary depending on number of ROMs you plan to install on the 2nd EXT4 partition.
The 1st partition (check size) is automatically detected as your external storage
In Terminal Emulator or ADB shell, check the existence of the two partitions by running the following command (in red):
Code:
[email protected]:/ # [COLOR="Red"]ls -l /dev/block/platform/msm_sdcc.3/[/COLOR]
drwxr-xr-x root root 2015-05-02 21:08 by-num
lrwxrwxrwx root root 2015-05-02 21:08 mmcblk1 -> /dev/block/mmcblk1
lrwxrwxrwx root root 2015-05-02 21:08 mmcblk1p1 -> [COLOR="Blue"]/dev/block/mmcblk1p1[/COLOR]
lrwxrwxrwx root root 2015-05-02 21:08 mmcblk1p2 -> [COLOR="Blue"]/dev/block/mmcblk1p2[/COLOR]
/dev/block/mmcblk1p1 is mounted by Android as your external storage.
/dev/block/mmcblk1p2 is NOT mounted & will be your MultiSystem partition.
Click to expand...
Click to collapse

How to check microSD card partitions for MultiSystem?
You can use any tool/program for partitioning on Android, Linux, Mac, or Windows. For example, MiniTool Partition Wizard is a good partitioning tool for Windows. So, let's use it for this task. Simply, you need to follow this PDF tutorial (thanks to @carl1961). In sum:
Step 1: delete old partitions on SD card
Step 2: create FAT32 PRIMARY partition
Step 3: create EXT4 PRIMARY partition
Then, apply changes (note that the program UI may get changed in newer versions).
Notes:
This partitioning tutorial doesn't create PRIMARY partitions (it creates logical partitions). So, you need to change "Create As" from "Logical" to "Primary" when creatig a partition.
The sizes of the two partitions are arbitrary depending on number of ROMs you plan to install on the 2nd EXT4 partition.
The 1st partition (check size) is automatically detected as your external storage
In Terminal Emulator or ADB shell, check the existence of the two partitions by running the following command (in red):
Code:
[email protected]:/ # [COLOR="Red"]ls -l /dev/block/platform/msm_sdcc.3/[/COLOR]
drwxr-xr-x root root 2015-05-02 21:08 by-num
lrwxrwxrwx root root 2015-05-02 21:08 mmcblk1 -> /dev/block/mmcblk1
lrwxrwxrwx root root 2015-05-02 21:08 mmcblk1p1 -> [COLOR="Blue"]/dev/block/mmcblk1p1[/COLOR]
lrwxrwxrwx root root 2015-05-02 21:08 mmcblk1p2 -> [COLOR="Blue"]/dev/block/mmcblk1p2[/COLOR]
/dev/block/mmcblk1p1 is mounted by Android as your external storage.
/dev/block/mmcblk1p2 is NOT mounted & will be your MultiSystem partition.
Click to expand...
Click to collapse

How to check MultiSystem Installation?
The 1st thing to do after installing MultiSystem is to check the /MultiSystem directory & its contents (it shouldn't be empty!). Then, check usage by running the following commands in Terminal Emulator or ADB shell:
Code:
su
bash
MultiSystem
If it retuns "MultiSystem not found" or permission denied, try to use open MultiSystem app to Update Configurations & try again. If this does't fix it, try the following command:
Code:
/MultiSystem/bin/MultiSystem
This should work if you've MultiSystem binaries installed in (extracted to) /MultiSystem directory. If so, you can create a symlink in /system/xbin as follows:
Code:
mount -o remount,rw /system
ln -sv /MultiSystem/bin/MultiSystem /system/xbin/MultiSystem
Then, test it by running:
Code:
MultiSystem
The last thing before using it is to check the boot options: reboot & monitor the GREEN LED indicator for 3 seconds (change in the app) , which give you the following options:
Volume UP = Primary virtual ROM
Volume DOWN = Secondary virtual ROM
HOME KEY = Stock System
Sure, you should have installed one or more virtual ROMs.
Backup & restore or creating/installing a virtual ROM are easy as copy & paste: all img's will be at
Code:
/MultiSystem/img/system
To backup a virtual/stock system, you have many options:
Use create function to create from stock system
Use copy function to copy the IMG
Copy & paste with a new name
Use FlashFire (fully supported on virtual/stock ROMs)
...
If you've IMG mounting issues, run the following commands:
Code:
mount -o remount,rw /system
busybox ln -sv /proc/self/mounts /system/etc/mtab
If this doesn't help, try mounting from Terminal Emulator or ADB shell after selecting the IMG in MultiSystem app, by running the following command:
Code:
MultiSystem mount virtual

@hsbadr
Multisystem is running on AT&T
and permissive is activated
I had to add symlink in installer
symlink("/MultiSystem/bin/MultiSystem", "/system/xbin/MultiSystem");
and I had to remove the cleaning script
Also no matter how tried (FlashFire and even Safestrap) the multiSystem apk would not install, I had to copy to sdcard and install with file manager or es explorer

Can i root my 9005?
Hi all, I have the note3 9005xxugboa2 running on kitkat 5.0. The most recent update. Since i updated it its slow as hell. I wanted to root it anyway but now more so. The problem is when i search for the method for my version it brings up too many results of people rooting and upgrading to kitkat. Not rooting from kitkat. Also i dont even know if im at&t lol. I have done this before though. If any1 could point me in the right direction it would save me a few hours later tonight. thanks

Great! I'll release v1.2.1 tonight with minor fixes/updates.

hsbadr said:
Great! I'll release v1.2.1 tonight with minor fixes/updates.
Click to expand...
Click to collapse
hsbadr updat installed fine, took me a couple reboots, but it may just be me. Permissive is set and running on sdcard going to install darkLord beta 2
MultiSystem status show different this time

carl1961 said:
hsbadr updat installed fine, took me a couple reboots, but it may just be me. Permissive is set and running on sdcard going to install darkLord beta 2
MultiSystem status show different this time
Click to expand...
Click to collapse
It is NOT; status NOT Status
Code:
MultiSystem status
Also enjoy bash shell with perfect environment
Code:
su
bash

MultiSystem Video Tutorial
Thanks To: @Tomsgt , aka RootJunky
Don't forget to subscribe & like the video to show appreciation of his great effort & time spent in making the video :highfive::good:

Ok

4GB app storage Patch for gionee m2 8 GB model

4 GB app storage for Gionee M2 / Qmobile M90 / Walton Primo HM
what this patch would do ?
It will solve the problem of low app storage i.e 1.78 GB permanently and you will have 4GB app storage and 1.78 GB internal SD permanently . once you have flashed this patch according to the instructions given below it wont be affected by flashing roms or mods unless you flash your phone with SP tools , even with sp tools you can keep this layout by just replacing the files given in firmware with the files (scatter EBR1 , EBR2 given in Zip file) be sure to check firmware upgrade or you may see PMT changed error.
Which model is this patch for ?
It is for the following
Gionee m2 8GB
Qmobile M90
Walton Primo HM 8 GB
Which model is not supported?
Gionee m2 4GB
Procedure
1) Backup current ROM using CTR or TWRP
2) Download the file (place in external SD otherwise this script will fail as internal SD and data will need to be wiped after this MOD)
3) Flash with TWRP / CTR
4) Restore the backup made with recovery (Crucial, other wise use recovery to advance wipe data and internal storage to make these partitions ready to mount in android OS)
5) Done
6) If you need to flash stock rom with sp-tool and want to retain this setup just replace these EBRs in stock Firmware and use firmware upgrade option (otherwise you may see PMT changed error)
Link for the patch is below
https://mega.nz/#!jU5AybKA!mqlVZl9UjUGlppB89UDT-wAWNmId_PSBzMdN5_Ah2I0

Muhammad Faraz said:
4 GB app storage for Gionee M2 / Qmobile M90
Procedure
1) Backup current ROM using CTR or TWRP
2) Download the file (place in external SD otherwise this script will fail as internal SD and data will need to be wiped after this MOD)
3) Flash with TWRP / CTR
4) Restore the backup made with recovery (Crucial, other wise use recovery to advance wipe data and internal storage to make these partitions ready to mount in OS)
5) Done
6) If you need to flash stock rom with sp-tool and want to retain this setup just replace these EBRs in stock Firmware and use firmware upgrade option (otherwise you may see PMT changed error)
Link for the patch is below
https://mega.nz/#!jU5AybKA!mqlVZl9UjUGlppB89UDT-wAWNmId_PSBzMdN5_Ah2I0
Click to expand...
Click to collapse
I have installed resurrection remix in my device and after that 4 GB of my 8 GB phone has been unmounted. Tried to fix that with your file it didn't worked. Tell me how can i fix that.

Sanchayan De said:
I have installed resurrection remix in my device and after that 4 GB of my 8 GB phone has been unmounted. Tried to fix that with your file it didn't worked. Tell me how can i fix that.
Click to expand...
Click to collapse
This post is not about fixing internal storage not mounting , please search relevant posts however decompile framework.res.apk and replace storage list.xml from working cm based rom . also take boot img from the rom in which storages mount properly

Would this work for the 4gb model?
It worked for my 8gb but my GF has the 4gb

eokwuanga said:
Would this work for the 4gb model?
It worked for my 8gb but my GF has the 4gb
Click to expand...
Click to collapse
No it wont because of practical limitation of internal memory , if you see the partition size of her phone she will have almost 700 MB of internal SD , so swapping would not be possible as internal sd is already smaller than app storage

eokwuanga said:
Would this work for the 4gb model?
It worked for my 8gb but my GF has the 4gb
Click to expand...
Click to collapse
how to install this patch..