Related
I was trying to upgrade to CM6 from CM5 and was facing lot of issues so I followed below process and got it worked. I thought of sharing it with everybody as lot of person are having issues.
I know most of the information is available on XDA but not on a single place.
I have made a separate thread because A2sd and SWAP are not supported by CM6 officially.
This is not an official method of installing CM6, this is how I got it worked and you can use it for reference.
1) Preperation: You need to get the below mention files, Please get these files from below mentioned thread:
a) CM6 and Gaaps
b) CustomMTD Patch - You only need FR-recovery and FR-boot latest version.
c) Script for a2sd and swap - get the latest script.
d) Fastboot - Fastboot should be setup and working, If you are on Linux go here
e) SD Card Partition - If you are not sure how to partition the sd card. If you want to use a2sd and swap, please partition your sd-card.Store all files on root of sd-card.
2) Connect the phone to PC, do not mount the phone.
3) Wipe the phone:
a) Boot into recovery(reboot while holding home and power). Wipe everything.
b) Boot in fastboot mode. (reboot while holding back and power)
Enter the command in terminal or command prompt on the PC
fastboot erase system -w c) reboot into recovery.
4) Install the custom MTD. (If you already have custom MTD then this step is not required.)
a) Flash customMTD fr-recovery file.
b) Reboot into recovery.
5) Install CM6 Gapps and boot loader.
a) Flash CM6
b) Flash Gapps
c) Flash Boot Loader fr-boot file
d) reboot phone
6) Once phone is booted and you are on the home screen, go to
CyanogenMod Settings > Application Settings > Install location - Set Install location as Internal, make sure allow application moving is not checked.
CyanogenMod Settings > Performance Settings - make sure that Compcache, JIT, dithering is not checked. If something is checked please uncheck it.
Lock home in memory can be checked, but some guys has reported that it drains a lot of battery.
Reboot the phone.
7) Go to terminal type below code
su
sh /sdcard/fr-patch140.txt a2sd
It will ask if you want to install a2sd, type Y and press enter. Once APKManager is installed, type quit to exit.
Reboot the phone.
8) If you are not using a2sd and want to setup swap, please enter the below command in the terminal otherwise continue to step 9.
su
sh /sdcard/fr-patch140.txt sdext
reboot the phone.
9) Go to terminal type below code
su
sh /sdcard/fr-patch140.txt swap
It will ask for swappiness, I use 60 there, but its your own preference. After that it will ask you if you want to use swap-file, press n and enter.
After this enter below to terminal
FreeIf you get swap setup it will show in front of swap in terminal, if the result show zero swap then reboot and do the step 9 again.
Now you have a CM6 with apps2sd and swap. All the newly installed apps will automatically go to ext.
If you don't like 3d gallery and want it to replace it with old gallery..This has been provided by ZilverZurfarn on CM6 thread.
Extract Gallery.apk from a older CM update (like 5.0.8) somewhere (c:\temp in the example below)
Using adb:
adb remount
adb shell rm /system/app/Gallery3D.apk
adb push c:\temp\Gallery.apk /system/app/Gallery.apk
Also there are some apps which I don't prefer, as I don't use android native keyboard, Android browser, POP email, amazon MP3 etc. So I have created a script for my use which has been shared and it can be run from the terminal..
download remove-app-v1.0.txt and store it to root of your sd card. than enter below commands in terminal
su
sh /sdcard/remove-app-v1.0.txt
currently this script will remove below mention apps based on user input.
Amazon MP3, Live Wallpaper picker, CM Wallpapers, POP Email, Android Native Browser, Android Native Onscreen Keyboard, Genie Widget...
Note: - Before removing browser and keyboard please make sure you have a replacement for them.
I do not take any credit for work, its just a reference for installing CM6. Thanks to Cyanogen and team, Firerat, Lbcoder for producing these amazing roms and methods.....
Please provide your feedback and suggestion for the guide.
If you like my guide and want to Donate
Can I have swap without app2sd?
I skipped the app2sd part, but the swap wouldn't work.
it didn't ask me about the swap file.
It ended with:
use
/system/bin/swappy on # to turn swap on
supa2001 said:
Can I have swap without app2sd?
I skipped the app2sd part, but the swap wouldn't work.
it didn't ask me about the swap file.
It ended with:
use
/system/bin/swappy on # to turn swap on
Click to expand...
Click to collapse
Yes, swap can be there without A2sd..
Do you have Fr-Patch139.txt script or any other version...could you please reboot and so the step 8 again
I did it many times
Do I need to create some files like userinit ?
Thanks for replying.
supa2001 said:
I did it many times
Do I need to create some files like userinit ?
Thanks for replying.
Click to expand...
Click to collapse
Try below command:
sh /sdcard/fr-patch139.txt sdext
reboot the phone
sh /sdcard/fr-patch139.txt swap
If this doesn't work, could you please pass on the message you are getting from the script.
G1sanju said:
Try below command:
sh /sdcard/fr-patch139.txt sdext
reboot the phone
sh /sdcard/fr-patch139.txt swap
If this doesn't work, could you please pass on the message you are getting from the script.
Click to expand...
Click to collapse
It works now. Thanks.
What does sdext do ?
When I ran sdext, it said "danger detected" though, is it still safe?
Same thing appeared when I did swap.
G1sanju said:
I was trying to upgrade to CM6 from CM5 and was facing lot of issues so I followed below process and got it worked. I thought of sharing it with everybody as lot of person are having issues.
I know most of the information is available on XDA but not on a single place.
I have made a separate thread because A2sd and SWAP are not supported by CM6 officially.
This is not an official method of installing CM6, this is how I got it worked and you can use it for reference.
1) Preperation: You need to get the below mention files, Please get these files from below mentioned thread:
a) CM6 and Gaaps
b) CustomMTD Patch - You only need FR-recovery and FR-boot latest version.
c) Script for a2sd and swap - get the latest script.
d) Fastboot - Fastboot should be setup and working, If you are on Linux go here
d) SD Card Partition - If you are not sure how to partition the sd card. If you want to use a2sd and swap, please partition your sd-card.Store all files on root of sd-card.
2) Connect the phone to PC, do not mount the phone.
3) Wipe the phone:
a) Boot into recovery(reboot while holding home and power). Wipe everything.
b) Boot in fastboot mode. (reboot while holding back and power)
Enter the command in terminal or command prompt on the PC
fastboot erase system -w c) reboot into recovery.
4) Install the custom MTD. (If you already have custom MTD then this step is not required.)
a) Flash customMTD fr-recovery file.
b) Reboot into recovery.
5) Install CM6 Gapps and boot loader.
a) Flash CM6
b) Flash Gapps
c) Flash Boot Loader fr-boot file
d) reboot phone
6) Once phone is booted and you are on the home screen, go to
CyanogenMod Settings > Application Settings > Install location - Set Install location as Internal, make sure allow application moving is not checked.
CyanogenMod Settings > Performance Settings - make sure that Compcache, JIT, dithering is not checked. If something is checked please uncheck it.
Lock home in memory can be checked, but some guys has reported that it drains a lot of battery.
Reboot the phone.
7) Go to terminal type below code
su
sh /sdcard/fr-patch139.txt a2sd
It will ask if you want to install a2sd, type Y and press enter. Once APKManager is installed, type quit to exit.
Reboot the phone.
8) Go to terminal type below code
su
sh /sdcard/fr-patch139.txt swap
It will ask for swappiness, I use 60 there, but its your own preference. After that it will ask you if you want to use swap-file, press n and enter.
After this enter below to terminal
FreeIf you get swap setup it will show in front of swap in terminal, if the result show zero swap then reboot and do the step 8 again.
Now you have a CM6 with apps2sd and swap. All the newly installed apps will automatically go to ext.
If you don't like 3d gallery and want it to replace it with old gallery..This has been provided by ZilverZurfarn on CM6 thread.
Extract Gallery.apk from a older CM update (like 5.0.8) somewhere (c:\temp in the example below)
Using adb:
adb remount
adb shell rm /system/app/Gallery3D.apk
adb push c:\temp\Gallery.apk /system/app/Gallery.apkI do not take any credit for work, its just a reference for installing CM6. Thanks to Cyanogen and team, Firerat for producing these amazing roms and methods.....
Please provide your feedback and suggestion for the guide.
Click to expand...
Click to collapse
Thanks mate this will really help me to put my apps on SDcard..as past days m really trying to get my phone memory safe...
supa2001 said:
It works now. Thanks.
What does sdext do ?
When I ran sdext, it said "danger detected" though, is it still safe?
Same thing appeared when I did swap.
Click to expand...
Click to collapse
"danger detected" message is for SPL, It checks for the SPL first and you have danger spl installed.
By default CM6 does not mount ext partition as it does not support a2sd right now. sdext creates a mount point for ext partition. a2sd internally does that but as you are not using a2sd this was not done.
vermaekansh said:
Thanks mate this will really help me to put my apps on SDcard..as past days m really trying to get my phone memory safe...
Click to expand...
Click to collapse
Thanks, If you use this guide then please provide your feedback and suggestion towards it.
Sorry, but is there a script to disable swap? I am gonna do some test to see what works best.
Thanks.
supa2001 said:
Sorry, but is there a script to disable swap? I am gonna do some test to see what works best.
Thanks.
Click to expand...
Click to collapse
In the terminal
sh /sdcard/fr-patch139.txt rev swap
this will turn the swap off.
Watch out...newbie in the room
Okay, you are going to love this.... I'm sorry if this is too long but I hope you can help a newbie trying to learn this stuff!
I am REALLY new to all this, and did a Root and Rom Update as the Unlockr.com videos taught me, to get CM6. And then also added the gapps file because I read a thread that that was needed to get gmail and the market on my phone. Once rebooted, everything worked ok but slow. Then I noticed that my gmail wasn't syncing, and then it started to force close. So I did a wipe and loaded CM5 because I saw on a thread that that was faster for the G1. With all of this, after reading your thread and suggestion, I am wondering...
1. Is CM6 slow for you?
2. Should I have loaded gapps? IS that how to get gmail and should it sync automatically? If not, is there a way to make it?
3. Should I stick with CM5 or try CM6 following these suggestions??
And big ones.... I wish there was a website somewhere with definitions to all the terms and apps used. Lol.. I Google all of them but don't always find anything that actually describes what they are.
Swap and app2sd were mentioned on the video instructions for loading a new ROM but do they automatically come in the ROM zip files? Because in the video they didn't load them separately. They partition the card "for" them, but don't show installing them. Obviously I assume App2sd is a program to store your apps on your sd card. Is this something that I SHOULD install? Is swap something I should install?
And what is a CustomMTD Patch? Annnnnnd, what is fastboot??
I know this is a lot of questions... I decided to ask them all here because they pertain to this thread because I'm wondering if I should do this...
Thanks for any and all answers!
I would assume that you have a G1, and my answer is based on that assumption. If you have different phone let me know.
1. Is CM6 slow for you?
If I don't use a2sd and swap, answer is yes. I install lot of apps, with cutomMTD it works fine in starts but slows down after some time. With a2sd and swap it is worth a try.
2. Should I have loaded gapps? IS that how to get gmail and should it sync automatically? If not, is there a way to make it?
CM roms does not distribute google apps with the rom as its not legal. So if you want gapps then yes that file has to be flashed. CM6 can be run without gapps, but you won't get gmail, market etc..once you have gmail it should sync automatically.
3. Should I stick with CM5 or try CM6 following these suggestions??
CM5 is quite stable rom and runs fine. Choice is yours...CM6 is in initial stages, but is good too...I go with CM5 for my daily driver as a2sd is not officially supported. It will be there in CM6.1....
And what is a CustomMTD Patch? Annnnnnd, what is fastboot??
G1 was build with a low memory and the way internal memory has been partition todays rom can't fit into it. That's why dangerSPL, but there is a risk involved in installing dangerSPL. If you don't follow the instruction you can brick your phone. CustomMTD is a safe method. This increase the size of data partition so you can install more apps internally. link for that thread is in first post.
a2sd is a way to store apps on sdcard, sdcard needs to be partitioned to support that..step 1 - e in my guide. That's a manual way of doing it. If you have AmanRA recovery then it will have a menu option for that. Most of the rom supports it automatically, so if you have sd card partition then rom will automatically do that.
CM6 does not support a2sd so it has to done in different way. CM5 supports it but in settings - application - a2sd has to be checked on to move your apps to sdcard.
Swap is kind of extra memory to help running the applications. if you run multiple application together then you need swap on CM5 and CM6.
G1sanju said:
CM5 is quite stable rom and runs fine. Choice is yours...CM6 is in initial stages, but is good too...I go with CM5 for my daily driver as a2sd is not officially supported. It will be there in CM6.1....
Click to expand...
Click to collapse
So when CM6.1 is comming out for G1..do you have nay idea about HCTCLAY's ROM over CM6
vermaekansh said:
So when CM6.1 is comming out for G1..do you have nay idea about HCTCLAY's ROM over CM6
Click to expand...
Click to collapse
Nope I don't follow htcclay but it is based on CM so should be updated
Sent from my HTC Dream using XDA App
G1sanju said:
Nope I don't follow htcclay but it is based on CM so should be updated
Sent from my HTC Dream using XDA App
Click to expand...
Click to collapse
No hard feeling for CM but for me htcclay's ROM's are more stable than CM's.....any release date for CM6.1 for G1?
vermaekansh said:
No hard feeling for CM but for me htcclay's ROM's are more stable than CM's.....any release date for CM6.1 for G1?
Click to expand...
Click to collapse
Roms are personal preferences, I also tried lot of roms before settling on CM... and for CM there are no eta it will be released when it's done...
Sent from my HTC Dream using XDA App
WOW!
THANK YOU!!! You are awesome for going through all of those!
Yes, it is a G1.
Are there any features in CM6 that aren't in CM5, or is it faster than CM5 with the ap2sd & swap?
I believe I partitioned the sd card when I loaded the CM6 ROM.
So I'd like to try the CM6 with the ap2sd, swap and the CustomMTD. I do have the AmanRA recovery, but not sure about how to select the ap2sd.
Any chance you would tell me how to get the ap2sd, swap and CustomMTD on the phone if I have already Flashed CM6 on there?
Thanks again, regardless. The info you gave me helped me learn a little more. I'm still a bit confused about what fastboot is though. But I will just keep at it and keep learning!
Are there any features in CM6 that aren't in CM5, or is it faster than CM5 with the ap2sd & swap?
CM6 is based on froyo, latest version of android...its good and yes speed is comparable. Also CM has added new stuff in it, like fully customizable power bar and other stuff...Full changelog is there in CM6 thread.
I believe I partitioned the sd card when I loaded the CM6 ROM.
So I'd like to try the CM6 with the ap2sd, swap and the CustomMTD. I do have the AmanRA recovery, but not sure about how to select the ap2sd.
For CM6 a2sd is through script, instruction is in first post. I have included customMTD also there. So if you follow the guide, you will be having customMTD, a2sd and swap...swap require an partition on your sdcard, if you don't have that partition then it will ask for swap file.
Any chance you would tell me how to get the ap2sd, swap and CustomMTD on the phone if I have already Flashed CM6 on there?
you can wipe and start over again, first post should be good for you.
Thanks again, regardless. The info you gave me helped me learn a little more. I'm still a bit confused about what fastboot is though. But I will just keep at it and keep learning!
Oh I forgot about the fastboot, fastboot and adb are tool, which give an option to control, flash and do other thing on the phone from PC. The link for setup guide is in first post.
Thanks again!!
Man! You are great! Thanks again for all your help! Now let's see if I can manage to follow your thread and not brick my phone! Lol
Until next time....
[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)
I developed a flashable zip to help configure dual boot. Zip is designed to be independent of ROM type, version and install method, whether by flashable zip, cloning primary ROM to SD, or in general copying a ROM system image to SD.
Then I overhauled this thread...
Config-Dual-Boot-v1.0-signed.zip: http://www.mediafire.com/?edgat0koyp7d33l
Backs up /sdcard[-ext]/Boot (if it exists) to /sdcard[-ext]/Boot.bak
Creates Boot/ROM1 and Boot/ROM2 directory paths under /sdcard[-ext]
Installs Script Manager on ROM1 and ROM2
Contains shell script “copy-boot.sh” to copy ROM boot partition to boot image file
Contains shell script “boot-rom.sh” to switch to boot ROM2 from ROM1 and vice versa
The updated “boot-rom.sh” script now features generic boot image directory names: Boot/ROM1 and Boot/ROM2, and automatically captures the SD Boot directory path (/sdcard for CM ROMs and /sdcard-ext for Blur ROMs).
Instructions:
1. Boot to ROM1 (emmc)
2. Reboot to CWM and flash: http://www.mediafire.com/?edgat0koyp7d33l . Doing so will backup any existing Boot directory under /sdcard[-ext] and push a new Boot directory containing empty subdirectories ROM1 and ROM2 and two shell scripts: copy-boot.sh (copy boot partition to image file) and boot-rom.sh (boot switcher).
In the following steps, the shell (sh) commands can be run using ADB (Android SDK Platform Tools), Terminal Emulator, Script Manager or other suitable app.
3. Reboot to ROM1
4. Enter: “sh /sdcard[-ext]/Boot/copy-boot.sh”. This detects which ROM is running, ROM1 in this case, and copies its boot image to /sdcard[-ext]/Boot/ROM1
5. Configure Script Manager to execute “sh boot-rom.sh 2” which enables booting to ROM2. But do not run this command until ROM2 “boot.img” is in place. We'll do that now.
6. Reboot to fastboot and connect phone to computer.
7. Enter: “fastboot flash boot boot.img” where boot.img is a boot image file modified to host ROM2 on SD. Please see my Auto-Modify Boot Image thread.
8. Enter: “fastboot reboot"
9. Enter: “sh /sdcard[-ext]/Boot/copy-boot.sh” as in step 4.
10. Configure Script Manager to execute “sh boot-rom.sh 1” which enables booting to ROM1.
More on configuring Script Manager:
Go to Settings > More > Advanced Options > Config > Home Directory. Set home directory to /sdcard/Boot. Then while still in SManager, navigate to /sdcard/Boot and press boot-rom.sh to configure. Valid arguments are:
Code:
blank: Reboot to current ROM
1: Reboot to ROM1 (emmc)
2: Reboot to ROM2 (SD)
3: Reboot to recovery
Press the “Su” box to run as root (note green symbol) and press “Save” at top right. Then press “Run” at top left to launch boot-rom.sh and reboot to the other ROM.
Place shortcut to Script Manager on home screen.
If all goes well, you can now boot ROM2 from ROM1 and vice versa with just a few screen taps.
This procedure was tested working with Neutrino V2.8 EE (CM) on emmc and NottachTrix 1.3.1 ATT (Blur) on SD.
Legacy YouTube video (3:38) showing reboots from one ROM to the other: http://www.youtube.com/watch?v=31TPyAguQ60
Credits
Special thanks to jokersax11, Notorious544d, ATRIXXIRTA, ghost_og, hatefuel19, J-Roc and many others for their technical direction, useful suggestions and encouragement. And of course to the Photon/Atrix/Android dev teams, Koush and https://sites.google.com/site/devwom/
Thanks a lot dude! Im going to try this!
how do you install two roms at the same time? i thought this was showing how to do that but im confused. how do you change the cwm zip installers to .img?
edit:: sorry i thought this was the other thread showing how to install a dual boot system but in fact its how to configure it to boot into them easier. sorry for the mixup ill defiantly read over your 1st thread
Note: Joker recommended as a refinement to place all apps in sdcard to keep apps common to both builds. Good idea.
Click to expand...
Click to collapse
Does this mean that across both on CM7 and CM9, the same apps will be installed? And if you install a new app, it will be seen in both CM7 and CM9?
And is data for apps accessible as well for both CM7 and CM9? So saving a data file with CM9 for example will be saved in /data and when I boot back into CM7, the same data I saved from CM9 will be there in CM7?
Lastly, did you manage to get that dalvik cache thingy working?
That's a lot of questions, but I hope you understand what I'm trying to say.
If it is, then WOW!
Notorious544d said:
Does this mean that across both on CM7 and CM9, the same apps will be installed? And if you install a new app, it will be seen in both CM7 and CM9?
And is data for apps accessible as well for both CM7 and CM9? So saving a data file with CM9 for example will be saved in /data and when I boot back into CM7, the same data I saved from CM9 will be there in CM7?
Lastly, did you manage to get that dalvik cache thingy working?
That's a lot of questions, but I hope you understand what I'm trying to say.
If it is, then WOW!
Click to expand...
Click to collapse
Thanks for the good questions. I haven't yet considered Joker's tip in detail as I spent most of yesterday writing this thread, researching other related topics (and watching Downton Abbey with my beloved wife ). But off the top, I assume that if a given app works on both ROMs, theoretically there should not be a problem hosting it and its corresponding data on the kitchen table (sdcard).
I guess one of the challenging questions is: Are there certain apps for which data should be kept separate to enable ROM-specific customization?
I just updated my thread with this...
"Alternatively (and actually preferred), you can extract the contents of this zip: http://www.mediafire.com/?0kdp4qvy6fv71kp to /sdcard. It makes ROM selections generic, and also fixes a problem with boot-rom.sh (Android shell apparently does not like trailing spaces in script files.) Then drop your boot.img files into /sdcard/Boot/ROM1 and ROM2 and you're good to go."
Cheers.
I developed a flashable zip to help configure dual boot. Zip is designed to be independent of ROM type, version and install method, whether flashable zip, cloning primary ROM to SD, or in general copying a ROM system image to SD.
Then I overhauled this thread...
MIUI: http://www.mediafire.com/?oqvzpc61x3s5w44
GApps: http://www.mediafire.com/?1c2br6sw6330lwn
These flashable zips and corresponding procedure are intended for intermediate to advanced users, i.e. those who have 1) unlocked their Atrix, 2) partitioned their SD card for dual boot, and 3) have a working knowledge of ClockWorkMod (CWM) Recovery and how to install and configure dual boot. If you are not in this category or would simply like a refresher, you can review some of my other threads on this topic, namely:
Dual Boot threads:
http://forum.xda-developers.com/showthread.php?t=1651356
http://forum.xda-developers.com/showthread.php?t=1642185
http://forum.xda-developers.com/showthread.php?t=1645344
Please understand this MIUI port is not a “dual boot flashable zip” (DBFZ); rather it is a single boot flashable zip of MIUI ported to SD card. However it should preserve your existing primary ROM (ROM1) along with /cache and /data, and thus is actually more versatile than DBFZ which gives you two ROMs that you may not even want.
I strongly recommend that after flashing MIUI, you first reboot to MIUI before flashing GApps.
To reboot to ROM1 after installing MIUI, you could fastboot flash a ROM1 boot image (easiest and fastest way), or configure dual boot as described here ( http://forum.xda-developers.com/showthread.php?t=1645344 ) . I have often found it convenient to simply extract the /Boot directory of an existing DBFZ and customize from there by inserting the boot images of my choice.
If you presently have dual boot and need to wipe the /cache and /data partitions of your second ROM (ROM2) before installing MIUI, then CWM-flash these zips:
Wipe /cache: http://www.mediafire.com/?mc881zjhl9oqr0q
Wipe /data: http://www.mediafire.com/?4k4fey6gxe1nbn0
Now you may be wondering... How do I backup an existing ROM2 since stock recovery tools cannot backup an SD card-based ROM? Here is one way:
Boot phone to CWM 5.0.2.0, connect it to ADB-enabled computer and enter:
Code:
adb devices (make sure device is listed)
adb shell (should get # sign, indicating “root” on Android)
umount /cache (since internal memory /cache is mounted by default)
mount /sdcard
mkdir /sdcard/ROM2-backup
cat /dev/block/mmcblk1p2 /sdcard/ROM2-backup/system.img
cat /dev/block/mmcblk1p3 /sdcard/ROM2-backup/cache.img
cat /dev/block/mmcblk1p4 /sdcard/ROM2-backup/data.img
Standard disclaimers apply. In short, I am not responsible for any harm you or your phone may incur by using any or all of this material.
Many thanks to stevendeb25 (MIUI ported to Atrix), www.angeeks.com (GApps), the CM/Photon/Atrix/Android dev teams and to Koush (CWM Recovery).
yeah....downloading...
tks mate,tks very much,u make my wish come true and every one here who love miui,is there any way i can help u 'cause i dont have visa to donate for u
Sent from my MB860 using Tapatalk 2
mafiarock93 said:
tks mate,tks very much,u make my wish come true and every one here who love miui,is there any way i can help u 'cause i dont have visa to donate for u
Sent from my MB860 using Tapatalk 2
Click to expand...
Click to collapse
Thank you... I am so glad to know that you and your friends can benefit in some way from this little project.
If you have PayPal, you can click the "Donate to me" button, and it takes you to my PayPal donation site. I would probably use the funds to buy a faster SD for experimentation.
Take care.
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?