Viper4Android Fix for Lollipop - Galaxy Tab 4 Q&A, Help & Troubleshooting

Most Samsung users reported that V4A is not working after upgrading to lollipop cause of the unswitchable SELinux, switching SELinux mode compromises the security of the device, so here is the solution without flashing custom kernel:
Note:
*This method should be used with Systemless SU(not magisk) installed*
Con's:
Not working with some music apps with built in equalizers
Steps:
1. Assuming that you have installed systemless root, but still check if /su/bin/supolicy exists...* WORKING IS NOT GUARANTEED ON OTHER SYSTEMLESS METHODS eg. Magisk*
2. Download the latest build of V4A in this thread: https://www.google.com.ph/url?sa=t&...uRG6XJ1DsKgOZngeg&sig2=O8sZ4LawAMMb_9I4inOJ-Q
3. Install the apk as a system app and reboot, after open Root Explorer and create su.d folder in /system partition , set permissions rwxr-xr-x
4. Create 50viper.sh inside the folder and edit and paste:
#! /system/bin/sh
/su/bin/supolicy --live "allow mediaserver mediaserver_tmpfs:file { read write execute };"
5. Save and set permissions rwxr-xr-x
6. Now launch V4A and grant permissions and install drivers.
7. After finished installing of drivers, reboot
8. Disable and clear data of SoundAlive in settings and reboot
Tested with my device: SM - T235(Galaxy Tab 4 7.0 LTE)

http://forum.xda-developers.com/showpost.php?p=65106000

Related

[Z3 All variant][Locked Bootloader][Noob Friendly] How to root

