To Sum up what is discussed on this topic and to get Viper4Android functioning on the Verizon Variant:
(It is a good idea to restart phone after every step)
1. Disable namespace separation in SuperSU (Restart Phone)
1A.(haven't confirmed if this is really required, but worked for me) Install SELinux and change mode to Persuasive.
2. Install Busybox app and install into xbin.
3. Install Viper4Android and grant SU access and click Yes to install drivers.
A Big thanks to everyone who contributed. (And incase I missed anyone, please let me or a moderator know so we can add you) @TotallyAnxious @gerguter @mcbeat257 @carycooke
I'll get it going later today for you
I am pretty sure everyone else has this same problem :3
here is the file i used and just installed with root explorer
I installed busybox from the playstore
https://play.google.com/store/apps/details?id=stericson.busybox
I do not use this but it is up and running on my V10
credit:http://forum.xda-developers.com/showthread.php?t=2191223
carycooke said:
here is the file i used and just installed with root explorer
I installed busybox from the playstore
https://play.google.com/store/apps/details?id=stericson.busybox
I do not use this but it is up and running on my V10
credit:http://forum.xda-developers.com/showthread.php?t=2191223
Click to expand...
Click to collapse
That program was already installed on the device - it's just that V4A fails to recognize that it is installed to install the driver.
mcbeat257 said:
That program was already installed on the device - it's just that V4A fails to recognize that it is installed to install the driver.
Click to expand...
Click to collapse
all you need is the busybox i have a link to in previous post
carycooke said:
all you need is the busybox i have a link to in previous post
Click to expand...
Click to collapse
Issue with this is I have busybox and it still comes up with this issue:
http://uploads.tapatalk-cdn.com/20160316/d2192a31050084bbc50234edb091737c.jpg
I also have proof that busybox is installed:
http://uploads.tapatalk-cdn.com/20160316/39442dc5dfd51068d57fa0cd98220d2f.jpg
Sent from my VS990 using Tapatalk
mcbeat257 said:
Issue with this is I have busybox and it still comes up with this issue:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I also have proof that busybox is installed:
Spoiler
Sent from my VS990 using Tapatalk
Click to expand...
Click to collapse
thats a good one and not sure ALL i could tell you is to try and unistall busybox and goto superuser and make sure it is not blocking it on permission rights
then reinstall it again and make sure superuser has allowed it
carycooke said:
thats a good one and not sure ALL i could tell you is to try and unistall busybox and goto superuser and make sure it is not blocking it on permission rights
then reinstall it again and make sure superuser has allowed it
Click to expand...
Click to collapse
Been there, done that. Pretty sure it is a big system glitch or the app itself is glitching.
Sent from my VS990 using Tapatalk
mcbeat257 said:
Been there, done that. Pretty sure it is a big system glitch or the app itself is glitching.
Sent from my VS990 using Tapatalk
Click to expand...
Click to collapse
i have also read somewhere that busybox has to be installed before V4A if not you have to uninstall V4A and busybox
then reinstall busybox first then V4A
hope this helps
carycooke said:
i have also read somewhere that busybox has to be installed before V4A if not you have to uninstall V4A and busybox
then reinstall busybox first then V4A
hope this helps
Click to expand...
Click to collapse
I also did that, I even factory resetted it, still not working. Pretty sure V4A is the culprit of this glitch.
Try disabling namespace separation in SuperSU and reinstall busybox. Namespace separation can cause issues with apps being able to write to system. So even if busybox is there V4A might have issues with writing to system and the app assumes it's a busybox issue even if it isn't.
---------- Post added at 08:36 PM ---------- Previous post was at 08:29 PM ----------
And don't forget about selinux needing to be permissive.
I can confirm that changing the name space setting works. I'm on At&t.
TotallyAnxious said:
Try disabling namespace separation in SuperSU and reinstall busybox. Namespace separation can cause issues with apps being able to write to system. So even if busybox is there V4A might have issues with writing to system and the app assumes it's a busybox issue even if it isn't.
---------- Post added at 08:36 PM ---------- Previous post was at 08:29 PM ----------
And don't forget about selinux needing to be permissive.
Click to expand...
Click to collapse
Unfortunately, after setting SELinux to permissive and toggling namespace separation, it STILL seems to not recognize busybox.
mcbeat257 said:
Unfortunately, after setting SELinux to permissive and toggling namespace separation, it STILL seems to not recognize busybox.
Click to expand...
Click to collapse
Did you reboot after toggling? And reinstall busybox after rebooting? If that doesn't work, I would uninstall viper reboot and reinstall and try again.
TotallyAnxious said:
Did you reboot after toggling? And reinstall busybox after rebooting? If that doesn't work, I would uninstall viper reboot and reinstall and try again.
Click to expand...
Click to collapse
After doing that, still no luck.
mcbeat257 said:
After doing that, still no luck.
Click to expand...
Click to collapse
Perhaps walk me through everything you did? I'll see if it's any different from what I did.
Are you still getting the busybox error or something else?
TotallyAnxious said:
Perhaps walk me through everything you did? I'll see if it's any different from what I did.
Are you still getting the busybox error or something else?
Click to expand...
Click to collapse
Still getting the same error. I uninstalled v4a and busybox, then rebooted, then installed busybox and set SELinux, then installed V4A. Still the same issue.
Sent from my VS990 using Tapatalk
mcbeat257 said:
Still getting the same error. I uninstalled v4a and busybox, then rebooted, then installed busybox and set SELinux, then installed V4A. Still the same issue.
Sent from my VS990 using Tapatalk
Click to expand...
Click to collapse
Did you uninstall the busybox app or busybox itself?
TotallyAnxious said:
Did you uninstall the busybox app or busybox itself?
Click to expand...
Click to collapse
I did forget to mention I did this twice with both uninstalling the app and busybox itself and it didn't work.
Sent from my VS990 using Tapatalk
Related
You guys should try the SuperSU app by chainfire. It's a hundred times better than the usual SuperUser app. Trust me, you will be benefited. I am currently using it with gingercruzt- xs. Works great.
Install instructions:
1) Go to the play store and Install SuperSU.
2) Open it.
3) It will prompt for a binary update. Accept it.
4) After installation succeeds configure the app to suit your needs.
5) Reboot
Note- You can't use SuperUser(not SuperSU) app with SuperSU. Either delete it using a root browser or don't open it.
Cheers.
Oh really?
So tell me, what is there so much better than regular Superuser.
i use SuperSU with CM9 and it's a nice option for ics i think, but both apps are good, don't think that one is better, i only like the SuperSU interface more
Defy mit Android 4.0.4 CM9 RockZ
dey both do tha same function... OP why not post screenies??
AnTerNoZ said:
i use SuperSU with CM9 and it's a nice option for ics i think, but both apps are good, don't think that one is better, i only like the SuperSU interface more
Defy mit Android 4.0.4 CM9 RockZ
Click to expand...
Click to collapse
How much do you REALLY use the UI?
Someguyfromhell said:
How much do you REALLY use the UI?
Click to expand...
Click to collapse
i dont even remember when last i open mine....!
once a year?? ... ok every nightly update when if forgotten to integrate in the update... normally never, but when i really like a black background because i flash the roms after midnight and the white superuser interface hurts my eyes
Defy mit Android 4.0.4 CM9 RockZ
Unless Superuser runs into problems, I won't change it at this point. Superuser just works... if and when I start learning to be a dev myself then I would need to understand su logs, but for the moment I don't need the granular control of SuperSU.
And I Quote......
"SuperSU takes SuperUser and enhances just about every bit of it! It comes with a better access prompt/logging/notifications, lets you configure notifications for each apps, unroot your device temporarily so you can access non-root-only services like Google Videos and more. These features are included in the free version while the pro version comes with features like an OTA Survival Mode in which SuperSU attempts making through an OTA update that normally removes root access, PIN protection, color-coded input, output and error command content logging...."
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"SuperSU obviously requires root permissions to run, so be sure to root your Android device first. After rooting, you may install SuperSU so that it can manage root permissions. If you already have SuperUser installed, then you don’t have to do anything special: installing SuperSU automatically dethrones SuperUser from root management..."
"I’ve been using SuperSU for the past few weeks and, to be very honest with you, haven’t noticed any significant differences between it and SuperUser. Unless you’re an advanced enthusiast, you won’t either. But yes, the Android developer community has been singing praises for it, so we still highly recommend you get it for your device...."
For our phones, OTA update doesn't remove root anyway.
Other features seem a bit useless to me.
Someguyfromhell said:
For our phones, OTA update doesn't remove root anyway.
Other features seem a bit useless to me.
Click to expand...
Click to collapse
Question to OP. Why do we need to use (Super)SU at the first place?
Thanks,
Rick
DragonClawsAreSharp said:
Question to OP. Why do we need to use (Super)SU at the first place?
Thanks,
Rick
Click to expand...
Click to collapse
It's up to personal preference. But, I would use it mainly for the segmentation error free binary, ability to use su even when android is not booted and more sleeker and darker ui than superuser. It's binary updater is also good.
@Someguyfromhell, why are you being so rude? Have I posted something wrong?
Guys, a lot of people started using this so I suggested that you guys should also try this out.
Sent from my iPhone 3GS using Tapatalk
Will there aany problem when I use both SU and SuperSU? Or can I remove SU after installing SuperSU without problem?
cafelak said:
Will there aany problem when I use both SU and SuperSU? Or can I remove SU after installing SuperSU without problem?
Click to expand...
Click to collapse
the only thing is the different su binarys, if u install the SuperSU su-binary the normal su app stop working because it isn't compatible with the su-binary from super su.
u can remove superuser.apk, BUT don't forget if u want to revert to the normal superuser u have to upgrade the su binary with it, others u will lose root access.
Defy mit Android 4.0.4 CM9 RockZ
AnTerNoZ said:
the only thing is the different su binarys, if u install the SuperSU su-binary the normal su app stop working because it isn't compatible with the su-binary from super su.
u can remove superuser.apk, BUT don't forget if u want to revert to the normal superuser u have to upgrade the su binary with it, others u will lose root access.
Defy mit Android 4.0.4 CM9 RockZ
Click to expand...
Click to collapse
Hmm, so complicated, i've just installed this app but i am going to remove it now. I'm a general user, so using this app or a normal superuser app is not important for me. I just care that my phone is rooted. Avoiding trouble is better
I installed it quite a while ago.. Apart from the nice looking UI I didn't find anything else better than regular SU so I uninstalled.
Newb here.
I have just rooted my xperia z1and as per advice installed SuperSu.
I rooted because I was having SD card permissions problems.
Can you tell me how I can change permissions on Apps or sd card.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Greetings to Friends
A few days ago in xperiablog
Root was introduced to the Xperia Z1
Mod edit: Links removed
I 've tested the same time I realized that the Xperia sp
This software can be easily routed
get to share with your friends
Although is very easy
But I will give a simple video tutorial
First, the software VRoot Download the attachment to this post
Or from the manufacturer's site
Mod edit: Links removed
1 - Install drivers for your phone
2 - Activate the option in your phone Enabled usb debugging
Settings / Developer options
3 - After opening the software and USB cable to connect your phone
4 - When was your phone program
Right click the first option
As shown
Your phone will then reboot
And successful Root the message on the screen
This method will work on most Sony devices
If it is successful, then reboot the phone, the application icon will appear in Root
Thanks
Amir
It worked!
But the app is in Chinese or something, no setting for English?
pergane said:
It worked!
But the app is in Chinese or something, no setting for English?
Click to expand...
Click to collapse
Just install SuperSu from playstore open it update the su binary and then remove the chinese superuser app
Sent from my C5302 using Tapatalk 4
Thanks!!!
undisputedpro said:
Just install SuperSu from playstore open it update the su binary and then remove the chinese superuser app
Sent from my C5302 using Tapatalk 4
Click to expand...
Click to collapse
Doesn't work on my Z1. Happens like this:
Root... Check
Install SuperSu... Check
unintelligible Chinese. superuser... resulting in unrooted phone.
Another idea to get a nonChinese superuser?
Gesendet von meinem C6903 mit Tapatalk 4
Herman.TM said:
Doesn't work on my Z1. Happens like this:
Root... Check
Install SuperSu... Check
unintelligible Chinese. superuser... resulting in unrooted phone.
Another idea to get a nonChinese superuser?
Gesendet von meinem C6903 mit Tapatalk 4
Click to expand...
Click to collapse
Try to install CWM for your XZ1 then flash SuperSu from here : SuperSu.zip
Sent from my C5302 using Tapatalk 4
Is it works with the new 2.254 firmware?
Raz9 said:
Is it works with the new 2.254 firmware?
Click to expand...
Click to collapse
Yes it does
Edit: I can't update SU binary with Supersu. :/
It not works with the 2.254 firmware and it gives you phone restarts when try to do any root thing for example delete a system file.
SuperSu does not work either. I can update the binary but gives you unlimited phone restarts right after boot. So bootloop.
I deleted it in safe mode.
Waiting for the new version. :\
I have now installed supersu and updated binairy.
also i have tried superuser from chainsdd ant had no bootloop anymore but lost root when removing the chinese version.
how do i delete the chinese superuser app without losing root?
EDIT:
Somehow i managed to root my phone while the chinese superuser was removed and it didn't come back after root using Vroot
so now i am using supersu and it's working perfect.
EDIT:
Phone force reboot when removing system app or changing /system to r/w.
Pietertje_ said:
EDIT:
Phone force reboot when removing system app or changing /system to r/w.
Click to expand...
Click to collapse
use better this vRoot Mod edit: Links removed
After first start let it update itself to v1.7 and root your SP easy.
Then open flashtool and install busybox, phone reboots.
Open flashtool again and install busybox. now reboots should be gone.
now install recovery from SaM, download "Clockworkmod superSu" as flashable zip, go to recovery and install zip. now chinese Supersu is gone. :good:
when reboots will not be gone, then use this rebootfix
heross said:
use better this vRoot Mod edit: Links removed
After first start let it update itself to v1.7 and root your SP easy.
Then open flashtool and install busybox, phone reboots.
Open flashtool again and install busybox. now reboots should be gone.
now install recovery from SaM, download "Clockworkmod superSu" as flashable zip, go to recovery and install zip. now chinese Supersu is gone. :good:
when reboots will not be gone, then use this rebootfix
Click to expand...
Click to collapse
I have used this rebootfix and works perfectly.
Thanks
this method works for both locked bootloaders and unlocked bootloaders
Thread closed and links removed until such time as the validity of this software can be determined due to some security concerns regarding this application. If you have any concerns you can PM me.
Here is a way for us to change the SELinux status to Permissive on our ATT N3.
Prerequisites
1. Busybox must be installed.
2. Have to be on NC2 or MLG Kernel. If not then download it from here (http://d-h.st/lBR) and flash it using Odin (select PDA). (You DON'T have to upgrade your BL to NC2. Just the kernel. I'm still on MLG BL, so I can still roll back to 4.3 if I wanted).
3. Most importantly. Have to be on SuperSU 2.13 http://d-h.st/afU
Instructions: (only if you plan on applying manually after every reboot)
1. Download http://www78.zippyshare.com/v/1605705/file.html
2. Move the file to /data/local/tmp/
3. Change Permission to 0755 (-rwxr-xr-x)
3. Open up the Terminal Emulator and type the following.
Code:
su -c /data/local/tmp/SE_Status_Change_via_kmem.sh
4. Enjoy.
OR
Instructions: (to apply automatically at reboot)
1. Download http://www78.zippyshare.com/v/1605705/file.html
2. Change its name from "SE_Status_Change_via_kmem.sh" to "SE_Status_Change_via_kmem"
3. Move that file to /system/etc/init.d/
4. Change permission to 0777 (-rwxrwxrwx)
5. Reboot.
Proof.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Pardon my n00bness, but what are the benefits of this?
Face_Plant said:
Pardon my n00bness, but what are the benefits of this?
Click to expand...
Click to collapse
+1
Face_Plant said:
Pardon my n00bness, but what are the benefits of this?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=55912097#post55912097
dcscorpio76 said:
+1
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=55912097#post55912097
Walter.White said:
http://forum.xda-developers.com/showthread.php?p=55912097#post55912097
Click to expand...
Click to collapse
Sweet! I'm not a huge fan of AOSP, but something other than TouchJizz ROMs would be a nice change.
I second that. I miss me some halo and over clocking.
Not sure what I'm missing but mine stays enforced, I've tried using terminal and it runs but remains enforced. What I'm doing wrong?
Sent from my SM-N900A using XDA Premium HD app
Face_Plant said:
Sweet! I'm not a huge fan of AOSP, but something other than TouchJizz ROMs would be a nice change.
Click to expand...
Click to collapse
You can still benefit hugely from a custom kernel
+1. Tried both methods above, and I also tried using script manager to run the script. Would love to get this working; NTFS mounting through Total Commander is a bit annoying....
Dirtburgler said:
Not sure what I'm missing but mine stays enforced, I've tried using terminal and it runs but remains enforced. What I'm doing wrong?
Sent from my SM-N900A using XDA Premium HD app
Click to expand...
Click to collapse
optimusv45 said:
You can still benefit hugely from a custom kernel
Click to expand...
Click to collapse
I never noticed a huge difference with custom kernels on my old Galaxy Nexus.
Face_Plant said:
I never noticed a huge difference with custom kernels on my old Galaxy Nexus.
Click to expand...
Click to collapse
Maybe it wasn't a good custom kernel I always have on every device I owned
optimusv45 said:
Maybe it wasn't a good custom kernel I always have on every device I owned
Click to expand...
Click to collapse
I've tried the ever popular Franco kennel and many others that I can't remember. The only BIG difference I noticed was the colors were a bit different, but that's about it.
Yo Heisenberg! I may be doing something wrong, everytime I run the shell I see the permission goes from enforced to enforced.
Sent from my SM-G900A using XDA Free mobile app
T3hPWN said:
Yo Heisenberg! I may be doing something wrong, everytime I run the shell I see the permission goes from enforced to enforced.
Sent from my SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
+1 Same for me.
---------- Post added at 01:01 PM ---------- Previous post was at 12:05 PM ----------
I wonder if it's staying enforced because I do not have killer kat installed on the stock rom slot.
Nah, don't think that's it. I'm currently using the stock slot, and nothing has changed. Crossing my fingers that this can be straightened out...
Dirtburgler said:
+1 Same for me.
---------- Post added at 01:01 PM ---------- Previous post was at 12:05 PM ----------
I wonder if it's staying enforced because I do not have killer kat installed on the stock rom slot.
Click to expand...
Click to collapse
Ya I just booted into stock slot and tried it and got the same result.
Weird. I took a look at the script, and it mentioned busybox. It turns out that for some reason I lost busybox, and I am going to try this again and let you guys know if this is working on my end.
Dirtburgler said:
Ya I just booted into stock slot and tried it and got the same result.
Click to expand...
Click to collapse
---------- Post added at 12:50 PM ---------- Previous post was at 12:44 PM ----------
Looks like I'm seeing the script run now, but I am getting the whole SELinux has been set to Enforcing. Here's to hoping this gets fixed...
gangpe said:
Weird. I took a look at the script, and it mentioned busybox. It turns out that for some reason I lost busybox, and I am going to try this again and let you guys know if this is working on my end.
Click to expand...
Click to collapse
I tried the busybox route as well. I'm sure it is something simple that I'm forgetting.
Is there any other benefit than the possibility of flashing custom kernels when changing to "permissive"? If not, why am I changing it?
Any suggestions on how to get Substratum or other theme engine working on our device? The only version I can get to work consistently is v12.
V17 sorta works if you dirty flash, but not a clean install. No luck with ZenUI rom either.
After some testing by myself and others, Substratum does work in Legacy mode on V12 with no modification.
In order to get it working properly on V17 I recommend the following:
Flash the permissive boot.img provide by @vampirefo
Issue the adb remount command via pc
Create the 'overlay' folder in /system/vendor either via adb shell or root file manager
Copy the 'aopt' and 'aapt' file from /data/data/projekt.substratum/files into /system/bin either via adb shell or root file manager
Clear theme cache in Substratum if themes are not applying. Reboot. Attempt to apply theme again.
This works for me using Orange Kitten Pro, Swift Black, Swift Dark, The Kittens, Navigate and Navbars themes.
Thanks to @vampirefo and @keredini for their assistance.
exjinn said:
Any suggestions on how to get Substratum or other theme engine working on 6.6?
Click to expand...
Click to collapse
By "Modified 6.6" do you mean the one without Amazon bloatware from this thread (http://forum.xda-developers.com/r1-hd/development/prime-stock-rom-6-5-flashed-via-twrp-t3455532)? And is your phone rooted?
Unscedeo said:
By "Modified 6.6" do you mean the one without Amazon bloatware from this thread (http://forum.xda-developers.com/r1-hd/development/prime-stock-rom-6-5-flashed-via-twrp-t3455532)? And is your phone rooted?
Click to expand...
Click to collapse
Yes to both those questions.
Substratum for Blu R1 HD
exjinn said:
Yes to both those questions.
Click to expand...
Click to collapse
Yes, there is in fact a way to get Substratum working on your R1 HD.
1. Get the Substratum app from the Google Play Store
2. Launch the application, and give it superuser access
3. Download anything you want!
Important:
There is a bug though with Substratum on the R1 HD. If you do download a theme that changes your whole System UI (not just the navbars), your power menu will not open. The phone will just restart once you turn the screen off. To fix this I have installed NeoPowerMenu using the Xposed Module. If you don't have Xposed, you should look into getting it. If you don't want to get it, you can just look for other alternate menus on the Play Store.
Hope it helps!
Ive gotten it to work on the non-prime but not prime. Applying the theme fails
exjinn said:
Ive gotten it to work on the non-prime but not prime. Applying the theme fails
Click to expand...
Click to collapse
Hmm, that's interesting. I had the Prime version and had gotten it to work on that. What does it say when you try to apply the theme?
I get an error stating:
Theme compilation has completed
An error has occurred during overlay installation.
Gave up on 6.6 went back to OEM, everything works.
I managed to get substratum working on v17 by creating a directory named overlay in /system/vendor/
Edit only temporary success, unable to change themes.
After flashing a permissive boot.img, I am able to successfully install and change some themes in Substratum.
cyanix-tech said:
After flashing a permissive boot.img, I am able to successfully install and change some themes in Substratum.
Click to expand...
Click to collapse
Where/how I can find/make a permissive boot.img?
Alex19Gam said:
Where/how I can find/make a permissive boot.img?
Click to expand...
Click to collapse
Read this post
cyanix-tech said:
Read this post
Click to expand...
Click to collapse
Didn't work for me I checked in adb after flashing and it says Permissive, so what can i do?
I already installed busybox, the Adway works but the layers/substratum don't work
Hmmm. Have created the directory /system/vendor/overlay? Have you tried adb remount?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
cyanix-tech said:
Hmmm. Have created the directory /system/vendor/overlay? Have you tried adb remount?
Click to expand...
Click to collapse
Yes, I did all of that, I only can do r/w folders of system with the app Root Essentials, there I created the folder "overlay", and i tried "adb remount", it says success, but still with that I can't install themes
Alex19Gam said:
Yes, I did all of that, I only can do r/w folders of system with the app Root Essentials, there I created the folder "overlay", and i tried "adb remount", it says success, but still with that I can't install themes
Click to expand...
Click to collapse
If you already have busybox setup this suggestion might not get you anywhere. But try to replace the toolbox binary. I made recovery flash able package for it.
http://forum.xda-developers.com/showpost.php?p=70020045&postcount=1777
Try the v12-toolbox one.
I can't recommend that as I use BusyBox.
Well I will try, but I think I will back to v12 because the battery performance is much better, thanks for the help
Alex19Gam said:
Where/how I can find/make a permissive boot.img?
Click to expand...
Click to collapse
There is a link in Vampirefo's post here
Note that for some reason i couldn't use fastboot and flash it, i had to use Flashify to do so. But after that I could use Substratum (with a few other steps to get it running).
keredini said:
There is a link in Vampirefo's post here
Note that for some reason i couldn't use fastboot and flash it, i had to use Flashify to do so. But after that I could use Substratum (with a few other steps to get it running).
Click to expand...
Click to collapse
What were your other steps?
I do believe you need to do more than just put busybox binary into xbin. It needs to be linked to be useful. Easiest way to do it is with the busybox app from play store. Then from in the app select install. Then that should all work.
http://android.wonderhowto.com/how-to/android-basics-install-busybox-commands-0161945/
Hey guys, I am Redmi 3 user with Mokee 7.1 newest ROM and ARM64 7.1 Nano GApps and I also allowed Root for Apps and ADB in Dev. options..
I have newest AdAway app installed but it's not blocking the Ads, can you tell me why? :/
You have to have the latest version (3.2) and check enable systemless mode.
tripper22 said:
You have to have the latest version (3.2) and check enable systemless mode.
Click to expand...
Click to collapse
Sorry but I don't understand what you mean by "enable systemless mode" .. Where can I find it please?
Do I need SuperSu installed or smth..?
Adaway only works with root. You can select it under the three dots then preferences.
tripper22 said:
Adaway only works with root. You can select it under the three dots then preferences.
Click to expand...
Click to collapse
I wish you could be more specific Im not expert in this stuff.. :/ I just installed SuperSu latest version through TWRP but In the logs I see AdAway needs SuperSu Pro version :/
EDIT: Found it, thanks! Anyway still Im wondering why I cant use SuperSu... The Super Su pro requirement problem.. :/
spark995 said:
I wish you could be more specific Im not expert in this stuff.. :/ I just installed SuperSu latest version through TWRP but In the logs I see AdAway needs SuperSu Pro version :/
EDIT: Found it, thanks! Anyway still Im wondering why I cant use SuperSu... The Super Su pro requirement problem.. :/
Click to expand...
Click to collapse
You don't need the pro version. When you apply the adblocking it should ask for root permission. If not look for the supersu app on your phone and give adaway the permissions manually.
tripper22 said:
You don't need the pro version. When you apply the adblocking it should ask for root permission. If not look for the supersu app on your phone and give adaway the permissions manually.
Click to expand...
Click to collapse
Yes but when I am trying to give AdAway permission in SuperSu it doesn't work.. And when I check logs in SuperSu it says that I need Pro version
spark995 said:
Yes but when I am trying to give AdAway permission in SuperSu it doesn't work.. And when I check logs in SuperSu it says that I need Pro version
Click to expand...
Click to collapse
Reinstall using SuperSU from this post. https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
tripper22 said:
Reinstall using SuperSU from this post. https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Click to expand...
Click to collapse
Do I need to install dm verity? I mean lazyflasher-no-verity-opt-encrypt to use SuperSu?
I have no idea. I got my phone unlocked as soon as I got it. I'm using Mokee 6.0. If you are using a locked phone with Miui you will have to do some reading.
tripper22 said:
I have no idea. I got my phone unlocked as soon as I got it. I'm using Mokee 6.0. If you are using a locked phone with Miui you will have to do some reading.
Click to expand...
Click to collapse
No as I mentioned before I am using Mokee Open Source ROM..
As you can see in these pictures, I have enabled systemless mode in AdAway and now as you can see SuperSu is working but still when I am trying to play some video through YouTube app Adds still playing before the video
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You need Xposed to block ads in YouTube using a specific module. Xposed is not compatible with Nougat yet so you will continue to see ads on YouTube. You would have to downgrade to Mokee 6.0 Marshmallow to run Xposed.
Try to set system mount rewritable before downloading the host files in adaway. As for youtube, try to find some modded apk, not the official one.
Sent from my Redmi 3 using Tapatalk
khnoizer said:
Try to set system mount rewritable before downloading the host files in adaway. As for youtube, try to find some modded apk, not the official one.
Sent from my Redmi 3 using Tapatalk
Click to expand...
Click to collapse
How to do that? Recovery I suppose? If yes where to do that? Thanks for tip anyway
spark995 said:
How to do that? Recovery I suppose? Thanks for tip anyway
Click to expand...
Click to collapse
There are apps in play store that can mount system rewritable. Root essential for example.
Sent from my Redmi 3 using Tapatalk
khnoizer said:
There are apps in play store that can mount system rewritable. Root essential for example.
Sent from my Redmi 3 using Tapatalk
Click to expand...
Click to collapse
I use TWRP recovery and in Mount menu I unticked Mount system partion read-only ... Is it what you talking about ?
Yea, but after reboot I think you should still check if system still mounted r/w before execute the adaway.
Sent from my Redmi 3 using Tapatalk
you guys should use moadb(mother of all adblocking) mod. its not as aggressive as adaway app blocking all ads but it will get the job done for the most
jokerpappu said:
you guys should use moadb(mother of all adblocking) mod. its not as aggressive as adaway app blocking all ads but it will get the job done for the most
Click to expand...
Click to collapse
Link please?
khnoizer said:
Yea, but after reboot I think you should still check if system still mounted r/w before execute the adaway.
Sent from my Redmi 3 using Tapatalk
Click to expand...
Click to collapse
So in TWRP - Mount options I ticked system and unticked Mount system partion read-only and tried to open AdAway and install all again and restart but still there are Ads in my Kernel Adiutor, Youtube etc.. :/
spark995 said:
Link please?
So in TWRP - Mount options I ticked system and unticked Mount system partion read-only and tried to open AdAway and install all again and restart but still there are Ads in my Kernel Adiutor, Youtube etc.. :/
Click to expand...
Click to collapse
Install all and restart? Did you mean that adaway has already succeed in applying the host files? And there are still ads?
Sent from my Redmi 3 using Tapatalk