Database Info

[Q] [Solved] Superuser: isn't asking for permissions BUT apps work

I'm confused! I have superuser installed and as of yet no app has asked for permissions; they just work. With the exception of ROM Manager which just freezes (needs long hold on back key). On previous ROMs I've flashed, requests for permissions pop up and you allow/deny etc. I've tried using the updater from the marketplace (force closes) and updating the binary (force closes). Am not able to uninstall superuser. I've turned on/off USB Debugging, fixed permissions, almost everything else I've found on the net.
As apps are working it isn't the end of the world but I'm confused about why they are working and also slightly concerned over the security aspect of apps not asking me and just running.
Apps that work without asking include: Titanium Backup, CPU Master, NSTools, File Explorer
I9020
Matr1x 15 Kernel
Orca 1 RC-0.1 (Drew Garen/BamtauMod)

What version is it? Try flashing version 3.0.7, this was the first to work with ICS if I remember correctly.
http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip

Hi,
According to the app it's version 3.0.7 (41).
I should've mentioned that it's an ICS ROM, sorry.

flodb113 said:
What version is it? Try flashing version 3.0.7, this was the first to work with ICS if I remember correctly.
http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
Click to expand...
Click to collapse
You sir, are awesome! Thank you for link. I installed it and now my apps are requesting permissions.

Dynamo Nath said:
You sir, are awesome! Thank you for link. I installed it and now my apps are requesting permissions.
Click to expand...
Click to collapse
Glad you're happy with it! When ICS came out, we had to wait a week (I think) for the update to make SU work properly. Great work from the dev, as always.

Help with wiping and/or reinstalling busybox

Hey guys and gals,
I've got a 7.7 on stock ROM rooted using the original root method the day I purchased the tablet. I've been using my tablet happily for over a month now.
Unfortunately, late last night I opened up Google Play and started updating all my apps, including Busybox by stericson. There was a new busybox version out (1.20.1) and I decided to install it using "Smart install." I'm not sure if it tried to install to /system/bin or /system/xbin but after the install I saw the app give me an error message explaining that the install was unsuccessful. Anyways, now a lot of my root-requiring apps including Titanium Backup Pro is not functioning at all. It seems that my BusyBox installation is corrupt.
I tried using BusyBox Pro by stericson to uninstall but the corrupt busybox seems to have prevented a proper uninstall, so it still lingers. I downloaded JadeEyedWolf's root.zip from his pinned "Root" post which includes SU & BusyBox thinking that installing the root.zip from CWM Recovery would over-write the corrupt busybox. After flashing I rebooted the tablet and I still got the same corrupt busybox issues.
Anyone have any suggestions?
Thanks!
Edit: The corrupt busybox causes the Wifi to show Error when I try to turn on the radio. Not that internet is vital in repairing the tablet, but I've worked around it by tethering Bluetooth internet off of my OG HTC Evo 4G. It's strange though - I can peruse websites and view the items in the Google Play Store but it will never actually download, though the "Downloading --- " bar does display.

I had the same problem, stock rom as well. If you check the reviews for Stericson's Busybox on Google Play, the two top ones a few minutes ago both mentioned the same issue.
Trying to root again and reinstalling Superuser didn't help, neither did a factory reset (manually salvaging settings and data was a pain too).
Re-flashing the original rom fixed it, following the guide at http://forum.xda-developers.com/showthread.php?t=1469635
I switched to JRummy16 Busybox installer and it seems to work.
Surprising that no one else here mentioned the problem ...

Try this fix.

To be more specific: BusyBox installer 8.0 replaces /system/bin/sh and /system/bin/ash binaries. I don't have any idea why would it do that (considering that I specified /system/xbin as an install folder), but this quick fix restores original ash binary (and sh as a symlink to it).
Installer 8.1 and above has this bug fixed.

Had the same problem with busybox and had to re-install the rom. What does this fix do?
Sent from my GT-P6800 using xda premium

Already answered, see post above.

Deleted
Sent from my GT-P6800 using xda premium

Too late for me to try it, but thanks the same

ginkage said:
To be more specific: BusyBox installer 1.20.1 replaces /system/bin/sh and /system/bin/ash binaries. I don't have any idea why would it do that (considering that I specified /system/xbin as an install folder), but this quick fix restores original ash binary (and sh as a symlink to it).
Click to expand...
Click to collapse
Thank you so much it works well now! You're a life-saver ginkage. Should I keep the stericson busybox 1.20.1 original install or should I use the busybox installer to install a fresh copy of 1.20.1 in /system/xbin?
Thanks again!

Thank you so much it works well now!
Click to expand...
Click to collapse
That's why we are here.
Should I keep the stericson busybox 1.20.1 original install or should I use the busybox installer to install a fresh copy of 1.20.1 in /system/xbin?
Click to expand...
Click to collapse
Personally I always use /system/xbin, so that some custom kernel (like CWM) could use /system/bin if it wanted to.
BTW, the BusyBox installer bug was fixed in version 8.1, and current version is 8.2, so you should update it anyway. I was wrong to mention "1.20.1" version. Post edited.

