Recently it has come out xposed framework by rovo89 for android N:
https://forum.xda-developers.com/showthread.php?t=3034811
Has anyone tried it on the p10 lite, with rom stock + recovery + root? or in some other device huawei with rom stock and emui 6?
Thanks in advance.
I've tried it and it works fine, but since I rooted my p10 and installed xposed my battery started to drain noticeably faster, so I went back to stock.
I use xposed with magisk v14 and no battery drain(I think)
Testing and work fine.
Some times, after reboot, xposed in disabled. Need run this attached script on init, in /su/su.d
mpiero11 said:
Testing and work fine.
Some times, after reboot, xposed in disabled. Need run this attached script on init, in /su/du.d
Click to expand...
Click to collapse
I get this too, but to fix I just untick all enabled modules in xposed, reboot, enable modules again and reboot again.
hayabusa2yk said:
I use xposed with magisk v14 and no battery drain(I think)
Click to expand...
Click to collapse
How did you install magisk?
plerohero said:
How did you install magisk?
Click to expand...
Click to collapse
Just flash in TWRP
sorry for my bad English
mpiero11 said:
Testing and work fine.
Some times, after reboot, xposed in disabled. Need run this attached script on init, in /su/su.d
Click to expand...
Click to collapse
I am facing the same problem and when I tried to use your solution its not working either.
I somehow able to found out the error (by using init.d scripts app):
Path is not correct for
/data/user_de/0/de.robv.android.xposed.installer/conf/enabled.modules.list
/data/user_de/0/de.robv.android.xposed.installer/conf/modules.list
On checking the path appears to be correct. Then whats the issue here? Please guide.
My P10-Lite is rooted. So I can see the path actually exists in my phone's root folder.
Thanks
mzeeshan2 said:
I am facing the same problem and when I tried to use your solution its not working either.
I somehow able to found out the error (by using init.d scripts app):
Path is not correct for
/data/user_de/0/de.robv.android.xposed.installer/conf/enabled.modules.list
/data/user_de/0/de.robv.android.xposed.installer/conf/modules.list
On checking the path appears to be correct. Then whats the issue here? Please guide.
My P10-Lite is rooted. So I can see the path actually exists in my phone's root folder.
Thanks
Click to expand...
Click to collapse
Change permisions for .sh file, chmod 777 to script, reboot and enjoy.
No problems for my.
Related
Follow these steps and you will definitely get it working
1.Flash the latest Supersu.zip beta
2.Flash these files Check link here
3.Install app and enable it
4.It works
I wonder what changed with nougat in order to you'se this method?with MM and before the app was enough and just working well.
Midomad said:
I wonder what changed with nougat in order to you'se this method?with MM and before the app was enough and just working well.
Click to expand...
Click to collapse
Basically Nougat made harder to write system partition. That zip applies a workaround making the default hosts file (/system/etc/hosts) a symlink to another host file in a writable mountpoint (/su/etc/hosts). You can find more info here https://github.com/AdAway/AdAway/issues/770.
Midomad said:
I wonder what changed with nougat in order to you'se this method?with MM and before the app was enough and just working well.
Click to expand...
Click to collapse
It is the same issue as discussed here:
http://forum.xda-developers.com/nex...-to-unlock-tethering-nexus-5x-t3231301/page20
The workaround described above doesn't change /system (which would get error corrected back to original), but instead masks the file in /system with an alternate one during boot.
Thank you very much. It works like a charm.
Work also with SuperSU?
Skar3 said:
Work also with SuperSU?
Click to expand...
Click to collapse
Sure,why not?
Midomad said:
Sure,why not?
Click to expand...
Click to collapse
sorry, you're right, I misread Superuser
Am I mistaken, it's working for me without any trick? I am on nougat rooted stock.
Enviado desde mi Nexus 5X mediante Tapatalk
maluus said:
Am I mistaken, it's working for me without any trick? I am on nougat rooted stock.
Click to expand...
Click to collapse
Without this "trick" AdAway It doesn't show an error or fail... but it doesn't works. Try pinging any "supposed to be blocked" url. You may realized it's not blocked anymore.
I attempted this but it does not appear to have installed. I flashed via chainfire. Any ideas?
Thanks, this is much appreciated!
VivaErBetis said:
Without this "trick" AdAway It doesn't show an error or fail... but it doesn't works. Try pinging any "supposed to be blocked" url. You may realized it's not blocked anymore.
Click to expand...
Click to collapse
Yes, this "trick" essentially writes the hosts file to another location, and creates a symlink to it. This way it doesn't need to write to the /system/ directory.
There is a one-line command you can run in terminal emulator that lets you write to /system, but you need to run it each time you reboot, and it's a bit of a nuisance to do so. This lets Adaway work each time without the necessity of a terminal command.
daver68 said:
There is a one-line command you can run in terminal emulator that lets you write to /system, but you need to run it each time you reboot, and it's a bit of a nuisance to do so. This lets Adaway work each time without the necessity of a terminal command.
Click to expand...
Click to collapse
Just an FYI, if you install SuperSU you can write to system and it will stick. You wouldn't need to do anything each boot in that case.
sfhub said:
Just an FYI, if you install SuperSU you can write to system and it will stick. You wouldn't need to do anything each boot in that case.
Click to expand...
Click to collapse
Strange, this is not my experience. I'm running PureNexus (7) and SuperSU Pro, and Adaway does not write to the system. It errors out, until I re-mount /system in terminal emulator
VivaErBetis said:
Without this "trick" AdAway It doesn't show an error or fail... but it doesn't works. Try pinging any "supposed to be blocked" url. You may realized it's not blocked anymore.
Click to expand...
Click to collapse
I didn't try any specific url but it seems like working on their test site.
Enviado desde mi Pixel XL mediante Tapatalk
daver68 said:
Strange, this is not my experience. I'm running PureNexus (7) and SuperSU Pro, and Adaway does not write to the system. It errors out, until I re-mount /system in terminal emulator
Click to expand...
Click to collapse
That is a different problem than the one on stock Noguat then.
On stock without dm-verity disabled, the kernel will use forward error correction to "fix" you changes (ie data corruption) and replace with original. Basically you make the changes and they don't show up.
Nougat , flashed and no app installed, I downloaded adway from official website and working.
Link to original thread just for sure: http://forum.xda-developers.com/showthread.php?t=2190753
Please create Update for Android O.
AdAway works fine on O; no change from Nougat.
Hi guys. I just installed and rooted (normal root) Android Nougat. Well, adaway seems not to be working, when i tap "Download and Apply" it says "Copy failed - Copying of host file failed". I think it's because the system files does not have the "write" permission =\
I also installed busybox
Any suggestion?
darkalex97 said:
Hi guys. I just installed and rooted (normal root) Android Nougat. Well, adaway seems not to be working, when i tap "Download and Apply" it says "Copy failed - Copying of host file failed". I think it's because the system files does not have the "write" permission =\
I also installed busybox
Any suggestion?
Click to expand...
Click to collapse
Search man, search....
google adaway on nougat:
https://www.google.com/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=adaway on nougat
OR
https://www.google.com/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=adaway+on+android+n
Somewhat relating to you but just a question really.....
Whenever you need to find something out like information about something or the definition of a word online, whether it's ebonics or whatever, do you Google it?
Well, all the links in that page are purple, this means that i have already do it.
Already tried others' suggestions. (do the thing with the terminal etc..)
Here (https://www.reddit.com/r/Nexus6P/comments/4k0ghq/adaway/d6j8ygu?context=3) he says to flash it if I have systemless root. Does it work also with normal root?
Flash systemless root file in AdAway thread and it will work.
therock3181 said:
Flash systemless root file in AdAway thread and it will work.
Click to expand...
Click to collapse
Thank you it worked!
darkalex97 said:
Thank you it worked!
Click to expand...
Click to collapse
No problem.
I managed to have magisk and magiskhide working sucessfully, with some manual tricks and workarounds
There is a bug in f2fs that prevents /data/magisk.img to me mounted writable, so the tweek is just moving that file to the /cache partition, which is ext4 and creating a symlink to the original file.
So the steps for a working magisk is.
- Unlock your bootloader
- Install Twrp
- Flash magisk without mounting data partition and boot once.
- Reboot to recovery and open terminal (advanced)
- move magisk.img to /cache partition, changing name ( example: mv /data/magisk.img /cache/magisk_2.img)
- Create a symlink between_files ( ln -s /cache/magisk_2.img /data/magisk.img)
Would be nice if anybody can try to reproduce.
Ah, so there is a way after all. I gather it works normally afterwards, with phh superuser, xposed and everything? I'm willing to try and reproduce your steps if so, maybe tweak the installer script so it does this automagically as well.
lpchaim said:
Ah, so there is a way after all. I gather it works normally afterwards, with phh superuser, xposed and everything? I'm willing to try and reproduce your steps if so, maybe tweak the installer script so it does this automagically as well.
Click to expand...
Click to collapse
I did not installed Xposed because I wanted to pass SafetyNet, but I cannot think a reason why it shouldn't work.
jblancoperez said:
I did not installed Xposed because I wanted to pass SafetyNet, but I cannot think a reason why it shouldn't work.
Click to expand...
Click to collapse
Right. I think I'll try this out today and see how things turn out. As for SafetyNet, I though the unlocked bootloader alone was enough reason for it not to work, is this only for some models?
Update: So, @jblancoperez, I've reproduced your steps and Magisk Manager tells me it's installed but root isn't activated and it doesn't let me do anything else as a result.
Things to have a look,
Please confirm in the terminal if /magisk is mounted.
Go back to TWRP terminal and also confirm if the symlink is OK.
Nice to get the output from /cache/magisk.log
It took me a while to have everything right, doing it on TWRP is not the easiest places to move things around.
So, an update. Your method just wouldn't work for me at all, no matter how many times I tried. What worked was following the first part only, as in unmounting data and then flashing Magisk afterwards. I've tried Xposed and Viper4Android; they worked, but both did have to be flashed through twrp as opposed to Magisk Manager, which would throw an error. Not sure if that's on them or on this particular method. I should mention though that SafetyNet wouldn't pass even before xposed and with the hiding settings, not sure why.
You may want to try the kernel where the f2fs bug is fixed, which may be the cause when Magisk hide is not working which would cause Safetynet to fail.
Is there anyone wanting to test brand new Magisk 11.0 if it runs fine on Moto Z Play? With and/or without that f2fs fix?
tag68 said:
Is there anyone wanting to test brand new Magisk 11.0 if it runs fine on Moto Z Play? With and/or without that f2fs fix?
Click to expand...
Click to collapse
I got bootloop when I install magiks 11.0.
Do you have a logfile of that action in /cache or /cache/recovery which we could show in the Magisk thread?
I was able to upgrade the 10.2 installation.
Will try a new clean installation on the weekend with the f2fs fixed kernel.
I think I got why my procedure is not working for other people. Please try to copy the image instead of moving with the flags preserving de selinux attributes.
jblancoperez said:
Please try to copy the image instead of moving with the flags preserving de selinux attributes.
Click to expand...
Click to collapse
Keeping attributes when copying or moving is what my guide regarding timestamp is about. It's not that easy using Android.
tag68 said:
Keeping attributes when copying or moving is what my guide regarding timestamp is about. It's not that easy using Android.
Click to expand...
Click to collapse
I used the same cp commands @topjohnwu used in the magisk script, cp -afc orig dest.
jblancoperez said:
I used the same cp commands @topjohnwu used in the magisk script, cp -afc orig dest.
Click to expand...
Click to collapse
cp -a tries to copy attributes including timestamps. But it only succeeds if you are currently running as root.
Since OTA updates NXT-L09CxxxB580+ for our devices is out and because of the fixes in the kernel, we are now able to root our device using Magisk.
This is a step-by-step guide leading you throughout the process and also stating the pros of using Magisk over using SuperSU.
News:
09/11/2017
- Magisk was updated to v14 which adds more root hiding mechanisms and also more devices compatibility.
07/18/2017
- Magisk was updated to version 13.3 and will once again pass SafetyNet without any issues
- To update, just open MagiskManager and press Download and Install (if you are new to Magisk, just follow guide below)
07/14/2017
- Google updated SafetyNet and Magisk devices will not pass it
Pros of using Magisk over SuperSU:
Automatic updates
Does not break OTA updates
Does not break SafetyNet (you will be able to use AndroidPay, play Pokemon Go, install Netflix from Google Play and use apps requiring SafetyNet pass)
Ability to install modules from the repository (much like xposed modules)
Before installation:
Unlock your bootloader
Make sure you have stock boot.img
Make sure you are on B580+ as Magisk cannot be installed on older versions
Installation:
Flash this recovery in fastboot: https://forum.xda-developers.com/mate-8/orig-development/twrp-t3576364
Flash latest Magisk in TWRP recovery: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Boot into system
Check your apps for Magisk Manager
[OPTIONAL] In the magisk manager, you can check if you pass SafetyNet
Troubleshooting:
Magisk Manager was not installed
- Open the Magisk.zip, inside open common folder and install magisk.apk
SafetyNet does not pass
- First try disabling and enabling Magisk Hide in the Magisk Manager
- If above does not help open stock Huawei dialer, dial *#*#2846579#*#*, tap Background settings, tap LOG settings, check all checkboxes, open Magisk Manager and disable and enable Magisk Hide
Supported devices:
All NXT-L29 B580+ devices
All NXT-L09 B580+ devices
All other Mate 8 versions with B580+
Basically any other device as Magisk is not device dependent (works with like 95% of all devices, as long as the device's kernel supports loop mount and few other things)
My Magisk Modules for Mate 8:
[Magisk] Official Huawei Automatic Call Recorder
Hope this will help you guys!
car nikolaj
. I recommend this app to anyone who want for the root acces. :good::good::good::good::good::good::good:
Does this method and the TWRP attached work on B585?
Thanks.
Just installed B581 via OTA and decided to give Magisk a try. I was able to get it installed by following your instructions but I'm not able to pass SafetyNet due to CTS profile mismatch. Any idea?
xxlap1xx said:
Just installed B581 via OTA and decided to give Magisk a try. I was able to get it installed by following your instructions but I'm not able to pass SafetyNet due to CTS profile mismatch. Any idea?
Click to expand...
Click to collapse
Same here. CTS profile mismatch
Fresh B581
Thanks for this, have not tried it yet but if I do, and I for some reason wish to unroot, how does one do that?
necc0 said:
Does this method and the TWRP attached work on B585?
Thanks.
Click to expand...
Click to collapse
Yes
xxlap1xx said:
Just installed B581 via OTA and decided to give Magisk a try. I was able to get it installed by following your instructions but I'm not able to pass SafetyNet due to CTS profile mismatch. Any idea?
Click to expand...
Click to collapse
sZx1 said:
Same here. CTS profile mismatch
Fresh B581
Click to expand...
Click to collapse
Did you installed Xposed? Check Magisk manager settings if you have Magisk hide enabled.
shestolemyusrname said:
Thanks for this, have not tried it yet but if I do, and I for some reason wish to unroot, how does one do that?
Click to expand...
Click to collapse
You just press uninstall button in Magisk manager
Boosik said:
Yes
Did you installed Xposed? Check Magisk manager settings if you have Magisk hide enabled.
You just press uninstall button in Magisk manager
Click to expand...
Click to collapse
When I boot into TWRP for the first time, should I keep Ready Only or Swipe to Allow Modifications?
Can you help me??
Magisk installed -all its ok, but im trying copy one folder and set attributes to system\app folder, but unfortunatelly - cannot write to system\app.... (i must install HwCallRecorder)
I tested Total commander and Root explorer
thx
Boosik said:
Yes
Did you installed Xposed? Check Magisk manager settings if you have Magisk hide enabled.
You just press uninstall button in Magisk manager
Click to expand...
Click to collapse
Nope, freshly installed B581. I read something about SafetyNet was being updated so that's probably why.
Sent from my HUAWEI NXT-L29 using Tapatalk
woji said:
Can you help me??
Magisk installed -all its ok, but im trying copy one folder and set attributes to system\app folder, but unfortunatelly - cannot write to system\app.... (i must install HwCallRecorder)
I tested Total commander and Root explorer
thx
Click to expand...
Click to collapse
I have the same issues as woji, and also can't write hosts file for AdAway.
Seemingly the simple reasons for rooting aren't available in systemless root, or we have errors preventing this?
Hilton.Swart said:
I have the same issues as woji, and also can't write hosts file for AdAway.
Seemingly the simple reasons for rooting aren't available in systemless root, or we have errors preventing this?
Click to expand...
Click to collapse
Same, I had issues with adaway not being to write hosts files using magisk as well. I went back and flashed SuperSU and the problem is gone.
Sent from my HUAWEI NXT-L29 using Tapatalk
Hilton.Swart said:
I have the same issues as woji, and also can't write hosts file for AdAway.
Seemingly the simple reasons for rooting aren't available in systemless root, or we have errors preventing this?
Click to expand...
Click to collapse
xxlap1xx said:
Same, I had issues with adaway not being to write hosts files using magisk as well. I went back and flashed SuperSU and the problem is gone.
Sent from my HUAWEI NXT-L29 using Tapatalk
Click to expand...
Click to collapse
Open Magisk Settings and enable Systemless hosts data.
Systemless root means you can't directly edit /system partition, because editing it voids SafetyNet. Magisk uses Magic Mount to systemlessly replace /system files and folders on-the-fly without actually modifying the original ones. All you need is appropriate modules from magisk manager "Downloads" tab.
woji said:
Can you help me??
Magisk installed -all its ok, but im trying copy one folder and set attributes to system\app folder, but unfortunatelly - cannot write to system\app.... (i must install HwCallRecorder)
I tested Total commander and Root explorer
thx
Click to expand...
Click to collapse
Try installing it as user app and use App Systemizer module in magisk manager to convert it to system app.
xxlap1xx said:
Nope, freshly installed B581. I read something about SafetyNet was being updated so that's probably why.
Sent from my HUAWEI NXT-L29 using Tapatalk
Click to expand...
Click to collapse
Yea you are right, I have it working, but the process is a bit tedious. We better wait for new Magisk version, where it should be fixed.
shestolemyusrname said:
When I boot into TWRP for the first time, should I keep Ready Only or Swipe to Allow Modifications?
Click to expand...
Click to collapse
Keep it Read Only.
Boosik said:
Open Magisk Settings and enable Systemless hosts data.
Click to expand...
Click to collapse
This was my first logical step when hosts would not apply, I've changed the settings numerous times and the host simply will not write.
Tried Magisk for the ability to keep SafetyNet intact, but it still fails any tests. So I think I'll follow xxlap1xx, and try Magisk at another time.
Boosik said:
Yes
Did you installed Xposed? Check Magisk manager settings if you have Magisk hide enabled.
You just press uninstall button in Magisk manager
Click to expand...
Click to collapse
No Xposed installed. Hide was enabled in settings and in hide tab as well.
Reading about SafetyNet looks like unlocked bootloader can be a problem.
V13 beta same results.
Probably have to wait for workaround
Thanks.
Hilton.Swart said:
This was my first logical step when hosts would not apply, I've changed the settings numerous times and the host simply will not write.
Tried Magisk for the ability to keep SafetyNet intact, but it still fails any tests. So I think I'll follow xxlap1xx, and try Magisk at another time.
Click to expand...
Click to collapse
sZx1 said:
No Xposed installed. Hide was enabled in settings and in hide tab as well.
Reading about SafetyNet looks like unlocked bootloader can be a problem.
V13 beta same results.
Probably have to wait for workaround
Thanks.
Click to expand...
Click to collapse
I already know how to workaround it, but the process is a bit unfriendly to normal users (requires terminal emulator). We better wait for new Magisk beta.
Boosik said:
Yes
Did you installed Xposed? Check Magisk manager settings if you have Magisk hide enabled.
You just press uninstall button in Magisk manager
Click to expand...
Click to collapse
Boosik said:
I already know how to workaround it, but the process is a bit unfriendly to normal users (requires terminal emulator). We better wait for new Magisk beta.
Click to expand...
Click to collapse
Can you, please, share. I'm pretty handy with terminal and willing to experiment. Worst - have to return to stock.
Thanks
Just safety fix module gonna work, every other module gonna bugged.
To install modules you have to wait the f2f2 fixed kernel.
Guys after some testing on magisk i discover that have some modules that work with this method, but carefully because some modules like app systemizer gives a bootloop. So do a backup.
Click to expand...
Click to collapse
For your security make a backup of boot partition first
Click to expand...
Click to collapse
Hi everyone, I decided to do a tutorial, to explain how to get safetynet working while the kernel with f2f2 fixed is not released
{Unlocked bootloader is needed}
{stock rom is needed too}
{TWRP is needed too}
1. you have to reboot in TWRP and install Magisk 14 and reboot (is needed to reboot to create all files) and reboot again into TWRP
2. to work the correct function of magisk you need to do the trick maked by jbblancoperez
3.you have open terminal on TWRP and move the file
mv /data/magisk.img /cache/magisk2.img
Click to expand...
Click to collapse
4.after you have to symlink the files
ln -s /cache/magisk2.img /data/magisk.img
Click to expand...
Click to collapse
5.boot system and check on magisk manager if SafetyNet works if it not works ( install the safety net universal fix) (link above)
6. If you had to install the SafetyNet Fix after works you can unistall the module because its gonna work without it
If anybody have a problem with magisk hide on 14 version just install the 13.3 version and use root explorer to copy the .core folder to sdcard and then install 14 version and put .core folder in appropriate place]
The directory of . core folder is /magisk/.core
Click to expand...
Click to collapse
Links
SafetyNet Fix (for the 14 magisk version you need to install the zip with hotfix, which is in same post of last beta but is in the end of the post) https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
Magisk : https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Worked like a charm, thank you!
It worked perfectly. Just one thing, you had a syntax error in step 6:
Its '/cache/...' not '/cacve/..."
Anyway, thank you very much. I needed it :good::fingers-crossed:
flapcon said:
It worked perfectly. Just one thing, you had a syntax error in step 6:
Its '/cache/...' not '/cacve/..."
Anyway, thank you very much. I needed it :good::fingers-crossed:
Click to expand...
Click to collapse
I have not seen it ! thanks
Guys after some testing on magisk i discover that have some modules that work with this method, but carefully because some modules like app systemizer gives a bootloop. So do a backup.
Safetynet still fail. Could you explain how to get Safetynet pass? THanks
Magsik dont work with Xposed. Install Magisk 14.3 it will work perfect without doing anything, i am on Security Patch August.
Nchls said:
Safetynet still fail. Could you explain how to get Safetynet pass? THanks
Click to expand...
Click to collapse
Did you move the image to cache and symlink with the correct comands? Check if you don't have sure, try the process again. And if you don't get the safety net working try the module.
I just applied the hotfix plus the "mv and ln" to my moto z play, I passed the entire safetynet check for the first time ever and Google Pay just works.
Thanks a million!!
p.s. I am running magisk 14.3 beta IIRC.
The trick with symlink worked. I can pass SafetyNet and HideRoot on my Moto Z play (7.1.1 Nougat - august security patch).
PS: there is an extra space before symlink parameter. it should be like this:
ln -s /cache/magisk2.img /data/magisk.img
Click to expand...
Click to collapse
razorsbk said:
The trick with symlink worked. I can pass SafetyNet and HideRoot on my Moto Z play (7.1.1 Nougat - august security patch).
PS: there is an extra space before symlink parameter. it should be like this:
Click to expand...
Click to collapse
Thanks! I gonna correct!!
Can I use the latest version of magisk (15.3)? It doesn't seem to work when i try to use Superuser functions in Automate
GiantPlaidSquirrel said:
Can I use the latest version of magisk (15.3)? It doesn't seem to work when i try to use Superuser functions in Automate
Click to expand...
Click to collapse
I relock my bootloader so i can't test or try another way. Sorry about that, but i don't know if something can be done to work