Has anyone managed to install adaway on any official rom?
The program fails when trying to apply the hosts file.
Yes i have rooted the phone and yes i have granted permisions with supersu to adaway.
revery0 said:
Has anyone managed to install adaway on any official rom?
The program fails when trying to apply the hosts file.
Yes i have rooted the phone and yes i have granted permisions with supersu to adaway.
Click to expand...
Click to collapse
I had it many times. AdAway is working very wele. Maybe you have not full rooted phone. Use MyRoM it is full rotted and AdAway is preinstalled and many others additions.
Hey...
First step is normal root. If you are ready you have to delete the immutable.list on system. Then you can use adaway.
Booth ways need busybox! Install it before you try to delete immutable.
Make it with my tool - easy update and adjust (http://forum.xda-developers.com/asc...eandadjust-t2941186/post56774286#post56774286) or make it manuelly with your PC and ADB.
adb shell
su
mount -o rw,remount /system
cd system
chattr -R -i *
rm –f /system/set_immutable.list
lsattr (to see if it's still there)
On my device with stock Rom it works well!
Thank you, it works like a charm!!!
revery0 said:
Thank you, it works like a charm!!!
Click to expand...
Click to collapse
No problem...
Wich way you have choosed?
Your script, cause command prompt returned an error when trying to change attributes, the reason was that adb hadnt have su permissions and for some reason supersu didnt prompt me to grant them. But with your script supersu prompt me to give adb su permissions and so i did, after that it worked.
Strange dont you think?
revery0 said:
Your util, cause command prompt returned an error when trying to change attributes, the reason was that wasanted su permiadbwasntions and suidnt proe to give it permissions, but when I tried your script then I got the prompt from supersu and itsusupersudidntsupersu..
Sounds strange dont you think?
Click to expand...
Click to collapse
I dont understand you complete. But my batch is working for you, thats fine
Auto correction on swype keyboard sucks.... I edited the previous post
revery0 said:
Auto correction on swype keyboard sucks.... I edited the previous post
Click to expand...
Click to collapse
yeah it corrects way u dont want it .. just turn off auto and leave options to pick..
Related
All others rooted phones have a message showed when an application asks root, why don't we have this on Tattoo ?
On Tattoo root permissions are always enabled
Ok, it's nice but we can't see which application ask root :/
Like Terminal Emulator, when you launch it, the shell is always in normal user "$", not in root :/
JoOoSs said:
Ok, it's nice but we can't see which application ask root :/
Like Terminal Emulator, when you launch it, the shell is always in normal user "$", not in root :/
Click to expand...
Click to collapse
This is true, but I dont know how, after isntalling 5faif ROM, terminal emulator shows me the #, id command shows me that I'm root.
I'm on stock ROM, this is the problem i think!
Anybody has SetCPU ?
The problem with this is that every application can obtain root without our knowledge.
It is a serious security flaw.
Not really. Android is pretty secure. Even if you get a brick from a Andirus (Virus + Android), it's a piece of cake to undo the damage.
Netbuster said:
This is true, but I dont know how, after isntalling 5faif ROM, terminal emulator shows me the #, id command shows me that I'm root.
Click to expand...
Click to collapse
Because that rom you've flashed contains custom boot.img by mainfram3 that gives to you root at startup and loads tattoo-hack.ko (partition r/w always mounted)
Coburn64 said:
Not really. Android is pretty secure. Even if you get a brick from a Andirus (Virus + Android), it's a piece of cake to undo the damage.
Click to expand...
Click to collapse
Actually i wasn't having viruses in mind. More like keyloggers and such. SU prompt wasn't invented for no reason...
I think the OP was asking about SuperUser.apk.
It's a modified su plus a service that asks for user intervention when a program calls /system/bin/su. It's nifty and it should be used by everyone.
Android apps are prevented from looking into other apps data. If su is readily available, a app can escalated it's privileges and steal your personal info, by reading data from other apps.
mainfram3 said:
I think the OP was asking about SuperUser.apk.
It's a modified su plus a service that asks for user intervention when a program calls /system/bin/su. It's nifty and it should be used by everyone.
Android apps are prevented from looking into other apps data. If su is readily available, a app can escalated it's privileges and steal your personal info, by reading data from other apps.
Click to expand...
Click to collapse
Exactly my point.
MoDaCo Custom ROM 1 includes Superuser apk for root access.
P
Anyone know how to fix Superuser Permissions manually?
I have Tattoo with rooted boot.img (mainfram3)
I pushed su into /system/bin/
Made chmod 4577 /system/bin/su
Pushed superuser.apk from Modaco Rom to /system/app/
Restart sure...
SuperUser Permissions can be executed (list is clear)
But any app doesn't send request to Superuser Permissions.
What i could forget?
Finally, I solved it partially.
Sure, i have rooted boot.img
I extracted from Modaco Custom ROM for Tattoo:
su
Superuser.apk
copied su to: /system/bin/su
copied Superuser.apk to: /system/app
run in terminal: chmod 4577 /system/bin/su
restarted and everything works fine now... Superuser Permissions shows all root-requests, Titanium Backup works, other root-things works too
But i notice, that su-binary from Modaco ROM is about 34-36 kb, but
su-binary from guide of getting root is about 80-85 kb.
1-2 months ago we faced with difference in size of su. We choosed bigger su in case, what it can run "flash_image", smaller su can't run.
But maybe it fixed already? I did not test it yet.
Thanks @5[Strogino]
I was trying to use Titanium today to back up my apps but it didn't work.
lukic said:
Thanks @5[Strogino]
I was trying to use Titanium today to back up my apps but it didn't work.
Click to expand...
Click to collapse
What exactly wrote TB?
Did you download busybox via TB?
I don't remember exactly.
It did ask me to download busybox and I did that, but still it didn't work.
I'm rooted with SuperSU 2.79 systemless on OOS 4.1.0 and I can't get permission to write on /system.
I tried using ES FIle Explorer and the option keeps changing to RO. I also tried via recovery. Root permissions are granted and It's properly root.
Any clues?
belumira said:
I'm rooted with SuperSU 2.79 systemless on OOS 4.1.0 and I can't get permission to write on /system.
I tried using ES FIle Explorer and the option keeps changing to RO. I also tried via recovery. Root permissions are granted and It's properly root.
Any clues?
Click to expand...
Click to collapse
I had the same issue. I don't remember what I did. Try uninstalling super su from the app and then install it again.
Migdilu said:
I had the same issue. I don't remember what I did. Try uninstalling super su from the app and then install it again.
Click to expand...
Click to collapse
Did that, I even clean flashed OOS again nothing seems to be working.
belumira said:
I'm rooted with SuperSU 2.79 systemless on OOS 4.1.0 and I can't get permission to write on /system.
I tried using ES FIle Explorer and the option keeps changing to RO. I also tried via recovery. Root permissions are granted and It's properly root.
Any clues?
Click to expand...
Click to collapse
I also had problem with ES File Explorer while writing to system. Try solid Explorer. It's better
Vaibhunk786 said:
I also had problem with ES File Explorer while writing to system. Try solid Explorer. It's better
Click to expand...
Click to collapse
Still nothing. For some reason permissions won't change.
You have systemless root?
If yes I think you can only modify data Partition. Maybe you need a magisk module?
Remove superSU and just go with Magisk. It works much better than SuperSU ever will. It's easily removable and won't adjust partition permissions, including system. Make sure you mount system in twrp before flashing any root access zip file as well. It helps prevent problems like this.
Fix To Grant ES File Explorer SuperSU Access Using Terminal Emulator
Start Terminal Emulator. Type su.
ENTER EXACTLY LIKE THIS: echo "BINDSYSTEMXBIN=true" >> /data/.supersu
Spaces.......................................................................................... ^....^.........
Make a backup first incase ****e goes south... This has worked for me on a couple of devices.
Standard disclaimer... Yada...
I have the same problem.
jhill110 said:
Fix To Grant ES File Explorer SuperSU Access Using Terminal Emulator
Start Terminal Emulator. Type su.
ENTER EXACTLY LIKE THIS: echo "BINDSYSTEMXBIN=true" >> /data/.supersu
Spaces.......................................................................................... ^....^.........
Make a backup first incase ****e goes south... This has worked for me on a couple of devices.
Standard disclaimer... Yada...
Click to expand...
Click to collapse
Sorry but I dont understand what I have to write, I understand type su
and type echo "BINDSYSTEMXBIN=true" >> /data/.supersu
but whats mean:
Spaces.......................................................................................... ^....^.........
Mean: ^ ^
doesnt mean anything? :crying::crying:
Hi, long story short, I want to make some apps system apps with Link2SD.
I tried using LO14 or some other LO14 based rom and just can't. I read som ewhere that it may be because I have no permissions to write on the system folder. I tried starting TWRP wizard again and setting it to be able to write with no success.
Any help?
I am rooted with magisk working just fine.
thanks!
groggycl said:
Hi, long story short, I want to make some apps system apps with Link2SD.
I tried using LO14 or some other LO14 based rom and just can't. I read som ewhere that it may be because I have no permissions to write on the system folder. I tried starting TWRP wizard again and setting it to be able to write with no success.
Any help?
I am rooted with magisk working just fine.
thanks!
Click to expand...
Click to collapse
As I've seen, Some apps don't work well with other SU except for SuperSU. Get rooted using superSU, everything should work just fine. You can always Uninstall and go back to magisk once you're done.
mhrajib said:
As I've seen, Some apps don't work well with other SU except for SuperSU. Get rooted using superSU, everything should work just fine. You can always Uninstall and go back to magisk once you're done.
Click to expand...
Click to collapse
But should I delete magisk, unroot and root again with super su?
Or is it as simple as installing supersu or something?
groggycl said:
But should I delete magisk, unroot and root again with super su?
Or is it as simple as installing supersu or something?
Click to expand...
Click to collapse
It's better to follow the procedure you mentioned Uninstall magisk, install supersu then install magisk again... But only flashing superSU zip will also work I guess. You can give it a try. I've done it once I guess
mhrajib said:
It's better to follow the procedure you mentioned Uninstall magisk, install supersu then install magisk again... But only flashing superSU zip will also work I guess. You can give it a try. I've done it once I guess
Click to expand...
Click to collapse
I managed to install supersu but anyways wasn't able to get the /system partition writable. Used many guides and even apps that should do it with superuser permissions and nothing. Just cant.
Any help?
groggycl said:
I managed to install supersu but anyways wasn't able to get the /system partition writable. Used many guides and even apps that should do it with superuser permissions and nothing. Just cant.
Any help?
Click to expand...
Click to collapse
What kind of error do you get?? Can you do other operations through link2sd??
mhrajib said:
What kind of error do you get?? Can you do other operations through link2sd??
Click to expand...
Click to collapse
the error is the following..
mount: '/dev/block/bootdevice/by-name/system'->':/system': Device or resource busy
Thats the error. Tried with titanium backup pro version and it gets stuck "PROCESING" the thing... It uninstall the app I want to move to system app, but then never finishes processing..
I also used a app called mount "/system ro/rw". I grant it superuser permissions and when I hit the "mount /system rw" a message appears that says; "Your device might not be rooted or is it not compatible!"
groggycl said:
mount: '/dev/block/bootdevice/by-name/system'->':/system': Device or resource busy
Click to expand...
Click to collapse
Do this from terminal emulator (don't use GUI apps for things like this, they hide important errors most of the time):
Code:
$ su
# lsof /system
And watch for processes that hold the mountpoint.
Code:
# kill <that process id, one by one>
if you're sure they're not doing anything important, then try:
Code:
mount -o rw,remount /system
again.
P.S.: you might need to install BusyBox, I don't know if lsof is available out of the box.
leledumbo said:
Do this from terminal emulator (don't use GUI apps for things like this, they hide important errors most of the time):
Code:
$ su
# lsof /system
And watch for processes that hold the mountpoint.
Code:
# kill <that process id, one by one>
if you're sure they're not doing anything important, then try:
Code:
mount -o rw,remount /system
again.
P.S.: you might need to install BusyBox, I don't know if lsof is available out of the box.
Click to expand...
Click to collapse
I've installed busybox and when I try lsof /system it says "toybox: Unknown command lsof", is there any solution?
Anyone had any luck getting viper4android to work with Mate 10 Pro
I tried several methods but the driver does not install
Thanks
waiting for it
Tried several things like flashing Viper4android with pre-installed drivers, which did not work as the app tells me to install the drivers again but fails at busybox not found.
Bordo_Bereli51 said:
Tried several things like flashing Viper4android with pre-installed drivers, which did not work as the app tells me to install the drivers again but fails at busybox not found.
Click to expand...
Click to collapse
What recovery did you try flashing with?
I used the app FlashFire from Chainfire. You can find it on Play Store. Make sure when you flash something with that app, select mount system R/W
Bordo_Bereli51 said:
I used the app FlashFire from Chainfire. You can find it on Play Store. Make sure when you flash something with that app, select mount system R/W
Click to expand...
Click to collapse
Where do you get the option to select mount system R/W, once you start flashing?
vibrantliker said:
Where do you get the option to select mount system R/W, once you start flashing?
Click to expand...
Click to collapse
Yes, when you select the zip-file it will automatically show you some Misc-Options, where you can select to mount system read write.
No One else getting anywhere with this?
Bordo_Bereli51 said:
Yes, when you select the zip-file it will automatically show you some Misc-Options, where you can select to mount system read write.
Click to expand...
Click to collapse
I just tried flashing with flash fire and it looked like it went through fine but it's nowhere to be found on phone after the reboot.
vibrantliker said:
I just tried flashing with flash fire and it looked like it went through fine but it's nowhere to be found on phone after the reboot.
Click to expand...
Click to collapse
Did you select Mount System R/W? Otherwise it will not work. If its still not working, then I do not know why. For me it worked but viper4android asked my always for installing busybox even though it is installed.
Bordo_Bereli51 said:
Did you select Mount System R/W? Otherwise it will not work. If its still not working, then I do not know why. For me it worked but viper4android asked my always for installing busybox even though it is installed.
Click to expand...
Click to collapse
I did Mount System R/W
vibrantliker said:
I just tried flashing with flash fire and it looked like it went through fine but it's nowhere to be found on phone after the reboot.
Click to expand...
Click to collapse
If you haven't removed Verity on system it would remove what was flashed on reboot. You can do this in /vendor/etc/fstab.kirin970
And you should remove verity off of the other partitions as well.
Etoerh way it probably won't work. I manually installed everything yesterday, including driver. This worked fine on Mate 9 Nougat without even installing driver.
And make sure you have busybox. I can't remember if it had busybox or su as a hardcoded path... I have su in /sbin/ and busybox applets symlinked to /sbin/ from su.d. Still no go. :/
I'll try some more later.
And a question, permissive is usually required, can you guys type in a terminal: setenforce 0
Or setenforce permissive?
I get invalid parameter, so Huawei might've tightened security.
With P10plus oreo setenforce do not work in terminal. I try to install viper4android too.
Gesendet von meinem VKY-L29 mit Tapatalk
ante0 said:
If you haven't removed Verity on system it would remove what was flashed on reboot. You can do this in /vendor/etc/fstab.kirin970
And you should remove verity off of the other partitions as well.
Etoerh way it probably won't work. I manually installed everything yesterday, including driver. This worked fine on Mate 9 Nougat without even installing driver.
And make sure you have busybox. I can't remember if it had busybox or su as a hardcoded path... I have su in /sbin/ and busybox applets symlinked to /sbin/ from su.d. Still no go. :/
I'll try some more later.
And a question, permissive is usually required, can you guys type in a terminal: setenforce 0
Or setenforce permissive?
I get invalid parameter, so Huawei might've tightened security.
Click to expand...
Click to collapse
Don't know why but Viper is having a hard time with Oreo. No problems on any phone with Nougat.
has anyone tried https://forum.xda-developers.com/nexus-6p/general/guide-installing-viper4android-t3250579 ?
Hello.
This game (GIGANTIC X) Me detects the access root Magisk, the hidden through "Magisk Hide" and when I restart it again detects me again and does not work.
https://play.google.com/store/apps/details?id=com.ActionSquare.GiganticX
D-Mak said:
Hello.
This game (GIGANTIC X) Me detects the access root Magisk, the hidden through "Magisk Hide" and when I restart it again detects me again and does not work.
https://play.google.com/store/apps/details?id=com.ActionSquare.GiganticX
Click to expand...
Click to collapse
Have you tried the v19.0 Beta ?
lahceneamine said:
Have you tried the v19.0 Beta ?
Click to expand...
Click to collapse
I just tried the V19.0 and the same thing happens.
any root-using apps installed or magisk.zip still in storage?
D-Mak said:
I just tried the V19.0 and the same thing happens.
Click to expand...
Click to collapse
Do you pass SAFETYNET with v19.0 ? If not, there's something wrong in your config.
Oh... it's using Lockin Company's Liapp(https://liapp.lockincomp.com/ )...
It's not a problem like misconfig since it detects Magisk itself. Liapp updates frequently to apply new root (especially Magisk) detection methods, so it's hard to bypass it.
(Magisk 17.3+ bypasses 5.0.0, 18.2+ bypasses 5.0.1, but 5.0.2+ cannot be bypassed currently.)
same here.cantplay it on root device,well that sucks.Im not gonna sacrifice my magisk for this game,not worth it
I made a bypass script for it (and all other apps using Liapp and UDS detection method)!
Download it on https://github.com/Ingan121/UDSBypass/blob/master/udsbypass and run 'su -c sh /sdcard/Download/udsbypass com.ActionSquare.GiganticX/com.epicgames.ue4.GameActivity'. Make sure you added this app to MagiskHide.
Ingan121 said:
I made a bypass script for it (and all other apps using Liapp and UDS detection method)!
Download it on https://github.com/Ingan121/UDSBypass/blob/master/udsbypass and run 'su -c sh /sdcard/Download/udsbypass com.ActionSquare.GiganticX/com.epicgames.ue4.GameActivity'. Make sure you added this app to MagiskHide.
Click to expand...
Click to collapse
Thanks! How do i use this script? i tried in terminal but it keep saying no such file or directory
Predatorhaze said:
Thanks! How do i use this script? i tried in terminal but it keep saying no such file or directory
Click to expand...
Click to collapse
Did you download it in Download folder? Then it should be started by 'sh /sdcard/Download/udsbypass' (without quotes).
Also, you can copy it to /sbin, chmod 755, and then just run 'udsbypass'.
Ingan121 said:
Did you download it in Download folder? Then it should be started by 'sh /sdcard/Download/udsbypass' (without quotes).
Also, you can copy it to /sbin, chmod 755, and then just run 'udsbypass'.
Click to expand...
Click to collapse
I copied the text and made a text file saved .sh..or do I something wrong here
Predatorhaze said:
I copied the text and made a text file saved .sh..or do I something wrong here
Click to expand...
Click to collapse
sh /sdcard/path/to/udsbypass.sh
Ingan121 said:
sh /sdcard/path/to/udsbypass.sh
Click to expand...
Click to collapse
I am a noob with this,I don't get it.Cant get it to work.I think will uninstall magisk
Predatorhaze said:
I am a noob with this,I don't get it.Cant get it to work.I think will uninstall magisk
Click to expand...
Click to collapse
Termux can't be used for this.
Use other terminal app.
Ingan121 said:
Termux can't be used for this.
Use other terminal app.
Click to expand...
Click to collapse
It can be used if you adjust the script to check for /sbin in $PATH and then add it if it isn't already there.
Or adjust the script to use the absolute paths to the Magisk binary, but that is a lot less elegant and won't work if the paths change.
Ingan121 said:
Termux can't be used for this.
Use other terminal app.
Click to expand...
Click to collapse
well then i try material terminal.
by the way im running pie gsi.
How is the game btw? is it good? bored fast?
Predatorhaze said:
well then i try material terminal.
by the way im running pie gsi.
How is the game btw? is it good? bored fast?
Click to expand...
Click to collapse
I didn't play it, just deleted immediately after succeeding to bypass.
Alright.i really want to play this game but i cant get this bypass to work.Can someone explain more clear steps?
Ingan121 said:
Did you download it in Download folder? Then it should be started by 'sh /sdcard/Download/udsbypass' (without quotes).
Also, you can copy it to /sbin, chmod 755, and then just run 'udsbypass'.
Click to expand...
Click to collapse
I managed to run the script by putting the file in /sbin but the game is still detecting root
Ingan121 said:
I didn't play it, just deleted immediately after succeeding to bypass.
Click to expand...
Click to collapse
can u explain with a short video the game has official release yesterday