MOD EDIT @gregbradley
Also, users should be aware that Kingo root sends your IMEI to an unknown IP address in china during the root process, you have been warned. For more information read the whole OP here
XPERIA ANDROID 5 LOLLIPOP EASY ROOT :​
ALL LOCKED&UNLOCKED BOOTLOADERS.
1-) Copy ALP folder in phone memory.
2-) Settings >Security > Unknown sources make it open. And Settings > Developer Options > USB debugging make it on. (If developer options exist go Settings > About phone and click Build number (7 times))
3-) Install Root.apk Allow all messages.
4-) Install Recovery.apk
5-) Install Busybox.apk
6-) Open KingRoot and click Root button.
MOD EDIT @gregbradley
Also, users should be aware that Kingo root sends your IMEI to an unknown IP address in china during the root process, you have been warned. For more information read the whole OP here
6-) Wait to complete. İf you see a chinese blue button click it. All of messages you will allow.
7-) When you see blue tick symbol or %100 its ok.
Look to the menu KingUser its in here ok. No problem don't open it.
9-) Open busybox and install it. When you see It looks like busybox installed succesfully congratulations message its ok.
10-) Open XZRecovery and click Install Recovery .
11-) Phone will be reboot and recovery will open.
12-) Install > find ALP folder and select SuperSU.zip then swipe and install it.
13-) Complete the install Wipe Cache/Dalvik and reboot the phone.
14-) You can see SuperSU in menu and check with rootchecker your root access.
15-) Everything OK. You can enjoy with your rooted Android 5 lollipop device.
16-) You can uninstall KingRoot, busybox, Xzrecovery app. (won't delete supersu or ndrutils)
PREPARED BY ALPEREN ÇUBUK.
DOWNLOAD LİNK : https://yadi.sk/d/qMsejobDgedBw
MIRROR :
https://app.box.com/s/86e7vlwfmu5z62lo95vu2kfej38uj01q
NOTE: Extract downloaded zip and copy ALP folder your phone memory.
Thanks for the comprehensive guide. For some reason step 11) Getting my D6653 into recovery is not working (Also tried ADB reboot recovery)
Any ideas?
EDIT: After updating BusyBox, and then re-installing the Recovery, it re-started and is now stuck in a bootloop..
EDIT2: The bootloop is very likely related to this (from this post: http://forum.xda-developers.com/showthread.php?t=2261606):
"@vaisakh7 found a busybox updater which seems to be compatible with XZDualRecovery: Busybox On Rails, which installs a version of busybox created by stericson, which leads me to believe his Busybox installer should also install a version which works together with XZDualRecovery.
Either case, be careful with updating busybox as there still is a possibility it will break your ability to enter recovery or even break full root, which means you might not be able to recover from the broken situation. Your best bet is the installer version, using that to break the lock on the system partition and reinstall the correct busybox."
Recommended to NOT update BusyBox
Busybox can never be installed through this process always failed and there is no other option left once busybox installation failed except to reinstall the whole firmware please add the steps to guide for busybox installation too
Does this method null the waranty?
Sent from my Xperia Z3

[GUIDE] How to get Viper4Android working

Got V4A fully working (Spotify, Google play music etc.)
I've tried the same steps mentioned in the s6 edge forum HERE
Do a full backup first!
These steps worked for me:
(Of course you need root on your device)
1. Install Busybox.
2. Install Viper4Android 2.4.0.1
3. Grant Viper4Android permissions to write (Settings ->Applications -> Applicationmanager -> V4A -> Permissions -> Enabled)
4. Delete SoundAlive with RootExplorer (or disable/freeze it with Titanium Backup)
5. Go to /system/etc/ and rename audio_effect.conf to audio_effect.conf.bak
6. Download the modified audio_effect.conf HERE and copy it to /system/etc/ and /vendor/etc/
7. Set permissions of the new config file to rw-r-r (0644) (important! Otherwise --> Bootloop)
8. Reboot
9. Start V4A and install the drivers
10. Reboot
DONE
{
"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"
}
You might want to add that you need "root" access first.
nappent said:
You might want to add that you need "root" access first.
Click to expand...
Click to collapse
I thought it is too obvious.
But Ive added it
@NQNH,
Hey buddy, Been struggling with this for days, My V4A app keeps on asking to install drivers every-time I open the app no matter how I install it. Could you clarify the following -
* Where did you install Busybox to ? (System/xbin or Su/xbin)
* Have you rooted with Cf-Root or TWRP + Systemless SU?
Thanks a ton in advance!
JazonX said:
@NQNH,
Hey buddy, Been struggling with this for days, My V4A app keeps on asking to install drivers every-time I open the app no matter how I install it. Could you clarify the following -
* Where did you install Busybox to ? (System/xbin or Su/xbin)
* Have you rooted with Cf-Root or TWRP + Systemless SU?
Thanks a ton in advance!
Click to expand...
Click to collapse
Hi, good day,
I downloaded busybox from the playstore and installed it with standardsettings (/su/xbin)
Ive rooted it with cf-root
Did you grant permission to v4a to write data?
You can try to move the v4a folder from /data/app/ to /system/priv-app/
which v4a version are you using? I've used the 2.4.0.1 material one
NQNH said:
Got V4A fully working (Spotify, Google play music etc.)
I've tried the same steps mentioned in the s6 edge forum HERE
Do a full backup first!
These steps worked for me:
(Of course you need root on your device)
1. Install Busybox.
2. Install Viper4Android 2.4.0.1
3. Grant Viper4Android permissions to write (Settings ->Applications -> Applicationmanager -> V4A -> Permissions -> Enabled)
4. Delete SoundAlive with RootExplorer (or disable/freeze it with Titanium Backup)
5. Go to /system/etc/ and rename audio_effect.conf to audio_effect.conf.bak
6. Download the modified audio_effect.conf HERE and copy it to /system/etc/ and /vendor/etc/
7. Set permissions of the new config file to rw-r-r (0644) (important! Otherwise --> Bootloop)
8. Reboot
9. Start V4A and install the drivers
10. Reboot
DONE
Click to expand...
Click to collapse
I have done all the steps mentioned above. The driver is installed but not working. The only thing I couldn't - although I'm not sure that this is the problem - is to set selinux enforcing. I couldn't find any method to enforce without disabling the internal encryption
rzvny said:
I have done all the steps mentioned above. The driver is installed but not working. The only thing I couldn't - although I'm not sure that this is the problem - is to set selinux enforcing. I couldn't find any method to enforce without disabling the internal encryption
Click to expand...
Click to collapse
I told you man, flash that file I posted, it does all that stuff and fixed everything.
Please help me, I’ve been going nuts trying to get this to work…
Performed a full clean system install twice now…
Followed your steps 101% the only things that you didn’t include was the following:
1) Busy box to install? By Steriscon?
2) While moving the files and changing permission set to RW and then back to RO?
3) There is no other files in vendor/etc – that dir is empty by default?
Here is my Status:
Driver Version: 2.4.0.1
NEON Enabled: NO (in the past during the install I had the option to choose but not anymore???)
Enabled: NO
Status: Abnormal
Audio Format: Unsupported
Processing: NO
Sampling Rate: 0
PLEASE HELP 
My device is Galaxy S7 Edge SM-G935F
GODSPD said:
Please help me, I’ve been going nuts trying to get this to work…
Performed a full clean system install twice now…
Followed your steps 101% the only things that you didn’t include was the following:
1)Busy box to install? By Steriscon?
2)While moving the files and changing permission set to RW and then back to RO?
3)There is no other files in vendor/etc – that dir is empty by default?
Here is my Status:
Driver Version: 2.4.0.1
NEON Enabled: NO (in the past during the install I had the option to choose but not anymore???)
Enabled: NO
Status: Abnormal
Audio Format: Unsupported
Processing: NO
Sampling Rate: 0
PLEASE HELP 
My device is Galaxy S7 Edge SM-G935F
Click to expand...
Click to collapse
Flash this https://drive.google.com/file/d/0B4PtT1mslzvtRWxtcnJTMUFYams/view?usp=docslist_api
Brava27 said:
Flash this https://drive.google.com/file/d/0B4PtT1mslzvtRWxtcnJTMUFYams/view?usp=docslist_api
Click to expand...
Click to collapse
Thanks, I also found this that worked for me - could be the same file HERE
why wasn't this included in the initial instructions and how did others get it working without that file?
I also looked into other fixes - removing KNOX and installing setlinux mode changer... but couldnt find a way to remove knox yet and selinux apparently wont run with knox installed...
The link in the op doesn't work for me. It opens in a new tab(something with tapatalk in the URL)and then goes back to the app. Oh and btw is this for s7 only?
Sent from my XT1092 using XDA-Developers mobile app
Brava27 said:
Flash this https://drive.google.com/file/d/0B4PtT1mslzvtRWxtcnJTMUFYams/view?usp=docslist_api
Click to expand...
Click to collapse
will flashing this do or is this in addition to the steps in the first post?
EDIT................................................
NQNH said:
Got V4A fully working (Spotify, Google play music etc.)
I've tried the same steps mentioned in the s6 edge forum HERE
Do a full backup first!
These steps worked for me:
(Of course you need root on your device)
1. Install Busybox.
2. Install Viper4Android 2.4.0.1
3. Grant Viper4Android permissions to write (Settings ->Applications -> Applicationmanager -> V4A -> Permissions -> Enabled)
4. Delete SoundAlive with RootExplorer (or disable/freeze it with Titanium Backup)
5. Go to /system/etc/ and rename audio_effect.conf to audio_effect.conf.bak
6. Download the modified audio_effect.conf HERE and copy it to /system/etc/ and /vendor/etc/
7. Set permissions of the new config file to rw-r-r (0644) (important! Otherwise --> Bootloop)
8. Reboot
9. Start V4A and install the drivers
10. Reboot
DONE
Click to expand...
Click to collapse
In driver status , processing status is no, what to do
Sent from my Moto G 2014 using XDA-Developers mobile app
is this a big improvement? S7 Audio quality on headphones aren't really great and was hoping this could improve the quality, if not I might resort on switching to HTC 10...
Thanks!
Many Thanks for the guide
NQNH said:
Got V4A fully working (Spotify, Google play music etc.)
I've tried the same steps mentioned in the s6 edge forum HERE
Do a full backup first!
These steps worked for me:
(Of course you need root on your device)
1. Install Busybox.
2. Install Viper4Android 2.4.0.1
3. Grant Viper4Android permissions to write (Settings ->Applications -> Applicationmanager -> V4A -> Permissions -> Enabled)
4. Delete SoundAlive with RootExplorer (or disable/freeze it with Titanium Backup)
5. Go to /system/etc/ and rename audio_effect.conf to audio_effect.conf.bak
6. Download the modified audio_effect.conf HERE and copy it to /system/etc/ and /vendor/etc/
7. Set permissions of the new config file to rw-r-r (0644) (important! Otherwise --> Bootloop)
8. Reboot
9. Start V4A and install the drivers
10. Reboot
DONE
Click to expand...
Click to collapse
Followed the guide word for word and it worked like a charm on my Verizon gs7e running play store rom. Downloaded the latest V4A from the main thread. Thanks man!
omg what the hell am i waiting for in order to root this dang phone...,cant make a decision between Samsung Pay and Viper...seems like an easy one
GODSPD said:
Thanks, I also found this that worked for me - could be the same file HERE
why wasn't this included in the initial instructions and how did others get it working without that file?
I also looked into other fixes - removing KNOX and installing setlinux mode changer... but couldnt find a way to remove knox yet and selinux apparently wont run with knox installed...
Click to expand...
Click to collapse
I used the smaller file you linked and that worked! I was going nuts trying to figure it out and agree, this should have been included in the original setup.
Tried the guide and it works on Note 5 6.0.1. I used Viper 2.4.0.1. A little issue though: the super audio quality, balanced and power saving menu that normally pops out did not appear.

