Installation of Viper4android in Remix OS - Remix OS for PC

For those Audiophiles like me if you wanna get Viper4Android to work with RemixOS here is the noob friendly guide;
1) MAKE SURE WHAT'S YOUR BOOT INSTALL : LEGACY OR UEFI (32 AND 64-bit) ; As for mine I have Legacy boot. So it's the guide of as such system. BTW for 64-bit system please see this awesome guide made by @electrikjesus
http://forum.xda-developers.com/remix/remix-os/guide-using-jides-remountrw1-method-to-t3431595
2) For Legacy boot of RemixOS boot installs (32 & 64 bit) using MBR from Jide's Installer (NON-UEFI)
You will want to make sure you can view hidden and system files in Explorer options, Once you do that, travel to C:\RemixOS (or where yo installed it) and using Notepad++ or your code editor of choice, find and open the menu.lst file. Then add a second entry containing the REMOUNT_RW=1 entry like you see below:
Code:
default 0
timeout 10
title Resident mode - All your data and apps are saved
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ DATA= CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
boot
title Resident mode - RW enabled
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ REMOUNT_RW=1 DATA= CREATE_DATA_IMG=1 initrd /RemixOS/initrd.img
boot
3) Once you are done, you can reboot, and choose the entry you added. It will then extract the system.sfs file to a system_dev.img, and mount it as RW for you. Once booted, go to /system partition (myself use Root explorer, it's personal choice) and you can toggle Mount R/W to R/O and lets see Supersu enabled you to make change any file in /system. If succeeded then nobody can stop you lol!
4) Now turn to Viper things , I personally use ARISE Viper4Android (it has a good reputation and large fan based forum, just see it) sound systems http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
download stable Exodus or Leviticus 1.3 or Numbers.
5) Now extratct the (say Numbers) zip file and see there is a Numbers folder (in case of Exodus or Leviticus it's pretty straight forward, you will see system folder) inside. Now copy system folder directly into /system while Make sure it's Mounted as R/O.
In case of Numbers only, If copy is succeeded then go to the customize folder and extract app and vendor folder. Rename the app folder as ViPER4Android_FX_A4.x and put it to /system/priv-app.
6) (*It's an optional step for Numbers only*) Now put the vendor to /system and merge it. When everything is installed there'll be /vendor in root, alongside /system, but it will be a symlink to /system/vendor.
** A symlink is symbolic link, it's basically a way for the file system to protect files or in this case be universally compatible because some phones have a dedicated vendor partition that would normally conflict with ARISE vendor if it wasn't symlinked, since it is it just knows the contents are within the linked directory and can display them as if they were, often with different permissions etc. **
7) Last but not the least, finally tap the ViPER4Android_FX_A4.x.apk inside priv-app folder and install it to sdcard. Open it and let's see if it requires driver update, Bang! you are done. V4A is in your system, now all you need is to reboot and see V4A is processing like shown in the picture.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Play your favorite music player and load a profile of your choice (from the extra folder in) in V4A to see what's the difference in SQ. Check it by enabling Master Power on/off. Make sure UI setting as Expert.
Finally to @Ventricle and @ephexxis , I owe to you guys and thanks to @guitardedhero and his ARISE team for this awesome mode and to @electrikjesus for his REMOUNT_RW=1 method to achieve R/W & true root in RemixOS.
Fly with ARISE!

ranaxda200 said:
For those Audiophiles like me if you wanna get Viper4Android to work with RemixOS here is the noob friendly guide;
1) MAKE SURE WHAT'S YOUR BOOT INSTALL : LEGACY OR UEFI (32 AND 64-bit) ; As for mine I have Legacy boot. So it's the guide of as such system. BTW for 64-bit system please see this awesome guide made by @electrikjesus
http://forum.xda-developers.com/remix/remix-os/guide-using-jides-remountrw1-method-to-t3431595
2) For Legacy boot of RemixOS boot installs (32 & 64 bit) using MBR from Jide's Installer (NON-UEFI)
You will want to make sure you can view hidden and system files in Explorer options, Once you do that, travel to C:\RemixOS (or where yo installed it) and using Notepad++ or your code editor of choice, find and open the menu.lst file. Then add a second entry containing the REMOUNT_RW=1 entry like you see below:
3) Once you are done, you can reboot, and choose the entry you added. It will then extract the system.sfs file to a system_dev.img, and mount it as RW for you. Once booted, go to /system partition (myself use Root explorer, it's personal choice) and you can toggle Mount R/W to R/O and lets see Supersu enabled you to make change any file in /system. If succeeded then nobody can stop you lol!
4) Now turn to Viper things , I personally use ARISE Viper4Android (it has a good reputation and large fan based forum, just see it) sound systems http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
download stable Exodus or Leviticus 1.3 and if you are an adventerous audiophile like Me, then use Latest Testing Sound Systems (like Numbers now).
5) Now extratct the (say Numbers) zip file and see there is a Numbers folder inside. Now copy all the contents directly into /system while make sure it's Mounted as R/O. If copy succeeded then go to the customize folder and extract app and vendor folder. Rename the app folder as ViPER4Android_FX_A4.x and put it to /system/priv-app and put the vendor to /system and merge it. When everything is installed there'll be /vendor in root, alongside /system, but it will be a symlink to /system/vendor. This is so that for those with an actual vendor partition so it's importatnt.
6) Last but not the least, finally tap the ViPER4Android_FX_A4.x.apk and install it to sdcard. Open it and let's see if it requires driver update, Bang! you are done. V4A is in your system, now all you need is to reboot and see V4A is processing like shown in the picture.
Play your favorite music player and load a profile of your choice (from the extra folder in) in V4A to see what's the difference in SQ. Check it by enabling Master Power on/off. Make sure UI setting as Expert.
Finally to @Ventricle and @ephexxis , I owe to you guys and thanks to @guitardedhero and his ARISE team for this awesome mode and to @electrikjesus for his REMOUNT_RW=1 method to achieve R/W & true root in RemixOS.
Fly with ARISE!
Click to expand...
Click to collapse
In extracted files I see only extras, leviticus and META-INF folders. I don't see a customize folder
There are a priv-app and vendor inside the (in my case) leviticus folder

lollyjay said:
In extracted files I see only extras, leviticus and META-INF folders. I don't see a customize folder
Click to expand...
Click to collapse
You downloaded leviticus 1.3 guess. It has no customize folder. It's in new Testing Numbers edition. I would suggest Numbers 0.9.8.7 zip. It's fine

Is it possible to make it systemless?
Sent from my Moto G using XDA Labs

OK QUESTIONS ARE ENCLOSED BY <<<>>>
4) Now turn to Viper things , I personally use ARISE Viper4Android (it has a good reputation and large fan based forum, just see it) sound systems http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
download stable Exodus or Leviticus 1.3 and if you are an adventerous audiophile like Me, then use Latest Testing Sound Systems (like Numbers now). <<<SINCE YOU BASE YOUR DIRECTIONS ON NUMBERS THEN ONLY SUGGEST NUMBERS OTHERS DO NOT HAVE THE SAME SUBFOLDERS>>>
5) Now extratct the (say Numbers) zip file and see there is a Numbers folder inside. Now copy all the contents<<<COPY THE CONTENTS, OR THE FOLDER? >>>directly into /system while make sure it's Mounted as R/O. If copy succeeded then go to the customize folder and extract app and vendor folder. Rename the app folder as ViPER4Android_FX_A4.x and put it to /system/priv-app and put the vendor to /system and merge it<<<WHAT DO YOU MEAN BY MERGE?>>>. When everything is installed there'll be /vendor in root, alongside /system, but it will be a symlink to /system/vendor.<<<MOST OF US DON'T KNOW WHAT YOU MEAN>>>This is so that for those with an actual vendor partition so it's importatnt.
6) Last but not the least, finally tap the ViPER4Android_FX_A4.x.apk<<<DO YOU MEAN THE ONE IN THE /SYSTEM/PRIV-APP/? >>>and install it to sdcard. Open it and let's see if it requires driver update, Bang! you are done. V4A is in your system, now all you need is to reboot and see V4A is processing like shown in the picture.

lollyjay said:
OK QUESTIONS ARE ENCLOSED BY <<<>>>
4) Now turn to Viper things , I personally use ARISE Viper4Android (it has a good reputation and large fan based forum, just see it) sound systems http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
download stable Exodus or Leviticus 1.3 and if you are an adventerous audiophile like Me, then use Latest Testing Sound Systems (like Numbers now). <<<SINCE YOU BASE YOUR DIRECTIONS ON NUMBERS THEN ONLY SUGGEST NUMBERS OTHERS DO NOT HAVE THE SAME SUBFOLDERS>>>
5) Now extratct the (say Numbers) zip file and see there is a Numbers folder inside. Now copy all the contents<<<COPY THE CONTENTS, OR THE FOLDER? >>>directly into /system while make sure it's Mounted as R/O. If copy succeeded then go to the customize folder and extract app and vendor folder. Rename the app folder as ViPER4Android_FX_A4.x and put it to /system/priv-app and put the vendor to /system and merge it<<<WHAT DO YOU MEAN BY MERGE?>>>. When everything is installed there'll be /vendor in root, alongside /system, but it will be a symlink to /system/vendor.<<<MOST OF US DON'T KNOW WHAT YOU MEAN>>>This is so that for those with an actual vendor partition so it's importatnt.
6) Last but not the least, finally tap the ViPER4Android_FX_A4.x.apk<<<DO YOU MEAN THE ONE IN THE /SYSTEM/PRIV-APP/? >>>and install it to sdcard. Open it and let's see if it requires driver update, Bang! you are done. V4A is in your system, now all you need is to reboot and see V4A is processing like shown in the picture.
Click to expand...
Click to collapse
OK ANSWERS ARE ENCLOSED BY **
*4)Good point. I'll re-edit in the OP, Leviticus and exodus has 'system' folders that needs to be extracted to /system patition, then no need to extract 'app' from customize as there's already priv-app in that folder. But since Numbers has been officially initial released from today I would rather suggest to try it.*
*5)copy the contents is right, means everything including ARISE version info.text to be copied to /system. It's current version info helpful for future update. Merging means merge the contents of /vendor with the existing system contents. Vendor in /customize is so that /customize/vendor will go to /system/vendor or /vendor depending on the device. As far I know symlink to /system/vendor was written to mitigate the TWRP 7 error but as this is RemixOS I'll take it as optional. :good:*
*6) As I told in exodus and leviticus there's already priv-app in the /system folder. *
Just let me know if everything goes well or not. Enjoy.