Hi guys,
First of all, I want to apologize sincerely for the bug that my application introduced in 8.0. I didn't catch the bug because my device wasn't affected by the bug.. (I always test my app myself before releasing..yet I still miss things due to devices file structure being so different.)
At any rate, the bug was that the application symlinked all applets to Busybox. Normally, this is done if you use smart install and change the settings manually. By default smart install will not overwrite applets that are not already symlinked to Busybox.
This was not a problem with Busybox 1.20.1 but was a problem with my application and how it performed the install.
Again, I am very very sorry that this has occured, as a result I am scouring the web trying to find people with the issue and help them resolve it.
If you have this problem, it can easily be fixed by reflashing your current rom. you do not have to wipe or clear any data. Once this is done, you can download my installer, version 8.1 or greater and upgrade busybox as normal.
Please let me know if you guys have any questions.
Best Regards,
Stephen - Stericson

ginkage said:
Try this fix.
Click to expand...
Click to collapse
Deleted

I too had the same situation, updated busybox then noticed something was awry when hidebar wouldn't work. My issues go way beyond broken root and WIFI, I've also been getting constant reboots. I was just about to re-install the stock rom until I read about the possible udate.zip fix. I'm very interested in how to apply the zip (I don't have CWM) being that i do extensive customization (with no backup, I know, I know) and I'd hate to re customize everything again. If I can get things right the first thing I'll do is install CWM and perform a nandroid backup.

ninpo said:
I too had the same situation, updated busybox then noticed something was awry when hidebar wouldn't work. My issues go way beyond broken root and WIFI, I've also been getting constant reboots. I was just about to re-install the stock rom until I read about the possible udate.zip fix. I'm very interested in how to apply the zip (I don't have CWM) being that i do extensive customization (with no backup, I know, I know) and I'd hate to re customize everything again. If I can get things right the first thing I'll do is install CWM and perform a nandroid backup.
Click to expand...
Click to collapse
you don't need CWM, just copy the fix onto external storage card,enter recovery (PWR + Vol. up Buttons) and apply the update from there. just fixed my tablet this way

regius said:
you don't need CWM, just copy the fix onto external storage card,enter recovery (PWR + Vol. up Buttons) and apply the update from there. just fixed my tablet this way
Click to expand...
Click to collapse
A thousand thanks kind sir, I'm back in business, that was pain free
---------- Post added at 07:29 PM ---------- Previous post was at 07:27 PM ----------
ginkage said:
Try this fix.
Click to expand...
Click to collapse
Thanks for posting this, I'm in love with my 7.7 once again.

Appreciate the response stericson. I had purchased your Pro version but even after I fixed the uninstall failed and it also did not detect superuser permissions even though SU gave a notification that Busybox Pro was granted superuser. All other root-requiring apps work. Had to refund the Pro purchase though

No problem. there seems to be an issue with the application detecting root sometimes, that's why you can still try the install.
I'm looking into this issue, it just started showing up so I am not sure what is going on.

ginkage said:
Try this fix.
Click to expand...
Click to collapse
Really appreciate this fix. On the verge of wiping out everything....
But decide to see if its busy box since its the last thing i install before all this happens....
Just to note that uninstall busybox also doesnt solve the issue...
so need to fix.

I had a lot of problems with root permissions not being granted by Superuser app. Recently I have tried SuperSu from the market and uninstalled original Superuser app (important to follow the instructions for the App! ).
My main problem was that ntfssd was not granted root permissions at startup, so I had to start it again manually. With SuperSu it is no problem. Also I use Busybox and successfully updated to the latest binary recently.

ginkage said:
Try this fix.
Click to expand...
Click to collapse
Thank you so much for that, I had been driven crazy and had also gone through a factory reset to try and get my device back working, to no avail. Can I ask where you got the ash you're including here? It worked for my Samsung Galaxy Tab 7 Plus, on 3.2, but is it a generic enough file that it can be dropped on nearly all Android devices without any issues arising?
I only ask out of curiosity and understanding the system more.

[Root][APP]TowelPieRoot v1.2 10/5/2014

