Database Develop

[SCRIPTS][GUIDE] Resizing Tattoo partitions - damn simple

Hello Friends,
If you want to re-size you tattoo to have more space for system and data partitions
Here is simple how to do.
No chance of bricking your phone, and it doesn't involve SPL
It works for installed ROM as well as new installations
It was done using the the scripts and information from following thread
http://forum.xda-developers.com/showthread.php?t=717874
Installation instructions:
download FR-recovery-v1.5.3-CustomMTD_S.zip and FR-boot-v1.5.3-CustomMTD_S.zip
reboot to recovery
and use following commands to specify partition size
Explanation of commands used below : after the mtd command first number is system size and the next is cache and remaining will be data partition
choose your cache partition size based on the fact, whether it uses for dalvik-cache or not.
If it used for dalvik-cache do not go less than 80mb (roughly) other wise 20 mb is fine.
Code:
adb shell
mount /sdcard
echo "mtd 200 20" > /sdcard/mtdpartmap.txt
backup your rom
wipe cache + data
If you are 'growing' system, make sure cache and data are clean
if your 'shrinking' system make sure system is clean
To wipe system you need clockworkmod-recovery​
flash FR-recovery-v1.5.3-CustomMTD_S.zip
repeat wipe cache + data
reboot to recovery
At this point if you can either restore your existing installation
OR Flash fresh ROM and other extras
Finally flash FR-boot-v1.5.3-CustomMTD_S.zip
reboot
You could see re-partitioned tattoo with more space for system and data
Here are my Tattoo partition sizes before
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 95188 0 95188 0% /dev
/dev/block/mtdblock3 [B][COLOR="Red"]153600[/COLOR][/B] 137452 16148 89% /system
/dev/block/mtdblock4 [B][COLOR="Red"]153600[/COLOR][/B] 1172 152428 1% /cache
/dev/block/mtdblock5 [B][COLOR="Red"]169088[/COLOR][/B] 56596 112492 33% /data
and after following above instructions
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 95188 0 95188 0% /dev
/dev/block/mtdblock3 [B][COLOR="Red"]204800[/COLOR][/B] 118140 86660 58% /system
/dev/block/mtdblock4 [B][COLOR="Red"]20480[/COLOR][/B] 1164 19316 6% /cache
/dev/block/mtdblock5 [B][COLOR="Red"]251648[/COLOR][/B] 123200 128448 49% /data
It is recommended to use clockworkmod-recovery, although i could use AmornRA recovery (for a fresh install of ROM)
HELP TIPS or POINTS
You don't need to flash both of the files each time you install a new ROM.
You only need to flash the recovery patch once, unless you want to re-size or you installed a new recovery.
The boot patch *must* be flashed after you have installed a new ROM or kernel (boot.img) or for every restoring of backup.
If you are 'growing' system, make sure cache and data are clean
if your 'shrinking' system make sure system is clean
In order to wipe system, data, cache partitions
flash clockworkmod-recovery, and from recovery the recovery menu
go to "mounts and storage" option and wipe required partitions
If you want to restore original MTD, flash original recovery to wipe custom MTD
Here is the information for Developers to include this in their ROMs
ROM Zip Patcher for Devs
To make life even simpler for end users it is possible to integrate the 'patch' within a ROM
AutoMTD_partitionPatcher_v1.5.3.zip
currently Linux only,
within the zip is a tarball, untar that.
get that directory into your PATH, ( or just cd into it )
and then execute
Code:
PatchUpdateScript.sh <zip file to patch>
it will then
create a temp directory ( in your current directory )
copy your zip to it
extract required files
patch update(r)-script
zip and sign.
It simply saves the user from flashing the boot patch after flashing your ROM
Click to expand...
Click to collapse
Hope that is useful
All credit goes to Firerat (Custom MTD Partitions)

i have tested this now!
And it works great...
Although my linux machine did not have the java packs installed to patch the boot.img, i simply made nandroid backup and put img into zip afterwards.
Thanks for guide

Dexter_nlb said:
i have tested this now!
And it works great...
Although my linux machine did not have the java packs installed to patch the boot.img, i simply made nandroid backup and put img into zip afterwards.
Thanks for guide
Click to expand...
Click to collapse
Good that you could use it
I didn't have time to look in to ROM patching script, But how do you mention the partition sizes with this script?
Please let me know.
Cheers

rallapag said:
I didn't have time to look in to ROM patching script, But how do you mention the partition sizes with this script?
Click to expand...
Click to collapse
i initially used the txt file on /sdcard to configure the recovery, then when rom was installed patched it. then a nandroid backup and copied rom to my update.zip and reinstalled rom normally, with patch included..
this solution is of course for one size of mtd's, but it was even easier..

Sorry for my misunderstanding I just went through the autoMTD script and realized what you said earlier.
Auto MTD script patches boot.img, so for patched ROM's as well you need flash FR-recovery with mtdpartmap.txt in user sd card defining partition sizes.
Cheers