Aguys said:
Is it possible to make it systemless?
Click to expand...
Click to collapse
No idea about system less v4a right now. BTW the main difference between system less and system, besides partition, is that thise sound system files will be symlinked (symbolic link) to /system, those are files that don't exist in /system. The only exception being audio_effect.conf, which will be moved to data/media/0 so that the sound system's audio_effect.conf will be symlinked.
BTW IMO /system installation is rather better to enjoy the fuller sound quality.

OP is updated. Symlink and other regular stuffs are clearly explained

I will try this ASAP!
This gives a life to my horrible sound driver on Linux
??

modaifallah said:
I will try this ASAP!
This gives a life to my horrible sound driver on Linux
??
Click to expand...
Click to collapse
Make sure you Remount system RW to RO using step by step jide's guide( link in OP) for Linux and download following ARISE NUMBERS (official stable release from Today). Enjoy :good:
https://www.androidfilehost.com/?w=files&flid=97426

it's possible using viper without set selinux permission?

ulum.misbahul said:
it's possible using viper without set selinux permission?
Click to expand...
Click to collapse
Selinux is disabled for this ROM mate. U may check
Code#
su
#getenforce

ranaxda200 said:
For those Audiophiles like me if you wanna get Viper4Android to work with RemixOS here is the noob friendly guide;
1) MAKE SURE WHAT'S YOUR BOOT INSTALL : LEGACY OR UEFI (32 AND 64-bit) ; As for mine I have Legacy boot. So it's the guide of as such system. BTW for 64-bit system please see this awesome guide made by @electrikjesus
http://forum.xda-developers.com/remix/remix-os/guide-using-jides-remountrw1-method-to-t3431595
2) For Legacy boot of RemixOS boot installs (32 & 64 bit) using MBR from Jide's Installer (NON-UEFI)
You will want to make sure you can view hidden and system files in Explorer options, Once you do that, travel to C:\RemixOS (or where yo installed it) and using Notepad++ or your code editor of choice, find and open the menu.lst file. Then add a second entry containing the REMOUNT_RW=1 entry like you see below:
Code:
default 0
timeout 10
title Resident mode - All your data and apps are saved
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ DATA= CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
boot
title Resident mode - RW enabled
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ REMOUNT_RW=1 DATA= CREATE_DATA_IMG=1 initrd /RemixOS/initrd.img
boot
3) Once you are done, you can reboot, and choose the entry you added. It will then extract the system.sfs file to a system_dev.img, and mount it as RW for you. Once booted, go to /system partition (myself use Root explorer, it's personal choice) and you can toggle Mount R/W to R/O and lets see Supersu enabled you to make change any file in /system. If succeeded then nobody can stop you lol!
4) Now turn to Viper things , I personally use ARISE Viper4Android (it has a good reputation and large fan based forum, just see it) sound systems http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
download stable Exodus or Leviticus 1.3 or Numbers.
5) Now extratct the (say Numbers) zip file and see there is a Numbers folder (in case of Exodus or Leviticus it's pretty straight forward, you will see system folder) inside. Now copy system folder directly into /system while Make sure it's Mounted as R/O.
In case of Numbers only, If copy is succeeded then go to the customize folder and extract app and vendor folder. Rename the app folder as ViPER4Android_FX_A4.x and put it to /system/priv-app.
6) (*It's an optional step for Numbers only*) Now put the vendor to /system and merge it. When everything is installed there'll be /vendor in root, alongside /system, but it will be a symlink to /system/vendor.
** A symlink is symbolic link, it's basically a way for the file system to protect files or in this case be universally compatible because some phones have a dedicated vendor partition that would normally conflict with ARISE vendor if it wasn't symlinked, since it is it just knows the contents are within the linked directory and can display them as if they were, often with different permissions etc. **
7) Last but not the least, finally tap the ViPER4Android_FX_A4.x.apk inside priv-app folder and install it to sdcard. Open it and let's see if it requires driver update, Bang! you are done. V4A is in your system, now all you need is to reboot and see V4A is processing like shown in the picture.
View attachment 3846678
Play your favorite music player and load a profile of your choice (from the extra folder in) in V4A to see what's the difference in SQ. Check it by enabling Master Power on/off. Make sure UI setting as Expert.
Finally to @Ventricle and @ephexxis , I owe to you guys and thanks to @guitardedhero and his ARISE team for this awesome mode and to @electrikjesus for his REMOUNT_RW=1 method to achieve R/W & true root in RemixOS.
Fly with ARISE!
Click to expand...
Click to collapse
in the screenshot you posted..
the neon status is not enabled then how you are saying its working

ajaikumarnadar said:
For those Audiophiles like me if you wanna get Viper4Android to work with RemixOS here is the noob friendly guide;
1) MAKE SURE WHAT'S YOUR BOOT INSTALL : LEGACY OR UEFI (32 AND 64-bit) ; As for mine I have Legacy boot. So it's the guide of as such system. BTW for 64-bit system please see this awesome guide made by @electrikjesus
http://forum.xda-developers.com/remix/remix-os/guide-using-jides-remountrw1-method-to-t3431595
2) For Legacy boot of RemixOS boot installs (32 & 64 bit) using MBR from Jide's Installer (NON-UEFI)
You will want to make sure you can view hidden and system files in Explorer options, Once you do that, travel to C:\RemixOS (or where yo installed it) and using Notepad++ or your code editor of choice, find and open the menu.lst file. Then add a second entry containing the REMOUNT_RW=1 entry like you see below:
in the screenshot you posted..
the neon status is not enabled then how you are saying its working
Click to expand...
Click to collapse
Neon is a ARM instruction for more efficient processing. It's for x86 architecture so it's not needed.

ranaxda200 said:
For those Audiophiles like me if you wanna get Viper4Android to work with RemixOS here is the noob friendly guide;
1) MAKE SURE WHAT'S YOUR BOOT INSTALL : LEGACY OR UEFI (32 AND 64-bit) ; As for mine I have Legacy boot. So it's the guide of as such system. BTW for 64-bit system please see this awesome guide made by @electrikjesus
http://forum.xda-developers.com/remix/remix-os/guide-using-jides-remountrw1-method-to-t3431595
2) For Legacy boot of RemixOS boot installs (32 & 64 bit) using MBR from Jide's Installer (NON-UEFI)
You will want to make sure you can view hidden and system files in Explorer options, Once you do that, travel to C:\RemixOS (or where yo installed it) and using Notepad++ or your code editor of choice, find and open the menu.lst file. Then add a second entry containing the REMOUNT_RW=1 entry like you see below:
Code:
default 0
timeout 10
title Resident mode - All your data and apps are saved
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ DATA= CREATE_DATA_IMG=1
initrd /RemixOS/initrd.img
boot
title Resident mode - RW enabled
find --set-root /RemixOS/kernel
kernel /RemixOS/kernel root=/dev/ram0 androidboot.hardware=remix_x86 androidboot.selinux=permissive quiet SERIAL=random logo.showlogo=1 SRC=RemixOS/ REMOUNT_RW=1 DATA= CREATE_DATA_IMG=1 initrd /RemixOS/initrd.img
boot
3) Once you are done, you can reboot, and choose the entry you added. It will then extract the system.sfs file to a system_dev.img, and mount it as RW for you. Once booted, go to /system partition (myself use Root explorer, it's personal choice) and you can toggle Mount R/W to R/O and lets see Supersu enabled you to make change any file in /system. If succeeded then nobody can stop you lol!
4) Now turn to Viper things , I personally use ARISE Viper4Android (it has a good reputation and large fan based forum, just see it) sound systems http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
download stable Exodus or Leviticus 1.3 or Numbers.
5) Now extratct the (say Numbers) zip file and see there is a Numbers folder (in case of Exodus or Leviticus it's pretty straight forward, you will see system folder) inside. Now copy system folder directly into /system while Make sure it's Mounted as R/O.
In case of Numbers only, If copy is succeeded then go to the customize folder and extract app and vendor folder. Rename the app folder as ViPER4Android_FX_A4.x and put it to /system/priv-app.
6) (*It's an optional step for Numbers only*) Now put the vendor to /system and merge it. When everything is installed there'll be /vendor in root, alongside /system, but it will be a symlink to /system/vendor.
** A symlink is symbolic link, it's basically a way for the file system to protect files or in this case be universally compatible because some phones have a dedicated vendor partition that would normally conflict with ARISE vendor if it wasn't symlinked, since it is it just knows the contents are within the linked directory and can display them as if they were, often with different permissions etc. **
7) Last but not the least, finally tap the ViPER4Android_FX_A4.x.apk inside priv-app folder and install it to sdcard. Open it and let's see if it requires driver update, Bang! you are done. V4A is in your system, now all you need is to reboot and see V4A is processing like shown in the picture.
View attachment 3846678
Play your favorite music player and load a profile of your choice (from the extra folder in) in V4A to see what's the difference in SQ. Check it by enabling Master Power on/off. Make sure UI setting as Expert.
Finally to @Ventricle and @ephexxis , I owe to you guys and thanks to @guitardedhero and his ARISE team for this awesome mode and to @electrikjesus for his REMOUNT_RW=1 method to achieve R/W & true root in RemixOS.
Fly with ARISE!
Click to expand...
Click to collapse
what about dolby atmos or dolby digital for remix os ? any possibilities ?
good work bro.. for bringing viper installation tutorial for remix os..

i just install it, and it sounds not too good. There is no low tons(bass) only high, even if i boost bass to max i hear only small change. I tryed exodus and numbers 3,5 and imhave same problem.
Second thing. Installing this mods corrupting my MBR and i can't boot to windows, only remix os
any ideas how to fix