*** DISCLAIMER ***
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE! OR IF YOU LOSE ANY DATA, ITS CALLED BACK IT UP BEFORE HAND!
Towel Pie Root is a one click untethered app to root the Moto X, Moto G and the Droid Series(maybe others but these for sure) running 4.4.3 and below. It does NOT and WILL NOT root 4.4.4 so stop asking about it!
I want to started off by Thanking Geohot for Towelroot and JCase for Pie root, without them this wouldn't have been possible and I take NO credit for their exploits. If either of them doesn't want this posted they may contact me and I will gladly remove it.
Towel Pie Root combines Towelroot's futex exploit with a modified version of Pie root's xbin.img mount into one app. To achieve a one click untethered root for write protected devices! This DOES NOT remove write protection, and is still technically a temp root, I did include the option to enable root on boot. Which will re-root your device every time you reboot your phone, it also includes the option to perform a full reboot, or a soft reboot from within the app.
Here is a more technical description of what my app does. It includes TR's libexploit.so(aka the native exploit by Geohot) which I use to gain root privileges. Once it has root privileges it then echo's the file path to my modified Pie root file to uevent_helper. It then causes a hotplug event to trigger the kernel to execute the file path just echoed to uevent_helper. My modified Pie root files, kill TR's daemonsu and mounts Pie root's xbin.img over /system/xbin. Then it copies the newer version of SuperSU's su binary and executes the new daemonsu daemon and viola root
If you enjoyed my app, please donate to Geohot at https://towelroot.com/, and JCase at [email protected]ninglogic.com! I do not want any donations, I set out to develop this app purely as a challenge to broaden my development skills not to get a donation.
Installation Instructions: You need to have unknown sources checked in Settings>>Security, and if you have Towelroot installed uninstall it. In order to use TR's exploit I had to name the app's package name to the same name as TR's package name, so you will have to uninstall TR to install my app. Also if you are currently rooted with Pie root please reboot before running my app, to clear Pie's su daemon, and to unmount Pie's xbin.img. Then just click Make it ra1n on Moto, and wait for it to say Root Acheived Enjoy! If you encounter any issues please uninstall v1.0 then re-install v1.1.
Download link:
Version 1.2 for 4.4.2 devices
Version 1.2 for 4.4.3 devices
Version 1.1
Version 1.0
Known Issues: If after running it says Failed to Achieve Root, close the app and clear it from most recent's then reopen the app.
Screen Recording: https://www.youtube.com/watch?v=f6fXs3VJQHg (I will try to update this video with the full installation steps)
Changelog
-v1.2 10/5/2014
---Created a new bin.img from the tmo 4.4.3 sbf to fix the wifi issues
---Changed the modstring for the XT1032 hopefully it works now if it doesn't then there isn't anything else I can do
---Redid the device check to not allow unsupported devices to run the app
-v1.1 9/22/2014
---Added Moto G support, if I missed a model number let me know
---Fixed the issue with Xposed not working by mounting a bin.img over /system/bin
---Added in the ability to Uninstall the app and all files
---Added in various checks and prompts
Additional Thanks:
Verttex(Dier325) - for being my main tester and testing the numerous test apk's I sent him
jpond83 - for testing
mohlsen8 - for testing on the Moto G
NipplesOfTheFuture - for testing, some workflow ideas, and for convincing me to try and get the bin.img method working correctly

iKrYpToNiTe said:
*** DISCLAIMER ***
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE! OR IF YOU LOSE ANY DATA, ITS CALLED BACK IT UP BEFORE HAND!
Towel Pie Root is a one click untethered app to root Motorola devices running 4.4.2 maybe 4.4.3 and below.
I want to started off by Thanking Geohot for Towelroot and JCase for Pie root, without them this wouldn't have been possible and I take NO credit for their exploits. If either of them doesn't want this posted they may contact me and I will gladly remove it.
Towel Pie Root combines Towelroot's futex exploit with a modified version of Pie root's xbin.img mount into one app. To achieve a one click untethered root for write protected devices! This DOES NOT remove write protection, and is still technically a temp root, I did include the option to enable root on boot. Which will re-root your device every time you reboot your phone, it also includes the option to perform a full reboot, or a soft reboot from within the app.
Here is a more technical description of what my app does. It includes TR's libexploit.so(aka the native exploit by Geohot) which I use to gain root privileges. Once it has root privileges it then echo's the file path to my modified Pie root file to uevent_helper. It then causes a hotplug event to trigger the kernel to execute the file path just echoed to uevent_helper. My modified Pie root files, kill TR's daemonsu and mounts Pie root's xbin.img over /system/xbin. Then it copies the newer version of SuperSU's su binary and executes the new daemonsu daemon and viola root
If you enjoyed my app, please donate to Geohot at https://towelroot.com/, and JCase at [email protected]! I do not want any donations, I set out to develop this app purely as a challenge to broaden my development skills not to get a donation.
Installation Instructions: You need to have unknown sources checked in Settings>>Security, and if you have Towelroot installed uninstall it. In order to use TR's exploit I had to name the app's package name to the same name as TR's package name, so you will have to uninstall TR to install my app. Then just click Make it ra!n on Moto, and wait for it to say Root Acheived Enjoy!
Download link: http://www.androidfilehost.com/?fid=23578570567716728
Screen Recording: https://www.youtube.com/watch?v=f6fXs3VJQHg
Click to expand...
Click to collapse
Thank you Sir, and Jcase and geohot... now the big question... I just factory reset 4.4.2 and rooted Pie.. installed your entitlement hack.. worked dandy... than I tried the tr... and guess what..... your app no longer works.. so, do I need to do another factory reset and install this new towelpie app or will your entitlement hack not work with this either? Or should I be the test pilot and find out myself...

