Related
hey guys i have one problem with supersu.
i installed clean master and do cleaning **** and startup cleaning things and after reboot all apps that have granted root permission( foldermount, gmd gestures, lightflow, etc), these apps shows no toast popup after boot and to make them grant permissions i have to open them. Same thing when i installed boot manager and did not do anything but boot and again no supersu toast popups about root permissions after boot.
is there a way to keep the root grants after the boot? ( i have checked default acces to grant in supersu app)
I'm having problems with clean master working with SuperSu too.
clean master is so powerfull that disables supersu permissions.
They probably change some file permissions that SuperSU frowns at.
Chainfire said:
They probably change some file permissions that SuperSU frowns at.
Click to expand...
Click to collapse
i want to maintain supersu permissions after every boot no matter what. is there some option in supersu to be activated for that?
i'm on note 3 rooted with stock tw.
''enable supersu during boot''
please explain to me for what is this option
thx :good:
bump
dancapitan said:
''enable supersu during boot''
please explain to me for what is this option
thx :good:
Click to expand...
Click to collapse
This option has a summary that's pretty unclear. I've emailed the dev, hope to receive an answer soon. Fact is apps running during the boot_completed seem to get root randomly if this option is not enabled! Let me insist on the random fact, as my apps get root on boot frequently but not all the time. Other users have reported the same random behavior. Once the option is enabled everything works as expected!
However the option seem to imply that any root request on boot will be granted!? Regardless of user choice????
To make it short, check the option "enable supersu during boot" and root apps will receive root on boot as they used to!
3c said:
This option has a summary that's pretty unclear. I've emailed the dev, hope to receive an answer soon. Fact is apps running during the boot_completed seem to get root randomly if this option is not enabled! Let me insist on the random fact, as my apps get root on boot frequently but not all the time. Other users have reported the same random behavior. Once the option is enabled everything works as expected!
However the option seem to imply that any root request on boot will be granted!? Regardless of user choice????
To make it short, check the option "enable supersu during boot" and root apps will receive root on boot as they used to!
Click to expand...
Click to collapse
You should turn this into a proper bug report in the proper thead (either the beta or its own new thread) with all the useful information you think may be relevant. There is no email support, all support is here.
The option itself is for apps that run before Android is fully up and running, or su from adb shell during a bootloop, etc. I thould not influence apps running su from bootcomplete receivers, and if it does, then that needs to be investigated.
Is there currently any way to enable this feature via ADB on a boot looped phone? I really wish I would have known about this! I wouldn't be stuck where I'm at if I had only checked this option. Device is stuck at LG logo, no download or recovery, but has access to ADB. SU was installed, but I don't have root via ADB since the phone isn't finished booting...thus I'm not able to copy over the proper system.img or change the recovery/laf. Dang!
I have the problem too, when I install Fake Wifi, the automatic SuperSU granted is not working. Please help some advance. Thank's.
Hey guys why root required apps request for root access after installing super su
I have the same problem, have to add a task in tasker, auto open supersu and root granted apps once after boot,
Root SM-T707A on Lollipop with SuperSu - Xposed & Debloated - Part II
Where are we right now?
* Part I: Flash Stock Lollipop 5.0.2.
* Part II: Gain Root access for Lollipop with SuperSU. <---- YOU ARE HERE!
* Part III: Flash Xposed Framework thru Flashfire.
* Part IV: Debloat the tablet from both AT&T and most of Samsung stuff.
* Part V: Improve usability and aspect with Xposed Modules.
Once again, some words of our sponsors: NO, I'm NOT resposible for any consequence originated from the use of this guide, being that the death of your tablet, or your smart tv, the Panama Papers or Luis Suarez just playing rough with Filipe Luiz's foot. Whatever happens to your tablet, it's ON YOU.
Introduction (PLEASE READ!):
This guide works as a continuation of Part I, so we assume you flashed KitKat and applied Lollipop updates as described.
If you are already on Lollipop and have several weeks using it, of course you can try this guide, but I STRONGLY SUGGEST to start from zero, backup your files and use the guidelines on Part I of this guide.
Part II: Gain Root access for Lollipop with SuperSU
IMPORTANT - During the first boot on our brand new lollipop, don't try to connect to your WiFi and remove your SimCard if availble before even selecting any option. We don't want any internet at this time.
Our first move in Lollipop is to Reject all the AT&T offers..
Then accept terms of Samsung EULA (and hit No Thanks below)...unless you want to share information with Sammy.
Then you can put your name (I didn't), it' s up to you.
Disable the 3 checkboxes for location services (you can enable this later).
Then skip the Samsung Account creation and hit also Next on my "Find my mobile" screen without doing nothing.
Finally, you'll reach the Android Desktop.
Setting the stage for rooting with KingRoot
Still avoiding any conection to the internet, go to your apps and tap Settings.
Before doing nothin, I strongly suggest you change your language to english in case you use another.
If your first language is English, you're good.
If it's not, you can change it on General TAB, then "Language and Input".
After this, tap the Device tab, choosing then Display option on the left.
Choose Screen timeout and select 10 minutes.
Now select Lock screen on your left and Screen lock on your right. Tap "None".
Now go to "General" tab and tap "Security".
Enable the Unknown sources checkbox and press OK on the popup.
Press home button. Now you can connect to your Wifi.
The moment you got Internet, Samsung will start forcing some updates on your tablet.
At the same time, several Google popups will ask you to "regularly check device for security".
Decline them all the time!
There is a "Games" app that loves to open itself without asking
When that happens, it will introduce you to an agreement that you will REJECT.
If it doesn't show, better. But it will eventually.
Now enter the Play Store and Log in with your credentials.
Accept the playstore conditions when prompted. If you are kicked out of the app just enter again.
Still inside Playstore, now swipe from your left side border to gain access to the menu.
Tap "My Apps" and use the "Update All" button on the right.
Accept all APP Permisions (seven times in my case).
The update process will start. This will take some time so BE PATIENT and do nothing else.
When everything is updated, you'll notice some warning on your status bar.
Swipe down your status bar. It will ask several times to Update Google Play Services.
Tap any of update offers for Play Services. Playstore will open again offering the update.
Hit Update and Accept. When the update of Google Play Services is finished, hit the Open button.
You gain access to Google Settings. Tap Security.
Disable "Remote locate this device" - "Allow remote lock and erase".
Disable also "Scan device for security threats" and "Improve harmfull app detection" (unless is greyed out).
Hit the home button and go back to desktop.
Installing KingRoot
For the next step, you need to download these files on your PC:
* Kingroot V4.90
* RemoveKing
Copy them on your tablet's internal memory. Specifically on the root of your internal memory. If you copy them inside a folder, later commands will fail.
Back to your tablet's desktop, look for the folder icon on the bottom left corner. This will open the Samsung File Manager. Look for "Device Storage" on the left column. If you copied the files correctly, you'll find both on the right pane of the display. Extract the RemoveKing.zip file by tapping it and clicking "OK". A RemoveKing folder will appear on the root of your filesystem.
Now open the Kingroot V4.90 file. Hit Next and then Install.
If a google warning appears citing - "Installation blocked". Hit "Install anyway" (unsafe).
If it doesnt, just hit Open. A blue screen shows up with the legend "ROOT auth".
Swipe upwards twice (assuming you're holding your tablet in portrait).
Now hit the "Try it" button. The app will verify root status in a matter of seconds.
Now tap the "TRY THE ROOT" button at the bottom.
When the root is sucessful, you'll be asked to "Forbid Knox".
Tap Cancel and press the home button. Now you are rooted with Kingroot.
Installing and preparing Terminal Emulator
Now that we are rooted, enter the playstore and install the app "Terminal Emulator for Android". Open it. You'll notice some small font selected so, hit the 3 dots on the right upper corner and go to preferences. On Font Size choose 24 pt. Hit the back physical button of the tablet. Now the "white letters" become readable. And it shows something like:
Code:
klimtlteatt:/ $
Next type the following and hit enter:
Code:
su
A Kingroot popup will ask for root permission. Tap "Allow".
Now the $ symbol will change for #.
Next you hit the HOME button to exit the app briefly (don't close the app in any other way, just hit the HOME button).
Uninstalling KingRoot
After that, go to your apps and enter the KingRoot app.
Now tap the 3 dots on the upper right corner and select "General Setting". Disable "Smart Authorization", then disable "Enable Root Authorization". Finally choose below "Uninstall KingRoot". Hit Continue. Uncheck "Backup Root" when prompted and hit OK. When all is over, you're back to the desktop. Go back again to your apps and uninstall Purify.
Applying the Scripts
Open again Terminal Emulator app (thru the app Icon) . Now we need to hit a couple of scripts by moving first to our extracted folder by entering the following command on the terminal (plus enter):
Code:
cd /sdcard/RemoveKing/
To run the first script type (then press enter):
Code:
./step0.sh
It just takes 3 seconds, then type the following and press enter:
Code:
./step1.sh
This last script will ask for a confirmation during its process.
Type just an "y" and hit enter: (WARNING, the Y won't appear on your display after typing it)
Code:
y
You'll notice a bunch of errors, don't mind them.
Installing SuperSU
Now hit the home button and go to the play store.
Search and Install SuperSU (free version). Open it. Choose Expert.
The app will ask "The SU binary needs to be updated, continue?".
Hit Continue and then choose "Normal" when asked on the next popup.
You'll receive an "Installation Sucess!". Tap the Reboot option.
Congratulations! You are now rooted with SuperSU.
After rebooting, enter the Terminal app once more, and tap the X on the right upper corner and hit OK.
That will finish the current terminal session.
If you're interested in getting Xposed Framework, go to part 3 of this guide.
If you're just interested in debloating the SM-T707A and improve its performance, go to part 4 (Soon).
Part 5 is where I discuss the modules I'm using on Xposed and also some Playstore apps to improve functionality, and remove as much Touchwiz as possible, while also working on better battery life (Soon too).
Final Considerations (suggested reading - not mandatory)
While this guide may seem easy to carryout, it took me almost a month to get SuperSu to work on Lollipop.
I'm no coder (a soon to be Certified Public Accountant), and the real magic to pull this off was to try many combinations of different app versions, different situations with google services and several strategies with the script and superSU. In fact, most of KingRoot versions don't work on this tablet to get root, also tried SuperSume app from the playstore. The same could be said for KingoRoot (don't confuse it with KingRoot), it worked but I couldn't remove it without losing root.
Why I'm telling you this? Because using KingRoot and similar apps to root this tablet, your mileage may vary while doing it. In fact, even while applying my first two guides there's a respectable chance of KingRoot tool failing to root your tablet. If you followed this couple of guides to the last comma, your chances of success are very close to 100%. But I have noticed in similar Galaxy Tab S threads, that the use of KingRoot and KingoRoot to achieve root is just a matter of using the root tool many times until it works, and I wanted to avoid you guys going thru that. To take sucess rate as close as it gets to 100%, we took all of this steps. They were included to avoid many failures. I believe they're are 99% flawless to achieve root on Lollipop with SuperSU.
Also, the second script won't remove many KingRoot files, because it was thought for KingoRoot on KitKat.
I have to give myself more time to develop something that could really clean up the last traces of KingRoot.
Special Thanks
* @chixvicious - For showing how to achieve the same over KitKat and KingoRoot instead.
* @bakageta - For creating these scripts for the Alcatel smartphone over KingoRoot.
* @Kingxteam - For developing KingRoot to allow us to root our device.
Oh wow, I had forgotten all about those scripts. Glad to see someone getting some use out of them.
bakageta said:
Oh wow, I had forgotten all about those scripts. Glad to see someone getting some use out of them.
Click to expand...
Click to collapse
They were life-savers, thanks a lot for them!!
Broken links?
First and foremost, thank you for the thorough walkthrough.
I've come across an issue with the provided links to KingRoot and RemoveKing. When I click on either, I receive the following message:
"Invalid Attachment specified. This can happen for a variety of reasons-- most likely because the thread or post you are trying to view has been moved or deleted. Please return to the forum home and browse for another similiar post."
Do you have any alternate links available?
EDIT: I did find an alternate method that worked for proper replacement of KingRoot with SuperSU. All good, and glad for the compatible xposed framework.
zopert said:
First and foremost, thank you for the thorough walkthrough.
I've come across an issue with the provided links to KingRoot and RemoveKing. When I click on either, I receive the following message:
"Invalid Attachment specified. This can happen for a variety of reasons-- most likely because the thread or post you are trying to view has been moved or deleted. Please return to the forum home and browse for another similiar post."
Do you have any alternate links available?
EDIT: I did find an alternate method that worked for proper replacement of KingRoot with SuperSU. All good, and glad for the compatible xposed framework.
Click to expand...
Click to collapse
Thanks for the heads up!!. I'll check them ASAP.
EDIT: All links are fixed!!
kainanmaki said:
Thanks for the heads up!!. I'll check them ASAP.
EDIT: All links are fixed!!
Click to expand...
Click to collapse
Man, can't thank you enough for this...So great for someone like me with little knowledge for all this magic. I am gonna do this when I get back from vacation. Can't wait for the rest of it!
Thanks again
ElCid43 said:
Man, can't thank you enough for this...So great for someone like me with little knowledge for all this magic. I am gonna do this when I get back from vacation. Can't wait for the rest of it!
Thanks again
Click to expand...
Click to collapse
I hope to get part IV and V in no more than 10 days...
I'm in the process of testing removing/freezing many services, just a sneak preview:
So far I was able to disable close to 180-190 apps/services from a total 250-260 (can't remember the exact number).
Of course there are some key services removed (for e.g multi windows, but that's just one service).
Still you can easily remove like 165 without losing any stock functionality. That's how much bloated the tablet is.
Removing useless stuff from samsung and 3rd party (eg. VPN, Policy Updates) or more evident like MultiWindow, the gallery app or even the file browser.
Or the weird ones like the phone app that is hidden and you can't use (you can disable it and still keep LTE Data).
More to come.
Need Help - Having Untimely Reboot Issues
Wow...Thanks SO MUCH for this guide! It gives me hope that I can actually enjoy using my T707A to the fullest!
Alas, I need some assistance PLEASE:crying:
I'm following your guide to the letter, and I've successfully achieved Part 1. Part 2, however, alludes me even after many, many tries. Here is what is going right and wrong:
a) Achieved root with KingRoot
b) installed and achieved SU with Terminal
c) ISSUE - KingRoot (or something) reboots the tablet during Uninstall, which kills SU access obtained with Terminal
d) ISSUE - after reboot, I no longer have permission to run the scripts to uninstall KingRoot
Is there another way for me to do this? As long as the tablet is rebooting during uninstall of KingRoot I have no SU access, so can't do anything but start over and experience the same thing time after time.
ANY assistance would be so very much appreciated...MOST humbly & sincerely...Tom
Where did you find the alternate method??
zopert said:
First and foremost, thank you for the thorough walkthrough.
I've come across an issue with the provided links to KingRoot and RemoveKing. When I click on either, I receive the following message:
"Invalid Attachment specified. This can happen for a variety of reasons-- most likely because the thread or post you are trying to view has been moved or deleted. Please return to the forum home and browse for another similiar post."
Do you have any alternate links available?
EDIT: I did find an alternate method that worked for proper replacement of KingRoot with SuperSU. All good, and glad for the compatible xposed framework.
Click to expand...
Click to collapse
Hi...I am VERY interested in your "alternate" method for replacement of KingRoot with SuperSU that actually worked. Would you be so kind as to share that with me? I'm having huge troubles (see my post) replacing KingRoot as it reboots thus killing my SU access necessary to run the uninstall scripts provided in OP. Any help would be GREATLY appreciated. MOST humbly & sincerely...Tom
TomandJonna said:
Wow...Thanks SO MUCH for this guide! It gives me hope that I can actually enjoy using my T707A to the fullest!
Alas, I need some assistance PLEASE:crying:
I'm following your guide to the letter, and I've successfully achieved Part 1. Part 2, however, alludes me even after many, many tries. Here is what is going right and wrong:
a) Achieved root with KingRoot
b) installed and achieved SU with Terminal
c) ISSUE - KingRoot (or something) reboots the tablet during Uninstall, which kills SU access obtained with Terminal
d) ISSUE - after reboot, I no longer have permission to run the scripts to uninstall KingRoot
Is there another way for me to do this? As long as the tablet is rebooting during uninstall of KingRoot I have no SU access, so can't do anything but start over and experience the same thing time after time.
ANY assistance would be so very much appreciated...MOST humbly & sincerely...Tom
Click to expand...
Click to collapse
I had that problem many times, the uninstall reboots the tablet before you can establish SuperSu.
The most reliable way I found of overcoming this is to follow the exactly in this order and without stopping to much because google wants to run updates behind scenes that mess with our process (that's why sometimes it works and sometime it doesn't). My recommendation is to start over from scracth again (I know it's boring). I'll probably do it again on my tablet just to validate and to try some other things related to the original services).
TomandJonna said:
Hi...I am VERY interested in your "alternate" method for replacement of KingRoot with SuperSU that actually worked. Would you be so kind as to share that with me? I'm having huge troubles (see my post) replacing KingRoot as it reboots thus killing my SU access necessary to run the uninstall scripts provided in OP. Any help would be GREATLY appreciated. MOST humbly & sincerely...Tom
Click to expand...
Click to collapse
Other thing I forgot to ask, did you started clean from the first part or just started with part 2 of the guide?
Will this method trip Knox?
i need * RemoveKing file now...
Hello, new user here.
Since I stuggled with root on my Phone and somehow managed to maintain it, I thought, I 'd share you the stuff I did with you.
I put the TL;DR between hide, if you want to read the story behind my struggle anyway, you are welcome.
I am better with explaining stories then explaining things.
Spoiler
I am using a Samsung S4 mini, Stock ROM and just don't want to flash a cROM.
But I wanted more functions to do - a swiss knife like my old GT-S3650, which was able to boot a PC from.
Most of the things I want to use need root, so why not rooting this sleep S4 mini baby?
And I managed to root it using Kingroot. And all of the things I want to use worked.
After a few days, I noticed network traffic, even with the most network apps and Sync disabled.
Weird? Yes. So I installed "Shark" on my Phone and "Wireshark" on my PC, and started logging.
I noticed an increase of Jabber (the protocol) and a lot of request on domains from China.
Some requests even included my IMEI, how I am connected to the Internet, etc... pretty private Stuff.
I found most of the sources, the IMEI sending App was Shark itself.
Used Lucky Patcher to get rid of it and /etc/hosts blocked the DNS with Hosts Editor.
Did the same with some Kingroot DNS.
But then I asked myself: "Can Kingroot still root my phone, even when cut of the web?".
So I UNROOTED my Phone from Kingroot. Bad idea. Really bad one.
After I ran Kingroot again, it told me, it didn't have a network connection.
I have no idea how I was able to edit the hosts file without SU.
Rerooted the Phone, even if it left a bitter taste of having unwanted network traffic.
This is which made me want to switch to SuperSU.
I tried to mount system as RW prior and installing SuperSU over Kingroot SU. And it failed.
I even tried to make my own uninstall script to uninstall KR by unpacking the Kingroot APK and look what it does.
Not working, the script failed (I am not used to Linux), so I stayed at Kingroot.
While I was working on Kingroot, I was thinking about the idea of having 2 SU Apps, which everyone said it won't work.
But I wanted it to make work - and this is actually the focus on this topic.
During tests, it didn't work as intended, so I stopped working on it and forgot it overtime, resting within my /system.
Days passed, Weeks and Months and I lived with Kingroot, forgot all the trouble and access to/from China.
Recently, I started SuperSU - it was still on my phone. This "cannot install su binary" nagged me and thought:
Oh, why not use this instead.
And then there was SuperSuME... which I didn't want to use, since I was able to brick BlueStacks with it.
But I really wanted to get rid of Kingroot and use SuperSU. This was yesterday.
My phone still has warranty and I think I have Odin here (just in case), but not the 100% exact ROM file.
So I did SuperSuME anyway -I always could return the phone and claim it "broken after OTA update", lol.
Well, SuperSuME did it's Job better then expected and no bricks. Nice Job.
While playing around with SuperSU, I did another mistake.
And here we are... at the main topic.
TD;TR for those who didn't want to read the story:
I rooted my phone 2 times with Kingroot and finally wanted to switch to SuperSU.
After I accidentally broke Kingroot the first time, blocked it's Internet access and unrooted afterwards, I got stuck with a unrooted phone and Kingroot failed to root it.
I was lucky to fix that problem and rooted again with Kingroot.
After months, I used SuperSUME to change that. After SuperSU was installed, i made the mistake of unticking "Enable Superuser". Bad idea.
Tapping "Enable" again, it failed to update the su-binary. oh god. I unrooted again.
While traversing through my directories to start Kingroot again to root, I found my "shadow copy" of SU.
Wut? Shadow copy? Let me explain:
After my first unroot, I wanted to have a SU backup anyway at all costs, just in case I accidentally messup root again.
Now after hours I think I know why it doesn't work.. the normal way, of course.
I installed SuperSU, went into /data/data (or where ever SuperSU has its files) and took a look at them.
Unpacked the SuperSU APK on the PC and gathered all "needed" (I think were needed) files.
I hexedited the most SU binaries from SU to ZU and changed all other referenced binaries as well.
I am sorry about that, Chainfire. I was just testing things.
SU => ZU
SUpolicy => ZUpolicy
setup_su => setup_zu
99SuperSUDaemon => 99SuperZUDaemon
daemonsu => daemonzu
zygote => zugote
I had no idea what sukernel was for, so I left that out.
Why call it ZU? "Sun Tzu" thats why. Known as "Sunzi", he wrote Book about "the Art of War".
After I made sure everything is properly renamed and edited, I moved them onto my phone in the right directories required and chmod them.
I don't know much about that, I just copied the chmod numbers from Kingroot SU and some weird script I found on the web.
Tried to run it using JuiceSSH local terminal, and BAM!! the SuperSU box popped up.
But pressing "Allow" accepted it and nothing else happened.
It became stuck after ZU... it did nothing, but the daemon was running as daemonzu and daemonsu at the same time..
JuiceSSH popped up in SuperSU (while it told me the SU bin was outdated), though.
So I was on the right track, but a piece of the puzzle was missing, so I stopped delving deeper into it.
And forgot about it until about yesterday - where I disabled "Superuser" in SuperSU.
Midwhile the su binary changed from Kingroot SU to SuperSU SU.
Note: It should really ask "Do you want to disable Superuser? SuperSU will delete su binary" Yes/NO.
As I found those files, I started JuiceSSH and typed "zu".
This time, ZU somehow worked like it should.
It spawned a root shell. OMG...
I guess it somehow requires something else needed, which wasn't working while Kingroot was active.
I tried "Root Checker" and it failed. I had no "official" root. But still root available in JuiceSSH.
Somehow I managed to restore SuperSU to normal status. Guess this thing can latch onto an active root user or so.. no idea.
I even screenshotted this, cause I couldn't believe it. If you want, I can post those.
I have now a working second su on my phone, which is hidden from most apps.
But I think it is not perfect, it relies on something SuperSU does or installs during installation.
I apologize again to Chainfire for editing his stuff.
So, now my questions:
1. How can I make it perfect to run standalone, only using SuperSU as a GUI for (Allow/Deny)?
1b. Can we make it part of SuperSU? As a special function: "Install Stealth SU"?
2. Can we use that for something else? -> Probably for this? http://forum.xda-developers.com/apps/supersu/suhide-t3450396
3. Why must the binary be called SU? I know it's for the most apps to do their job and somehow Linux standard.
hello guys
i had s7edge which was totaly trash quality for music.
so i want to buy mi5 and root it for v4a.
does any one faced any problem?
when i root samsung devices it does not detect bluetooth headphones...
have any one tried v4a with bluetooth headphones cause they use qualcom security when u root it may cause problem
rooted s7 s6 s3 all dont detect bluetotoh headphone used to be detected
please help me sorry FOR BEING NOOB!
THANKS
big bang021 said:
hello guys
i had s7edge which was totaly trash quality for music.
so i want to buy mi5 and root it for v4a.
does any one faced any problem?
when i root samsung devices it does not detect bluetooth headphones...
have any one tried v4a with bluetooth headphones cause they use qualcom security when u root it may cause problem
rooted s7 s6 s3 all dont detect bluetotoh headphone used to be detected
please help me sorry FOR BEING NOOB!
THANKS
Click to expand...
Click to collapse
My MI5 runs official global MIUI 8.2.2.0 rooted with SuperSU and v4a installed.
I am using AWEI A885BL bluetooth headset and it is working just fine.
my old s4 (i9505) with rooted stock ROM detected this headset (and previous one I had - some cheap noname bluetooth headset)
th3cr0w said:
My MI5 runs official global MIUI 8.2.2.0 rooted with SuperSU and v4a installed.
I am using AWEI A885BL bluetooth headset and it is working just fine.
my old s4 (i9505) with rooted stock ROM detected this headset (and previous one I had - some cheap noname bluetooth headset)
Click to expand...
Click to collapse
Can u provide link or file with step ? Sorry im newbie ,thanks
pukiman1204 said:
Can u provide link or file with step ? Sorry im newbie ,thanks
Click to expand...
Click to collapse
the problem was that i should keep bluetooth headphone 10seconds to be seeing discovered....very bad lucky i sold s7edge
fk my luck
Gui
pukiman1204 said:
Can u provide link or file with step ? Sorry im newbie ,thanks
Click to expand...
Click to collapse
Here's the guide mate;
DISCLAIMER: I'll not be responsible for any damage caused to your device, earphone or the knife you use to slice apples by following this guide.
First off, your phone needs to be rooted, since V4A needs proper root to work.
All links to needed files will be placed at the bottom of this post. I'm assuming that you have downloaded and install all of them.
[UPDATE] : I had forgotten to mention this the first time i wrote this guide, but if you're on MIUI, you need to disable MusicFX (or uninstall with a system app remover) otherwise V4A will not be used to process your audio. Same goes for other stock equalizers like AudioFX or DOLBY or Beats etc.
Steps after confirming you have root access.
1. Check if you have any version of BusyBox on your phone via the BusyBox app, if not, then proceed to install it from the BusyBox app.
2. Open SELinux Toggler, grant it root access and set it to permissive. Also, if you're on MIUI, enable autostart for it in Security app.
3. Now, Open up Viper4Android, grant it root access and permission to storage, it'll ask to install drivers, press "yes" on the dialog box and wait till it says that drivers were installed successfully. After that reboot your phone.
4. Once your phone starts, fire open Viper4Android, if it doesn't show any message, it means that the drivers have been installed.
5. You can now enjoy V4A goodness. If you need help setting it up, reply to this post or check the XDA for threads on setting it up.
6. Drop a thanks to the developers' threads on XDA, they deserve it.
Links:
BusyBox
SELinux Toggler
Viper4Android v2.5.0.5
Notes/Known Issues:
1. Sometimes, the V4A driver isn't installed even though it says it is, if this happens it either means you don't have enough space in the system partition or there's some IO error, if this happens, reply to this post or check other threads for solution.
2. We all know MIUI memory management is crap, often times it will boot out the V4A app, leaving you without any effects . The best you can do to avoid it is set it to "no restrictions" in the Settings>Battery & Performance>Manage Apps Battery Usage>Choose Apps, then keep V4A locked in the recents screen.
3. Need help setting V4A up, just check xda for guides on that or ask me.
4. If you've set it all up, laid back and started to listen to something to relax you after all the work and it still doesn't feel like there's any difference, then fire open V4A, slide right for the menu and click "Driver status", if it says "abnormal", "unsupported" then you've probably forgotten to give autostart permission to SELinux Toggler, simple fix for this is to open SElinux Toggler and set it to permissive, this time remember to enable autostart for it.
5. If I helped a thanks would be much appreciated.
my Experience with Viper and MI5
I had a problem with the viper4android, which consisted of the calls not working, the phone made the call, but you could not speak because they were not listening.
migueltopsp said:
I had a problem with the viper4android, which consisted of the calls not working, the phone made the call, but you could not speak because they were not listening.
Click to expand...
Click to collapse
I don't think V4A has anything to do with that. V4A only has an effect on your headphone audio, speaker audio, bluetooth audio and when you're using it for USB docking. Calls use none of those unless you put them on speakerphone. Are you sure that V4A is causing this?
Sent from my Mi 5 using XDA Labs
iamffj said:
I don't think V4A has anything to do with that. V4A only has an effect on your headphone audio, speaker audio, bluetooth audio and when you're using it for USB docking. Calls use none of those unless you put them on speakerphone. Are you sure that V4A is causing this?
Sent from my Mi 5 using XDA Labs
Click to expand...
Click to collapse
But it was, I could hear the calls and after I installed the viper I stopped being able to listen, I went to the official viper xda post and noticed that I was not the only one with this problem, remembering that I'm using the developer rom 7.7. 20 (nougat).
After I uninstalled the viper the phone became normal again and worked perfectly.
Viper worked fine, I just had this bug that needs to be fixed.
iamffj said:
Here's the guide mate;
DISCLAIMER: I'll not be responsible for any damage caused to your device, earphone or the knife you use to slice apples by following this guide.
First off, your phone needs to be rooted, since V4A needs proper root to work.
All links to needed files will be placed at the bottom of this post. I'm assuming that you have downloaded and install all of them.
Steps after confirming you have root access.
1. Check if you have any version of BusyBox on your phone via the BusyBox app, if not, then proceed to install it from the BusyBox app.
2. Open SELinux Toggler, grant it root access and set it to permissive. Also, if you're on MIUI, enable autostart for it in Security app.
3. Now, Open up Viper4Android, grant it root access and permission to storage, it'll ask to install drivers, press "yes" on the dialog box and wait till it says that drivers were installed successfully. After that reboot your phone.
4. Once your phone starts, fire open Viper4Android, if it doesn't show any message, it means that the drivers have been installed.
5. You can now enjoy V4A goodness. If you need help setting it up, reply to this post or check the XDA for threads on setting it up.
6. Drop a thanks to the developers' threads on XDA, they deserve it.
Links:
BusyBox
SELinux Toggler
Viper4Android v2.5.0.5
Notes/Known Issues:
1. Sometimes, the V4A driver isn't installed even though it says it is, if this happens it either means you don't have enough space in the system partition or there's some IO error, if this happens, reply to this post or check other threads for solution.
2. We all know MIUI memory management is crap, often times it will boot out the V4A app, leaving you without any effects . The best you can do to avoid it is set it to "no restrictions" in the Settings>Battery & Performance>Manage Apps Battery Usage>Choose Apps, then keep V4A locked in the recents screen.
3. Need help setting V4A up, just check xda for guides on that or ask me.
4. If you've set it all up, laid back and started to listen to something to relax you after all the work and it still doesn't feel like there's any difference, then fire open V4A, slide right for the menu and click "Driver status", if it says "abnormal", "unsupported" then you've probably forgotten to give autostart permission to SELinux Toggler, simple fix for this is to open SElinux Toggler and set it to permissive, this time remember to enable autostart for it.
5. If I helped a thanks would be much appreciated.
Click to expand...
Click to collapse
Yep, thanked your post for the helpful step-by-step. I have a problem that's not covered in your guide, though - V4A isn't processing audio from my phone. That is, the driver status always look something like this:
Driver Version: 2.5.0.4
NEON Enabled: Yes
Enabled: Yes
Status: Normal
Audio Format: Supported
Processing: No
Sampling Rate: 48000
and there's perceptibly no difference between having the driver off or on with the master switch. Any ideas?
Cendolizer said:
Yep, thanked your post for the helpful step-by-step. I have a problem that's not covered in your guide, though - V4A isn't processing audio from my phone. That is, the driver status always look something like this:
Driver Version: 2.5.0.4
NEON Enabled: Yes
Enabled: Yes
Status: Normal
Audio Format: Supported
Processing: No
Sampling Rate: 48000
and there's perceptibly no difference between having the driver off or on with the master switch. Any ideas?
Click to expand...
Click to collapse
Hmm...Seems like your music player isn't using V4A to process the audio. I use mine only when I have headset connected, if i'm not playing anything, it shows exact same thing in my driver status. But if i play something, the driver status shows "Yes" for processing. I use BlackPlayer Ex, it allows you to use its own equalizer or your system's stock equalizer(v4a in my case). Maybe you should give that a try, but I'm not sure if that is the problem.
One thing I do know though is that if there is no audio playing on your phone, processing will (and should) show "No".
UPDATE: If you're on MIUI, you need to disable MusicFX. If you're on a custom ROM, then audioFX needs to be disabled. Will update my original guide with this too. Forgot to mention it there.
This is probably gonna fix it for you.
I rooted my phone at the beginning of November to install call recording - and everything went well.
I needed to check a recording yesterday and it had not recorded properly (caller was not recorded) and when I checked my phone rootchecker showed that the phone was no longer rooted.
What would have caused the phone to de-root without intervention from myself.
My phone is an Xiaomi Redmi Note 9 on Android 10.
The "root checker" apps are useless, they just ask the root manager for root permission for no reason at all, since you can simply take a look at the magisk manager and check if stuff is working properly from there. So you're basically giving root permission (which is a not a toy) for a random app so it can say if you have root or not lol.
Anyways, could you send more info like screenshots from the manager, and things like that? Your report lacks info.
Even so, I could recommend you to simply try and reinstall magisk to see if it fixes the problem, just download the magisk zip and install it as if it was a module, using the manager, and reboot. If you can't do that, install through the recovery (twrp or whatever you use).