Related

[MultiROM] [LINUX] [How-to] Rom installers for sdcard

This is an (hopefully) updated collection of all roms (not android based, but other linux OS, like ubuntu, archlinux, fedora...) for nexus 7 (grouper and tilapia) available using the MultiROM system.
MultiROM is an amazing hack (I want to thank again its author, Tasssadar) that permits to boot different OS (multiboot) and different android roms. It starts between kernel and rom init, showing a sort of bootloader dialog to choose which system to boot.
It supports installing (and booting, of course) roms to USB drives.
To use MultiROM you need multirom installation zip , a modified TWRP recovery and kernels with kexec support. Relax, is not hard or long to do this.
More information and installation (of MultiROM, recovery and kernels) --> [ MULTIROM ]
PS: I need to specify I coded nothing, my only work was helping with issues, repacking roms, make them work. I want to say thank you to all devs are developing for Nexus 7, I'm doing this because I appreciate their work and I want MultiROM to rise. It deserves to.
HOW TO INSTALL A ROM.
Tasssadar provided also a zip template (see the [ WIKI ] for more info) that is incredibly easy to use.
To install a linux os to sdcard, you just need to download the zip and flash it like a normal update.zip.
It won't replace your internal rom, because it is going to install in /sdcard, not in /system or /data. And it WON'T wipe anything.
Remember that flashing ubuntu or android rom is DIFFERENT from flashing those zips. To flash ubuntu or another android rom you need to use MultiROM menu under ADVANCED voice in recovery (again, see wiki or multirom thread if you need more information).
ROM PACKS.
In the next post I'll share links for rom zips. If you have other zips or if you have built other zips, please share them. They will be (hopefully) added to the list. If not, please pm me. I can't read all posts.
If you want to share a zip, please try it first. I don't know if I'll be able to test everything real-time, and I don't want anyone to see his sdcard erased or strange things like this. MultiROM has a percent of risk, but nobody has lost his data till now. So please share zips consciously.
ROM LIST (DOWNLOADS)
* [NEW] PLASMA ACTIVE 4.0 (20140121)
mirror: http://d-h.st/Khh
old version: https://docs.google.com/file/d/0B9ZvdqAbuJi2blQ0TDgweFFKTlU/edit
description: KDE for embedded devices. Very cool and interesting. 4.0 version is more stable, video codec is working as well. Little slow booting.
* BODHI LINUX 20130109
old version: INITIAL RELEASE
notes: old version passwd for root and armhf user is trustno1 (sorry for that, is my fault. In new release it is again bodhilinux)
description: Ubuntu with E17 (Enlightenment) with mobile GUI. Pretty stable and... veeery fast.
*ArchLinux 20130113-2
old version: -
description: ArchLinux. Simply. Not designed for basic users. Really powerfull, with already packed KDE, Gnome-shell, LXDE, XFCE, Enlightenment environments (and many others probably). Needs testing, and some love, as it's initial release.
*WebOS ALPHA
old version: http://www.mediafire.com/?3m58uuvysxiwypw
description: still in alpha stage, unstable. Interesting project. Needs love.
* [MANUAL INSTALL] Ubuntu Touch Tablet DEVELOPER PREVIEW
old version: -
description: developer preview, android-based, with the new Ubuntu Touch UI.
[NEW] Use MultiROM app to install the latest version in the easiest way
ROMS TO BE PACKED/MADE WORKING:
fedora4nexus7?
PAY ATTENTION: NEW MULTIROM CHANGED THE ROM ZIP STRUCTURE!
NEW STRUCTURE HERE.
I GUESS YOU CAN USE OLD ZIPS, BUT I CAN'T TRY AND IT'S BETTER TO USE NEW METHOD (REPACK NEEDED)
STEPS TO CREATE A NEW ROM ZIP (EASY-WAY):
* first, download the template (reworked by me)
* then, unzip the template, put the root.tar.gz and rom_info.txt inside rom folder (if you don't know what I'm talking about, read again the wiki - link above)
* edit rom name inside of scripts/extract.sh script (it's the only thing you have to edit, unless you want it to do something else, but be careful in that case)
* select the 3 folders (META-INF, rom, scripts) and zip them in a zip called <DISTRONAME>-MultiROM-Installer-<VERSION>.zip (I think it's a good standard, if you don't like simply name it another way, but I reckon that using a standard would be a very good thing)
*when the zip is finished, upload your zip somewhere (I use google drive now, but I hope I'll have my storage sometime in the future) and share the link here. I will add it to the list.
If I don't, pm me.
[EDIT] new packing method for webos available https://github.com/Tasssadar/webos_multirom_packer [/EDIT]
MORE INFORMATION.
PLASMA ACTIVE.
known bugs: https://wiki.merproject.org/wiki/Community_Workspace/Tegra3/Nexus7/PA_Known_Issues
username/password : mer/mer, root/mer
Interesting features : Plays 720p movies full screen with sound and 1080p full screen down scaled with sound.
BODHI LINUX.
known bugs: http://forums.bodhilinux.com/index.php?/forum/40-nexus-7/
username/password: armhf/bodhilinux
useful page (customization, add software, guides): http://wiki.bodhilinux.com/doku.php
ARCHLINUX.
armv7h images: http://os.archlinuxarm.org/os/ (see tegra directory)
username/password: arch/arch, root/root
useful link (bible): https://wiki.archlinux.org/
infos: needs an OTG keyboard or to use "sudo screen /dev/ttyACM0 115200" to connect via usb.
While you are connected you need to configure wifi. I use a script that simply uses iwconfig, wpa_supplicant.conf and dhcpcd to get a wifi connection.
The rest is up to you.
Enlightenment is preinstalled in build 20130113-2.
UBUNTU TOUCH.
infos: use MultiROM Manager app to install it.
GENERAL.
lintz said:
Recomended "fixes" after first install (Mer, Plasma ndr) :
Install custom keyboard (write this comands in terminal start with su and after the password for root by default mer)
1. zypper ar -G http://repo.pub.meego.com/home:/won...wonko:branches:Project:KDE:Trunk:Testing.repo
2. zypper up maliit-active libmaliit-quick
3. killall -9 maliit-server
Update the system (use su and root password first)
zypper ref && zypper up
Install GUI package manager (same here su and root password)
zypper in apper
Click to expand...
Click to collapse
Thanks to lintz for the suggestions.
LATEST HOT NEWS.
-updated with latest Plasma version.
-updated with Ubuntu Touch
-updated with latest Plasma & WEBOS version (repacked for new MultiROM structure)
-updated with Ubuntu Touch Dev Preview
-updated OP with arch infos.
-Making zip for new BodhiLinux version, that now has correct passwd
Code:
bodhilinux
as it should be.
xela92 said:
Making zip for new BodhiLinux version, that now has correct passwd
Code:
bodhilinux
as it should be.
Click to expand...
Click to collapse
thx xela, I'm still having trouble creating a zip with the template. perhaps you could post the steps you took to create the new bodhi release
bonzer2u said:
thx xela, I'm still having trouble creating a zip with the template. perhaps you could post the steps you took to create the new bodhi release
Click to expand...
Click to collapse
Steps how-to done
Later (when upload ends) I'll share Bodhi new version installer link
Nice thread. Can't wait to try some other distro's.
xela92 said:
ROM LIST (DOWNLOADS)
* PLASMA ACTIVE 20130109
old version: -
description: KDE for embedded devices. Very cool and interesting, but still an alpha.
* BODHI LINUX (uploading new version)
old version: INITIAL RELEASE
notes: old version passwd for root and armhf user is trustno1 (sorry for that, is my fault. In new release it is again bodhilinux)
description: Ubuntu with E17 (Enlightenment) with mobile GUI. Pretty stable and... veeery fast.
Click to expand...
Click to collapse
Needs more info.
Add following kategories
Plasma Active
Bugs : https://wiki.merproject.org/wiki/Community_Workspace/Tegra3/Nexus7/PA_Known_Issues
Username passwords : mer/mer, root/mer
Recomended "fixes" after first install :
Install custom keyboard (write this comands in terminal start with su and after the password for root by default mer)
1. zypper ar -G http://repo.pub.meego.com/home:/won...wonko:branches:Project:KDE:Trunk:Testing.repo
2. zypper up maliit-active libmaliit-quick
3. killall -9 maliit-server
Update the system (use su and root password first)
zypper ref && zypper up
Install GUI package manager (same here su and root password)
zypper in apper
Features : Plays 720p movies full screen with sound and 1080p full screen down scaled with sound.
Same thing for Bodhi. But I dont know the detales about it since I don't use it.
PS as it is now this thread feels as a start to a redundant thread to what is written in Tassadars first 3 posts in the MultiRom thread. Better if you focus on the current distros that don't have any "real" maintener here on xda.
I will add those categories later
lintz said:
Needs more info.
Add following kategories
Plasma Active
Bugs : https://wiki.merproject.org/wiki/Community_Workspace/Tegra3/Nexus7/PA_Known_Issues
Username passwords : mer/mer, root/mer
Recomended "fixes" after first install :
Install custom keyboard (write this comands in terminal start with su and after the password for root by default mer)
1. zypper ar -G http://repo.pub.meego.com/home:/won...wonko:branches:Project:KDE:Trunk:Testing.repo
2. zypper up maliit-active libmaliit-quick
3. killall -9 maliit-server
Update the system (use su and root password first)
zypper ref && zypper up
Install GUI package manager (same here su and root password)
zypper in apper
Features : Plays 720p movies full screen with sound and 1080p full screen down scaled with sound.
Same thing for Bodhi. But I dont know the detales about it since I don't use it.
PS as it is now this thread feels as a start to a redundant thread to what is written in Tassadars first 3 posts in the MultiRom thread. Better if you focus on the current distros that don't have any "real" maintener here on xda.
Click to expand...
Click to collapse
thanks
this solved my onscreen keyboard problem (not working over browser) ... now only gui glitches was left (multitasking bar )
xela92 said:
STEPS TO CREATE A NEW ROM ZIP (EASY-WAY):
* first, download the template (reworked by me)
* then, unzip the template, put the root.tar.gz and rom_info.txt inside rom folder (if you don't know what I'm talking about, read again the wiki - link above)
* edit rom name inside of scripts/extract.sh script (it's the only thing you have to edit, unless you want it to do something else, but be careful in that case)
* select the 3 folders (META-INF, rom, scripts) and zip them in a zip called <DISTRONAME>-MultiROM-Installer-<VERSION>.zip (I think it's a good standard, if you don't like simply name it another way, but I reckon that using a standard would be a very good thing)
*when the zip is finished, upload your zip somewhere (I use google drive now, but I hope I'll have my storage sometime in the future) and share the link here. I will add it to the list.
If I don't, pm me.
Click to expand...
Click to collapse
Hi xela,
I understand the process except for creating the 'root.tar.gz' file from a compressed image (.img or .raw) file. Do you need to extract the image file to the /root folder and then recompress with a command similar to:
sudo tar --numeric-owner -zpcf root.tar.gz ./*
Nice Topic, i've tried your first Bodhi Zip and it seems very fast and stable to me. A few bugs, but nothing major.
I'm waiting for the new Version to finish uploading
bonzer2u said:
Hi xela,
I understand the process except for creating the 'root.tar.gz' file from a compressed image (.img or .raw) file. Do you need to extract the image file to the /root folder and then recompress with a command similar to:
sudo tar --numeric-owner -zpcf root.tar.gz ./*
Click to expand...
Click to collapse
I couldn't find out how to mount those IMG files. I thought they were ext4 fs but they aren't. I tried to use dd to flash them on a drive but failure again. So to extract rootfs I install them with standard procedure (Ubuntu) and the repack roofs to tar.gz. It could be useful to find out how to directly extract rootfs, because it's the same method used by Ubuntu. With the difference that Ubuntu uses zsync to permit fast upgrade...!
xela92 said:
I couldn't find out how to mount those IMG files. I thought they were ext4 fs but they aren't. I tried to use dd to flash them on a drive but failure again. So to extract rootfs I install them with standard procedure (Ubuntu) and the repack roofs to tar.gz. It could be useful to find out how to directly extract rootfs, because it's the same method used by Ubuntu. With the difference that Ubuntu uses zsync to permit fast upgrade...!
Click to expand...
Click to collapse
I could never get it mounted as well.... Is this why your having a delay in uploading the new bodhi release?
bonzer2u said:
Hi xela,
I understand the process except for creating the 'root.tar.gz' file from a compressed image (.img or .raw) file. Do you need to extract the image file to the /root folder and then recompress with a command similar to:
sudo tar --numeric-owner -zpcf root.tar.gz ./*
Click to expand...
Click to collapse
If you can get the files from the .img files, you really dont need the zip to install it, just creat a dir with the name for the OS, then inside create a dir called root, then inside extract the .img
For the rom_info.txt file, just make the changes needed and put them on the same dir that ../root is and restart and you should be able to boot form it.
Rafase282 said:
If you can get the files from the .img files, you really dont need the zip to install it, just creat a dir with the name for the OS, then inside create a dir called root, then inside extract the .img
For the rom_info.txt file, just make the changes needed and put them on the same dir that ../root is and restart and you should be able to boot form it.
Click to expand...
Click to collapse
Unfortunately we have been unable to mount/extract anything from the image although it appears it may install via the multirom/ubuntu method
bonzer2u said:
I could never get it mounted as well.... Is this why your having a delay in uploading the new bodhi release?
Click to expand...
Click to collapse
I'm not at home right know, but in 30 minutes I'll post it
shared the latest bodhi linux version get the link in OP
bonzer2u said:
Unfortunately we have been unable to mount/extract anything from the image although it appears it may install via the multirom/ubuntu method
Click to expand...
Click to collapse
I think zip solution is the best and most "standard". When I make a zip I know it will work, because it's the final, multiROM surely compatible, version. And I can test it immediately, fix it, reflash, and try without messing the world up. I think update zips are the most user-friendly way too. But that's only MHO.

[EOL] [KITCHEN] ArchiKitchen - Android Kitchen [Linux]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ArchiKitchen - Brand new Android Kitchen
Commits/Changes -> https://github.com/JustArchi/ArchiKitchen/commits/master
Source -> https://github.com/JustArchi/ArchiKitchen
TODO list -> https://github.com/JustArchi/ArchiKitchen/issues?state=open
Download. Of course you can also clone my repository to stay up to date.
[SIZE="+1"]Features:[/SIZE]
Compatible with every Linux, which provides bash shell (every available distro nowadays)
Full ARM/X86 support for all included android binaries (Root, Busybox)
Dynamic permissions - A generic list of all available permissions, with proper filter for your local build and device
Dynamic symlinks - A generic list of all available symlinks, with proper filter for your local build and device. Additionaly if you're building from stock image, support for including symlinks from image itself, which results in best 1:1 copy
FS-friendly method of flashing - ROMs created with ArchiKitchen are fully compatible with every available partition, which means that they don't reformat /system partition during flashing. This is extremely important for dual-FS support for example for EXT4 and F2FS on SGS3.
Kernel repacking - Powered by mkbootimg, repacking a kernel never was easier. With one click you're extracting the kernel along with ramdisk to the proper folder, and with the second you repack it back
Deodexing - With one click you can easily deodex your whole ROM. With multi-threaded process and automatic API detection, this never was easier as well.
ArchiDroid Init.d - Forget about relying on kernel's ramdisk. Implement init.d in your ROM, not the kernel!
Latest [Bak]smali
Latest SuperSU
Latest Busybox
Latest Zipalign
And many more in the unique shell ktichen
[SIZE="+1"]Credits:[/SIZE]
@osm0sis - For mkbootimg
@Chainfire - For SuperSU
@Stericson - For BusyBox
@JesusFreke - For [Bak]smali
@bgcngm - For MTK-Tools
AOSP - For Zipalign
ArchiKitchen Tutorial
Part 1 - Setting up Linux & ArchiKitchen on Windows
https://www.youtube.com/watch?v=ktedmhWHz2M
By watching above step-by-step video, you'll learn:
1. How to install Debian on your VirtualBox machine
2. How to connect Windows with Linux through a shared VBox folder
3. How to install ArchiKitchen
4. How to create your first custom ROM, with built-in Root and Busybox
Extra information:
- You can use any virtualization method you want. I suggest using VirtualBox, as it's very easy, flexible and free virtualization solution.
- You can use nearly any Linux distro. I suggest either Debian or Ubuntu, as both of them have excellent support and are very easy to install and use, compared to some other ones. However if you feel fine in Linux environment, you can install nearly any distro you like.
Mini.iso link
Weekly Debian Testing.iso link
Installing virtualbox additions: apt-get install virtualbox-guest-dkms
Installing required tools: apt-get install zip unzip openjdk-7-jdk
Mounting a shared VBox folder: mount -t vboxsf yourName /path/to/yourFolder
Tutorials made by other developers: @bigrammy
Part 1. Prepare for linux Installation https://www.youtube.com/watch?v=aDsQTcDvSMY
Part 2. Install Linux (Ubuntu/Zorin) https://www.youtube.com/watch?v=KwnIjCXXM5Y
Part 2.5. Edit Winows bootloader to boot Linux: https://www.youtube.com/watch?v=gNpQucQxcFQ
Part 3. Work as Root Mod & Install ArchiKitchen https://www.youtube.com/watch?v=T_ad7uML8QM
Part 4. How to add your device locally to the Kitchen: http://youtu.be/YXNDcmf6GhI
ArchiKitchen Questions & Answers
Q: What is this "ArchiKitchen"?
A: A Linux-based kitchen, with a main objective of converting stock ROM drops in .img, .tar.md5 or similar formats to CWM-flashable .zip.
Q: So I can create my own custom ROM based on stock ROM with it?
A: Exactly.
Q: Is it for Linux only? Why windows is not supported?
A: Let's face it, Android is based on Linux kernel and we could call it a mobile UNIX fork. It's hard to work with Linux-based things on Windows, in fact, Windows doesn't even offer Bash (Bourne-again shell), which is absolutely core for ArchiKitchen. Working with windows is painful, for example - .img mounting. I can very easily mount any filesystem image on Linux with just one command, while doing so on Windows usually requires a massive convertion of whole image to .zip file, then extracting a single files. Also, Windows doesn't support symbolic links, and this makes it impossible to create 1:1 copy of the image "translated" to zip file. Therefore, making a Windows port would require lots of more work and solving issues, and even with that it would still cause some core features to be unavailable. However, launching Linux on Windows is very easy thanks to VirtualBox and other virtualization software, so you don't need to reformat your PC or stick purely with Linux. In fact, this is the proposed way of using ArchiKitchen - Installing a native Linux distro (suggested: Debian or Ubuntu) and then installing ArchiKitchen on it. Take a look at tutorial to see how easily you can install and run ArchiKitchen in Linux VBox.
Q: Is Cygwin supported?
A: No. Cygwin IS NOT supported and it's not planned to add such support. Reason is nearly the same as above one. However, ArchiKitchen is open-source project and I'm open for all pull requests, so perhaps somebody will add support for Cygwin in the future. Until then, ArchiKitchen is compatible ONLY with Linux, and if you use it on Cygwin you're on your own with the issues that may happen.
Q: Which phones are supported?
A: ArchiKitchen contains a local "database" of devices, which includes a kernel/modem blocks to be used. However, as long as you know the partition layour of your device (kernel block), ArchiKitchen works with every phone and every Android variant. I'm trying to make it as universal as possible, so even if your device does not exist in our local database, it should work.
Q: How can I add my own phone to the local database?
A: If it doesn't exist yet, take a look at "product" folder. Inside you can notice various devices with name based on their models. ArchiKitchen will detect your ROM's model and check inside if it exists, if it does, then some properties for this model will be loaded, if it doesn't exist, then ArchiKitchen will ask user for them. Probably the best idea is to copy one of the already available models (for example "m0" - Samsung Galaxy S3), then rename new copied folder to your model name and finally edit files inside.
Q: What is "NULL" text found for example in some MODEM files in the database?
A: Some phones have a possibility to flash modem directly from CWM, others don't. "NULL" text indicates that this model does not support flashing modem.bin, so even if ArchiKitchen finds and recognizes it, it will pop up an error telling you that it unfortunately can't be used.
Q: Where is SYSTEM block?
A: System block is not being used at all, as it's a valid partition and should be located in "fstab" file in recovery already. ArchiKitchen mounts system automatically through "mount" binary, with automatic filesystem and /system path. I consider providing a system block as something obsolete, because it's only required when you're formatting a partition, and even during flashing, a wipe - delete_recursive() function is enough. Therefore, ArchiKitchen does NOT require providing a /system block.
ArchiKitchen Troubleshooting
Q: It looks like something is wrong with zipalign command. I can notice errors like "./zipalign: No such file or directory"
A: This is because zipalign is x86 binary (32-bit), while you have amd64 (64-bit) Linux. Therefore, we must install some missing core packages to properly support x86 binaries. This will do the trick:
Code:
apt-get install lib32stdc++6 lib32z1
[SIZE="+1"]ArchiDroid Init.d[/SIZE]
ArchiDroid Init.d is an innovative method for including init.d support in the ROM itself, and not in the kernel. ArchiKitchen supports adding ArchiDroid Init.d to any Android ROM.
ArchiDroid Init.d is based on two files. A core - debuggerd hook, and a check part - simple init.d script.
Init.d script is named 00ARCHIDROID_INITD, and it only creates a special file to notify the core that init.d has been already executed, therefore it can't conflict with anything and it's completely safe.
The core is a hook for special /system/bin/debuggerd binary, which is normally called once during initial boot. Therefore, when it's called, ArchiDroid Init.d firstly waits a specified amount of time (default: 5 seconds), in case if user has already a kernel with init.d support. This is required because otherwise all init.d scripts would be executed twice - by kernel and our init.d. After specified time, if init.d is still not executed, our hook executes all scripts in alfabetical order. Lastly, when we're done, hook is executing original debuggerd binary (default: debuggerd.real) and shares the environment, arguments and everything. This is a perfect method for implementing init.d in the ROM itself, because we don't need to trust the kernel that it supports and executes init.d properly. We give it a 5 seconds to execute it, and eventually we do the job if kernel is not interested in that. This way we can support both custom kernels with native init.d support (we wait initial delay, if kernel executes init.d, all is fine and we don't have to do so), and also pure stock kernels without init.d support (we wait initial delay, kernel doesn't care about init.d, so we're executing it).
I think that such hook works far better than relying on the kernel and modyfing stock ramdisks. Also we're sure that even if user changes kernel to any custom one, we still have reliable init.d support, regardless if custom kernel supports init.d or not.
Reserved.
JustArchi said:
It's a bit quiet in here, I was expecting more noise
Click to expand...
Click to collapse
Me too!
THX for your work!!!
If i get my new Laptop next few days i will dl and test it!
Gesendet von meinem GT-I9505 mit Tapatalk 2
Harris_xx said:
Me too!
THX for your work!!!
If i get my new Laptop next few days i will dl and test it!
Gesendet von meinem GT-I9505 mit Tapatalk 2
Click to expand...
Click to collapse
Looking forward.
i really appreciate your work, like every time
In general whole kitchen needs a magic touch more or less but firstly I'll want to make it fully usable (and modern!) then eventually rework it.
As for now it's more or less up-to-date. Also added Note3 variant.
Thanks for your work and projekt!
I will download and test it with the new Galaxy Note 10.1 2014 :good: (Android 4.3)
Feel free to test it, but keep in mind that it's still work in progress .
Today I've added new experimental method for *better* handling setting up rom directory. As for now it supports only system.img in sgs format, however it automatically extracts it (if needed) from any tar/zip package, also with properly detecting cache.img. This is the main feature I was missing in original kitchen.
https://github.com/JustArchi/Android-Kitchen/commit/cf025ebf6573d23e5d2b7cfde258d9b7c36abd29
Just please don't track "wip" branch, as it's rebased often and merged into master when ready .
This is great, as I love the kitchen it is awesome that you've updated it. I'll be trying it out tonight. Thanks for your work.
Sent from my XT1032 using XDA Premium 4 mobile app
Great work :good:
Tested New device LG G2
Looks very good, thanks for updating the kitchen.
Got an error when using the kitchen:
Code:
-----------------------------------------------------------------
BusyBox is an executable file that combines tiny versions of
many common UNIX utilities. It is required for some root-enabled
applications.
-----------------------------------------------------------------
Add BusyBox (y/n)? (default: y):
Found ./system/xbin/su
Found /system/xbin
Working folder already has /system/xbin/busybox
Replace with BusyBox 1.21.1 (y/n)? (default: y):
Replacing /system/xbin/busybox
Adding /system/xbin/busybox
Error: No update-script found!
Press Enter to continue
Due to that I converted the update-script to edify.
Perka said:
Got an error when using the kitchen:
Code:
-----------------------------------------------------------------
BusyBox is an executable file that combines tiny versions of
many common UNIX utilities. It is required for some root-enabled
applications.
-----------------------------------------------------------------
Add BusyBox (y/n)? (default: y):
Found ./system/xbin/su
Found /system/xbin
Working folder already has /system/xbin/busybox
Replace with BusyBox 1.21.1 (y/n)? (default: y):
Replacing /system/xbin/busybox
Adding /system/xbin/busybox
Error: No update-script found!
Press Enter to continue
Due to that I converted the update-script to edify.
Click to expand...
Click to collapse
Actually kitchen can work only with update-script, although it converts it to updater-script when building rom.
This is on my todo but it's a bit complicated (many dependencies), so it needs major rework.
As for now I suggest avoiding conversion before final build.
JustArchi said:
Actually kitchen can work only with update-script, although it converts it to updater-script when building rom.
This is on my todo but it's a bit complicated (many dependencies), so it needs major rework.
As for now I suggest avoiding conversion before final build.
Click to expand...
Click to collapse
Thanks.
Also
1. with koush rooting theres no deamonsu in xbin, is this right?
2. when rooting the kernel is still ro.adb.secure=1 should be 0 or?
3. would be great if the kitchen adds a modded adbd in ramdisk/sbin (to get root directly in adb)
Again thanks
Perka said:
Thanks.
Also
1. with koush rooting theres no deamonsu in xbin, is this right?
2. when rooting the kernel is still ro.adb.secure=1 should be 0 or?
3. would be great if the kitchen adds a modded adbd in ramdisk/sbin (to get root directly in adb)
Again thanks
Click to expand...
Click to collapse
1. That's right, koush doesn't have direct support for su daemon.
2. User should be able to modify this, on todo with many other things...
3. I think we can do it, soon .
JustArchi said:
1. That's right, koush doesn't have direct support for su daemon.
2. User should be able to modify this, on todo with many other things...
3. I think we can do it, soon .
Click to expand...
Click to collapse
Sounds good
---------- Post added at 03:50 PM ---------- Previous post was at 03:44 PM ----------
Donation made
4T106212CC7164407
i worked with planty firmwareswith the latest kitchen for my devices but anytime the SuperSu after installation was saying something like "there is a SuperSu, but not Supersu binary installed". that thing was gone after i flash the SuperSu update binary. Does your kitchen gonna give me SuperSu from the start (instalation)?

[Mini-Howto] Layers Management via Init.d script

Like many of you, I like to keep my Android system rootless and true to stock as much as possible. However, I like to be able to enjoy the native support of layers for better look n feel. I wrote the script attached to help me with it however, it doesn't come easy without root access. There are some work cut out for you, read below.
Prerequisites:
Have extracted theme from layers theme app from Play Store. No, I'm not talking about the main theme app which is used by Layers Manager. Rather, it's the apks that go into the /vendor/overlay. I tried to extract respective apks out of the main one without using Layers Manager. However, my attempts yielded no success as I'm getting FCs all over, so I must be missing something. I current have a Nexus 9 which is rooted with Layers Manager, I use N9 for testing out and bring the /vendor/overlay/*.apk onto my N6P under /sdcard for my script to process. If you know of a better way, by all means share.
Of course, kernel which support INIT.D.
TWRP installed for root access via recovery, a MUST.
Busybox installed via flashable zip
Install:
- Download the script attached
- Rename .txt to .sh
- Have all extracted themed apks in one directory. For instance, I like fa and art layers, so my directory on sdcard as such /sdcard/0flash/layers/fa/fa_*.apk
- Change up the first few lines to match your environment
- Boot into twrp, mount /system if needed
- Drop the script into /system/etc/init.d
- chmod 755 /system/etc/init.d/01layersmanager.sh
- Create a file named ".current_theme" in /sdcard/
- In the above file (.current_theme), put the name of theme you want init.d to install. Example, if I want to install "fa" then I'll just have a line of text fa in it (same goes to art, coalesce,etc). IMPORTANT: no trailing new line.
- Reboot and test it out
- If theme successfully installed, you'll see it.
- Also, the /sdcard/.current_theme file will be updated with "current" to avoid theme installation on next reboot if you don't want to install new themes.
Troubleshoot:
See /sdcard/debug.txt for info. If you want additional information dumped, edit the init.d script to echo out more.
O bio hnki
vboyz103 said:
Like many of you, I like to keep my Android system rootless and true to stock as much as possible. However, I like to be able to enjoy the native support of layers for better look n feel. I wrote the script attached to help me with it however, it doesn't come easy without root access. There are some work cut out for you, read below.
Prerequisites:
Have extracted theme from layers theme app from Play Store. No, I'm not talking about the main theme app which is used by Layers Manager. Rather, it's the apks that go into the /vendor/overlay. I tried to extract respective apks out of the main one without using Layers Manager. However, my attempts yielded no success as I'm getting FCs all over, so I must be missing something. I current have a Nexus 9 which is rooted with Layers Manager, I use N9 for testing out and bring the /vendor/overlay/*.apk onto my N6P under /sdcard for my script to process. If you know of a better way, by all means share.
Of course, kernel which support INIT.D.
TWRP installed for root access via recovery, a MUST.
Busybox installed via flashable zip
Install:
- Download the script attached
- Rename .txt to .sh
- Have all extracted themed apks in one directory. For instance, I like fa and art layers, so my directory on sdcard as such /sdcard/0flash/layers/fa/fa_*.apk
- Change up the first few lines to match your environment
- Boot into twrp, mount /system if needed
- Drop the script into /system/etc/init.d
- chmod 755 /system/etc/init.d/01layersmanager.sh
- Create a file named ".current_theme" in /sdcard/
- In the above file (.current_theme), put the name of theme you want init.d to install. Example, if I want to install "fa" then I'll just have a line of text fa in it (same goes to art, coalesce,etc). IMPORTANT: no trailing new line.
- Reboot and test it out
- If theme successfully installed, you'll see it.
- Also, the /sdcard/.current_theme file will be updated with "current" to avoid theme installation on next reboot if you don't want to install new themes.
Troubleshoot:
See /sdcard/debug.txt for info. If you want additional information dumped, edit the init.d script to echo out more.
Click to expand...
Click to collapse
Yt? Bird :
Sent from my Nexus 6P using XDA-Developers mobile app

I need help on how to flash "Magisk" to Remix OS

Read the title.
Flashfire can't seem to work.
Hope you can help me.
vinnce143 said:
Read the title.
Flashfire can't seem to work.
Hope you can help me.
Click to expand...
Click to collapse
Obviously you can't use flashfire as RemixOS doesn't have and can't exactly use a recovery.img
What would you need Magisk for? I did try a while ago to install it manually but that didn't work... I might try again as I know slight more about how it works; but can't really see the benefit of it on Remix.
benefit of magisk on Remix OS:
be rooted but able to quickly and easily unmount root for apps that use safetynet, such as pokemon go.
trevorcobb said:
benefit of magisk on Remix OS:
be rooted but able to quickly and easily unmount root for apps that use safetynet, such as pokemon go.
Click to expand...
Click to collapse
I'll take another look but I don't think RemixOS would pass safety net, regardless of magisk.
And I'm not sure why anyone would want to play Pokemon GO on a PC/tablet
HypoTurtle said:
I'll take another look but I don't think RemixOS would pass safety net, regardless of magisk.
And I'm not sure why anyone would want to play Pokemon GO on a PC/tablet
Click to expand...
Click to collapse
you make a good point about passing safetynet even with magisk installed and functional.
people play Pokemon Go on a PC/Tablet by using a GPS location spoofer, which is usually accompanied by an Xposed module that hides that mock location is turned on, so they don't get banned by Niantic. this enables people to "walk" around with a little on-screen GPS. my interest is because I have Nougat on my N6P and there is no Xposed for Nougat yet.
trevorcobb said:
you make a good point about passing safetynet even with magisk installed and functional.
people play Pokemon Go on a PC/Tablet by using a GPS location spoofer, which is usually accompanied by an Xposed module that hides that mock location is turned on, so they don't get banned by Niantic. this enables people to "walk" around with a little on-screen GPS. my interest is because I have Nougat on my N6P and there is no Xposed for Nougat yet.
Click to expand...
Click to collapse
I have just now made a ramdisk/magisk.img for magisk with 64bit 3.0.205.
Only done the magisk part (no magisk SU or xposed yet)
Screenshot attached - using stock ro system (system.sfs). Essentially that would be the limit of ro system; I could add a magisk SU and have the magisk app claim proper root installed but all disabling root would do is revert back to the stock com.android.setting su
To use it properly I'd say you would need to unroot system:
boot with REMOUNT_RW=1
Install SuperSU and let it replace com.android.settings su
Unroot with SuperSU
Then probably optionally to convert system_dev.img to system.sfs to make it ro again
@trevorcobb the selinux might be an issue with SafetyNet - see if you can boot without that added to grub {gonna check on mine but doubt it'll boot}
My point about Pokemon Go is that there more/better apps than that if you don't play it properly with GPS; but I guess that's just the orienteer in me...
I'll post a build of magisk with SU and Xposed added {it'll be up at least tomorrow}. Install will be the similar to Systemless SU/xposed [a modified ramdisk and a /data/magisk.img file]
UPDATE phh superuser added to magisk which has turned root off {blocks com.android.settings} - but can't seem to install phh's supersu apk; so stuck unrooted {ALT&F1 still has su but it uses phh's su now}. Will need to recheck with the x86 version.
UPDATE2 not going to get anywhere with phh due to the the superuser baked into settings; going with SuperSU should be fine - it just means another .img is needed.
UPDATE3 Having a bit more trouble with this. Tried Magisk; Magisk superSU [essentially just Systemless-SU] and Magisk xposed but can't get xposed to activate. Will try with Magisk, SuperSU and Systemless xposed - but don't know if there is actually any benefit here [would need an updated x86_64 xposed version for suhide to work]
HypoTurtle said:
I have just now made a ramdisk/magisk.img for magisk with 64bit 3.0.205.
Only done the magisk part (no magisk SU or xposed yet)
...
I'll post a build of magisk with SU and Xposed added {it'll be up at least tomorrow}. Install will be the similar to Systemless SU/xposed [a modified ramdisk and a /data/magisk.img file]
Click to expand...
Click to collapse
holy chit! thanks so much!!
I am jumping in to follow along.....for the record I am using this solely to play Pokemon Go with my son.
I modify initrd.img,use /mnt/$SRC/su folder,and mount su/sbin、su/init.rc,needn't modify ramdisk.img ,I edit more su/sbin/launch_daemonsu.sh ,delete mount img .
about “magisk”,I just edit su/init.rc,symlink su /magisk,I edit more /su/sbin/magic_mask.sh ,delete mount img .
youling257 said:
I modify initrd.img,use /mnt/$SRC/su folder,and mount su/sbin、su/init.rc,needn't modify ramdisk.img ,I edit more su/sbin/launch_daemonsu.sh ,delete mount img .
about “magisk”,I just edit su/init.rc,symlink su /magisk,I edit more /su/sbin/magic_mask.sh ,delete mount img .
Click to expand...
Click to collapse
@youling257 Just to clear up anyone elses confusion... you are running on a ext4 partition, right?
The issue is more with the xposed version. For this to be of any benefit over systemless, you`d need suhide to work, which needs v86.2 and we don`t have a version for x86_64, there is one for x86 so I`ll try and get around to making a x86 magisk.img I already have modified the installer script for it.
HypoTurtle said:
@youling257 Just to clear up anyone elses confusion... you are running on a ext4 partition, right?
Click to expand...
Click to collapse
please see this screenshot,i use f2fs partition
trevorcobb said:
holy chit! thanks so much!!
Click to expand...
Click to collapse
youling257 said:
I modify initrd.img,use /mnt/$SRC/su folder,and mount su/sbin、su/init.rc,needn't modify ramdisk.img ,I edit more su/sbin/launch_daemonsu.sh ,delete mount img .
about “magisk”,I just edit su/init.rc,symlink su /magisk,I edit more /su/sbin/magic_mask.sh ,delete mount img .
Click to expand...
Click to collapse
Mind doing a walk through for the less genisus in the group.
laserspeeddemon said:
Mind doing a walk through for the less genisus in the group.
Click to expand...
Click to collapse
I am sorry if this is annoying, and please don't hold any ill towards me for this, however genius in plural is genii (I had also thought that it is geniuses before I had learned this a few years ago).
moriel5 said:
I am sorry if this is annoying, and please don't hold any ill towards me for this, however genius in plural is genii (I had also thought that it is geniuses before I had learned this a few years ago).
Click to expand...
Click to collapse
In this usage it is actually geniuses, if it was the original Latin use [to refer to a genie/jinn] the plural would be genii but the meaning of intellect is old English, so the plural is geniuses...
Any way what @youling257 did was take the changed files from the ramdisk that would be made to run magisk and add them to another folder in his RemixOS folder along with what would be the contents of magisk.img and had the initrd.img mount them where they would originally be. This can be done using a folder instead of an .img as youling257 is using a linux partition [ext4/f2fs] with fat/ntfs you can't do this with a folder but could with a .img
HypoTurtle said:
This can be done using a folder instead of an .img as youling257 is using a linux partition [ext4/f2fs] with fat/ntfs you can't do this with a folder but could with a .img
Click to expand...
Click to collapse
of course . ext4/f2fs , mount /mnt/$SRC/su folder on /android/su , /android/magisk link to /android/su ; ntfs/fat , mount /mnt/$SRC/su.img on /android/su , /android/magisk link to /android/su .
needn't /android/data/su.img and magisk.img .
moriel5 said:
I am sorry if this is annoying, and please don't hold any ill towards me for this, however genius in plural is genii (I had also thought that it is geniuses before I had learned this a few years ago).
Click to expand...
Click to collapse
HypoTurtle said:
In this usage it is actually geniuses, if it was the original Latin use [to refer to a genie/jinn] the plural would be genii but the meaning of intellect is old English, so the plural is geniuses...
Any way what @youling257 did was take the changed files from the ramdisk that would be made to run magisk and add them to another folder in his RemixOS folder along with what would be the contents of magisk.img and had the initrd.img mount them where they would originally be. This can be done using a folder instead of an .img as youling257 is using a linux partition [ext4/f2fs] with fat/ntfs you can't do this with a folder but could with a .img
Click to expand...
Click to collapse
First, I'm not annoyed, I was tickled.
Second you're both are wrong as I simply typo'ed "genius." When I said "less than genius" this was an adjective referring to a group of people using a noun. When applying a adjective-noun to a noun, the adjective-noun is singular.
youling257 said:
of course . ext4/f2fs , mount /mnt/$SRC/su folder on /android/su , /android/magisk link to /android/su ; ntfs/fat , mount /mnt/$SRC/su.img on /android/su , /android/magisk link to /android/su .
needn't /android/data/su.img and magisk.img .
Click to expand...
Click to collapse
I was going to do exactly that a few months ago after I got the systemless SU setup done. Does the SU toggle on/off properly for you with Magisk?
Are you running this on CM13 or N? If CM13 have you tried adding xposed to it - I haven't gotten magisk xposed working on x86_64 - I probably could just use the systemless-SU files though.
@laserspeeddemon, I know you typo'd, that's why I didn't quote your post
HypoTurtle said:
I was going to do exactly that a few months ago after I got the systemless SU setup done. Does the SU toggle on/off properly for you with Magisk?
Are you running this on CM13 or N? If CM13 have you tried adding xposed to it - I haven't gotten magisk xposed working on x86_64 - I probably could just use the systemless-SU files though.
@laserspeeddemon, I know you typo'd, that's why I didn't quote your post
Click to expand...
Click to collapse
I modified initrd.img and use su folder ,two month ago,July 22nd ;I first tried magisk link to su ,magisk v2,the first ten days of August .
these two month,I used Chainfire supersu and my system less idea on 6.0 and 7.0 ; the first ten days of August ,your idea /su/xpo,I modifed rovo89 xposed x86 v86 app_process ; the x86_64 xposed,we only has MIUI x86_64 v85 June,we still use /su/xpo . I didn't know magisk too much,I didn't try magisk in September .
about xposed system less,why we need topjohnwu magisk method ? why we use his ?
youling257 said:
I modified initrd.img and use su folder ,two month ago,July 22nd ;I first tried magisk link to su ,magisk v2,the first ten days of August .
these two month,I used Chainfire supersu and my system less idea on 6.0 and 7.0 ; the first ten days of August ,your idea /su/xpo,I modifed rovo89 xposed x86 v86 app_process ; the x86_64 xposed,we only has MIUI x86_64 v85 June,we still use /su/xpo . I didn't know magisk too much,I didn't try magisk in September .
about xposed system less,why we need topjohnwu magisk method ? why we use his ?
Click to expand...
Click to collapse
The only reason for magisk xposed here would be for PokemonGo to bypass the SafetyNet check that they added. I couldn`t get phh to work with Magisk as there is already a superuser added to Remix via Settings. Which means 86.2 is needed for suhide which is needed if using superSU.
The benefit of magisk over systemless would be probably with allowing adding files to ro system and modifying ro. entries in build.prop (although that wasn`t working on Remix last I checked).
I`ll try and get around to a simple patcher for this. Had planned on a initrd auto-patcher for sometime as well - for continued ota support.
HypoTurtle said:
The only reason for magisk xposed here would be for PokemonGo to bypass the SafetyNet check that they added. I couldn`t get phh to work with Magisk as there is already a superuser added to Remix via Settings. Which means 86.2 is needed for suhide which is needed if using superSU.
The benefit of magisk over systemless would be probably with allowing adding files to ro system and modifying ro. entries in build.prop (although that wasn`t working on Remix last I checked).
I`ll try and get around to a simple patcher for this. Had planned on a initrd auto-patcher for sometime as well - for continued ota support.
Click to expand...
Click to collapse
menuentry "6.0.1 (DEBUG mode)" {
set DIR=/6.0.1
search --set=root --file /32/kernel
linuxefi /32/kernel root=/dev/ram0 androidboot.hardware=android_x86 DIR=$DIR SRC=$DIR intel_idle.max_cstate=0 i915.enable_psr=0 DEBUG=2
initrdefi /initrd.img
}
menuentry "remixos 64" {
set DIR=/remixos
search --set=root --file /64/kernel
linuxefi /64/kernel quiet root=/dev/ram0 androidboot.hardware=remix_x86_64 DIR=$DIR SRC=$DIR intel_idle.max_cstate=0
initrdefi /initrd.img
}
menuentry "cm13 (DEBUG mode)" {
set DIR=/cm13
search --set=root --file /64/kernel
linuxefi /64/kernel root=/dev/ram0 androidboot.hardware=android_x86_64 DIR=$DIR SRC=$DIR intel_idle.max_cstate=0 DEBUG=2
initrdefi /initrd.img
}
I use the same kernel、modules、initrd.img with 6.0、cm13、remixos ; kernel 、initrd.img on fat32/esp partition .
auto mount f2fs partition on /mnt , auto mount /mnt/modules ; /mnt/6.0.1 , /mnt/cm13 , /mnt/remixos, if ota,just update /mnt/remixos files

How To Guide How To Backup Your Entire Hard Drive and Build an ISO

Hello Friends~!
I have built a new lab for us that will teach you how to use Several features of the Windows ADK to be able to backup your entire Windows system with any files, folders, apps, programs, or drivers preinstalled and saved onto an iso.
Spoiler: PRE-REQS
A USB Thumb drive is required for this method! (or any external drive or whatever workaround you have.)
Download ADK:
https://go.microsoft.com/fwlink/?linkid=2196127
Download WinPE Addon:
https://go.microsoft.com/fwlink/?linkid=2196224
Download VMWare Player:
https://customerconnect.vmware.com/en/downloads/details?downloadGroup=WKST-PLAYER-1624&productId=1039&rPId=91446
Download MODWIN:
MODWIN.EXE
drive.google.com
Spoiler: WRITTEN GUIDE
Spoiler: PREPARING THE USB
Once all the pre-reqs are installed... Copy the entire WISM Folder to your usb thumbdrive:
Code:
C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\WSIM
Go to the link above, click on DeploymentTools in the toolbar and copy WISM and paste to the thumbdrive.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then Copy your WIM File to thumbdrive.
Spoiler: WIM SOURCE
You can use MODWIN to source a WIM file from your Windows ISOs. In order to do so, run MODWIN.exe once to install MODWIN for us. Now in C:\MODWIN paste your Windows ISO contents into the ISO folder of MODWIN. Now run MODWIN.bat
Select option 2 to source WIM and option 1 for ESD.
Then you may choose whatever version of windows you want, and it will pull the wim for us.
When it is done you will have an install.wim file in sources that you can cut and paste to your USB.
Further knowledge about MODWIN can be found on it's official thread
Spoiler: VMWARE PREPARATION
We are using VMWARE because it is easier to sysprep and generalize an image in a VM as opposed to our host. You do not have to use vmware, you could use virtual box, qemu, or your host pc.
That being said, your machine needs to have it's network adapter turned off or removed entirely so it cannot connect to the internet. For good measure it is advised to build a new machine using only a Microsoft Windows 11 iso, not a Modded iso, and freshly install the image without internet so you have a clean sysprep environment.
This is how to disable internet during win 11 install using OOBE code
Spoiler: SYSPREP AND AUDIT MODE
In the VM Open:
Code:
C:\Windows\System32\Sysprep
Open Sysprep and tick the Generalize box. Leave it on reboot then select OK.
When you get to this screen press:
Ctrl + Shift + F3
This will cause the vm to reboot into audit mode.
Spoiler: BUILDING AN ANSWER FILE IN WSIM
Unplug and replug your usb thumbdrive. This will cause Vmware Player to send a popup. Select:
Connect the usb to the Virtual Machine.
To build a new Answer File:
Run Windows System Image Manager in the VM.
Select File, New Answer File, Yes.
Select your install.wim stored on the thumbdrive and Yes
Spoiler: THEN FOLLOW THESE STEPS
Then save the answer file to your thumbdrive with the name of "AnswerFile"
Spoiler: INSTALL AND SAVE SOFTWARE TO THE WIM
INSTALL ANY DRIVERS, SOFTWARE, OR FILES AND FOLDERS on the Machine
When done, In the VM Open:
Code:
C:\Windows\System32\Sysprep
To save, open command prompt by typing cmd in Sysprep's folder toolbar, then run:
Code:
sysprep.exe /generalize /oobe /shutdown /unattend:E:\AnswerFile.xml
Spoiler: BUILDING WINPE
On your host PC, Search for Deployment, run as admin and paste:
Code:
copype amd64 e:\WinPE
To make a WinPE ISO:
Code:
MakeWinPEMedia /iso E:\WinPE E:\Winpe.iso
Spoiler: RUN WINPE ON THE VM
Select the WinPE iso in vmware, run the machine, then press any button to enter the bios, and select boot from cd rom.
Spoiler: BUILD THE NEW WIM FILE
Unplug and replug your usb to re-sync to the vm
Type into command prompt:
Code:
Dism /Capture-Image /ImageFile:"E:\install.wim" /CaptureDir:C:\ /Name:install
This will create a new install.wim file for us that we can use in MODWIN to create a new iso with everything preinstalled for us!
Spoiler: BUILDING THE ISO
Copy the new WIM file and paste it back into the ISO/sources folder of MODWIN. Delete the install.esd file if it still exists.
Run the MODWIN.bat script again, and Select option 7
Run option 4 to build your new ISO it will go through the steps shown above and produce a new ISO for you in C:\MODWIN\MOD
Spoiler: REFS
A Very Special Thank you to @james28909 for suggesting finding this sort of a work-around for a problem in this reddit thread:
https://www.reddit.com/r/hacking/comments/xqv5dx
Capture and Apply Windows using a WIM file
Capture and apply Windows using a single WIM file
learn.microsoft.com
Windows System Image Manager Technical Reference
Windows System Image Manager Technical Reference
learn.microsoft.com
anyone who wants to try this, it is much easier than it looks. and once done you have your very own customized iso. you can also create the user and have everything preconfigured like dark mode or activation and more. thanks to @jenneh for the great guide!
p.s. for steam games i would suggest to backup your current games you want to a secondary drive and then restore them once you have reinstalled.
Wow! Just an amazing work!
Hi jenneh! I already commented on your other guide but I was also trying to follow this one and I ran into some problems figuring out how to follow this process:
- A multi-edition Windows 11 ISO from Microsoft does not seem to work for this process? I need to modify it with MODWINDOWZ first to have a single edition first.
- When I follow the MODWINDOWZ instructions to generate the final ISO, the install.esd or install.wim file inside the ISO can't be edited using WSIM, correct? I could only get it to work by using the mod.wim from this step
Instead of the final install.wim. Is it because of this part?
I am new to all this so I'm trying to understand everything.
@indospot Thank you for asking all this. This one may take me a day or two to give you a good answer on (Gotta finish assignment first). I wrote (or write all these silly guides) when I am brand new learning too, so I can try to remember how to do said thing. I only did this one once so I have to relearn it again and maybe it can be re-written easier and clearer haha. Bare with me Will share results when available and @ you like we did on the other thread
jenneh said:
@indospot Thank you for asking all this. This one may take me a day or two to give you a good answer on (Gotta finish assignment first). I wrote (or write all these silly guides) when I am brand new learning too, so I can try to remember how to do said thing. I only did this one once so I have to relearn it again and maybe it can be re-written easier and clearer haha. Bare with me Will share results when available and @ you like we did on the other thread
Click to expand...
Click to collapse
Haha it's the same thing here! We are trying to adapt this into an official tutorial on XDA and so I am trying to learn all the details so the instructions are as clear as possible. When it's published, I hope you can look at it and see if any changes are needed
@indospot okay now that I understand what's being asked
"- A multi-edition Windows 11 ISO from Microsoft does not seem to work for this process? I need to modify it with MODWINDOWZ first to have a single edition first."
Correct, if your windows iso comes with an install.esd file in it's Sources directory, then we need to source a WIM from it of our choosing. I updated the OP to show how to do this with modwin instead of the "classic" tool as you coined it before. You can use option number 2 in modwin to do this a lot easier.
"- When I follow the MODWINDOWZ instructions to generate the final ISO, the install.esd or install.wim file inside the ISO can't be edited using WSIM, correct? I could only get it to work by using the mod.wim from this step"
I also updated this step in the OP to use Modwin now. If you select option 7, then 4 it will be able to build the iso for us once the wim is replaced in the ISO directory, and the original install.esd deleted if it isn't already.
If there's anything else I can help with please let me know! Thank you for your time in testing these things and looking forward to reading anything you put out there!
jenneh said:
Hello Friends~!
I have built a new lab for us that will teach you how to use Several features of the Windows ADK to be able to backup your entire Windows system with any files, folders, apps, programs, or drivers preinstalled and saved onto an iso.
Spoiler: PRE-REQS
A USB Thumb drive is required for this method! (or any external drive or whatever workaround you have.)
Download ADK:
https://go.microsoft.com/fwlink/?linkid=2196127
Download WinPE Addon:
https://go.microsoft.com/fwlink/?linkid=2196224
Download VMWare Player:
https://customerconnect.vmware.com/en/downloads/details?downloadGroup=WKST-PLAYER-1624&productId=1039&rPId=91446
Download MODWIN:
MODWIN.EXE
drive.google.com
Spoiler: WRITTEN GUIDE
Spoiler: PREPARING THE USB
Once all the pre-reqs are installed... Copy the entire WISM Folder to your usb thumbdrive:
Code:
C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\WSIM
Go to the link above, click on DeploymentTools in the toolbar and copy WISM and paste to the thumbdrive.
View attachment 5733349View attachment 5733347
Then Copy your WIM File to thumbdrive.
Spoiler: WIM SOURCE
You can use MODWIN to source a WIM file from your Windows ISOs. In order to do so, run MODWIN.exe once to install MODWIN for us. Now in C:\MODWIN paste your Windows ISO contents into the ISO folder of MODWIN. Now run MODWIN.bat
View attachment 5870271Select option 2 to source WIM and option 1 for ESD.
View attachment 5870273
Then you may choose whatever version of windows you want, and it will pull the wim for us.
When it is done you will have an install.wim file in sources that you can cut and paste to your USB.
View attachment 5870275
Further knowledge about MODWIN can be found on it's official thread
Spoiler: VMWARE PREPARATION
Run your Windows iso in vmware and fully install it. Make sure to install VMWARE TOOLS as well to make things easier.
To install VMWARE TOOLS click on PLAYER>MANAGE>then install vmware tools
We are using VMWARE because it is easier to sysprep and generalize an image in a VM as opposed to our host. You do not have to use vmware, you could use virtual box, qemu, or your host pc. I simply prefer VMWARE due to it's rubust features, like once you have installed the VMWARE tools you are able to drag and drop files to the VM, as well as copy and paste to and from the machine.
Spoiler: SYSPREP AND AUDIT MODE
In the VM Open:
Code:
C:\Windows\System32\Sysprep
View attachment 5728361
Open Sysprep and tick the Generalize box. Leave it on reboot then select OK.
When you get to this screen press:
Ctrl + Shift + F3
View attachment 5728363
This will cause the vm to reboot into audit mode.
Spoiler: BUILDING AN ANSWER FILE IN WSIM
Unplug and replug your usb thumbdrive. This will cause Vmware Player to send a popup. Select:
Connect the usb to the Virtual Machine.
To build a new Answer File:
Run Windows System Image Manager in the VM.
Select File, New Answer File, Yes.
Select your install.wim stored on the thumbdrive and Yes
Spoiler: THEN FOLLOW THESE STEPS
View attachment 5728365View attachment 5728367View attachment 5728395
Then save the answer file to your thumbdrive with the name of "AnswerFile"
Spoiler: INSTALL AND SAVE SOFTWARE TO THE WIM
INSTALL ANY DRIVERS, SOFTWARE, OR FILES AND FOLDERS on the Machine
When done, In the VM Open:
Code:
C:\Windows\System32\Sysprep
To save, open command prompt by typing cmd in Sysprep's folder toolbar, then run:
Code:
sysprep.exe /generalize /oobe /shutdown /unattend:E:\AnswerFile.xml
Spoiler: BUILDING WINPE
On your host PC, Search for Deployment, run as admin and paste:
Code:
copype amd64 e:\WinPE
View attachment 5728381
To make a WinPE ISO:
Code:
MakeWinPEMedia /iso E:\WinPE E:\Winpe.iso
Spoiler: RUN WINPE ON THE VM
Select the WinPE iso in vmware, run the machine, then press any button to enter the bios, and select boot from cd rom.
View attachment 5728383
View attachment 5728387
Spoiler: BUILD THE NEW WIM FILE
Unplug and replug your usb to re-sync to the vm
Type into command prompt:
Code:
Dism /Capture-Image /ImageFile:"E:\install.wim" /CaptureDir:C:\ /Name:install
This will create a new install.wim file for us that we can use in MODWIN to create a new iso with everything preinstalled for us!
Spoiler: BUILDING THE ISO
Copy the new WIM file and paste it back into the ISO/sources folder of MODWIN. Delete the install.esd file if it still exists.
View attachment 5870327
Run the MODWIN.bat script again, and Select option 7
View attachment 5870333
Run option 4 to build your new ISO it will go through the steps shown above and produce a new ISO for you in C:\MODWIN\MOD
Spoiler: REFS
A Very Special Thank you to @james28909 for suggesting finding this sort of a work-around for a problem in this reddit thread:
https://www.reddit.com/r/hacking/comments/xqv5dx
Capture and Apply Windows using a WIM file
Capture and apply Windows using a single WIM file
learn.microsoft.com
Windows System Image Manager Technical Reference
Windows System Image Manager Technical Reference
learn.microsoft.com
Click to expand...
Click to collapse
Great job! Thank you!
jenneh said:
@indospot okay now that I understand what's being asked
"- A multi-edition Windows 11 ISO from Microsoft does not seem to work for this process? I need to modify it with MODWINDOWZ first to have a single edition first."
Correct, if your windows iso comes with an install.esd file in it's Sources directory, then we need to source a WIM from it of our choosing. I updated the OP to show how to do this with modwin instead of the "classic" tool as you coined it before. You can use option number 2 in modwin to do this a lot easier.
"- When I follow the MODWINDOWZ instructions to generate the final ISO, the install.esd or install.wim file inside the ISO can't be edited using WSIM, correct? I could only get it to work by using the mod.wim from this step"
I also updated this step in the OP to use Modwin now. If you select option 7, then 4 it will be able to build the iso for us once the wim is replaced in the ISO directory, and the original install.esd deleted if it isn't already.
If there's anything else I can help with please let me know! Thank you for your time in testing these things and looking forward to reading anything you put out there!
Click to expand...
Click to collapse
Hi jenneh!
So after some further testing, I have discovered another issue, though I am not sure what causes this one. When I use modwin to extract a WIM file, I eventually run into a problem at the end. If I use the WIM file generated by MODWIN, the install.wim file that's created at the end using WinPE is much larger, around 12GB with only one program installed. When I build an ISO with it, Windows fails to install. It fails after I choose a partition to install to.
indospot said:
Hi jenneh!
So after some further testing, I have discovered another issue, though I am not sure what causes this one. When I use modwin to extract a WIM file, I eventually run into a problem at the end. If I use the WIM file generated by MODWIN, the install.wim file that's created at the end using WinPE is much larger, around 12GB with only one program installed. When I build an ISO with it, Windows fails to install. It fails after I choose a partition to install to.
Click to expand...
Click to collapse
This method will definitely create a huge wim file, which is the sacrifice of having your applications or whatever it is you were trying to have preinstalled first. Why it is not installing after completion is a whole other question that I am afraid I don't know the answer to. For me mine installed but that was with 1 program added to the iso. Trouble is I still don't quite understand the basics of what we even did in it unfortunately, like the purpose of answer pages and whatnot. So I kinda am at a loss to answer these, sorry.
jenneh said:
This method will definitely create a huge wim file, which is the sacrifice of having your applications or whatever it is you were trying to have preinstalled first. Why it is not installing after completion is a whole other question that I am afraid I don't know the answer to. For me mine installed but that was with 1 program added to the iso. Trouble is I still don't quite understand the basics of what we even did in it unfortunately, like the purpose of answer pages and whatnot. So I kinda am at a loss to answer these, sorry.
Click to expand...
Click to collapse
I did some further testing using MODWINDOWZ, and it turns out MODWIN wasn't the problem, but I don't know what it is. There was one time I got it to work, but I don't know what I did differently to make it work. When it worked, though, it was a smaller install.wim file at the end. This is the error I get:
I don't know what settings I may need to change. I'm just following the steps, yet I can't get it to work again. I did it once and I can't repeat it.
@indospot I was able to do all the steps just now and created a small wim in file size, the only thing I did differently than what was in the guide was I built the VM with No Network Driver so it couldn't connect to the internet. Maybe you can try this and see if it reduces the size? I will add that to the guide just incase

Categories

Resources