doitinthedirt said:
Thank you Sir, and Jcase and geohot... now the big question... I just factory reset 4.4.2 and rooted Pie.. installed your entitlement hack.. worked dandy... than I tried the tr... and guess what..... your app no longer works.. so, do I need to do another factory reset and install this new towelpie app or will your entitlement hack not work with this either? Or should I be the test pilot and find out myself...
Click to expand...
Click to collapse
No need to factory reset. Just make sure you uninstall the towelroot app.
Then install this Towel-root-pie app. JUST this app. Run it, you should be good from there.
iKrYpToNiTe, I know you don't want creditz, but this is also such a helpful and much appreciated tool. I do want to thank you for sharing it with us.
My thanks go out to jcase and geohotz as well. A smörgåsbord of thanks to all of you!!
tapa'd on my moto x

Not good, I can't get it to stop rebooting. 4.4.3 moto g. Selected root on reboot, and now it reboots over and over.
Edit: Factory reset my phone through recovery using instructions at https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/97329/p/30,6720,9050
I'm at least back where I started from.
Sent from my Nexus 7 using Tapatalk

side note, don't try it on the moto G. I'm stuck in a bootloop.
edit: was going to try and uninstall the app before it reboots but so far no good.. might have to factory reset
edit2: apparently I'm not fast enough to hit okay for the uninstall.
edit3: YES! I win. I uninstalled faster than towelpieroot could trigger the reboot! whew... took like 20 tries...

For future reference, you can (attempt to) uninstall using adb. It takes a bit more knowledge, but it's simpler.
adb uninstall (package)
tapa'd on my moto x

chrisp6825 said:
For future reference, you can (attempt to) uninstall using adb. It takes a bit more knowledge, but it's simpler.
adb uninstall (package)
tapa'd on my moto x
Click to expand...
Click to collapse
I tried! I couldn't get to ADB while in fastboot. How would I get into ADB Shell if I can't get into anything outside of recovery?

chrisp6825 said:
No need to factory reset. Just make sure you uninstall the towelroot app.
Then install this Towel-root-pie app. JUST this app. Run it, you should be good from there.
iKrYpToNiTe, I know you don't want creditz, but this is also such a helpful and much appreciated tool. I do want to thank you for sharing it with us.
My thanks go out to jcase and geohotz as well. A smörgåsbord of thanks to all of you!!
tapa'd on my moto x
Click to expand...
Click to collapse
Worked perfect! thanks!
So I was already Pied... Pie files already pushed to phone prior to running trpie app.. does this app do the pushing or do we still need to run Pie on its own to push the files?

doitinthedirt said:
Worked perfect! thanks!
So I was already Pied... Pie files already pushed to phone prior to running trpie app.. does this app do the pushing or do we still need to run Pie on its own to push the files?
Click to expand...
Click to collapse
According to the message the OP sent me, PIE is no longer necessary - at all. He advised me that you can run this app on a bone-stock Moto X that has never had PIE used on it.
Have fun guys, AND HIT THE "THANKS" BUTTON TO THE OP!!!!!!

tronmech said:
Not good, I can't get it to stop rebooting. 4.4.3 moto g. Selected root on reboot, and now it reboots over and over.
Edit: Factory reset my phone through recovery using instructions at https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/97329/p/30,6720,9050
I'm at least back where I started from.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
windraver said:
side note, don't try it on the moto G. I'm stuck in a bootloop.
edit: was going to try and uninstall the app before it reboots but so far no good.. might have to factory reset
edit2: apparently I'm not fast enough to hit okay for the uninstall.
edit3: YES! I win. I uninstalled faster than towelpieroot could trigger the reboot! whew... took like 20 tries...
Click to expand...
Click to collapse
I'm sorry it caused bootloops for you, I remove 4.4.3 from the OP so others don't try.

iKrYpToNiTe said:
I'm sorry it caused bootloops for you, I remove 4.4.3 from the OP so others don't try.
Click to expand...
Click to collapse
I --really-- can't believe this isn't getting more attention than this!!! Not to mention more "THANKS" for the OP?!?!
Guys, if you use this method, SHOW SOME APPRECIATION! Five-Hundred-Seven (507) views, as of this posting, and only 7 "THANKS"? Where's the other 500?
EXCELLENT Job, Sir.

I have been having issues using this method. I was already using Pie for several weeks and wanted to try this to survive reboots. As soon as I installed and ran it I actually lost the root that I already had. The Towel Pie Root app would say that I had root access but none of my other apps would agree. I would get the message at the bottom of the screen stating the app was granted super user permissions but then the app would tell me that i don't have root, I tried adaway, xposed, and root checker. I uninstalled SuperSU and switched over to the ClockworkMod SuperUser and that worked for root. The problem that I had after that is that the root apps that I was using no longer work. Adaway shows as disabled and when I try to enable it it fails. The same whit xposed, every time I try to update/install it fails. I removed Towel Pie Root and went back to rooting with Pie and I am getting the same results. Has the Towel Root portion of this changed something that I am now going to have to factory reset?
Edit:
After a few more reboots once TowelPieRoot was removed and starting Pie again from the beginning I now have root as it was with everything working. For now I am just going to keep things the way they were. I have my terminal emulator setup to run the last Pie command on every start so it always attempts to root first. This makes it really easy regain root even if my device does get restarted and I lose root..

wow thanks, will this work with Xposed framework? I was looking for a simple root method without voiding my warranty, this seems nice, I'm gonna try it, thank yoU!