[Recovery] Customized CWM 3.0.1.3 fake-flash with ext4 support (03/06/2011)

OK, here's the deal. This is my attempt in customizing CWM. It features several changes in comparison to one from CM source...
Changes
removed menu entries for updating via /sdcard/update.zip (useless for fake-flash users)
stripped some "No" line entries from confirmation menus
removed some insane size values from partitioning list
added some sane size values to partitioning list
added option to add 2nd ext partition (for some data2sd variants)
added block alignment to partitioning part
added advanced backup submenu
Plans
add block alignment to partitioning part
add advanced backup submenu
add some additional wipe options
Issues
mounting /sdcard again after unmounting not possible
Installation
Just copy this file to root of your SD card and rename it to update.zip. You can also use previous non-customized version.
Source
Source for this project is available on GitHub.
CAUTION! This is still in test phase. And your phone may explode suddenly if you're not careful enough. But in general it is pretty much safe (if you stand several feet from your phone). If you encounter any problems relevant logs are /tmp/recovery.log and /data/sdparted.log which I will need for debugging.

Hi BlaY0!
does this file works even on s-off legend?
Thx

goose2600 said:
Hi BlaY0!
does this file works even on s-off legend?
Thx
Click to expand...
Click to collapse
Yes. Have fun!

Thanks a lot for this
Sent from my Legend using Tapatalk

goose2600 said:
does this file works even on s-off legend?
Click to expand...
Click to collapse
Yes, but why would you do that???
So you buy a Ferrari and put in the engine of Fiat 600? I don't get it

Thanks man, it's great.

goose2600 said:
Hi BlaY0!
does this file works even on s-off legend?
Thx
Click to expand...
Click to collapse
Well, sort of. If you go to recovery via ROM manager, you will not get CWM 3.0.0.6 and if you go to recovery from HBOOT you will not get CWM 3.0.0.6.
The only way is to go to recovery and then choose "Apply update.zip".
So, yes, it works. But it's a bit tricky.

Thanks a lot!
Really helped me!

Fantastic. Great stuff!

This is Super! Been stuck with a rom with ext4 enabled for quite some time now. And this worked!
Blay0! your the man!
Sent from my Legend using XDA App

thanks!but i don't understand !!!I'm not good at these things
i have update the file by recovery and now?where should I set???

No, you have only to put the update.zip on SD-card and that´s it.
Than you have CWM recovery in version 3.0.0.6...

My ext4 partition still can't mount. Is there any way to collect recovery logs or something?

CfYz said:
My ext4 partition still can't mount. Is there any way to collect recovery logs or something?
Click to expand...
Click to collapse
You can run
Code:
adb shell dmesg
just after trying to mount the sd-ext. Then put it in this thread.
BTW, BlaY0, if i correctly understood, in your B ROM ext4 creates with huge_files option. My ext4 partition was created being under your rom, and all had run smooth except current CWM could not mount partition saying
Code:
<6>[ 37.128723] yaffs: dev is 187695106 name is "mmcblk0p2"
<6>[ 37.128936] yaffs: passed flags ""
<4>[ 37.129150] yaffs: Attempting MTD mount on 179.2, "mmcblk0p2"
<6>[ 37.129791] yaffs: dev is 187695106 name is "mmcblk0p2"
<6>[ 37.130004] yaffs: passed flags ""
<4>[ 37.130371] yaffs: Attempting MTD mount on 179.2, "mmcblk0p2"
<3>[ 37.131561] EXT4-fs: mmcblk0p2: Filesystem with huge files cannot be mounted read-write without CONFIG_LBD.
until i turned this option off. Under working system with your kernel/modules ext4 mounts good even with huge_file option.

saw81 said:
thanks!but i don't understand !!!I'm not good at these things
i have update the file by recovery and now?where should I set???
Click to expand...
Click to collapse
as picz mentioned, you put this file in the root of your sd card.
than you switch off your phone. than on it holding the Vol- and the power button. Than select recovery. ant the red [!] screen. press Vol+ and the power button. wait for a blue menu list at the top of the screen. than select update.zip...
this is Fake Flash....

BlaY0 said:
OK, I made this update to S-ON recovery that adds ext4 support. Flash it just after you enter CWM. Test and report...
PS: This is temporary solution.
Click to expand...
Click to collapse
working perfectly. i've successfully backup and restore a CM7 with TGF's ext4 data2ext mod. everything works normal.

