Database Info

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.

CM11 get rid of Superuser?

I'm using a CM11 ROM, and Superuser is giving me problems - throws up errors now & again. I like and want to use SuperSU, but Superuser is integrated into the ROM.
How can I get rid of Superuser and replace with SuperSU (preferably just using my phone, no ADB).

setspeed said:
I'm using a CM11 ROM, and Superuser is giving me problems - throws up errors now & again. I like and want to use SuperSU, but Superuser is integrated into the ROM.
How can I get rid of Superuser and replace with SuperSU (preferably just using my phone, no ADB).
Click to expand...
Click to collapse
in the integrated superuser menu(can be found in device settings), if you open settings, you have the option of giving superuser access to "disabled" (by default it is apps only).
after disabling you just have to flash the supersu zip file(can be found on the supersu xda forum) via recovery mode. and you're done.

I flash the superSU.zip after flashing CM11 and Gapps so superSU is the main root app. Never had an issue.

Please keep it friendly and there is no need for name calling of any kind. We tend not to like people resurrecting old threads, but seen as this came in handy for someone there's no harm done.
Thread cleaned.

wedgess said:
Please keep it friendly and there is no need for name calling of any kind. We tend not to like people resurrecting old threads, but seen as this came in handy for someone there's no harm done.
Thread cleaned.
Click to expand...
Click to collapse
Thank you, mod. Wasn't trying to cause any problems, just trying to help a new member.

rdx93 said:
in the integrated superuser menu(can be found in device settings), if you open settings, you have the option of giving superuser access to "disabled" (by default it is apps only).
after disabling you just have to flash the supersu zip file(can be found on the supersu xda forum) via recovery mode. and you're done.
Click to expand...
Click to collapse
i'm having some problems in cm11 with superuser too so i took your advice and disabled it and flashed the supersu.zip but still no root and then i went back to enable it again under settings but now the superuser option is gone.
how do i fix this?

Just make clean flash of CM, then get SuperSU via store

JimZiii said:
i'm having some problems in cm11 with superuser too so i took your advice and disabled it and flashed the supersu.zip but still no root and then i went back to enable it again under settings but now the superuser option is gone.
how do i fix this?
Click to expand...
Click to collapse
In the SuperSU settings, there is a setting called something like "Respect Cyanogenmod Settings". Uncheck that.

Thnx alot! Works great! Now i just have to change that stupid google dialer that's in cm11
Sent from my GT-I9300 using Tapatalk

[Q] Non writable /system on Stock or something else?

I have done s-off via firewater, installed Philz CWM and done SU from there.
For all intents and purposes the system appears rooted (TiBu works, I get toast pop-ups etc).
I am also able to use ES File Explorer to mount /system as r/w.
I have also tried to remount system as r/w via adb shell.
All of these work as I am able to "touch /system/test.file" via adb and then delete it via ES File Explorer.
It would appear the system is writable.
However, when I try to install BusyBox from here:
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
I get "Insufficient storage available" (and I have plenty of space).
I have found this information on modifying the kernel either through a boot.img or a .ko:
http://forum.xda-developers.com/showthread.php?t=2708686
http://forum.xda-developers.com/showthread.php?t=2701816
But both have some indications that they may be out of date and cause problems with the latest release.
I'm not even sure I have to do either of these, because it appears writable from my tests.
It is possibly the busybox program - but that is the one I have used in the past.
I would like to find both a trusted way to install busybox AND understand why I might be getting this problem in the first place.
thanks

TraderJack said:
I have done s-off via firewater, installed Philz CWM and done SU from there.
For all intents and purposes the system appears rooted (TiBu works, I get toast pop-ups etc).
I am also able to use ES File Explorer to mount /system as r/w.
I have also tried to remount system as r/w via adb shell.
All of these work as I am able to "touch /system/test.file" via adb and then delete it via ES File Explorer.
It would appear the system is writable.
However, when I try to install BusyBox from here:
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
I get "Insufficient storage available" (and I have plenty of space).
I have found this information on modifying the kernel either through a boot.img or a .ko:
http://forum.xda-developers.com/showthread.php?t=2708686
http://forum.xda-developers.com/showthread.php?t=2701816
But both have some indications that they may be out of date and cause problems with the latest release.
I'm not even sure I have to do either of these, because it appears writable from my tests.
It is possibly the busybox program - but that is the one I have used in the past.
I would like to find both a trusted way to install busybox AND understand why I might be getting this problem in the first place.
thanks
Click to expand...
Click to collapse
If you do try one of the kernel related solutions do the first one as the second is based on firmware we won't have until next week. Also here is a little trick you can try: navigate from the root directory to /data/data ND look for the Busybox folder and delete it then attempt reinstalling it from the play store. May or may not work but worth a shot.