I like the app.. seems to work great.. but the only issue I have is is the OTA going to be stopped from downloading? I have two moto x, one still on 4.4 and rooted with slap, and a new one on 4.4.2 rooted with this app. below is a shot of what I get when i force check an update with the slapped moto, this is with the 3c_OTA files renamed to .bak
I dont get the same message with the new moto on 4.4.2, what I get is "your moto is up to date" and the same two 3c_OTA files are also renamed to .bak files.

xposed works with gravity
yabbandroid said:
wow thanks, will this work with Xposed framework? I was looking for a simple root method without voiding my warranty, this seems nice, I'm gonna try it, thank yoU!
Click to expand...
Click to collapse
yes, it works. have it running now. make sure that you softboot from within xposed.
i realize this is my first post here, finally decided to sign up ONLY for the reason to thank the OP for this.
I've been frustrated trying to get towel to work come to find out that geohot sold out and replaced the .apk on the site, wow........ then you had something secret for us and it was this thread and release of towelpie, GREAT work and goodjob!

xt1058 worked in 4.4.3!

most excellent!!!!!!!!
---------- Post added at 09:16 PM ---------- Previous post was at 08:38 PM ----------
can someone tell me or point me in the direction of how to get the exposed modules up and running. i use this towel root, then open exposed framework installer and hit install/update and get a pop up with some info where the last line says "failed to create a backup or /system/bin/app_process" i hit ok and there is still red dashes under active columns for both App_process and XposedBridge.jar? am i missing a step? the towel root app says "root achieved enjoy" when i use it.

yamaha83 said:
most excellent!!!!!!!!
---------- Post added at 09:16 PM ---------- Previous post was at 08:38 PM ----------
can someone tell me or point me in the direction of how to get the exposed modules up and running. i use this towel root, then open exposed framework installer and hit install/update and get a pop up with some info where the last line says "failed to create a backup or /system/bin/app_process" i hit ok and there is still red dashes under active columns for both App_process and XposedBridge.jar? am i missing a step? the towel root app says "root achieved enjoy" when i use it.
Click to expand...
Click to collapse
You have to do a softreboot in exposed to get it to activate.

wooddale said:
You have to do a softreboot in exposed to get it to activate.
Click to expand...
Click to collapse
i tried that? it seems i have root since i can access the system folder with Solid Explorer. but when i open framework installer. hit install/update i get the error, when i softreboot and go it and hit install/update i get the same error. i have the instal set to classic, should it maybe be something different?

yamaha83 said:
i tried that? it seems i have root since i can access the system folder with Solid Explorer. but when i open framework installer. hit install/update i get the error, when i softreboot and go it and hit install/update i get the same error. i have the instal set to classic, should it maybe be something different?
Click to expand...
Click to collapse
Were getting off topic here PM me Thanks

How to install Viper4Android on S7 Edge?

I cant figure out how to do it, I am rooted and I can't figure it out!

Brava27 said:
I cant figure out how to do it, I am rooted and I can't figure it out!
Click to expand...
Click to collapse
Need a SeLinux Permissive Kernel for S7Edge first. Have you found one?

Brava27 said:
I cant figure out how to do it, I am rooted and I can't figure it out!
Click to expand...
Click to collapse
Seems this guy has the answer on an enforcing kernel.
http://forum.xda-developers.com/s7-edge/review/audio-quality-t3336558

If you haven't seen this thread already, check it out. I successfully installed V4A on my 935F with it.
http://forum.xda-developers.com/showthread.php?t=3335007

And FYI... it sounds fantastic!

You DON'T need permissive kernel for v4a any more..after hundereds of trials and errors I just downloaded newest apk from original v4a thread, put it in private-apps folder then set correct permitions rw-r-r, restarted device and it works flowellesly ! I have stock enforced kernel.

tin2404 said:
You DON'T need permissive kernel for v4a any more..after hundereds of trials and errors I just downloaded newest apk from original v4a thread, put it in private-apps folder then set correct permitions rw-r-r, restarted device and it works flowellesly ! I have stock enforced kernel.
Click to expand...
Click to collapse
Does it work with Spotify as well?

Why don' you try? I don't use it.

tin2404 said:
You DON'T need permissive kernel for v4a any more..after hundereds of trials and errors I just downloaded newest apk from original v4a thread, put it in private-apps folder then set correct permitions rw-r-r, restarted device and it works flowellesly ! I have stock enforced kernel.
Click to expand...
Click to collapse
Tried hundered of ways here as well,
Mine just keeps asking to install the damn driver all the time mate, and even if installed, after reboot - it just asks again to install/update the driver again.
Tried with the su.policy zip flash as well. Still cant get it to work!
Tried with the MM compatible newest APK and placed it in Priv-app. Guess that's what you did too. Cant figure out what I'm missing here.

It happens to me also.That means you did NOT properly root device.Error with constant driver install is because busybox..I rerooted device ,wiped data for SU, and granted permission to busybox again.DO NOT use any other Viper app then original one from thread !