Kot_Ik said:
BTW, BlaY0, if i correctly understood, in your B ROM ext4 creates with huge_files option. My ext4 partition was created being under your rom, and all had run smooth except current CWM could not mount partition saying
Code:
<6>[ 37.128723] yaffs: dev is 187695106 name is "mmcblk0p2"
<6>[ 37.128936] yaffs: passed flags ""
<4>[ 37.129150] yaffs: Attempting MTD mount on 179.2, "mmcblk0p2"
<6>[ 37.129791] yaffs: dev is 187695106 name is "mmcblk0p2"
<6>[ 37.130004] yaffs: passed flags ""
<4>[ 37.130371] yaffs: Attempting MTD mount on 179.2, "mmcblk0p2"
<3>[ 37.131561] EXT4-fs: mmcblk0p2: Filesystem with huge files cannot be mounted read-write without CONFIG_LBD.
until i turned this option off. Under working system with your kernel/modules ext4 mounts good even with huge_file option.
Click to expand...
Click to collapse
Yeah, formatting ext4 partition under B or CM adds "huge_file" to the filesystem features by default. Actually this is default for mke2fs config (will be changed in the next B release). My customized and also CM kernal got this LBD alias LBDAF support built in but stock kernel from recovery doesn't hence the error. Unfortunately LBD support can't be built as a module so there is actually no way to add this support to stock recovery if your Legend is S-ON.
But... since LBD alias LBDAF and consequently "huge_file" support in ext4 is actually support for files bigger than 2TB we kinda don't need it I guess so what we can do is as you suggested remove "huge_file" feature from ext4 filesystem like this:
Code:
tune2fs -O ^huge_file /dev/block/<ext4_partition>
e2fsck -pf /dev/block/<ext4_partition>
...and we do this via recovery or system but ext4 partition shouldn't be mounted at that point! So unmount it first or disable data2ext/a2sd and reboot, do da above job, enable data2ext/a2sd and reboot again. To check if "huge_file" feature is actually enabled in your ext4 filesystem you do:
Code:
tune2fs -l /dev/block/<ext4_partition>
...and check "Filesystem features:" line.

Customized CWM 3.0.0.6 for S-ON Legends (fake-flash)
OK, here's the deal. This is my attempt in customizing CWM.
Check 1st post for update!

hi BlaY0 !
can you release img for S-off users ? (i know we can use this but i like IMG)

New update. Check 1st post.
jinxul said:
hi BlaY0 !
can you release img for S-off users ? (i know we can use this but i like IMG)
Click to expand...
Click to collapse
No, I decided not to. Will stick to fake-flash. But if you want, you can do it yourself and post it here...
EDIT: Rather post img in the other thread.

[Gen9]Modified init for HDD and flash G9, 350MB & "no-busybox" archos.ext4