S1L3nTShaDoWz said:
If you do try one of the kernel related solutions do the first one as the second is based on firmware we won't have until next week. Also here is a little trick you can try: navigate from the root directory to /data/data ND look for the Busybox folder and delete it then attempt reinstalling it from the play store. May or may not work but worth a shot.
Click to expand...
Click to collapse
Well if you read the thread for the first link it looks like people are saying it was for the "older firmware" and people were having issues. I am not sure what "firmware" they are referring to, but the OP closed that thread and I am wary to use that since all of this stuff seems to be back from April and nothing more on it.
What do you mean about the second link not having firmware until next week? I don't see anything in there that talks about a particular firmware version. Also, I found this thread:
http://forum.xda-developers.com/showthread.php?t=2731893
That Rom uses 1.55.506.2 (latest OTA I believe???) and states that it is using flar's method from the second link....so I'm confused by your statements (but want to understand!).
I don't have any busybox folders in /data/data.
I'm having a similar problem trying to install Xposed as well:
"Xposed Installer couldn't be installed. Free up some space and try again"
I'm really not sure what's going on since it appears I have proper s-off and root using the standard methods. I can't believe no one else is trying to do these things on a stock ROM and not having issues :/
UPDATE: I'm thinking you meant the 4.4.3 update coming for us? That second thread has .ko for both 4.4.2 and 4.4.3.

UPDATE:
I went ahead and did another factory reset. This time, instead of using the Philz CMW option for "Re-root System (SuperSU)" I used the supersu.zip to flash superSU.
After that, when I went to try and install busybox and xposed I had no issues at all.
I'm not sure why the Philz option didn't work entirely...as it stated it worked, and appeared to give me root when launching my apps...maybe I should switch to TWRP :/

TraderJack said:
Well if you read the thread for the first link it looks like people are saying it was for the "older firmware" and people were having issues. I am not sure what "firmware" they are referring to, but the OP closed that thread and I am wary to use that since all of this stuff seems to be back from April and nothing more on it.
What do you mean about the second link not having firmware until next week? I don't see anything in there that talks about a particular firmware version. Also, I found this thread:
http://forum.xda-developers.com/showthread.php?t=2731893
That Rom uses 1.55.506.2 (latest OTA I believe???) and states that it is using flar's method from the second link....so I'm confused by your statements (but want to understand!).
I don't have any busybox folders in /data/data.
I'm having a similar problem trying to install Xposed as well:
"Xposed Installer couldn't be installed. Free up some space and try again"
I'm really not sure what's going on since it appears I have proper s-off and root using the standard methods. I can't believe no one else is trying to do these things on a stock ROM and not having issues :/
UPDATE: I'm thinking you meant the 4.4.3 update coming for us? That second thread has .ko for both 4.4.2 and 4.4.3.
Click to expand...
Click to collapse
Yeah on the kernel my bad, didn't see it had a normal one for non 2.23 firmware users lol, if you don't wanna use that kernel you can always use one of the other ones, maybe Faux's or Evolutionmods kernel. I actually currently use Evolutions kernel and it's quite nice. Also that ROM will work fine I believe, quite sure 1.55 is the latest OTA and if not it doesn't really matter. All though as some people have stated on your previous thread (i think?) you might as well use an optimized stock ROM such as CleanROM or ARHD (Android Revolution HD 8.1), all it is is a stock ROM thats been optimized for better performance and maybe has some tweaks to make it better. To be clear on the ARHD ROM, I stated the version because any higher version than that is for 4.4.3 which we currently don't have the firmware for.
TraderJack said:
UPDATE:
I went ahead and did another factory reset. This time, instead of using the Philz CMW option for "Re-root System (SuperSU)" I used the supersu.zip to flash superSU.
After that, when I went to try and install busybox and xposed I had no issues at all.
I'm not sure why the Philz option didn't work entirely...as it stated it worked, and appeared to give me root when launching my apps...maybe I should switch to TWRP :/
Click to expand...
Click to collapse
Glad you got your issue solved!