tin2404 said:
It happens to me also.That means you did NOT properly root device.Error with constant driver install is because busybox..I rerooted device ,wiped data for SU, and granted permission to busybox again.DO NOT use any other Viper app then original one from thread !
Click to expand...
Click to collapse
Youv'e been a lot helpful mate,
I think I'm getting somewhere, Could you please tell me which busybox did you use?
Is it the Stericsson version, or the Meefik ?

Stericsson one. I hac problems as you did and concluded the most simple one was the best..All that modded Viper apps doesn't do any use.Just use original one,give permissions in private-apps, restart device and that is it

which music players support this? cuz so far all i see is status normal processing no

tin2404 said:
Stericsson one. I hac problems as you did and concluded the most simple one was the best..All that modded Viper apps doesn't do any use.Just use original one,give permissions in private-apps, restart device and that is it
Click to expand...
Click to collapse
Men! You put so much hope in my heart. Please, could you be so nice and prepare step by step to do list? I personally would ask you about 'give permissionso in private-apps'. Could you explain? Do you copy v4a to priv-apps? Where from? What permissions? And about busy box: when I open it it shows me that it is installed in su/xbin... in what folder did you install busybox? And one about reroot: did you go to su and choose: full unroot before flashing su again? And what about mount namespaces: checked or unchecked in su? Have to tell you that I've tried so much different ways and still v4a doesn't work. I would love to try your way but please put some lights here. Thanks!
SM-G935F powered by Echoe