[Gen9]Modified init for HDD and flash G9, 350MB & "no-busybox" archos.ext4
Updated version- should work on HDD models too
Disclaimer: use this at your own risk. I'm not responsible if your tablet wants to kill you.
Here's modified init for suduru_petru's rooted 3.2.80 firmware
Now also for HDD models
Tests were done by philmein
Before you start
-make sure that you have more than 512MB free space in internal memory (/data) or more than 350MB if you want to use attached system file
Features
-system image runs from /data partition (internal flash)
-dalvik-cache wipe is done for system updates, also can be triggered manually
Installation
1. Install SDE menu- INSTRUCTIONS
2. Prepare required files- copy archos.ext4.update file to the root of the card (if you have archos.ext4 just rename it to archos.ext4.update)
NOTE this MUST be archos.ext4.update file, zipped files will not work
3. Boot to Recovery (Volume+ and Power), then Developer Edition Menu -> Flash Kernel and Initramfs. New drive will popup on your pc, copy kernel_test_hdd7.zip contents on it
NOTE- you need zImage and initramfs.cpio.gz files, zip will not work
Click Ok to flash kernel.
4. Now boot to Special Developement Edition
NOTE- first boot will take longer (files must be copied) so don't panic
5. Do not delete archos.ext4.backup file from storage- this is a backup in case you have to do data wipe (Reset Android)
6. Enjoy
Usage:
To update system: copy archos.ext4.update file to storage and reboot
To wipe dalvik-cache: place an empty file wipe-dalvik.update in the storage and reboot- you can use djnilse's script
If you had to wipe data (Reset Android): don't worry, just reboot
If you had to format storage: make sure that when system boots
Download:
Kernel and initramfs
http://dl.dropbox.com/u/14106051/archos/kernel_hdd_test7.zip
smaller archos.ext4.update
This is shrinked suduru_petru's rooted firmware, now only 350MB
No other changes done
http://www.mediafire.com/?eqwlocit0nniw7k
"No busybox" archos.ext4
http://www.mediafire.com/?fzizmy60e769ow9
This is only rooted archos.ext4.update, custom busybox seems to make problems with USB host functions
Info for developers: http://forum.xda-developers.com/showpost.php?p=22310057&postcount=13
Old version
What is changed
-dalvik-cache is wiped for every firmware update
-dalvik-cache wipe can be started manually
How does it work
Dalvik-cache wipe is higly recommended with every firmware update (or replacing stock with a modified one), also can help with app FC's.
For every firmware update- archos.ext4/squashfs.update file- dalvik-cache is wiped automatically (and you can't do anything about it )
To trigger dalvik-cache wipe on your own place a file named wipe-dalvik.update in internal storage (/data/media) and reboot.
NOTE: first boot after wipe will take longer
Installtion
Zip contains both zImage and initramfs.cpio.gz, installation as usual: Developer Edition Menu -> Flash Kernel and Initramfs then copy zImage and initramfs.cpio.gz to the new drive that pops up on the pc and click OK on the tablet.
DOWNLOAD
http://dl.dropbox.com/u/14106051/archos/kernel.zip
MD5: 8EB000BC1105A3613B35C8F82F35EF41
Info for developers: http://forum.xda-developers.com/showpost.php?p=22179468&postcount=8
EDIT:
Script for easy creating wipe-dalvik.update file by djnilse: HERE

hi, Let's see if I understand correctly. for updating is necessary first copy new firmaware and empty file called "wipe-dalvik.update" in /data/media. reboot table in sde and copy zImage and initramfs.cpio.gz. rebooting and delete "wipe-dalvik.update". is correct? thank you

hitman72 said:
hi, Let's see if I understand correctly. for updating is necessary first copy new firmaware and empty file called "wipe-dalvik.update" in /data/media. reboot table in sde and copy zImage and initramfs.cpio.gz. rebooting and delete "wipe-dalvik.update". is correct? thank you
Click to expand...
Click to collapse
Not exactly.
When firmware is updated -archos.[...].update file- dalvik-cache is wiped anyway without any option not to wipe it.
Wipe-dalvik.update file is needed if you want to wipe dalvik-dache eg. when apps have a lot of FC's.
But in order to have possibility to wipe dalvik-cache you have to flash modified init posted here (for ease of use zImage is included in zip, flash it as usual)
tapatalked from Desire

good work
this will be a better alternative for cleaning the system
i've made a script to write and remove the dalvik-wipe.update to storage
simply run it with ScriptManager or with a Terminal Emulator
this script doesnt need root rights
@gen_scheisskopf you could include a link to this in your post
and THIS IS NOT A test file
simply just rename it in dalvik.sh
run it with:
Code:
sh dalvik.sh
and dont forget to hit the thanks button
------------------------EDIT--------------------------------------------
don't hit the thanks button, this was not difficult
try to make a shell script on your own Here a tutorial have fun
-----------------------EDIT:10.02.2012------------------------------------
i ve removed the option to wipe the dalvik-wipe.update because its not necessary

djnilse said:
good work
this will be a better alternative for cleaning the system
Click to expand...
Click to collapse
Dalvik-cache wipe is included in all "standard" recoveries and it really can help in various situations (sometimes for bootloop also)
djnilse said:
i've made a script to write and remove the dalvik-wipe.update to storage
simply run it with ScriptManager or with a Terminal Emulator
this script doesnt need root rights
@gen_scheisskopf you could include a link to this in your post
and THIS IS NOT A test file
simply just rename it in dalvik.sh
run it with:
Code:
sh dalvik.sh
Click to expand...
Click to collapse
There is no need to remove wipe-dalvik.update, init does this just as with firmware .update files.
djnilse said:
and dont forget to hit the thanks button
Click to expand...
Click to collapse
Oh, c'mon......

gen_scheisskopf said:
Dalvik-cache wipe is included in all "standard" recoveries and it really can help in various situations (sometimes for bootloop also)
There is no need to remove wipe-dalvik.update, init does this just as with firmware .update files.
Oh, c'mon......
Click to expand...
Click to collapse
i worked for that about an hour, now i know more about linux shell scripts
and for the changes in the init
can it be modified with all kind of linux shell commands ???

djnilse said:
i worked for that about an hour, now i know more about linux shell scripts
and for the changes in the init
can it be modified with all kind of linux shell commands ???
Click to expand...
Click to collapse
Ask letama, he knows initrd best
tapatalked from Desire

I've checked supercharger script and honestly I'm not sure if it's absolutely safe to use:
-dalvik-cache wipe is done when Android does not run in every device I've layed my hands on (samsung i5700, htc desire, prestigio multipad 3384 and android hardware belonging to my friends)
-if dalvik-cache is not present system creates it during system boot
-supercharger wipes dalvik-cache also during system boot so there is a possibility of conflict between wiping and creating processes
Modified init wipes dalvik-cache before Android starts to boot so it is 100% safe, and djnilse created a nifty script to create wipe-dalvik.update file without pc access

New version in the first post
Should work good on HDD models also

How long is a long time?
I have had mine on the Archos logo for around an hour now, and just a little worried that it is not going through.
EDIT: I use the HDD model

thefunkaygibbon said:
How long is a long time?
I have had mine on the Archos logo for around an hour now, and just a little worried that it is not going through.
EDIT: I use the HDD model
Click to expand...
Click to collapse
Should be not more than a minute before bootanimation kicks in.
Did you boot to SDE with card inserted?

gen_scheisskopf said:
Should be not more than a minute before bootanimation kicks in.
Did you boot to SDE with card inserted?
Click to expand...
Click to collapse
There is no card reader on the HDD model, so I have it on the root of the HDD (I think I have understood that right, but maybe not.)
Do I need a USB card reader and do it through the 3G port?

thefunkaygibbon said:
There is no card reader on the HDD model, so I have it on the root of the HDD (I think I have understood that right, but maybe not.)
Click to expand...
Click to collapse
Sorry, I didn't know that there is no SD slot.
Give me 5 minutes.

Corrected version of initramfs and updated instructions in the first post.
Sorry for trouble, Archos says that all G9 devices have SD card slot.
EDIT:
Bug fixed, please redownload (same link)

gen_scheisskopf said:
Corrected version of initramfs and updated instructions in the first post.
Sorry for trouble, Archos says that all G9 devices have SD card slot.
EDIT:
Bug fixed, please redownload (same link)
Click to expand...
Click to collapse
You sir, are a genius! Working brilliantly (so far)
Thanks.

Another stupid bug fixed, please update
http://dl.dropbox.com/u/14106051/archos/kernel_hdd_test7.zip

i seem to have the file ext4 on my hdd and somwhere in my internal storage my internal storage has dropped by500mb
i know i should keep the one on my hdd but how do i get rid of the one in my internal storgage i would like to reclaim that space
i think its here /data/local/archos.ext4 but i cannot see it in astro or file manager
250gb hdd model

philmein said:
i seem to have the file ext4 on my hdd and somwhere in my internal storage my internal storage has dropped by500mb
Click to expand...
Click to collapse
It's normal (as expected)
philmein said:
i know i should keep the one on my hdd but how do i get rid of the one in my internal storgage i would like to reclaim that space
i think its here /data/local/archos.ext4 but i cannot see it in astro or file manager
Click to expand...
Click to collapse
The one on HDD is a backup file (in case of wiping data).
You can't delete the one from flash- that is system image.
I can try to modify init so system file runs from HDD (not internal flash) but this may deplete your battery very fast

if its normal thats fine i still have 500mb free
i have hdd test 3 on mine is that ok do i just updat to hdd test 7 when a new rom comes out?
regards phil

philmein said:
if its normal thats fine i still have 500mb free
i have hdd test 3 on mine is that ok do i just updat to hdd test 7 when a new rom comes out?
regards phil
Click to expand...
Click to collapse
Flash test7- it is updated version (cleaner work)

[Q]Why can't my Galaxy Mini boot a CustomROM

Hi all,
I have kind of a strange problem with my girlfriends Galaxy Mini S5570.
It was bought with Android 2.2.1 installed, later on I flashed a 2.3.4 Stock ROM with Odin.
What I try to achieve now is using a CustomROM and so far I've tried to flash CM7.2 and emanoN 6, both without luck. Here comes what I did and what happens for both ROMs:
using Odin 4.42 and without SIM or SD installed, I flashed a Stock 2.3.6 (XWKTN) (PASS)
also with Odin I flashed CWM 4 (PASS)
in order to flash the CustomROM of my choice I wiped everything on the Galaxy (data/cache/DalvikCache)
SD card has a 256MB ext4 partition that is mounted later as /sd-ext
using zip installation I flashed CM7.2 stable or later emanoN 6, flashing went fine
at time of reboot it always gets stuck
Everytime I try to boot one of the CustomROMs it shows the initial Model information, then the boot animation that ends with the shiny SAMSUNG text, then screens turns black but backlight still on and every couple of minutes the phone vibrates very short.
The phone can be accessed by adb and responds fine there but screen is always black with dimmed backlight. All relevant volumes are mounted. data partition has some 10,000kB on it which varies up and down by some kB.
Code:
# df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 143016 32 142984 0% /dev
tmpfs 143016 0 143016 0% /mnt/asec
tmpfs 143016 0 143016 0% /mnt/obb
/dev/stl14 25436 4200 21236 17% /cache
/dev/stl13 182672 10668 172004 6% /data
/dev/stl12 211400 166728 44672 79% /system
/dev/block/mmcblk0p2 245692 4236 241456 2% /sd-ext
/dev/block/vold/179:1
1678340 98384 1579956 6% /mnt/sdcard
/dev/block/vold/179:1
1678340 98384 1579956 6% /mnt/secure/asec
Code:
# ls /system
ls /system
T9DB bin etc lib misc xbin
TEAM build.prop fonts lost+found usr
app cameradata framework media wifi
# ls /data
ls /data
aeqcoe.txt dalvik-cache lost+found system
anr data misc system_ordered
app data_ordered property tombstones
app-private dontpanic radio zipalign.db
backup gps sd_ordered zipalign.log
cache local secure
cache_ordered log soundbooster.txt
# ls /sd-ext
ls /sd-ext
lost+found
# ls /mnt/sdcard
ls /mnt/sdcard
Android LOST.DIR
DCIM emanoNROM-v6-signed.zip
When trying emanoN 6 after CM7.2 failed, of course I went through the full procedure again, starting with Stock ROM via Odin. Also I tried using CWM 5 which I zip-installed from within CWM 4. Both ROMs hav the exact same behavior and I have no idea what causes it.
I can always access CWM or Download mode, nothing looks bricked to me. When I flash a Stock ROM again, no matter which, it just boots and runs fine.
Now it's my hope that anybody has seen this before and can point me to where the problem is.
Thanks and very best regards,
Peter

Did u root your your device
Sent from my GT-S5570 using Tapatalk 2

Did u do a full wipe ?
Sent from my GT-S5570 using Tapatalk 2

Hi Messi10,
at which point is rooting required when installing a pre-rooted ROM like CM7.2 or emanoN? Did I miss something here? I didn't apply any separate root solutions in the process.
Hi R.A.G.E,
yes I did. I always wiped data/cache/Dalvik Cache and once even Battery Stats. All content in data that I've posted in my initial post came from first boot of the CustomROM, in this case it was emanoN.
Thanks, Peter

PeBo75 said:
Hi Messi10,
at which point is rooting required when installing a pre-rooted ROM like CM7.2 or emanoN? Did I miss something here? I didn't apply any separate root solutions in the process.
Hi R.A.G.E,
yes I did. I always wiped data/cache/Dalvik Cache and once even Battery Stats. All content in data that I've posted in my initial post came from first boot of the CustomROM, in this case it was emanoN.
Thanks, Peter
Click to expand...
Click to collapse
For me i rooted my device first then i installed CMW i don't have any problem when flash roms
Sent from my GT-S5570 using Tapatalk 2

I always use 2.3.4 as my base and everything is always fine.
Do u have the sim inserted when u boot the phone after flashing a rom?

roofrider said:
I always use 2.3.4 as my base and everything is always fine.
Do u have the sim inserted when u boot the phone after flashing a rom?
Click to expand...
Click to collapse
Hi roofrider,
I used XWKTN and also XWKTH, both are 2.3.6. I did because that is told to be the base ROM for the emanoN. In his TUT parasmi says any 2.3.x would do as base but I tried XWKTH many times as well which is the one he mentions in his changelog.
When booting after flash I tried both, with and without SIM inserted. Makes no difference.
Is there anything I can check via adb to see where the phone gets stuck?
Where can I find the OS log files? Would like to have a look at them.
This it what it shows in dmesg every now and then:
Code:
<3>[ 1547.963619] kgsl kgsl: |kgsl_yamato_waittimestamp| Device hang detected wh
ile waiting for timestamp: 6, last submitted(rb->timestamp): 7, wptr: 87

ya, just do
adb logcat > log.txt
Then later terminate it with ctrl+c

wipe is also needed after flash, so wipe two times before installing and after ibstalling

dheeraj (dhlalit11) said:
wipe is also needed after flash, so wipe two times before installing and after ibstalling
Click to expand...
Click to collapse
not mandatory (i mostly don't do), but if things don't work, sure why not.

roofrider said:
ya, just do
adb logcat > log.txt
Then later terminate it with ctrl+c
Click to expand...
Click to collapse
Thanks, I did that now during a full boot until the first time it vibrated after a couple of minutes.
Condition: no SIM, SD with Ext4fs and VFAT, data/cache/dalvik cache wiped -> first boot of emanoN v6
As soon as the phone booted up I fired adb logcat, even before adb was ready. First response was "- waiting for device -", then it captured as per attachment.

Actually ur phone boots just fine, i see this a lot
Code:
W/SharedBufferStack( 2782): waitForCondition(LockCondition) timed out (identity=1, status=0). CPU may be pegged. trying again.
but then this is just a warning..
So ur display is actually just freezing...
Pulling out the battery and rebooting again gives the same result?
Also the bootanimation does not end with a samsung logo..at least not for CM7.
Also it vibrating once just after the bootanimation(or end stage of bootanimation) is normal.

roofrider said:
Actually ur phone boots just fine, i see this a lot
Code:
W/SharedBufferStack( 2782): waitForCondition(LockCondition) timed out (identity=1, status=0). CPU may be pegged. trying again.
So ur display is actually just freezing...
Pulling out the battery and rebooting again gives the same result?
Also the bootanimation does not end with a samsung logo..at least not for CM7.
Click to expand...
Click to collapse
Pulling battery is the only way to get out of it. At next reboot the same happens again.
This log was from emanoN v6. It checks if there is a custom bootanimation on SD card, if not it shows the Samsung default. You can see this in early stages of booting in the log.
Anyway, I have not confirmed the details via log file but the behavior was exactly the same when CM7.2 was flashed.
The vibration is not at this early stage but after having it some minutes on the table... untouched. In the log a whole lot of things happens again then. Could this be caused by a partly restart of something? Also it vibrates not once but endless times if I just leave it in this state. (Sorry, I still have the 5 minutes time barrier for editing/posting)
Now what could cause this message which appears a thousand times?
@dheeraj: I have wiped so many times: before, after and also before + after flashing. I'm sure it's nothing that can be solved with another wipe.

I'm exactly not sure..but googling this error helps a little...try searching maybe u'll find something.
--sry.
try running logcat longer and check..that should tell a little more.
possible reasons:
-try booting without SD card, it could be cos of a2sd (just a blind guess).
-maybe a certain app that is included is the culprit (again just a guess).
--OT--
U've been a member since 2010 and this is the 1st time ur posting!

[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 need to correctly repartition microSD card into two partitions:
exFAT or FAT32 for the 1st partition (your new external storage)
EXT4 for the 2nd partition (your MultiSystem partition)
Use the directions in this post!
You should check your 2nd SD partition in EXT4 format mounted to /MultiSystem:
check that the /MultiSystem directory exists after a reboot
check that the 2nd SD partition (/dev/block/mmcblk1p2) is mounted to /MultiSystem by running the following command in Terminal Emulator or ADB shell:
Code:
mount | grep /MultiSystem
The output should be:
Code:
/dev/block/mmcblk1p2 /MultiSystem ext4 rw,seclabel,relatime,data=ordered 0 0

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
Pressing nothing will boot the active system: stock or primary virtual 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

This is the one thing missing from my Note 4. Thank you for the detailed Q&A and i can't wait to try this tool out.

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:

Thank you so much for this! My multbooting-manic* appetive is wet (read: RAVENOUS) :laugh: Thank you also for the extremely comprehensive and clear FAQ, which answered nearly every question that I had, as well as some other very helpful ones that hadn't even occurred to me! I just have a few other questions that arose when planning my own personal setup with the incredible tool (just to be clear, I don't plan on updating to TW LP.... propbably for a while). Also this is what I'm thinking for a 3x boot setup: stock odexed ROM (first question). virtual slot 1: Dynamic Kat 4.2 (KK), v-slot 2: AOSP LP... think I'm leaning towards XenonHD.
Questions:
1. Do you have a recommendation for a custom (Kit Kat) ROM compatible with the N910T? AFAIK JasmineROM isn't compatible, looks nice though. Am I correct in my interpretation that any stock-ish odexed ROM would be a good base for a stable installation? I need to look through the DevDB again, but just wondering if you had a recommendation.
2. I just want to make sure about this, because you asked and answered in the OP Would you consider using the stock kernel with the ROM in stock to be "best practice", or does it matter? I just ask because I've been a longtime supporter of the AEL kernel and would prefer to use that (with both the ROM in stock and v-slot 1). Thoughts?
3. RE: the BusyBox installation in the stock slot, is there a particular version/installer that you recommend? I usually use Sterickson's but have also used BB on Rails. both of which install to system/xbin (and remove any former installation from sbin), so just wondering if it made a difference.
Thank you so much again! BTW, just thought I'd mention that I while writing this, I saw that Amazon had PNY 128GB UHS-1 micro sd's for $75 and ordered one . I currently have 2 of that same card, one in my N4 and one in my Note 10.1 2014 and really think that PNY storage products in general are excellent. Just thought I'd put the word out.... curious why this topic made me think of that...
*multibooting-maniac adj. Descriptor of a person and/or geek who has "Hackintosh"-based triple boot installations on two or more personal conputers and needs the computer that they carrry around in their pocket to catch up with the rest of the gang :laugh:

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
First off, this sounds like a really nifty and useful program/app/modification? Sorry, I don't know what to really call it.
As per the above quoted, I am a little confused. The part about (same kernel)? I may be missing something but in regards to being able to run Lollipop ROM along with KitKat ROM either of which located as primary or virtual (SDcard) , how is this actually possible? As far as I know, while we can use say COD6 - bootloader & modem, I am not aware of an actual "Kernel" that could support both? Hope I am voicing this correctly... :silly:
Other question and I apologize if I missed it as I tried my best to read the well detailed OP's...
- What actual recovery is being used? Can I assume TWRP, and if so, is it a "Special - modified version" OR can we use any of the later TWRPs at our choice?
Thanks! Interested in following this!

jazzmachine said:
Thank you so much for this! My multbooting-manic* appetive is wet (read: RAVENOUS) :laugh: Thank you also for the extremely comprehensive and clear FAQ, which answered nearly every question that I had, as well as some other very helpful ones that hadn't even occurred to me! I just have a few other questions that arose when planning my own personal setup with the incredible tool (just to be clear, I don't plan on updating to TW LP.... propbably for a while). Also this is what I'm thinking for a 3x boot setup: stock odexed ROM (first question). virtual slot 1: Dynamic Kat 4.2 (KK), v-slot 2: AOSP LP... think I'm leaning towards XenonHD.
Questions:
1. Do you have a recommendation for a custom (Kit Kat) ROM compatible with the N910T? AFAIK JasmineROM isn't compatible, looks nice though. Am I correct in my interpretation that any stock-ish odexed ROM would be a good base for a stable installation? I need to look through the DevDB again, but just wondering if you had a recommendation.
2. I just want to make sure about this, because you asked and answered in the OP Would you consider using the stock kernel with the ROM in stock to be "best practice", or does it matter? I just ask because I've been a longtime supporter of the AEL kernel and would prefer to use that (with both the ROM in stock and v-slot 1). Thoughts?
3. RE: the BusyBox installation in the stock slot, is there a particular version/installer that you recommend? I usually use Sterickson's but have also used BB on Rails. both of which install to system/xbin (and remove any former installation from sbin), so just wondering if it made a difference.
Thank you so much again! BTW, just thought I'd mention that I while writing this, I saw that Amazon had PNY 128GB UHS-1 micro sd's for $75 and ordered one . I currently have 2 of that same card, one in my N4 and one in my Note 10.1 2014 and really think that PNY storage products in general are excellent. Just thought I'd put the word out.... curious why this topic made me think of that...
*multibooting-maniac adj. Descriptor of a person and/or geek who has "Hackintosh"-based triple boot installations on two or more personal conputers and needs the computer that they carrry around in their pocket to catch up with the rest of the gang :laugh:
Click to expand...
Click to collapse
@jazzmachine Curious if you ever found out anymore information on this elsewhere that I may be missing. I see it's reference, youtube videos, and whatnot coming up in various threads but little known as far as it's usability on a (910T) Note 4 - mainly what kernel has to be used that supports kexec on STOCK?

lazer9 said:
@jazzmachine Curious if you ever found out anymore information on this elsewhere that I may be missing. I see it's reference, youtube videos, and whatnot coming up in various threads but little known as far as it's usability on a (910T) Note 4 - mainly what kernel has to be used that supports kexec on STOCK?
Click to expand...
Click to collapse
Hey there man, wish I could provide you some useful info wrt this project, but unfortunately I've been unable to find anything directly relevant myself. However, this: http://forum.xda-developers.com/note-4/general/dual-boot-n910f-snap-dragon-variant-t3065211 (shout out and thanks to @aukhan!), which you've likely seen as well, has captured my interest. There are direct references to our device in that thread, but I haven't really been able to make any attempts towards making use of it due to "life stuff" conflicting with my phone tinkering / XDA activity . I haven't been able to follow it as much as I'd like (or hit you up with any actual "useful" info ) but at this point (from what I've read) it seems more... practical wrt our N910Ts.
BTW, I've read and been really appreciative of your contributions to the Emotion kernel thread :good: Definitely keep me posted if you make any progress towards the "multi/dual boot dream"... I'll do the same