TraderJack said:
UPDATE:
I went ahead and did another factory reset. This time, instead of using the Philz CMW option for "Re-root System (SuperSU)" I used the supersu.zip to flash superSU.
After that, when I went to try and install busybox and xposed I had no issues at all.
I'm not sure why the Philz option didn't work entirely...as it stated it worked, and appeared to give me root when launching my apps...maybe I should switch to TWRP :/
Click to expand...
Click to collapse
Just so you know, when asking the recovery to reroot the system it's going to use the supersu app packaged with the recovery. It's likely a much older supersu app. You're always better flashing the latest version from the recovery itself because you can be sure it's running the latest binaries. If you updated the app from the play store after installation it probably would've worked. It's also possible it simply just doesn't inject the file properly, but a flashable zip always will work.
I can assure you that philz is probably the most updated recovery. It runs very well and does everything it's supposed to do. Are you running the Verizon M8 build or the unified M8 build?
Sent from my HTC6525LVW using Tapatalk

BadUsername said:
Just so you know, when asking the recovery to reroot the system it's going to use the supersu app packaged with the recovery. It's likely a much older supersu app. You're always better flashing the latest version from the recovery itself because you can be sure it's running the latest binaries. If you updated the app from the play store after installation it probably would've worked. It's also possible it simply just doesn't inject the file properly, but a flashable zip always will work.
I can assure you that philz is probably the most updated recovery. It runs very well and does everything it's supposed to do. Are you running the Verizon M8 build or the unified M8 build?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I did update to the latest version...the way Philz works is you choose the "Re-root option" and then it tells you to go and install SuperSU from the store. The only thing I may have done wrong (or misunderstood since it isn't well documented) is this was my "root" as opposed to my "re-root." By that, I mean I rooted originally with weaksauce to install firewater, but I used the Root option in Philz instead of the more discussed supersu.zip flash.
The weird thing about it was that root appeared to work properly. I got toast popups and could use things like TiBu. SuperSU said it was rooted, and Philz was passing the root check.
That should teach me from straying from the guides at all to use a feature not very well discussed.

TraderJack said:
I did update to the latest version...the way Philz works is you choose the "Re-root option" and then it tells you to go and install SuperSU from the store. The only thing I may have done wrong (or misunderstood since it isn't well documented) is this was my "root" as opposed to my "re-root." By that, I mean I rooted originally with weaksauce to install firewater, but I used the Root option in Philz instead of the more discussed supersu.zip flash.
The weird thing about it was that root appeared to work properly. I got toast popups and could use things like TiBu. SuperSU said it was rooted, and Philz was passing the root check.
That should teach me from straying from the guides at all to use a feature not very well discussed.
Click to expand...
Click to collapse
Can't say I ever used that option, it probably just didn't flash it correctly. You may want to post the problem in the recovery thread so they know about it.
In theory it should've worked the same way as flashing the zip. The only thing I could think of is how old the binary was or the location of the flash was incorrect.
Sent from my HTC6525LVW using Tapatalk

BS_FREE_Lollipop_5.0_Rom_BPB1_Based

This is a modified version of @jrkruse stock BPB1 deodexed ROM with all(or most) of the stock BS removed.
INSTRUCTIONS:
I've included the links needed if you want to use xposed. If you chose not to use Xposed, then skip that step in the flashing process.
I have only used Safestrap to install this ROM, but FlashFire should work as well.
1) Flash NO_BS_BPB1_ROM_DEODEXED.zip
2) Flash Extra_toggles.zip
3) Flash xposed-v75-sdk21-arm-arter97-snapdragon.zip
4) Flash Lollipop_Safestrap_Reboot_Extended_PM_PB1.zip
5) Flash BPB1_Firmware_No_Bootloaders.zip
6) After first boot, open Lollipop Recovery Control and install the latest Safestrap.
7) Open up Viper4Android and install the driver. Then install Viper Fix 1.1.apk and run the Viper fix in the app.
There is no need to flash any Viper zips with this ROM. This ROM has all the same apps as BOK3 V5, but obviously updated to the BPB1 apps. The only app added is multiwindow. I don't use multiwindow, so I can be certain that all aspects of it work, but everything seemed to work normally when I played with it.
Note: Don't pay attention to the 1- prefix in front of some of the ROM versions. I prefix all my flashables in my ROM folder with a 1-, 2-, 3-, ect, so that I have them all in order when I flash them instead of having to remember the order every time lol. I forgot to remove those prefixes when I uploaded the ROMs.

reserved

reserved1