V4A on AEX Nougat (tutorial)

I had a rough time with this so I thought I'd share my fix. This may work on other Nougat ROMs as well. If your ROM uses Chainfire SuperSU you can skip all of the Magisk stuff and go straight to step 4.
1: Clean install AEX + gapps
2: Boot system and update Magisk(via settings/Magisk Manager) and BusyBox(via play store app) and reboot
3: Flash Magisk SELinux Permissive Script
https://forum.xda-developers.com/apps/magisk/module-magisk-selinux-permissive-script-t3577549
4: Use Root Explorer to copy ViPER4Android_FX_v2505_A7.x_Nougat_IO_test_fix.apk to System/Privapp and set permissions rw-r--r--
https://forum.xda-developers.com/showthread.php?t=2191223
5: Reboot, launch V4A app, grant Root, install driver, reboot
Bonus: AdAway works if copied to Privapp with correct permissions rw-r--r--, reboot and launch
aaron.a said:
I had a rough time with this so I thought I'd share my fix. This may work on other Nougat ROMs as well. If your ROM uses Chainfire SuperSU you can skip all of the Magisk stuff and go straight to step 4.
1: Clean install AEX + gapps
2: Boot system and update Magisk(via settings/Magisk Manager) and BusyBox(via play store app) and reboot
3: Flash Magisk SELinux Permissive Script
https://forum.xda-developers.com/apps/magisk/module-magisk-selinux-permissive-script-t3577549
4: Use Root Explorer to copy ViPER4Android_FX_v2505_A7.x_Nougat_IO_test_fix.apk to System/Privapp and set permissions rw-r--r--
https://forum.xda-developers.com/showthread.php?t=2191223
5: Reboot, launch V4A app, grant Root, install driver, reboot
Bonus: AdAway works if copied to Privapp with correct permissions rw-r--r--, reboot and launch
Click to expand...
Click to collapse
If you do so, I think you lost all benefit of systemless system, as you are touching directly to the system.
casual_kikoo said:
If you do so, I think you lost all benefit of systemless system, as you are touching directly to the system.
Click to expand...
Click to collapse
Good call. Not a problem for me. I think dudes selinux script enables permissive system wide which may also turn people off. But my app selection is minimal and I use my phone more like a media tool than anything else.
You don't need to change to Permissive at all. Just install V4A latest apk and flash the driver with Magisk. Works with Enforcing fine.