jazzmachine said:
Hey there man, wish I could provide you some useful info wrt this project, but unfortunately I've been unable to find anything directly relevant myself. However, this: http://forum.xda-developers.com/note-4/general/dual-boot-n910f-snap-dragon-variant-t3065211 (shout out and thanks to @aukhan!), which you've likely seen as well, has captured my interest. There are direct references to our device in that thread, but I haven't really been able to make any attempts towards making use of it due to "life stuff" conflicting with my phone tinkering / XDA activity . I haven't been able to follow it as much as I'd like (or hit you up with any actual "useful" info ) but at this point (from what I've read) it seems more... practical wrt our N910Ts.
BTW, I've read and been really appreciative of your contributions to the Emotion kernel thread :good: Definitely keep me posted if you make any progress towards the "multi/dual boot dream"... I'll do the same
Click to expand...
Click to collapse
Thanks, I will have a look at the thread you mention. It just seems odd that this post popped up in here some time ago with some questions/replies and went completely abandoned, lol :laugh:
Like one of those teaser posts I guess. I've tried to "Google" around and found some YouTube videos along with active threads on different sections of XDA but anything coming down to usability on our N910Ts and for that matter, other devices, seem to indicated the need for a kexec Kernel in "Stock" Rom. I have yet to find/confirm ANY 910T kernel providing kexec support oddly enough but then again, maybe my google skills are lacking. :cyclops:

Primary system IMG
I can't seem to get MultiSystem to create my primary system IMG. I let it sit while the red LED is on and for quite some time afterwards but it only creates an empty file. Any suggestions would be much appreciated.

Just happened to stumble across this, I used multirom on my older lg optimus g pro.... It worked goud until I had a few custom roms , then it just went all to hell... I think I may give this a try.

No Virtual IMG Mode works...
hsbadr said:
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 !
Click to expand...
Click to collapse
So I've chosen the image and tried booting it by VOL UP and over UI reboot into virtual/ active partition... both failed
/block/loop0 doesn't work, remains mmcblk0p23 though it changed to IMG Stock
Thanks for any help!!!
---------- Post added at 21:53 ---------- Previous post was at 21:48 ----------
fegar said:
I can't seem to get MultiSystem to create my primary system IMG. I let it sit while the red LED is on and for quite some time afterwards but it only creates an empty file. Any suggestions would be much appreciated.
Click to expand...
Click to collapse
How does the log show the empty file? Exit 0 or something like that? Or do you see a 0 MB sized file created?
Have you checked the MultiSystem installation?