Can this be dirty flashed over your bs free bok3?
Sent from my SM-G900V using Tapatalk
---------- Post added at 05:14 PM ---------- Previous post was at 04:53 PM ----------
Just dirty flashed. All is good so far. Thank you
Sent from my SM-G900V using Tapatalk

I've downloaded it multiple times from multiple mirrors, I keep getting 6619258FCFF93587050F9E15B2FFBAA9 as the md5 not
a1d8316898d604314b884dafb09298b0 that is listed for 1-NO_BS_BPB1_ROM_DEODEXED.zip on the download page. I'll give it a try anyway since I can always reflash my NCG stock.
Edit:
It works! But now I have 492 errors anytime I want to download something from google play? Anyone else with this issue?

renthispace said:
I've downloaded it multiple times from multiple mirrors, I keep getting 6619258FCFF93587050F9E15B2FFBAA9 as the md5 not
a1d8316898d604314b884dafb09298b0 that is listed for 1-NO_BS_BPB1_ROM_DEODEXED.zip on the download page. I'll give it a try anyway since I can always reflash my NCG stock.
Click to expand...
Click to collapse
Does anyone know what exactly is new/improved in this BPB1? I feel like these versions keep getting released, but I have no idea what is actually improved LOL.

Thanks! Seems to be working well. Google Calendar kept force closing, so I removed it and installed the Play Store version.

Some apps seen to have a touch recognition problem, like titanium backup. Haven't had any FC errors.

renthispace said:
Edit:
It works! But now I have 492 errors anytime I want to download something from google play? Anyone else with this issue?
Click to expand...
Click to collapse
twelvevyan said:
Some apps seen to have a touch recognition problem, like titanium backup. Haven't had any FC errors.
Click to expand...
Click to collapse
I don't have any of these problems on mine. Does anybody else? It sounds like you guys might have some bad data from a previous ROM. The Play Store was updated in this ROM, so clear data for the Play Store, and that might fix the problem.
Stupifier said:
Does anyone know what exactly is new/improved in this BPB1? I feel like these versions keep getting released, but I have no idea what is actually improved LOL.
Click to expand...
Click to collapse
It is just security patches in this ROM. I haven't found anything really new.
btonetbone said:
Thanks! Seems to be working well. Google Calendar kept force closing, so I removed it and installed the Play Store version.
Click to expand...
Click to collapse
I wouldn't expect Google Calendar to work, because it's not in the ROM lol.

Few Questions
First, since I'm pretty new to flashing ROMs with SafeStrap...
At each step of your process when you say "Flash" does that mean Safestrap-> Boot to Recovery ->Install Zip ???
I'm looking at needing Xposed in order to bypass my company's Exchange security requirement of encrypting my device in order to allow email access.
I got a little confused with all the Xposed documentation out there.
Does this set of instructions get me to where I can load the Xposed module to bypass that security and then continue from there?
Big Thanks for your help.
I'm going to start a backup of current ROM so I'll be ready to install this soon.
Regards,
NerdyKowboy

NerdyKowboy said:
First, since I'm pretty new to flashing ROMs with SafeStrap...
At each step of your process when you say "Flash" does that mean Safestrap-> Boot to Recovery ->Install Zip ???
I'm looking at needing Xposed in order to bypass my company's Exchange security requirement of encrypting my device in order to allow email access.
I got a little confused with all the Xposed documentation out there.
Does this set of instructions get me to where I can load the Xposed module to bypass that security and then continue from there?
Click to expand...
Click to collapse
Yes, flash means install in Safestrap.
If you flash the Xposed zip I linked in the original post, then you can use modules in the Xposed installer app included in the ROM.

CVertigo1 said:
This is a modified version of @jrkruse stock BPB1 deodexed ROM with all(or most) of the stock BS removed.
INSTRUCTIONS:
I've included the links needed if you want to use xposed. If you chose not to use Xposed, then skip that step in the flashing process.
I have only used Safestrap to install this ROM, but FlashFire should work as well.
1) Flash NO_BS_BPB1_ROM_DEODEXED.zip
2) Flash Extra_toggles.zip
3) Flash xposed-v75-sdk21-arm-arter97-snapdragon.zip
4) Flash Lollipop_Safestrap_Reboot_Extended_PM_PB1.zip
5) Flash BPB1_Firmware_No_Bootloaders.zip
6) After first boot, open Lollipop Recovery Control and install the latest Safestrap.
7) Open up Viper4Android and install the driver. Then install Viper Fix 1.1.apk and run the Viper fix in the app.
There is no need to flash any Viper zips with this ROM. This ROM has all the same apps as BOK3 V5, but obviously updated to the BPB1 apps. The only app added is multiwindow. I don't use multiwindow, so I can be certain that all aspects of it work, but everything seemed to work normally when I played with it.
Note: Don't pay attention to the 1- prefix in front of some of the ROM versions. I prefix all my flashables in my ROM folder with a 1-, 2-, 3-, ect, so that I have them all in order when I flash them instead of having to remember the order every time lol. I forgot to remove those prefixes when I uploaded the ROMs.
Click to expand...
Click to collapse
1.) In safestrap, just do wipe->factory reset or is more of a wipe required?
2.) Can I flash them all using the Zip Queue in Safestrap (TWRP 2.7.1.0) or should I do them one at a time?

