have anyone successfully installed drivers and ran Viper4android on HTC One A9 on Nougat 7.0?
please let me know..
Im on European Nougat 7.0, S-OFF, TWPR Installed, Rooted, Busybox installed, SElinux Permissive..
after i installed V4A (flashed zip via TWRP), driver installed but it repeatedly asks to install driver on every reboot..
i also tried moving v4a into system but still problem persist.
V4A not working , any fix for this?
Fixed..
Viper4Arise working like charm
scroll down, find reply by Fudgehog, click mediafire link, download zip.. thanks @Fudgehog
enter recovery TWRP 3.0.3-8, enter in Terminal, setenforce 0, flash the downloaded zip, reboot..
done, enjoy :highfive:
I had played around with this myself.
Try booting to TWRP, on the cleanest rom you can, terminal emulate setenforce 0, then flash this zip. Let me know if it works. Works on my stock rooted A9 developer, WNC's Rom.
Also on a friends M9 his phone did the same as mine where it would show numbers in TWRP then reboot instantly. I injected the apk and lib folder into system app on his phone, didn't work but then with permissive in TWRP, Flashing the numbers zip worked. Make sure you have Captains latest TWRP.
You can also try using Kernel Adiutor to set SELinux to permissive on boot. Make a file in system/etc/init.d called "setperm08", and edit it as a text file and put in #!/system/sh
setenforce 0
http://www.mediafire.com/file/suwzbl0l78guuwz/ARISE+Sound+Systems+Numbers+3.5.zip
Fudgehog said:
Try booting to TWRP, on the cleanest rom you can, terminal emulate setenforce 0, then flash this zip. Let me know if it works. Works on my stock rooted A9 developer, WNC's Rom.
Also on a friends M9 his phone did the same as mine where it would show numbers in TWRP then reboot instantly. I injected the apk and lib folder into system app on his phone, didn't work but then with permissive in TWRP, Flashing the numbers zip worked. Make sure you have Captains latest TWRP.
You can also try using Kernel Adiutor to set SELinux to permissive on boot. Make a file in system/etc/init.d called "setperm08", and edit it as a text file and put in #!/system/sh
setenforce 0
http://www.mediafire.com/file/suwzbl0l78guuwz/ARISE+Sound+Systems+Numbers+3.5.zip
Click to expand...
Click to collapse
superb.. thanx man.. :laugh:
it worked like charm :highfive:
You already know bud!
You're welcome, glad I could help! I hope more people find this thread and use my information, I tried to give you every possible solution I could.
{
"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"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for K6 power. It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port, once they are ported to our device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs, daily prebuilt image files to install Ubuntu Touch and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting, once they are ported to the Moto X Play
* Boot from USB drive attached via OTG cable
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is messing with boot sector and data partition. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
1. Via MultiROM Manager app (We do not have Official Support, so this is not an option for us yet)
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel (If you want to use Kexec) - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
2. Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 3 parts you need to install:
Modified recovery (TWRP.img) - download the IMG file from second post and use fastboot, TWRP or Flashify app to flash it.
MultiROM (multirom.zip) - download the ZIP file from second post and flash it in recovery.
You current rom will not be erased by the installation.
Adding Roms
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using USB drive (not tested yet)
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
In some cases, you might need to flash patched kernel - get coresponding patched kernel version from second post and flash it to the secondary ROM sama way you flashed ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - well, settings.
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
- Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.
Source code:
Device tree-https://github.com/karthick111/twrp/tree/karate
MultiROM - https://github.com/multirom-dev
Downloads
Karate: https://www.androidfilehost.com/?w=files&flid=230440
Karatep: https://www.androidfilehost.com/?w=files&flid=230445
FAQ and other notes
Device encryption:
Encryption isn't supported right now. So decrypt your device before using this.
About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.
Can I flash secondary roms on Micro SD?
Yes but it's is very slow, internal storage is much better to flash secondary roms.
How do I flash Gapps in Secondary ROMs?
After AddRom and is done, go back and Click on the installed Secondary ROM, you will see one of the option to 'Flash Zip', click and install Gapps. Then you can reboot into secondary ROMs, do gapps installation before rebooting otherwise as usual need to deal with SetupWizard FC, at least thats what I observe in my device.
The thug arrived...
I installed secondary ROM to microSD card but when I boot, it only shows in internal section internal ROM and external section is always refreshing. In MultiROM recovery it says I have secondary ROM installed to microSD card. But how can I boot it if it is not shown?
Thomas_xxxxx said:
I installed secondary ROM to microSD card but when I boot, it only shows in internal section internal ROM and external section is always refreshing. In MultiROM recovery it says I have secondary ROM installed to microSD card. But how can I boot it if it is not shown?
Click to expand...
Click to collapse
It won't work in external sd card. That external spot is for USB & it'll be slow. Better use only internal slot.
dr.bathman said:
It won't work in external sd card. That external spot is for USB & it'll be slow. Better use only internal slot.
Click to expand...
Click to collapse
From FAQ: Can I flash secondary roms on Micro SD?
Yes but it's is very slow, internal storage is much better to flash secondary roms.
So it should work from external SD card.
Thomas_xxxxx said:
From FAQ: Can I flash secondary roms on Micro SD?
Yes but it's is very slow, internal storage is much better to flash secondary roms.
So it should work from external SD card.
Click to expand...
Click to collapse
But sadly not working.
dr.bathman said:
But sadly not working.
Click to expand...
Click to collapse
Hope some update will fix it.
after installing zip mobile goes to download mode so i restore stock boot.img after that mobile boot up bt multi rom not working.any idea ?
raj2k8 said:
after installing zip mobile goes to download mode so i restore stock boot.img after that mobile boot up bt multi rom not working.any idea ?
Click to expand...
Click to collapse
Flash the two files the multirom.zip then the modified twrp edition. Make sure you flash the right file name to your device
firemax13 said:
Flash the two files the multirom.zip then the modified twrp edition. Make sure you flash the right file name to your device
Click to expand...
Click to collapse
i flashed both zip n img but its not working even i tried both karate n karatep bt same problem.
I have LineageOS 15.0 installed as primary ROM. Then in recovery I added OmniROM as secondary, I tried to boot it via multirom boot menu but then screen went black, LED diode was turned on even disconnecting mobile from PC and it keeped connecting/disconnecting to PC around. I cannot even see MultiROM boot menu and I was only able to boot to recovery and reflash LOS 15.0 to have my mobile working. Could it be caused by selecting OmniROM as secondary ROM? In past I tried Paranoid android and it worked without any problem. I thought my phone was bricked but fortunately I managed to fix that.
Has anybody experienced problem with Xposed framework on secondary ROM? (7.1.2). It flashed xposed in recovery successfully but after opening Xposed installer, it crashed and display started to blick. Only hard restart helped.
Thomas_xxxxx said:
Has anybody experienced problem with Xposed framework on secondary ROM? (7.1.2). It flashed xposed in recovery successfully but after opening Xposed installer, it crashed and display started to blick. Only hard restart helped.
Click to expand...
Click to collapse
Even the magisk wont work on secondary. So please use only SU.
firemax13 said:
Even the magisk wont work on secondary. So please use only SU.
Click to expand...
Click to collapse
Why magisk and xposed dont work on secondary?
MultiROM does not work with LineageOS 15.1. Is it going to be updated?
How to uninstall multirom? @karthick mostwanted bro please also provide the uninstaller zip.
nitesh9 said:
How to uninstall multirom? @karthick mostwanted bro please also provide the uninstaller zip.
Click to expand...
Click to collapse
Then search it on google how to. Bro you can search but please search on google please.
firemax13 said:
Then search it on google how to. Bro you can search but please search on google please.
Click to expand...
Click to collapse
I am not a total noob (I know how to google). I searched on google and didn't found any relevant result.
Then I studied the the multirom uninstaller provided by devs of other devices and figured it out myself how to remove and restore the modified files manually.
However, it would have been easier if karthick had provided the uninstaller zip like other devs. (Would have been much helpful for newbies/noobs).
Warning:This is an experimental find and i am not held liable if you brick your device (go into twrp and start over)
Installing Magisk in a Dual Boot Environment:
Things you need
(i advise to save all to your external card if you have one so it wont be erased):
Need to Create:
primary rom
secondary rom
gapps (unless you prefer one in link)
gapps in secondary (dual)
included in following link:http://www.mediafire.com/folder/95yswgomsz3d3/Magiskdualboot
gapps aroma(both normal and dual)
no verity zip(both normal and dual)
su remove(both normal and dual)
magisk 14.3 dualboot
dualbootutilities(just in case something goes wrong)
Dual boot patcher app
Step One:
Assuming your on the latest twrp for this rom (check official twrp app)
you will want to go to wipe in twrp and wipe data,
reboot to recovery,wipe advanced options and wipe everything except internal storaage and external storage then reboot into recovery again
Step 2:install primary rom,no verity,gapps,remove su addon,and magisk 14.3 dualboot zip.
(when everything loads set it up as you would normally making sure everythings up to date from play store,magisk manager update,etc
Step 3:install every magisk module you wish to have and reboot (once rebooted go into modules and unclick everything and reboot)
Step 4:get a root file manager and go into /data/adb in the root folder (make a copy of magisk.img and put on your sdcard)
step 5:install dual boot patcher app,run it,grant permission and when it asks to set kernal do so (everytime you change a rom it may ask you to set kernal)
step 6:use the patch zip file to patch your primary rom as an upgrade,then flash the patched primary rom then reboot to system (this allows nonconflict with other roms to avoid error and enables app sharing on the app)
step 7:assuming you downloaded the secondary rom,go to patch zip file section in the patcher app and add flash file and select your second rom zip and put it under secondary slot
step 8: patch as well in secondary:no verity zip,su remove zip and gapps.install the patched dual rom and files in twrp then reboot to system (it should start setting up your second rom)
step 9:update everything in second rom from play store plus do the setup
step 10:reboot back into recovery and install the dualboot magisk 14.3 zip again.reboot system and update that magisk manager and zip
step 11:install dual boot patcher app on the second rom now and itll ask you to set second kernal when you go to roms,do so
step 12:reboot back to recovery and then go advanced>file manager and then go /data/adb and select magisk.img copy file to data/multiboot/dual/data/adb/ then reboot to system.
step 13:now when you reboot into second rom you will notice in modules in magisk manager all the modules you had in primary are there
(be careful when enabling some as some will not work but its a small list)
(Warning:if theres any updates to any app you need to follow steps 12 and 13.
installing modules directly from the manager in second rom can cause bricks or crashes)
Step 14:have Fun
Tested Modules that work:
android mic fix,app systemizer,audio modification library,boot animation replacer,detach(doesnt really hide market links nomore but doesnt crash),google camera patch,google framework,init.d linker,iybp,mm recovery,max resolution for youtube,priviledged api booter,ram management by crok,secure if,single user mod,splatoon 2 font,sysconfig patcher,terminal app systemizer,terminal app debloater,teethering enabler,ts-bindsunified hosts adblock,universal dee buffer remover,busybox, universal safetynet fix beta v 5,volume steps increase,wifi bonding and xmlpak
Will give it a shot when I get the chance
could someone help me just install magisk with the either the stock rom, or even any of the custom ones?
Im unable to find a step by step guide similiar to this one, for installing magisk on lg k550 (without the dual boot option, as im a newbie and prefer not to add any extra possible complications )
takethe5th said:
could someone help me just install magisk with the either the stock rom, or even any of the custom ones?
Im unable to find a step by step guide similiar to this one, for installing magisk on lg k550 (without the dual boot option, as im a newbie and prefer not to add any extra possible complications )
Click to expand...
Click to collapse
All the ROMs on the 2 plus work for both models. Also do you have telegram. We are all there to give advice. I'm more the magisk expert though you can shoot a line thru there or follow guides we have posted. We welcome all new members
t.me/lgstylo2plus
Frosthaxx said:
All the ROMs on the 2 plus work for both models. Also do you have telegram. We are all there to give advice. I'm more the magisk expert though you can shoot a line thru there or follow guides we have posted. We welcome all new members
t.me/lgstylo2plus
Click to expand...
Click to collapse
I am looking for something similar but for LG Stylo 3 Plus.
Sent from my LGMS428 using XDA Labs
*Viper4android Pie* Magisk Module
Requirements -
1.Custom Rom (Tested on AEX custom rom for Realme X)
Not tested on rooted colorOS6, most probably it won't work because On Color OS, Magisk is working in Core Only Mode so no module works.
2.Root with Magisk v19.4 or v20
3.SELinux Permissive (most custom ROMs are already in Permissive mode)
4.Busybox
5. Magisk module download from here
https://drive.google.com/file/d/1qSOGFD-X3ULoYiAWZTk-3XZknA8KqDBq/view?usp=drivesdk
Procedure
1. So you are on Custom Rom with TWRP
2. Root with magisk v19.4 or v20.
3. Download Busybox from playstore and install
4. Check SELinux , if its enforcing then set it to permissive using Terminal in TWRP..
Command to set SELinux to permissive => setenforce 0
5. Open Magisk, go to 'Modules' option and add new module by clicking on + icon.. Navigate to your downloaded v4a module, select and install.. (keep your Internet ON during this step).. then Reboot.
6. Enter in V4A, it will ask to install/update driver, install it.. reboot.
7. your viper is ready to bite your ears..
What about Android 10 ROMs