Related
[CWM-APP] full_wipe && easy_upgrade_wipe ZIPs [EXT2,3&4], last updated [2014-06-23]
Hello everybody!
I got inspired by mero01, who made similar tools for my previous mobile phone, the HTC Desire HD.
Imho a new version of an Android ROM should NEVER ever do a full wipe. Personally I prefer to wipe on my own AND to _personally_ have the option which file system is going to be used.
That's why I've created my own zip files, which do either a FULL_wipe or an easy_upgrade_wipe.
These zip files could work on multiple phones, but they are only tested and confirmed to be working on the LG Optimus 2x (P990). Just for the sake I've also implemented a check inside of them if that's the phone, which the wipe(s) are performed on.
**** !NONE WILL FORMAT YOUR SDCARD! ****
I DON'T TAKE ANY RESPONSIBILTY FOR DATA LOSS OR ANY DAMAGE CAUSED TO YOUR DEVICES. USE AT YOUR OWN RISK!!! UNDO IS NOT POSSIBLE!
PREREQUISITES:
* Clockworkmod Recovery (recommended version: v6.0.2.5)
INSTRUCTIONS FOR EVERY FILE:
Code:
1. Download the zip file you want.
2. Place it anywhere in your /sdcard/
3. Reboot into CWM recovery
4. Install zip from sdcard
5. CONFRIM --- CAUTION! THIS IS UNDO-ABLE!!!
6. done :)
7. Don't reboot, flash any rom you want
8. Flash it
9. Reboot and have fun! ;)
FULL_WIPES
This patch comes in two versions (EXT3 and EXT4) and needs to be applied prior to the flash of any ROM. It will WIPE your device and format all partitions either in EXT3 or EXT4.
Wipes performed:
* SYSTEM
* DATA
* CACHE (always EXT3)
* Cleaned temporary SDCARD data ("/sdcard/.data/navigator/Data/Temporary")
EASY_UPGRADE_WIPES
These patches also come in the previous two versions (EXT3 and EXT4) and there is an additonal lite variation, which won't wipe your dalvik cache. Use the easy upgrade wipes if you DON'T want to remove your data (especially useful for ROM upgrades)!
Wipes performed:
* SYSTEM
* CACHE (always EXT3)
* non lite versions: Wipes the dalvik cache on DATA
* Cleaned temporary SDCARD data ("/sdcard/.data/navigator/Data/Temporary")
NO_JOURNAL
This won't do any wipes, but will remove the JOURNAL(S) on your file systems. If it gets applied to EXT3 partitions it clearly results in EXT2 partitions.
You will get the fastest possible EXT* file systems if it is applied to the EXT4 partitions.
It can also be applied on already existing file systems, although I'd suggest to use a clean file system. Make a backup if you still want to perform it, because it can be dangerous!
Wipes performed:
* NONE
CHANGELOG:
Code:
[U]2014-06-23[/U]
- New LITE easy upgrade wipes available, which won't clean your dalvik cache.
[U]2012-12-10[/U]
FULL_WIPES & EASY_UPGRADE_WIPES v0.5 (ICS versions only)
- Fixed system partition wipe.
[U]2012-11-27[/U]
FULL_WIPES & EASY_UPGRADE_WIPES v0.4
- Fixed progress bars.
- Now available in two versions: one for the old (GB), one for the new (ICS) partition layout
- Easy upgrade wipes will now also clean the dalvik cache
- All full and easy wipes re-made from scratch, please use with care and eventually perform a backup before using them.
[U]2011-12-28[/U]
FULL_WIPES & EASY_UPGRADE_WIPES v0.3
- First public release
************************************************************
[U]2012-12-10[/U]
NO_JOURNAL v0.3 (ICS version only)
- Fixed system partition converting.
[U]2012-11-27[/U]
NO_JOURNAL v0.2
- Fixed progress bars
[U]2011-12-28[/U]
NO_JOURNAL v0.1
- First public release
Have fun!
Greetings,
dr4go
Frequently asked questions (FAQ):
What is the difference between the o and n versions?
The o stands for OLD-, whereas n is an abbreviation for NEW-partitioning layout. Unfortunately LG changed the location of the data partition (from mmcblk0p8 to mmcblk0p9).
so what's the difference between the erase/reset data factory on CWM???
By default CWM will only format your partitions in ext3. Now you can choose ext4 which is usefull for ROMs/kernel with ext4 support but do not format the partitions in ext4. Also, you can use ext2 now the easy way.
koboltzz said:
By default CWM will only format your partitions in ext3. Now you can choose ext4 which is usefull for ROMs/kernel with ext4 support but do not format the partitions in ext4. Also, you can use ext2 now the easy way.
Click to expand...
Click to collapse
Exactly. Thanks for the answer koboltzz.
For the HTC Desire HD there was also an EXT4 version of CWM available, which changed the default algorithms of the "Wipe data/Factory reset" and the "Format" options to EXT4.
But with the latter possibility you loose the ability to format EXT3 partitions. That's also why I always used mero01's zip files to accomplish wipes.
Imho it's the best option, because if you REMOVE the formatting lines from the ROMs you want to flash it's absolutely no problem to also use an EXT3 designed ROM (like Hypnos2X for example) on EXT4 file systems (that's the operating system I'm currently on).
And I tell you also because I dislike the FULL wipes on nearly every ROM available for the LG Optimus 2X. If you have a problem and just want to reinstall the ROM without loosing any data there is no way to do that.
Yes, an easy wipe should always be done by the standard ROM zip itself - of course... but I've always also removed those lines, because that way you also get the freedom of the file system.
It's up to you...
sadly, I must report, that 0-full_wipe_0.3_ext4.zip is not working as expected.
Using it and after that flashing Fr19 with ext4 Kernel (from modaco) -> no boot at all ->freezing
This will not happen, if you first do a fullwipe by cwm (ext3), then flash Fr19 and after that use the universal converter to ext4 from benee.
But this only changes data and system partition to ext4 by default.
There is definitely something wrong with the script, an other example:
First flashing 0-full_wipe_0.3_ext4.zip
after that Fr19 ROM (up to this point it would have been a bootfreeze, look above)
and after that flashing universal converter to ext4, phone will boot now, but will not be able to install any app 'there is insufficient space' (which is totally not true), most likely because cache partition is fu.cked up by 0-full_wipe_0.3_ext4.zip
Time for version 0.4
koboltzz said:
sadly, I must report, that 0-full_wipe_0.3_ext4.zip is not working as expected.
[...]
Time for version 0.4
Click to expand...
Click to collapse
I will look into it. Thank you for the additional information.
Delete this comment i guess i need to learn how to read im sorry!
dr4go said:
I will look into it. Thank you for the additional information.
Click to expand...
Click to collapse
Anything new to this?
koboltzz said:
Anything new to this?
Click to expand...
Click to collapse
Unfortunately not yet... But I'll promise you: It's the next on my todo list, because it bugs me too.
dr4go said:
Unfortunately not yet... But I'll promise you: It's the next on my todo list, because it bugs me too.
Click to expand...
Click to collapse
hey dr4go got something weird here...
when i flash your ext3 zip everything is fine atleast the mount command say so
but then when i want to convert them to ext2 something really weirds occur the system partition becomes ext2 but the data and cache partition become ext4 according to the mount command using recovery 5.0.2.7R2
Here is the convert tool made by Topogigi, and slightly modified by me to include /system conversion.
/cache has not the same parameters it seems.
First (and second) post(s) updated.
And I'll promise you also to release something bigger next time. Guesses won't be commented.
ONly comment I can do is: Nice to see you my friend! How are you?
carburano said:
ONly comment I can do is: Nice to see you my friend! How are you?
Click to expand...
Click to collapse
Everything fine here! Nice to see you too. I finally found some free time and also motivation, because of the marvellously working CyanogenMod 10 on our phones. It's unbelievable... I was nearly freaking out when reading the notice.
And you? How are you? Hopefully everything is also great on your side?
Dr4go welcome bro, how are you?
Sent from my LG-P990 using xda app-developers app
maybe you can do this thing for the new Bootloader.
i try,but stay in Bootloop
Maybe you have a good Idea
spica1234 said:
Dr4go welcome bro, how are you?
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Thank you. As you may have realized... a little busy as usual... otherwise totally fine. How is it on your side? Everything ok?
cojo11 said:
maybe you can do this thing for the new Bootloader.
i try,but stay in Bootloop
Maybe you have a good Idea
Click to expand...
Click to collapse
What exactly did you do? And which ROM did you try to flash afterwards? Imho the zips should be fixed now - I didn't encounter a single problem since using them.
i try it with ICS 28E and 28G for my Ghostrider Aroma Rom with new Partition Layout,but when i use ext3 or ext4 i got a Bootloop,i put the stuff in the Updater-Script,all runs with Aroma and lokks fine but when i reboot,i got the Bootloop
[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)
This rom is a free, community built, aftermarket firmware distribution of Android 4.4 (KK), which is designed to increase performance and reliability over stock Android for your device. 100% stable ROM with no any bug
ROM FEATURES-
Based on latest KK and it's almost bugfree
Good Battery Life..........better than stock
Themed all icons to beautiful AOSP
Fully deodexed /app, /priv-app, /framework for faster apps opening speed
Gesture working
[U]---BUGS---[/U]
1. Show Phone Memory as SD-Card, SD-Card as Phone Memory..... but this not cause any problem in working. Others no any Bugs........if you found please let me know......
---FIXES---
1. Storage fix http://d-h.st/DgR
2. Network, GPS, Compass fix http://d-h.st/qy8
3. Launcher with Motion & Gesture Support http://d-h.st/hg6
4. BOOTIMG for 8GB users http://d-h.st/aU9
All fixes flashable through CTR/CWM...........Cache & Dalvik Cache cleaning is recomended.
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
First time installing to your GIONEE M2, or coming from another ROM:
- Make sure you're running a proper working CWM or CTR.
- Copy ZIPs to your SDCard
- Boot into Recovery
-Wipe all Data(System, Data, Cache, Dalvik Cache for wipe menu::::THIS STEP IS NECCESSARY)
- Flash zip from SDCard
- Reboot
DOWNLOAD SECTION
https://docs.google.com/uc?id=0B3s_rEgYp08YZ3pLZnFrTmNFU2s&export=download
New link:- single zip with all bug fixed. Thanks to Geo & Abizz for fixing all bug and uploading.
http://www.mediafire.com/download/q696695dcy60b9v/aosp_gesture_gioneem2_fullwrkng.zip. If you are downloading from this link then no need to download any fixes.
About KITKAT ROM 4.4.2:
ROM OS Version: 4.4.2 KITKAT
ROM Kernel: Linux 3.4.67
Based On: AOSP KITKAT
Version Information
Status: 100% Stable
SCREENSHOTS
Thanks for the update and your awesome work. Kindly upload this and other files to mediafire site or any other one. Am finding it difficult to download from Google Drive links
---------- Post added at 05:00 AM ---------- Previous post was at 04:56 AM ----------
Please do provide screenshots
Here's what am facing while trying to download it
paeffiong said:
Here's what am facing while trying to download it
Click to expand...
Click to collapse
Use desktop mode in ucweb.
---------- Post added at 06:35 AM ---------- Previous post was at 06:32 AM ----------
Restore applications from titanium backup not showing up, while it is working normally in cleankat rom, i m using titanium version 6.1.5.5
how to remove G symbolbefore each network bar
how to remove G symbolbefore each network bar , it takes space and looks ugly too
rakesh61 said:
how to remove G symbolbefore each network bar , it takes space and looks ugly too
Click to expand...
Click to collapse
You can install Gravity BOX and Xposed framework to your phone. Once installed open up gravity box, then go to display tweaks and there you can modify all settings. Hope this helps !:good:
LInk to download Xpose : http://repo.xposed.info/module/de.robv.android.xposed.installer
Just make sure you dont use ART, Xposed will not work with ART.
Titanium backup working before flashing storage swap zip, ;after flashing storage swap zip file it does not show any fies in restore file option. i M using titanium backup without flashing storage swap file. Using this rom for 2 days, indeed a very good rom, good job sir
Gallery application force closed sometimes
Cant stop the error pop up... This is bad. The zips dosnt work.. I tried putting in zip by modifying manually... Almost 6 hours now...
drdeepakpatel said:
Restore applications from titanium backup not showing up, while it is working normally in cleankat rom, i m using titanium version 6.1.5.5
Click to expand...
Click to collapse
root your device properly .
if problem persists , go to preferences -> back location->scan->select current location.
drdeepakpatel said:
Titanium backup working before flashing storage swap zip, ;after flashing storage swap zip file it does not show any fies in restore file option. i M using titanium backup without flashing storage swap file. Using this rom for 2 days, indeed a very good rom, good job sir
Click to expand...
Click to collapse
set default write disk as sd card in system settings.
go to preferences -> back location->scan->select current location.
thanks
finance.resat said:
Cant stop the error pop up... This is bad. The zips dosnt work.. I tried putting in zip by modifying manually... Almost 6 hours now...
Click to expand...
Click to collapse
...don't understand what are you talking about. No one faced any errors in zip files.
try downloading again with good internet speed.
thanks
HI
After installing the storage fix zip, my SD card is no longer writable, have tried the <media r/W> tweak but didnt help... Any body faced such an issue with this ROM ?
anilyarki, no body faced any problem like this. Have you changed default write disk in storage setting. Try clearing cache and dalvik cache from recovery.
can u port those android one stock roms
can u port those android one stock roms
that would be very nice
in your rom i have a problem some apps are incompatible like the hdfc bank in play store it says incompatible with ur device many such apps also reprt this problem , any fix please
Im constantly getting pop-up error like android.process.media has stopped. Tried everything but it still shows up.
Please help.
anisharsenal said:
Im constantly getting pop-up error like android.process.media has stopped. Tried everything but it still shows up.
Please help.
Click to expand...
Click to collapse
clear cache, dalvik cache from recovery.
this rom does not work in my device.. just waste of time... may be my device is faulty...
finance.resat said:
this rom does not work in my device.. just waste of time... may be my device is faulty...
Click to expand...
Click to collapse
Working fine with all M2 version (4gb & 8gb)
Reflash the ROM
1.reboot to ctr recovery
2.backup current ROM
3.preflash wipe (from wipe menu)
4.install ROM zip
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?
DISCLAIMER
By using this ROM, you agree that the developer is not responsible for any physical damage caused to you or your device, or non-physical damage which includes but not limited to:
- broke up with gf due to missed phone calls
- got fired by bossku due to missed alarm
- drove your car into the sea due to faulty GPS
- got caught while traveling in Japan because your camera has no shutter sound
- got last place in kahoot quiz due to device lagging
- accidentally fried the egg due to device overheating
Continue to read this thread only if you agree.
Click to expand...
Click to collapse
LineageOS 14.1 for Samsung Galaxy Note N7000
Beware, you are about to enter a danger zone!
ABOUT
This is more of like a learning attempt, as I never build cm-14.1 for n7000 before. Besides that, I think that it might be useful if I can rework the device sources to make it more proper and organized. I hope this build with new security patch will benefit people who wants to stay on cm-14.1.
CREDITS
All my builds are fully based on works by @rINanDO, @bauner, @ChronoMonochrome, fourkbomb, numerous n7000, Exynos4 and LineageOS developers. Full credits goes to all the developers. I hope no one is being left out, please notify me if there is.
INSTALLATION
All my builds are emulated storage capable. Repartition is required to install my builds.
And also, please backup EFS partition and store in a dry, safe place.
The below instructions assumes that your device has TWRP IsoRec installed, and all your data will be destroyed in the process.
1. Choose your desired emulated storage partitioning configuration: - Android 9/10 capable: lanchon-repit-20170115-system=1.5G+wipe-data=max+wipe-sdcard=min+wipe-preload=min+wipe-n7000.zip
- Android 7.1.2 capable: lanchon-repit-20170115-system=1G+wipe-data=max+wipe-sdcard=min+wipe-preload=min+wipe-n7000.zip
* Emulated + Non-emulated Internal Storage: change the values of -sdcard=min+wipe to -sdcard=4G+wipe, where 4G is your desired non-emulated Internal Storage size.
The last option provides best compatibility, as non-emulated storage ROMs will work as intended on such partitioning, and emulated storage ROMs will detect the non-emulated storage as an SD Card.
This allows you to switch back-and-forth between emulated capable and non-emulated capable ROMs without repartitioning.2. Reboot into recovery. Flash emulated storage capable TWRP IsoRec (flash as Image to Recovery): i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.img
3. Reboot recovery. Flash i9100-to-n7000 TWRP conversion: lanchon-twrp-patcher-20160417-n7000.zip
4. Reboot recovery. Flash the repartition script that you have chosen in Step 1.
5. Reboot recovery. Wipe /cache, /system, Non-emulated Storage. Then, run Format Data.
6. Proceed to flash my builds.
7. Flash ARM nano GAPPS and SU if desired.
8. Prepare a coffee or tea and sit back on your couch. Reboot system.
DOWNLOAD
Icedrive
XDA:DevDB Information
LineageOS 14.1, ROM for the Samsung Galaxy Note GT-N7000
Contributors
lee.wp14
Source Code: https://github.com/hikuii
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
ROM Firmware Required: TWRP 3.3.1-1 (Emulated Storage Compatible)
Based On: LineageOS
Version Information
Status: Testing
Created 2020-05-11
Last Updated 2020-05-26
LineageOS 14.1
LATEST BUILD
lineage-14.1-20200511-UNOFFICIAL-n7000
kernel-4c4d93693090e956abb234bca54368d46be42981
NOT WORKING/UNTESTED
- GPS/AGPS: untested
- DRM: untested
BUILD-SPECIFIC NOTES
- CPU Hotplug is disabled, please monitor battery usage.
- Thermal throttle for CPU is set to 1.2GHz at 69C, stop at 64C. Memory is 90C and stop at 85C.
INSTALLATION NOTES
- Nougat builds have DEXPREOPT disabled as it breaks the system on Exynos platform. Thus, first boot will take longer than usual.
CHANGELOG20200511
- Initial build.
Reserved
Thats great
plz help me i m stuck at flashing the script
Reboot recovery. Flash the repartition script that you have chosen in Step 1.
every time i flash the script Android 9/10 capable: lanchon-repit-20170115-system=1.5G+wipe-data=max+wipe-sdcard=min+wipe-preload=min+wipe-n7000.zip
- Android 7.1.2 capable: lanchon-repit-20170115-system=1G+wipe-data=max+wipe-sdcard=min+wipe-preload=min+wipe-n7000.zip
i try it the first didnt work also the second i mean i didnt try it together but i mean non of thes files working
there is an error says unable to mount all partions from sd card
same massege from memory card i tryied everything but didnt work man
installing from internal didnt work '
installing from memory card didnt work ???????????
Adham_android said:
plz help me i m stuck at flashing the script
Reboot recovery. Flash the repartition script that you have chosen in Step 1.
every time i flash the script Android 9/10 capable: lanchon-repit-20170115-system=1.5G+wipe-data=max+wipe-sdcard=min+wipe-preload=min+wipe-n7000.zip
- Android 7.1.2 capable: lanchon-repit-20170115-system=1G+wipe-data=max+wipe-sdcard=min+wipe-preload=min+wipe-n7000.zip
i try it the first didnt work also the second i mean i didnt try it together but i mean non of thes files working
there is an error says unable to mount all partions from sd card
same massege from memory card i tryied everything but didnt work man
installing from internal didnt work '
installing from memory card didnt work ???????????
Click to expand...
Click to collapse
Not sure what you mean by that error mentioned. Can you attach some pictures for reference?
lee.wp14 said:
Not sure what you mean by that error mentioned. Can you attach some pictures for reference?
Click to expand...
Click to collapse
https://b.top4top.io/p_1607stgxn1.jpg
Adham_android said:
https://b.top4top.io/p_1607stgxn1.jpg
Click to expand...
Click to collapse
The logs are pretty self-explanatory, repit requires you to run from /tmp. When the location of repit is to be unmounted during repartition, it will fail and require you to flash again from /tmp.
So you just copy the zip file to /tmp and flash from there.
lee.wp14 said:
The logs are pretty self-explanatory, repit requires you to run from /tmp. When the location of repit is to be unmounted during repartition, it will fail and require you to flash again from /tmp.
So you just copy the zip file to /tmp and flash from there.
Click to expand...
Click to collapse
i opend the file manager and go to /tmp and i found the script file there i didnt copy it so i try to install but didnt work the same massege appears ?
second question : tmp folder located in which storage exactly ?
Adham_android said:
i opend the file manager and go to /tmp and i found the script file there i didnt copy it so i try to install but didnt work the same massege appears ?
second question : tmp folder located in which storage exactly ?
Click to expand...
Click to collapse
Attach a picture of the error after you flash from /tmp.
Or maybe, manually unmount /sdcard1 and flash again from /tmp.
/tmp is not a storage, /tmp is a linux tmpfs, it is not a persistent storage. Think of it as a RAM.
You couldn't just update the assembly from bauner. Security patch. Or can your assembly be put on top of a bauner assembly?
Thanks for this ROM this is the most stable rom i have ever used and it gives me excellent performance much better than samsung own touchlagwiz on jellybean 4.1.1 the only issue i have encountered i the horrendrously bad battery life and overheating the phone gets so hot that you can boil a drop of water on it.
Sorry if I wasted your precious time.
Regards.
Even if it's an older version of Android, this one (LOS 14.1) might give the best experience of the currently maintained (2? ^^" ) N7000 ROMs.
Has anyone used this rom and the LineageOS 16.0 one also from lee.wp14? To have some feedback on responsiveness and RAM usage? To confirm of deny the above hypothesis.
tuxayo said:
Even if it's an older version of Android, this one (LOS 14.1) might give the best experience of the currently maintained (2? ^^" ) N7000 ROMs.
Has anyone used this rom and the LineageOS 16.0 one also from lee.wp14? To have some feedback on responsiveness and RAM usage? To confirm of deny the above hypothesis.
Click to expand...
Click to collapse
I used that Android 9 ROM but lot of times system ask to close or wait apps not responding, so I think it is too slow for daily usage (even with Lspeed and FDE.ai installed).
EDIT: Unfortunately it seems that it cannot install magisk in this ROM
and actually the Lineage 16 build with the LSpeed performance preset and trimming the partitions seems reasonably performant.