I've tried my best, in all possible variables and finally decided to give up after wasting 3 straight days of a perfect weekend.
My Driver just doesn't stick and I've tried all alternative installation methods. I've kept backups of system/*.* so all damages were reversed without any flashing. Root, Busybox everything runs perfectly and tested everything for integrity.
So far I've cornered the issue to Systemless Root, which seems to be the only entity having issues with v4a. Until a proper answer is digged up, I'm gonna stick with my Note 5 which has this working on System-Mode Root. (The driver didn't stick on the Note 5 when I tried to use it with System-less) Luckily the Note 5 is still on LP, with Su 2.64.
Good Luck to those who are trying, and thanks to all who helped!

OK...I made comprehesive tutorial here
http://forum.xda-developers.com/s7-edge/themes/viper4android-proper-installation-t3340525

JazonX said:
I've tried my best, in all possible variables and finally decided to give up after wasting 3 straight days of a perfect weekend.
My Driver just doesn't stick and I've tried all alternative installation methods. I've kept backups of system/*.* so all damages were reversed without any flashing. Root, Busybox everything runs perfectly and tested everything for integrity.
So far I've cornered the issue to Systemless Root, which seems to be the only entity having issues with v4a. Until a proper answer is digged up, I'm gonna stick with my Note 5 which has this working on System-Mode Root. (The driver didn't stick on the Note 5 when I tried to use it with System-less) Luckily the Note 5 is still on LP, with Su 2.64.
Good Luck to those who are trying, and thanks to all who helped!
Click to expand...
Click to collapse
FRM300 said:
Men! You put so much hope in my heart. Please, could you be so nice and prepare step by step to do list? I personally would ask you about 'give permissionso in private-apps'. Could you explain? Do you copy v4a to priv-apps? Where from? What permissions? And about busy box: when I open it it shows me that it is installed in su/xbin... in what folder did you install busybox? And one about reroot: did you go to su and choose: full unroot before flashing su again? And what about mount namespaces: checked or unchecked in su? Have to tell you that I've tried so much different ways and still v4a doesn't work. I would love to try your way but please put some lights here. Thanks!
SM-G935F powered by Echoe
Click to expand...
Click to collapse
Has anyone managed to get it working? I've tried every single method to install it and still nothing!

csr.rocha said:
Has anyone managed to get it working? I've tried every single method to install it and still nothing!
Click to expand...
Click to collapse
Yes. Actually there is a perfect package from @guitardedhero. You have to be rooted, busyboxed, twrp'ed. Flash this: http://forum.xda-developers.com/attachment.php?attachmentid=3701983&d=1459364213
It is Viper Atmos Sony Beats edition working beautifully on ny S7E. Three more step to do after flashing: 1. freeze SoundAlive and AdaptSound, reboot. 2. go to system preferences and check whether Viper has memory access granted. 3. go to SuperSu and DISABLE 'Mount namespace separation', reboot. Done!
Btw. If you want to play with Profiles inside Viper, go to your internal memory using root explorer and inside Viper folder create folder called 'Profiles'.
Btw2. 6.0.1new abowe destroy your conf files. Hope you have backup.
Better flash @guitardedhero mod on fresh rooted rom. hope you enjoy.
Btw3. Sound is AMAZING!
S7E powered by Echoe™ v5

Thanks for your reply!
Just after I asked for help here, i found a driverless package from @guitardedhero that worked! Glad to know you did it too, mate! :highfive:

Working but 10 second later turn normal mod
Why do you think's going on?
For example in youtube, 10 second viber4android active, later deactivate.
SM-G935F cihazımdan Tapatalk kullanılarak gönderildi

Nope.

Nope.
^Preemptively answering all PMs.

This sounds amazing, May i ask for a very wanted feature? Android 10(Q) battery! If you make this possible ill love you to the ends of the world and donate a bottle of something good lol ?

Thanks for this. Can you tell me if the transcripts for screened calls are available with this?

mikkis2k said:
This sounds amazing, May i ask for a very wanted feature? Android 10(Q) battery! If you make this possible ill love you to the ends of the world and donate a bottle of something good lol
Click to expand...
Click to collapse
What are you asking for?

lollyjay said:
Thanks for this. Can you tell me if the transcripts for screened calls are available with this?
Click to expand...
Click to collapse
I'm not sure if call screen saves the transcript, but I've interacted with live transcriptions with multiple responses. You can see my screenshots in the other call screen thread.

TotallyAnxious said:
What are you asking for?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6/themes/magisk-aod-lockscreen-weather-mods-oos-t3847008
"v1.7 (23/04/2019)
- Add Android Q battery icon style"
This, if its possible tho, its weird that the oneplus 6 thats on pie can and we cant, you think its possible? ?

mikkis2k said:
https://forum.xda-developers.com/oneplus-6/themes/magisk-aod-lockscreen-weather-mods-oos-t3847008
"v1.7 (23/04/2019)
- Add Android Q battery icon style"
This, if its possible tho, its weird that the oneplus 6 thats on pie can and we cant, you think its possible? ?
Click to expand...
Click to collapse
No idea. I'll maybe look into it. But it's not something that immediately hits me as "hey I can do that". I'm incredibly lazy and stoned a lot (stage 3 colon cancer survivor). So keep that in mind lol

Well dang, I still can't get call screening even with this. That's the only feature I truly missed when I left pixel 2 xl for a op7pro. I just have the worst luck trying to get it back.
Also I had a super nice stable device on 9.5.13 with root and a lot of nice things and the only reason I even went to 10 was the other thread said it was working on 10 and xxx said it worked on 10 and now I've been on 10.0.1 for 3 days and it's the buggiest thing I've used ever
Sent from my OnePlus7Pro using XDA Labs

spart0n said:
Well dang, I still can't get call screening even with this. That's the only feature I truly missed when I left pixel 2 xl for a op7pro. I just have the worst luck trying to get it back.
Also I had a super nice stable device on 9.5.13 with root and a lot of nice things and the only reason I even went to 10 was the other thread said it was working on 10 and xxx said it worked on 10 and now I've been on 10.0.1 for 3 days and it's the buggiest thing I've used ever
Click to expand...
Click to collapse
It's incompatible with your set up or you didn't follow the directions. (I'm not angry). But I've posted screenshots proving it works
So try eliminating variables till it works.
https://forum.xda-developers.com/on...bling-google-pixel-call-t3946535/post80596215

TotallyAnxious said:
It's incompatible with your set up or you didn't follow the directions. (I'm not angry). But I've posted screenshots proving it works
So try eliminating variables till it works.
https://forum.xda-developers.com/on...bling-google-pixel-call-t3946535/post80596215
Click to expand...
Click to collapse
Well I am on the T-Mobile version converted to international so mine is the gm1915 which you already said might not work. I completely clearer out every magisk module I had, rebooted to a stock rooted phone and things were fine, installed your first module, rebooted things were fine, installed the companion module and get a bootloop. Thankfully I have twrp and uninstalled the companion module and now it boots. I just have a gut feeling it's not going to work on here and I REALLY hate wiping my data so I'm just going to wait and see if someone else makes a breakthrough on the gm1915 model
Sent from my OnePlus7Pro using XDA Labs

spart0n said:
Well I am on the T-Mobile version converted to international so mine is the gm1915 which you already said might not work. I completely clearer out every magisk module I had, rebooted to a stock rooted phone and things were fine, installed your first module, rebooted things were fine, installed the companion module and get a bootloop. Thankfully I have twrp and uninstalled the companion module and now it boots. I just have a gut feeling it's not going to work on here and I REALLY hate wiping my data so I'm just going to wait and see if someone else makes a breakthrough on the gm1915 model
Click to expand...
Click to collapse
Well you didn't follow the instructions. You didn't install Google phone. Please reread.
If you don't install Google phone before flashing the companion. It won't boot.
I provided clear instructions. Follow them and you'll get call screen.
How to install (Magisk Manager or TWRP):
0. Uninstall kirisakura kernel companion, it's included.
1. Install "Anxious7Pro_v*.zip".
2. Reboot.
3. Install google phone apk from apkmirror or just use the apk in the companion module.
4. Set up google phone, i.e. grant all permissions (including "Draw over other apps" and "Modify system settings"), set as default phone app, open app and set up available features.
5. Install "Anxious7ProCompanion_v*.zip".
6. Reboot.
7. Profit.
Also you should pretty much always have BusyBox installed if you're rooted.

TotallyAnxious said:
Well you didn't follow the instructions. You didn't install Google phone. Please reread.
If you don't install Google phone before flashing the companion. It won't boot.
I provided clear instructions. Follow them and you'll get call screen.
How to install (Magisk Manager or TWRP):
0. Uninstall kirisakura kernel companion, it's included.
1. Install "Anxious7Pro_v*.zip".
2. Reboot.
3. Install google phone apk from apkmirror or just use the apk in the companion module.
4. Set up google phone, i.e. grant all permissions (including "Draw over other apps" and "Modify system settings"), set as default phone app, open app and set up available features.
5. Install "Anxious7ProCompanion_v*.zip".
6. Reboot.
7. Profit.
Also you should pretty much always have BusyBox installed if you're rooted.
Click to expand...
Click to collapse
I have no idea what kirisakura kernel companion is, but is compatible with Smurf kernel? Could that be my problem?
I also had Google phone installed before I did this, I preferred it over oos dialer from the start
Sent from my OnePlus7Pro using XDA Labs

spart0n said:
I have no idea what kirisakura kernel companion is, but is compatible with Smurf kernel? Could that be my problem?
I also had Google phone installed before I did this, I preferred it over oos dialer from the start
Click to expand...
Click to collapse
You should follow the instructions. If it says install Google phone, you should do that. If it's already installed that means you should uninstall to install. And it's just a handful of shell script commands. It is NOT the issue.
I'm not trying to be difficult. But you've twice not followed the instructions. If you don't follow them. It won't work.
The instructions were set up specifically for this. The non-boot that is caused by Google phone being installed as a system app prior to being a user app. I have no idea why in hell that would cause a non-boot. But it does. As I said I am very lazy. I did everything I could to make this a one and done module. So I wouldn't have to provide much support.
Kirisakira companion is listed as feature but I actually rewrote it and that will probably be put into the original mod from freak07. It's just to emphasize not needing to install both.

I think it's ridiculous it requires instructions but it's the only consistent way I've found to get all the listed features working. Please please please ? ?? read them carefully and follow them. Meaning the below paragraph is the ridiculous part btw.
It makes no sense Google phone causes a non-boot when installed as system app first. Even in a module by itself. It causes that.
I spent a week figuring out the easiest way to do this. And I got it down to under 10 steps. Please follow them.
I even spent time leanring how the unity module template works ecause the companion module is unity. And I'm really lazy.
Simplified instructions
How to install (Magisk Manager or TWRP):
0. Uninstall Kirisakura kernel companion and Google Phone, if both/either are installed. Reboot if you uninstalled.
1. Install "Anxious7Pro_v*.zip".
2. Reboot.
3. Install google phone apk from apkmirror or just use the apk inside the companion module.
4. Set up google phone, i.e. grant all permissions (including "Draw over other apps" and "Modify system settings"), set as default phone app, open app and set up available features.
5. Install "Anxious7ProCompanion_v*.zip".
6. Reboot.
7. Profit.
If you don't follow the instructions, you'll probably end up in a non-boot/bootloop.

@TotallyAnxious I will post here. I will be doing clean install of Beta 4 in a couple of hours, and post feedback here. One question though... I am a beta tester for Google Phone. Should I not use it, and instead install the nodpi version of latest .APK that you linked?
Sent from my JiaYu S3 using XDA Labs

lollyjay said:
@TotallyAnxious I will post here. I will be doing clean install of Beta 4 in a couple of hours, and post feedback here. One question though... I am a beta tester for Google Phone. Should I not use it, and instead install the nodpi version of latest .APK that you linked?
Click to expand...
Click to collapse
Didn't you just confirm it works with that screenshot? And I use beta too. But I have stable in the companion module and you can use any verison. I just don't want to provide a non stable starting point. I get less issues reported that way haha you'll learn overtime I consider how to minimize the effort I need to put into support beyond the OP. I'm incredibly lazy.

TotallyAnxious said:
Didn't you just confirm it works with that screenshot? And I use beta too. But I have stable in the companion module and you can use any verison. I just don't want to provide a non stable starting point. I get less issues reported that way haha you'll learn overtime I consider how to minimize the effort I need to put into support beyond the OP. I'm incredibly lazy.
Click to expand...
Click to collapse
lol same here (lazy). But I think that testing your modules with clean beta 4 install is worth the time and effort.
Sent from my JiaYu S3 using XDA Labs

lollyjay said:
lol same here (lazy). But I think that testing your modules with clean beta 4 install is worth the time and effort.
Click to expand...
Click to collapse
I don't think it is but I haven't tried beta OnePlus software yet. But I doubt it's gonna be that different with a clean install. Can you post the screenshot here so people see it works? Until it's posted here, people can click the link to see it.
https://forum.xda-developers.com/on...-nolimits-7-0-speed-ram-t3933927/post80645203

TotallyAnxious said:
I don't think it is but I haven't tried beta OnePlus software yet. But I doubt it's gonna be that different with a clean install. Can you post the screenshot here so people see it works?
Click to expand...
Click to collapse
Sure, np
Sent from my JiaYu S3 using XDA Labs

Hi, Ive just followed the instructions and got this working.. but i previously had the google phone installed as system app so went to my uninstaller and uninstalled 3 things, phone, phone .com and android.phone i think it was and now i have no mobile data.
Any idea what i install again to get this back? Thanks!