Maybe most people know about do this, but I wanna share for some people how don't know to do this.
1. Your phone must have unlocked bootloader and have twrp so you can root your phone and also install busybox. (Many tutorial in xda, just follow that. If u still can't, you can ask in comment)
2.
*If you root with superuser phh's, so go to twrp recovery mode and flash ViPER4Android_2.5.0.5_guitardedhero.zip (you can searching with Google and download)
*If you root with magisk, so you can go to magisk manager, choice menu-download- find ViPER4Android_FX_Legacy-v4.3 module and install.
Reboot your phone and you have Viper4Android v2.5.0.5 in your device. Open Viper4Android app, grant
superuser permission, and now there should has driver installed.
3. Open root explorer or other app like that go to dev/system/priv-app/ViPER4AndroidFX, find ViPER4AndroidFX.apk, delete it and paste ViPER4AndroidFX v2.7.1.0.apk here. ( You can searching with Google and download the ViPER4AndroidFX v2.7.1.0.apk file)
4. Reboot your phone and enjoy Viper4Android v2.7.1.0 in your phone.
Just install Viper4Android v2.5.0.5 for first. You can't just install Viper4Android v2.7.1.0 directly. If you use magisk, don't install Viper4Android v2.7.1.0 module and of course don't delete your Viper4Android v2.5.0.5 module. Viper4Android v2.7.1.0 is using driver v2.5.0.5. I think is more about interface update. Maybe...:laugh:
Sorry I don't know how to attach file here, but I'm sure is not difficult to find the file you needed.
Do with you own risk!
If you not clear please ask first!
Understanding all procedure before you do it.
I think if you phone is Moto E4 Plus Mediatek Variants, that's should be work.
Don't forget to backup before do this.!
Related
This tutorial will teach you how to root, install a custom recovery and deodex the ROM on your Mediatek processor smartphone. You can use this tutorial for other Android devices too, Lenovo or not.
I myself own a Lenovo A390 and I have rooted, installed recovery and deodexed using these software tools, without any pain. And I assure you, it will be extremely rare that anything can go wrong. And you don't need a computer to root or install recovery-yes, you can do it on your phone itself.
But let's get some things straight:
1. Rooting/installing recovery voids your warranty.
2. If you're not using a Lenovo device or a device that runs on a MediaTek processor, I recommend that you search for a version of recovery appropriate for your processor.
3. The chances of damaging your phone using these tools is extremely rare, trust me, but in case anything goes wrong, I, OR THE DEVELOPERS OF THESE TOOLS, OR XDA-DEVELOPERS WILL NOT BE RESPONSIBLE FOR ANY INTERNAL/EXTERNAL DAMAGE TO YOUR PHONE.
How to root your Lenovo a390:
1. Download Framaroot: http://forum.xda-developers.com/showthread.php?t=2130276 Note: Framaroot may not work on all Android devices. Please see compatibility list in the link.
Framaroot is an Android app created by XDA user alephzain. It allows you to root your device directly from your Android device-please click on link above to view full compatibility list. Download and Install this app. If it says "Installation blocked", go to your phone's Settings>Security and tick the "Unknown Sources" box. (Believe me, there are n00bs )
2. Open Framaroot. For the a390, there is only one exploit-Boromir, since it's a Mediatek powered device. Select Boromir.
3. Now you see two buttons: Install Superuser and Install SuperSU. You need to select only one of them. Framaroot will then root your device and install Superuser/SuperSU. (Superuser/SuperSU are apps which control root operations on your device ie. ensure no app uses root features without your permission-it is a MUST.)
The choice is up to you, but I'd recommend Superuser since it's like the Industry standard of rooted Android phones.
4. Reboot your phone. You'll find Superuser installed. Open it, swipe from left to right to access Superuser settings. The su binary is outdated and it'll appear in a red font. Tap it to update su binary.
This is proof enough that your phone is rooted, but if you really need to see, here's one more step.
5. Install Root checker from Google Play Store: https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck
Run this app, and if your phone is rooted, Superuser will come up automatically asking you whether Root Checker should be granted permission- press Yes and root Checker will deliver the result.
That's it-congratulations, you've rooted your a390 without any pain. Now you can flash a recovery, install Busybox, overclock your phone, get rid of the dumb apps Lenovo has included with the a390.... Enjoy! :laugh:
How to install a recovery
Now, there are two recoveries that rule the Android universe: ClockworkMod Recovery (CWM), and TeamWin Recovery Project (TWRP). The bad news is, neither is officially available for the Lenovo A390 or most of MediaTek devices. But where there's a will, there's a way- and some anonymous Android developer has created TWRP recoveries for the entire Lenovo smartphone series. <salute to the unsung hero> I used one specially customised for the A390, and it works fabulously.
First of all, ensure that your phone is rooted. If not, read the tutorial above.
1. Download this recovery.img file from this Google Drive: https://drive.google.com/file/d/11-...c9b-MfFTWpi9D_vBI0oVISPgRVcB/edit?usp=sharing
2. Install Recovery Tools-Flasher from the Google Play Store: https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
3. Now press "Flash Recovery" button, it will open a file browser. Select the recovery.img file you downloaded from the file browser.
4. It should show a dialog box that says Flashing done. Press OK to boot into recovery. Press OK, and you'll see the TeamWin IdeaPhone load screen-and boot into TWRP.
Congrats, you've installed the recovery. Now you can install custom ROMs on your phone and backup your phone's kernels as protection against troubles. Enjoy! :highfive:
How to deodex your phone's ROM
Sadly, you cannot do this using your phone. You'll need a Windows PC for this process, a good Internet connection as you'll have to download large files for this process, and plenty of time.
Here's a good XDA Developers Tutorial on how to deodex your rom, complete with step-by-step explanation and screenshots: http://forum.xda-developers.com/showthread.php?t=2374008
There you go. If you followed my tutorial completely, you are now a proud owner of a rooted, recovery-flashed, deodexed MediaTek device/Lenovo A390.
Enjoy!
Please hit Thanks button if my post helped you.
I'm not a dev so i cannot help you with bugs etc... I will not take any creds regard this program only wanted to share what i know and as always i'm not responsible for anything that happens to your devices..
Sorry for my bad English..
I've found a working method for V4A to work on Nexus 5X, and i know there are many threads about this...
I was looking around and found some solutions, but it seemed like there was not a specific thread about installing or was actually working.
It does not seem like you need permissive kernel for this to work (I've tried both Permissive and Enforcing, and both work).
Nexus 6's V4A have worked, but it it's missing audio focus sometimes. I've not got any FC. Dolby and Dolby Plus works too
I'm running:
ROM: ResurrectionRemix MM v5.6.4
Kernel: Jolla Kernel v6.0-Beta
Recovery: TWRP v3.0.0-0
What you will need:
-Nexus 5x (obviously)
Busybox (Recomended): meefik (Free)
Busybox: Stephen (Stericson) (Free)
Viper4Android (Recomended, but Doby is not included): Nexus 5 V4A
Viper4Android: Nexus 6 V4A
Install Method
1. First download Es File Explorer (or any other file explorer with root/system access).
2. Open File explorer and grant read write permission (in es file explorer you must go to left side panel and grant root access and then click on the text and choose "Mount R/W"). Then give "/", "/system" and "/vendor" r/w permission.
3. Afterwards you go to "/system/vendor/etc/" rename "audio_effects.conf" to "audio_effects.conf.bak" (in case something goes wrong or if you want to go back later. This is because V4A makes its own version of "audio_effects.conf". You will have to do it because in MM and V4A does not r/w for some reason.. It will then make its own file and it will work. If you want to go back to normal, just delete the "audio_effects.conf" V4A made and delete the ".bak" at the end of the original file. Also uninstall the driver from V4A, then use a system app remover to delete V4A. Then reboot).
4. Install the Busybox Version you prefer from Google Play Store. I'm currently running Busybox v1.24.1 (installed to "/system/xbin")
5. Go into recovery and take a backup (just to be on the safe side) before you flash the V4A of you liking, but I would suggest LolliViper (I will only link to the website not the file itself).
Then your done, if you have any questions or need help I can try my best. i cannot promise i can help tho..
I'm struggling with installing Viper4Android on my device.
I tried installing using either the apk from the original thread (http://forum.xda-developers.com/showthread.php?t=2191223). It install successfully but I keep getting a driver install prompt, after installing the driver and rebooting.
Things I already tried without success:
- Installed BusyBox with BusyBox app (https://play.google.com/store/apps/details?id=ru.meefik.busybox)
- Setting the SELinux mode to permissive using SELinuxModeChanger app (http://forum.xda-developers.com/showthread.php?t=2524485)
- Setting the SELinux mode to permissive using flashable permissive.zip
- Installing the apk from the Material design Viper4Android thread (http://forum.xda-developers.com/android/software/app-material-viper4android-2-3-4-0u-t3190352)
- Flashing the .zip from the same thread.
I'm currently running Android 6.0 GPE, flashable version (http://forum.xda-developers.com/showthread.php?t=2708589)
Root access is granted through SuperSU, so no problem on that matter I suppose.
2. With a File Manager(Solid Explorer Recommended) locate " /system/etc/htc_audio_effects.conf" and rename "htc_audio_effects.conf" to "htc_audio_effects.bak" (Renaming this file will make it inactive but while keeping it backed up just in case this doesn't work for you, however it appears this file is not needed as no negative effects occur, and this should fix V4A.)
3. Reboot Device.
And if this doesn't work I thin you should grant storage permission for V4A under settings. I hope I can help you!
Duccibreeezy said:
2. With a File Manager(Solid Explorer Recommended) locate " /system/etc/htc_audio_effects.conf" and rename "htc_audio_effects.conf" to "htc_audio_effects.bak" (Renaming this file will make it inactive but while keeping it backed up just in case this doesn't work for you, however it appears this file is not needed as no negative effects occur, and this should fix V4A.)
3. Reboot Device.
And if this doesn't work I thin you should grant storage permission for V4A under settings. I hope I can help you!
Click to expand...
Click to collapse
Thanks mate!! This worked for me.
Thanks for ur help
Enforcing is set by default on CM 13 so I tried to find some fixes trying to make it work then I got lucky.
If you want the new version of ViPER4Android you can download it here.
Firstly I advice you to install ViPER first (Do not open it yet) then go to Developer Options and disable the root access after that you can reboot to recovery and flash this and here is the link where the flashable zip came from.
Screenshot Here
You can enable the root access after boot and install the audio drivers. If you want to place ViPER4Android on the system you can use Lucky Patcher. (Trust me it helps)
Thanks to zhuhang for the app and AntonPanos for the flashable zip and lastly mobiusm.
Oreo Root For The S7/S7E (Will work on Rev4-Rev10/A Bootloader) Adb Install
A big thanks goes out to @klabit87 he is 99 percent the reason we have root! Also @stang5litre and stang5litre test group.Prefered Root Method Oreo Only Using Odin Only For Rev-4 Too Rev10/A
Odin Install Root Method For S7 Flat Can Be Found Here
Odin Install Root Method For S7 Edge Can Be Found Here
Root Method Using Odin Only For Rev-11/B -- Please Read Limitations On The Thread
Rev11/B Root Method For S7 Flat Can Be Found Here
Rev11/B Root Method For S7 Edge Can Be Found Here
ADB Method Oreo Or Nougat For Rev-4 Too Rev10/A -- Must Use Adb Method For Nougat Root
2023_S7_Flat_Edge _ADB_Root_Plus_Safestrap_V1.7z
Directions:
This works for Oreo Rev4-Rev10/A Bootloader Roms or Nougat Rev4
As always there is a chance of bricking your phone
1. Download and extract 2022_S7_Edge_ADB_Root_Plus_Safestrap.7z
2. Reboot your phone to download mode
3. Inside the 2022_S7_Edge_ADB_Root_Plus_Safestrap.7z folder you will find an Odin_Firmware folder. Use Odin and flash the Eng Boot Image for your phone
4. Once phone is rebooted and connected to computer click on the cmd-here.exe and type Install_One_Click.cmd in the command window and hit enter
5. Once root is done and root bat closes your phone will reboot too stock recovery where you must wipe data
6. Once booted click on SuperSu app and update su binary if app ask then reboot
7. Don't flash any superuser zips in recovery that are not made by me or use any other SuperSu apk
Rebooting Too Safestrap Recovery
1. Reboot phone as you would too boot stock recovery Pwr + VolUp + Home. It takes up too 40 seconds too boot recovery. Ignore the mount system errors on info screen
2. Enter recovery.
3. Too leave just reboot system ignore no system installed message if you get it
4. There is screen lag issues on scrolling in recovery. There is aroma file manager that takes care of this issue while in recovery but selecting zips too install may present a problem for this you can use the kernel manager recovery flash option while phone is booted too system. Simply select zip too flash and phone will reboot too recovery and flash it and reboot back too system. Most other function in recovery should work the issue is just scrolling too select files.
5. Flashfire is installed as an alternative as well
Features:
1. SuperSu Root- Do not use any other SuperSu app. Its ok to update su binary if app ask.
2. Safetrap recovery-Still working out scrolling issue
3. Flashfire
4. Kernel tweaks CPU governor set too Conservative
5. Entropy/Swapiness set to High
6. Build Prop tweaks to combat lag
7. Bloat removed from rom
8. Knox removed from rom
Bugs:
Eng Boot Image causes lag
Safestrap Recovery has scrolling issues
Random Reboots will most likely happen
Safetynet will not pass
Battery life may not be optimal
SuperSu cannot be updated
Flashfire may need date changed too 2016 to function if it just keeps closing on you
Volte And Hotspot Fix
View attachment 4555265
Old Downloads
S7_Oreo_Nougat_Adb_Advanced_Root_V12.zip Recommended Root Zip
This zip gives you the option to install some cpu tweaks and will also. Install the entropy tweak that the SEFix app does. The tweak sets entropy to high by default I also include the SEFix app if you want to change the settings. I also set the swappiness settings to very high. If you want to change these settings you can download the speedup swap app from playstore. The above zip also removes knox and changes the fstab.qcom file to disable dm-verity on system files and remove all file encryption which makes it seem to work better and make it compatible with my no root roms that has to have this done to allow safestrap to work. Installing the above zip requires a data wipe unless you have already installed it or you are coming from my non rooted roms
S7_Oreo_Su_Binary_Only_ADB_Root.zip Alternative Root Zip
This root zip is only for oreo an only installs the su binary to the system/xbin folder giving you root privelages it has no tweaks and does not change the fstab.qcomn file to remove dm-verity and system file encryption. There is no SuperSU app installed either but you will have root privelages.
Credits:
- @Raymonf for modified odin
- @afaneh92 for safestrap
- @me2151 for help and finding alternative flash methods
- @tytydraco for some instructions
- @mweinbach for some instructions
- @Craz Basics for help
- @partcyborg for help and guides other devices root methods
- @elliwigy for being great help when I need it
- @stang5litre
- @jds3118
- @Krog18
If I missed you please pm me
Donations
If you would like to donate please send all donations to @klabit87 PayPal Link Here and give a thanks!
Main Root thread with all discussion is found here
[2022 Root For S7/S7Edge Oreo Rev4_To_Rev10/A_Odin Flashable Or ADB Method] Plus [Limited Root Method Rev11/B _Using Combo_Firmware]
Oreo Root For The S7/S7E (Will work on Rev4-Rev10/A Bootloader) Adb Install A big thanks goes out to @klabit87 he is 99 percent the reason we have root! Also @stang5litre and stang5litre test group. Prefered Root Method Oreo Only Using Odin...
forum.xda-developers.com