unlimited hotspot for nougat [ROOT]

PLEASE NOTE:This is NOT a guide to root your phone but i did provide the links to the tools to do so for most Samsung's for help with root check your own phone model forum's section.
WARMING; Rooting a device may void the warranty on the device. It may also make the device unstable or if not done properly, may completely brick the device. Some methods may install additional apps/software on your device. XDA-Developers or the author does not take any responsibility for your device. Root at your own risk and only if you understand what you are doing! Additionally this may go against your service contract which I'm not responsible for as well.
Worked for my j700p running 7.1.1 stock rooted with TWRP/SUPERSU latest. If works for you leave a thank you and confirm device.
What you need to do to get tethering on Nougat is root the device (temporarily at least), enable tethering and then (if you want) unroot it so that everything is back to normal and you can take OTA updates and use Android Pay without any issues.
All you’ll need to enable tethering on Android nougat is TWRP recovery installed on your device and the latest systemless SuperSU zip (should work with magisk as well, if someone could confirm that'd be nice) to root the device. (Always remember to backup your system just in case)
How to Enable Tethering on Android Nougat
Root your android running nougat
Edit build.prop file: Add the
net.tethering.noprovisioning
line to the bottom of build.prop file on your Android device. (Download Build.Prop Editor from the play store if you don't know how to get to this, I suggest Rom toolbox as it has build.prop included as well as terminal emulator which you will need for the next step. LINKS BELOW)
Reboot device after saving changes to build.prop file.
Download/install a Terminal emulator app from Play Store (I used the terminal emulator included in ROM toolbox but you can choose whichever you'd like.) You also WILL need busy box installed as well to be able to execute this line. (will be prompted to install upon rom toolbox install with a link)
Open Terminal emulator on your device and issue the following commands one-by-one:
su
settings put global tether_dun_required 0
exit
└ Grant root access to the 3 apps when asked.
Reboot device
DONE!
If you wish to unroot now you can. I have not tested this so can't confirm if works after unroot but just go to SuperSu settings full unroot. Restart and you should be good. This should renable android pay.
CREDIT goes to Shivam Malani, Thank You!
Links;
Odin (for my sm-j700p I used latest everything)
https://samsungodin.com/download/
SUPERSU
http://www.supersu.com/download
TWRP
https://twrp.me
Rom toolbox lite (for build.prop editor and terminal emulator)
https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox
Busybox https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer

[2020]Replace KingRoot v5.x or Kingo ROOT with SuperSU

This is for those who are unable to uninstall Newer KingRoot using old Methods like SuperSUMe Free and old terminal emulator method by Mr.W0lf and waiting to uninstall Newer Kingroot versions.... or want to remove Kingo ROOT in a simple way.
Features:-
-Removes Kingroot v5.x (tested on latest v5.3.7-197), Kingo ROOT
-Removes all files of King(o)root in whole device
-Installs SuperSU-v2.82-SR5 to /system without custom-recovery and force system even on 6.0+
-No need of manual updating of su binary
-Installs latest Busybox to /system/xbin
Requirements:-
==> Terminal Emulator
==> Below attached ZIP
Procedure:-
To uninstall completely the script deletes files multiple times.
Optionally Untick KingRoot in Settings App->Security->Device administrators->KingRoot
Method 1:-
1.Make a folder with name mrw in internal storage
Extract this zip in that mrw folder
2.Download Terminal Emulator and run following commands
Bash:
su
sh /sdcard/mrw/root.sh
3.After succeeded with Green text type following
Bash:
sh /sdcard/mrw/root.sh
After this, your device will reboot by installing SuperSU
If your device not rebooted, then try executing root.sh for 5 times...
If still not rebooted then try other method
4.After booted open Terminal Emulator app and type following
Bash:
su
sh /sdcard/mrw/root.sh
Method 2 :- by uninstalling KingRoot manually
Root again with KingRoot
and follow below procedure
1.Type
Bash:
su
in Terminal Emulator and go to KingRoot app
Tap on 3 dot and
choose settings and
choose remove root, untick keep backup option and unroot
Note:- If your device rebooted at time of unrooting, this method will not work
2.Go to Terminal Emulator and type following
Bash:
sh /sdcard/mrw/root.sh
Your device will reboot after that and rooted with SuperSU
Method 3 :- by using older version of KingRoot
Requires :- Android Version less than 5.0
1.Unintall Kingroot by going to KingRoot app
Tap on 3 dot and
choose settings and
choose remove root, tick keep backup option and unroot
2.Install older version of KingRoot eg v4.5.0 from apkmirror
and root with it
3.Follow Method 1
Method 4 :- by using Kingo ROOT instead of KingRoot
1. Probably your device will lose root of KingRoot after following above methods, so root your device with Kingo ROOT.
2.Follow Method 1
Method 5 :- by using Magisk Manager
Requires :- 1)Android Version greter than or equal to 5.0
2)Unlocked bootloader (else your device will soft brick)
1.Reroot with KingRoot
2.Install Magisk Manager
install Magisk by connecting to internet
and tap on install option
and choose Direct Install(Recommended)
3.Go to Terminal Emulator and type following
Bash:
su
and go to Kingroot app
4.Uninstall Kingroot as said in Method 2
5.Go to Terminal Emulator and type following
Bash:
sh /sdcard/mrw/root.sh
reboot your mobile, after reboot
Bash:
su
sh /sdcard/mrw/root.sh
Method 6 :- by using SuperSU Me pro
If replacing Kingroot with SuperSU method from above doesn't work for you
You can try SuperSU Me by @gatesjunior
Which will remove all Kingroot apps installed in your device
Download and install Super-Sume Pro apps
Forum link: http://forum.xda-developers.com/general/paid-software/supersu-please-t3110954
Thats it...!
Thanks to @Mr.W0lf for this
If you want to create issue or suggest file edit through pull requests
Source:- https://github.com/HemanthJabalpuri/Replace_KingRoot_with_SuperSU
SHA1 of v5.zip:- 5cb2508180a4edc12316acfd4cb0fb59ad4dd402
Donate:- https://www.paypal.me/hemanthjabalpuri
Enjoy !
Test zip for testers:-https://github.com/HemanthJabalpuri/Replace_KingRoot_with_SuperSU/archive/master.zip
Testers:-
People who has custom recovery and know some basic things about restoring nandroid backup and get out of soft brick can test by following procedure....
-Root with SuperSU by flashing super.zip in recovery....
-Go to settings of SuperSU and choose switch super user and reboot...
-Install latest Kingroot.apk from apkmirror....
-Install and select fix now below Root Auth Error
It will root with Kingroot...
Test the zip by following procedure in first post....
Send the root.log in /sdcard/mrw folder... by making a post in this thread
Developers:-
For app devlopers who want to make this as an app can see some source examples from
==> https://github.com/inX95/RmKingroot
==> https://github.com/EliteTutorials/Open-King-Remover
Kingroot FAQ:-
https://forum.xda-developers.com/an...ot-tool-android-2-x-5-0-t3107461/post60829420
All questions about SuperSU:-
https://forum.xda-developers.com/an...ot-tool-android-2-x-5-0-t3107461/post61857510
What are another easy ways to replace?
Note:- Need unlocked bootloader
-Search Custom Recovery(TWRP, CWM, PhilZ , etc) for your particular mobile
-Flash that recovery.img with app like Flashify, Rashr, Kernel Adiutor, ROM Installer, Root Essentials etc
-Boot into custom recovery and Flash SuperSU.zip or Magisk.zip
-Reboot and Enjoy.....
All about ROOTING
How to Root Any Device
How to Root Your Android
Best One Click Root Methods
Best Root Apps for Android
Best Apps for Rooted Android Devices
How to do Everything on Your Phone
XDA’s Top Picks for Everything
Older Versions:-
v4:- Changelog, Source ZIP
v3:-Changelog, Source ZIP
v2:- Changelog, Source ZIP
v1:- Initial, Source ZIP
Who use Kingoroot or superSU in 2019 just use magisk more simple and more efficiency...
Envoyé de mon ONEPLUS A6003 en utilisant Tapatalk
black_file said:
Who use Kingoroot or superSU in 2019 just use magisk more simple and more efficiency...
Envoyé de mon ONEPLUS A6003 en utilisant Tapatalk
Click to expand...
Click to collapse
Yes, but many old devices does not have custom recoveries and also many people who use those devices does not have a PC to flash patched boot.img... and also some devices does not have firmware available too....
Many device's bootloader also locked...
If we install magisk then it will definitely soft brick..
since on a bootloader locked mobile tweaking recovery or boot partition will get result like brick
Thats why some people stick with King(o) root.....
Terminal Emulator app is another app or its BusyBox?
AndroPhobia said:
Terminal Emulator app is another app or its BusyBox?
Click to expand...
Click to collapse
Another app
Should i install busy box in xbin or bin?
AndroPhobia said:
Should i install busy box in xbin or bin?
Click to expand...
Click to collapse
Both of them will work
Done Twice and worked in a M4 SS4452 Android 5.1.1
Thanks
AndroPhobia said:
Done Twice and worked in a M4 SS4452 Android 5.1.1
Thanks
Click to expand...
Click to collapse
Hey thanks
I made a test branch in github for advanced users which contain 4 methods of replacing root and also contain Magisk flashing...
https://github.com/HemanthJabalpuri/Replace_KingRoot_with_SuperSU/archive/v3-Magisk.zip
at https://github.com/HemanthJabalpuri/Replace_KingRoot_with_SuperSU/tree/test
Older Versions:-
are available in 4th post
Updated to v4
Changes:-
-Replaced with Stericson 1.30.1 Busybox
-Fixed Arch Detection
-Try to fix force closes of KingRoot when removing by installing older version of KingRoot(v4.5.0)
-Fixed 64bit devices not rebooting after replace
-Removes debuggerd too
-More logging info
Full Changelog here
This update is NOT tested...
If you are tester not having KingRoot installed then see 2nd post for info..
Update v5-test:-
This update does not have any zip.
All the files are embedded in script file.
Just place root.sh somewhere and execute.
Those files are extracted at the time of usage in execution.
If you want to extract only files to see what are they, then execute
Code:
root.sh -x all
will extract files in working directory.
https://www.mediafire.com/file/9ir3fzipfsouimm/root.sh
If you are a tester and want to test this, then see 2nd post for details.
Anyone tried any of this on OnePlus 6T (A6013)?
I'd like to say thank you it works on my BOOX Max Carta, Android 4.4.4
fishman8 said:
I'd like to say thank you it works on my BOOX Max Carta, Android 4.4.4
Click to expand...
Click to collapse
Can you please telegram me at
https://t.me/HemanthJabalpuri
Thanks
Thanks worked for my Z1 Compact at Android 5.1.1.
it is not working well as I found

Categories

Resources