Factory reset in factory recovery. You can install all of them on one queue.

CVertigo1 said:
Factory reset in factory recovery. You can install all of them on one queue.
Click to expand...
Click to collapse
I did that, and this is AWESOME. Love the ROM. Tough to decide between the two launchers. Haven't had this level of control in a while.
Only snag was that Android Pay doesn't recognize the device as Android authentic, so can't use Android Pay (which I almost never used anyway).
Thanks for all the work @CVertigo1

NerdyKowboy said:
Only snag was that Android Pay doesn't recognize the device as Android authentic, so can't use Android Pay (which I almost never used anyway).
Thanks for all the work @CVertigo1
Click to expand...
Click to collapse
I believe Android Pay doesn't work sheerly because the device is rooted, not because of the ROM itself.

Can't get snapchat to login with Xposed. I've read the solution is to do an Xposed framework uninstall, login to Snap, then reinstall Xposed, but have found a lot of people get hung in a bootloop when uninstalling.
Is this from using the wrong uninstaller or something else?
Which uninstaller is correct?
Do you have another solution?
I have tried removing the modules and doing a reboot to see if that'd be adequate.
EDIT:
The issue was the xposed framework.
To anyone else doing this on Galaxy S5 with this ROM (or same version of Xposed)
1.) uninstall Snapchat
2.) Deactivate modules from Xposed
3.) Download and Flash "xposed-uninstaller-arter97.zip" from this post: http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3113463
4.) Reboot and wait for all the apps to Optimize
5.) Reinstall snapchat and login
6.) Flash the same Xposed framework in original post of this thread (apps will re-optimize)

Is there a way to disable the high volume warning? I can't believe they now also have it on Bluetooth...

renthispace said:
Is there a way to disable the high volume warning? I can't believe they now also have it on Bluetooth...
Click to expand...
Click to collapse
Since Xposed is already in the ROM, inside of Xposed, go to Downloads & download the module "NoSafeVolumeWarning". Enable it and reboot.
Boom. No more volume warning.

NerdyKowboy said:
Can't get snapchat to login with Xposed. I've read the solution is to do an Xposed framework uninstall, login to Snap, then reinstall Xposed, but have found a lot of people get hung in a bootloop when uninstalling.
Is this from using the wrong uninstaller or something else?
Which uninstaller is correct?
Do you have another solution?
I have tried removing the modules and doing a reboot to see if that'd be adequate.
EDIT:
The issue was the xposed framework.
To anyone else doing this on Galaxy S5 with this ROM (or same version of Xposed)
1.) uninstall Snapchat
2.) Deactivate modules from Xposed
3.) Download and Flash "xposed-uninstaller-arter97.zip" from this post: http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3113463
4.) Reboot and wait for all the apps to Optimize
5.) Reinstall snapchat and login
6.) Flash the same Xposed framework in original post of this thread (apps will re-optimize)
Click to expand...
Click to collapse
So were you able to uninstall Xposed? I see your edit of "fixed issue" but in case you didn't or having issues I posted this in another thread.
http://forum.xda-developers.com/showpost.php?p=65635081&postcount=18

al50 said:
So were you able to uninstall Xposed? I see your edit of "fixed issue" but in case you didn't or having issues I posted this in another thread.
http://forum.xda-developers.com/showpost.php?p=65635081&postcount=18
Click to expand...
Click to collapse
Yes, that fixed the issue.
Successfully uninstalled Xposed, Reinstalled SnapChat and logged in without issue. Then, reflashed the Xposed framework.
So easy, but I was so nervous doing it after seeing many, many people talking about getting hung in a bootloop.

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