Related
I know it's a known bug that if the data partition is in f2fs.
And if anyone roots any custom rom which doesn't have internal root.
Device unroot itself after sometime after reboot.
Is there any workaround for this?
I'm using tesla 3.4 beta and pico open gapps and supersu 2.79
SuperSU is not compatible with f2fs. Try phh suprsuser, it worls.
If you still want SuperSU try installing it in systemmode after fresh install or switch to ext4.
aadityarulez said:
SuperSU is not compatible with f2fs. Try phh suprsuser, it worls.
If you still want SuperSU try installing it in systemmode after fresh install or switch to ext4.
Click to expand...
Click to collapse
Wut... I've been using SuperSU with f2fs for the last couple months and haven't had any issues
sidhg said:
I know it's a known bug that if the data partition is in f2fs.
And if anyone roots any custom rom which doesn't have internal root.
Device unroot itself after sometime after reboot.
Is there any workaround for this?
I'm using tesla 3.4 beta and pico open gapps and supersu 2.79
Click to expand...
Click to collapse
Use system mode super su, sr4 worked great for me for months on arter97 rom all f2fs
aadityarulez said:
SuperSU is not compatible with f2fs. Try phh suprsuser, it worls.
If you still want SuperSU try installing it in systemmode after fresh install or switch to ext4.
Click to expand...
Click to collapse
Dupleshwar said:
Use system mode super su, sr4 worked great for me for months on arter97 rom all f2fs
Click to expand...
Click to collapse
Well, system mode supersu seems to work fine.
Thank you guys
Edit : Nope root is gone again this bug is really annoying
sidhg said:
Well, system mode supersu seems to work fine.
Thank you guys
Click to expand...
Click to collapse
Happy to help. Cheers.
sidhg said:
Well, system mode supersu seems to work fine.
Thank you guys
Edit : Nope root is gone again this bug is really annoying
Click to expand...
Click to collapse
Could you try with phh superuser ?
aadityarulez said:
Could you try with phh superuser ?
Click to expand...
Click to collapse
I dirty Flashed the Rom.. Then Flashed phh superuser
It solved the issue
Thanks
Phh works nicely, there are still a few issues with mount, but they will get fixed eventually. But I found myself going back to exfat, prefer SuperSU for now.
Can't install SuperSU on Huawei Watch 1 "Patching sepolicy ---Failure, aborting"
I apologize if this is a noob question. I'm no stranger to modding Android devices; only new to modding Wear devices, and unfortunately information about rooting this watch is so sparse (understandably) and I couldn't find anyone with the same issue when searching. So like the title says, I can't get SuperSU installed on my Hwatch running AW 2.0. When I try to install SuperSU via TWRP, it gets stuck when trying to patch sepolicy.
Do I need a custom kernel for this? Is there one with no modifications other than the sepolicy? Or is there a way to change the sepolicy on the stock kernel. Between the guides I've read and WinDroid Toolkit, nothing has mentioned needing to do anything else to allow flashing SuperSU, but I can't think of what else would be the cause of the issue and I suppose things could have changed since those guides and Windroid were written.
I kind of want to avoid custom kernels as they almost always have issues in my experience with running them on phones (no offense to any kernel devs out there) and I can't deal with that on something simple as a watch. I just want this rooted mostly so I can test out underclocking and powersave governor when needing some extra battery time and so the next time I flash or upgrade my phone, I don't have to wipe the watch.
Any help will be greatly appreciated. And if I must install a custom kernel, I would love recommendations on the most reliable and/or closest to stock one.
For me, WinDroid Toolkit doesn't work for rooting Android Wear 2.0. I am on AW2.0 with the stock kernel and I have rooted the device using Magisk v13.2. Magisk Manager works on Android Wear (even though it may be hard to use on a round screen), but SuperSU (app) crashes when I launch the app. All you have to do to install Magisk is to flash the latest Magisk installer in TWRP and sideload the latest Magisk Manager using adb. You can download Magisk here. I have tried SuperSU, but I would get an every time I try to flash the latest SuperSU zip.
Tristan Phan said:
For me, WinDroid Toolkit doesn't work for rooting Android Wear 2.0. I am on AW2.0 with the stock kernel and I have rooted the device using Magisk v13.2. Magisk Manager works on Android Wear (even though it may be hard to use on a round screen), but SuperSU (app) crashes when I launch the app. All you have to do to install Magisk is to flash the latest Magisk installer in TWRP and sideload the latest Magisk Manager using adb. You can download Magisk here. I have tried SuperSU, but I would get an error every time I try to flash the latest SuperSU zip.
Click to expand...
Click to collapse
Thank you! Sounds like we encountered the same issue when flashing SuperSU. I had thought about trying Magisk, but wasn't sure if it would cause some issues on Wear. Thanks to your positive report, though, I'm going to try it out when I get home later. :good:
neonixxx said:
Thank you! Sounds like we encountered the same issue when flashing SuperSU. I had thought about trying Magisk, but wasn't sure if it would cause some issues on Wear. Thanks to your positive report, though, I'm going to try it out when I get home later. :good:
Click to expand...
Click to collapse
I'd like to know if it works for you. ?
Tristan Phan said:
I'd like to know if it works for you.
Click to expand...
Click to collapse
It worked! I was unable to sideload Magisk Manager, though, but that's fine. I'm just stuck on v5.0.5 which works just fine for handling root requests.
That's great! The only real difference between Magisk Manager v5.0.6 and v5.0.5 is that v5.0.6 fixes a crash when downloading modules from the repo, so you shouldn't be that affected. If you want any modules, you can just download them from XDA or something and flash it in TWRP.
Tristan Phan said:
That's great! The only real difference between Magisk Manager v5.0.6 and v5.0.5 is that v5.0.6 fixes a crash when downloading modules from the repo, so you shouldn't be that affected. If you want any modules, you can just download them from XDA or something and flash it in TWRP.
Click to expand...
Click to collapse
Yeah, that's why I'm not bothering with it. I don't feel a need for any modules on my watch at the moment Thanks again for tipping me off that Magisk would work.
neonixxx said:
Yeah, that's why I'm not bothering with it. I don't feel a need for any modules on my watch at the moment Thanks again for tipping me off that Magisk would work.
Click to expand...
Click to collapse
Just saying (sorry to bother), but Magisk v13.3 came out and fixed SafetyNet bypass. If you want, you can update by flashing Magisk-v13.3 by flashing it in TWRP without needing to uninstall the previous version. Installing this should also update Magisk Manager to v5.1.0.
Tristan Phan said:
Just saying (sorry to bother), but Magisk v13.3 came out and fixed SafetyNet bypass. If you want, you can update by flashing Magisk-v13.3 by flashing it in TWRP without needing to uninstall the previous version. Installing this should also update Magisk Manager to v5.1.0.
Click to expand...
Click to collapse
No worries, haha. Yeah I already updated on my phone. Thought about updating the watch, but too lazy at the moment :silly: since I don't really need to pass SafetyNet on my watch for anything. Probably will do it later on.
I'm thinking that the reason that you couldn't install Magisk Manager v5.0.6 was that it was already installed by the Magisk-v13.2 zip and ADB wasn't able to install over the existing APK, but I'm still a noob so I have no idea.
Tristan Phan said:
I'm thinking that the reason that you couldn't install Magisk Manager v5.0.6 was that it was already installed by the Magisk-v13.2 zip and ADB wasn't able to install over the existing APK, but I'm still a noob so I have no idea.
Click to expand...
Click to collapse
Check the adb install switches in adb help to solve that. Use the -r or -d switch.
Code:
adb install [-lrtsd] <file>
- push this package file to the device and install it
(-l: forward lock application)
(-r: replace existing application)
(-t: allow test packages)
(-s: install application on sdcard)
(-d: allow version code downgrade)
Hey,
I've created a small magisk module, with that you can use the Argument Reality function inside the Google Camera.
It works on AOSP 8.0 Beta and Stable, maybe it also works on nougat.
When you want to test it on other devices than the Mi A1, please don't forget to make a backup even if bootloop and such things are very unlikely.
Wehen you have a device where it also works you are allowed to create a thread, only condition link me and very important Arnova8G2 because without his work it would not be possible.
Installation instructions:
The modules can easily flashed inside the Magisk Manager or with TWRP.
To get it fully working you have to flash both modules
Downloads:
All in one version:
https://forum.xda-developers.com/mi...re-modded-google-camera-t3720269/post75090632
ARcore Basic files:
https://drive.google.com/folderview?id=1C3pylJpeK9bc93L56v1JWrjJNXnNbU06
ARcore Basic files V2:
https://drive.google.com/file/d/16YyJN1PTDMZ5WPQ_F2VFZuyTJlAOmAyi/view?usp=sharing
Apps Module:
https://drive.google.com/file/d/12t5jRzlEM0tz1mkyKqjwu0RS8yZ37IeY/view?usp=sharing
Apps Module V2:
https://drive.google.com/file/d/19rtu2nUAcH2WKCBbGbm2F75uXsfwKXt4/view?usp=sharing
Do not thank me, just thank him @Arnova8G2
Thanks for your contribution! Will try as soon as I get the oreo beta working on my phone.
Unable to flash via magisk
Unable to flash via TWRP nor Magisk, maybe cause data partition is encripted
fosco_ said:
Unable to flash via TWRP nor Magisk, maybe cause data partition is encripted
Click to expand...
Click to collapse
My storage is also encrypted and it works.
AnnePunk said:
My storage is also encrypted and it works.
Click to expand...
Click to collapse
What version of Magisk and Magisk Manager?
fosco_ said:
What version of Magisk and Magisk Manager?
Click to expand...
Click to collapse
Latest Magisk Beta: v14.5 (code: 1456)
Magisk Manager: v5.4.3
AnnePunk said:
Latest Magisk Beta: v14.5 (code: 1456)
Magisk Manager: v5.4.3
Click to expand...
Click to collapse
I can't get Magisk Manager to install any module, it says something like /data/magisk not setup....
Yash98 said:
I can't get Magisk Manager to install any module, it says something like /data/magisk not setup....
Click to expand...
Click to collapse
Had the same bug, reinstall magisk with the Magisk Manager, reboot and try again.
I can flash other zip.. But these two can't be flashed on magisk
Rakibboss said:
I can flash other zip.. But these two can't be flashed on magisk
Click to expand...
Click to collapse
Hmm for me it works
Whatever, i managed to do it via this method
https://forum.xda-developers.com/redmi-note-3/themes/mod-updated-6-11-17-google-camera-hdr-t3701190
Yash98 said:
I can't get Magisk Manager to install any module, it says something like /data/magisk not setup....
Click to expand...
Click to collapse
"I can flash other zip.. But these two can't be flashed on magisk"
You must create an folder "magiskmanager" on internal sd card...then it works
I will try for Android Nougat. Thank you
It doesn't work on nougat .i tried
Hello, install without problems, but I would like to know which Gcam application exactly should I I must use, Thanks.
anyone got it working ?
jeneb11 said:
anyone got it working ?
Click to expand...
Click to collapse
Not working on Redmi Note 4 stock global miui9 with camera2 api enabled. Tried with both magisk, and TWRP, AR Stickers stoped.
how can you install magisk on oreo? when i booted to the twrp, it asks for my pattern and when i draw the pattern, it says pattern failed. so please tell me how can you install magisk on oreo
jigs4wkiller said:
Hmm for me it works
Click to expand...
Click to collapse
Which magisk version??
i installed busybox from the playstore and it doesnt seem to want to install. I'm currently on twrp 3.2.1, magisk 15 and magisk manager 15.
equlizer said:
i installed busybox from the playstore and it doesnt seem to want to install. I'm currently on twrp 3.2.1, magisk 15 and magisk manager 15.
Click to expand...
Click to collapse
Use the Magisk Module Busy Box for Android NDK. Works great.
felosisman said:
Use the Magisk Module Busy Box for Android NDK. Works great.
Click to expand...
Click to collapse
Where do i find it? thx
EDIT: NVM flashed it in magisk. Is it still normal to get the "theres an internal problem........"?
equlizer said:
Where do i find it? thx
Click to expand...
Click to collapse
Open Magisk Manager, go-to Downloads, find and download "BusyBox for Android NDK 1.27.2", reboot and profit.
Noob question but what is BusyBox and what's it's purpose
mackentosh said:
Noob question but what is BusyBox and what's it's purpose
Click to expand...
Click to collapse
Busybox allows programs to perform actions on your phone using Linux commands. So some apps require it to run some commands and wont work without it.
equlizer said:
Where do i find it? thx
EDIT: NVM flashed it in magisk. Is it still normal to get the "theres an internal problem........"?
Click to expand...
Click to collapse
You shouldn't be getting that error anymore if you're using the latest Magisk release. He released version 15.0(1500) a couple days ago, but that was actually fixed in the last beta 14.6.
You would have to reflash your Kernel boot and dtbo and repatch though with the new version. I just used the Magisk Uninstaller script in TWRP, flashed the latest zip of flash Kernel then latest Magisk in TWRP and all good.
This is actually relatively simple, and has worked with every update on Oreo.
Use at your own risk, while it's unlikely something like this will brick your device, I take no responsibility if anything happens. Always know how to get yourself out of a bootloop. The APKs and Magisk module posted by others should be fine, however feel free to extract the APK yourself from the Pixel 2/3 factory images.
Download the APK here (or extract it from the Pixel 2/XL's P DP1 factory image), install TWRP and Magisk (I used v16). Use a file manager with root permissions, I used ES file manager. Copy Framework-res__auto_generated.apk from here to System/Vendor/Overlay/ and overwrite (you could also copy the original somewhere if you wanted a backup). SystemUI will crash or the phone will reboot. Due to this, apps will constantly be crashing, to fix this, open up the file manager again and set the permissions correctly.
(Incase anyone is curious why I don't have a navbar, I removed it with a buildprop edit, I'm a bit nervous about burn in, and that way I can avoid it. Also, AOD moves around slowly)
Based on what I've seen with the leaks from the Pixel 3, it may be this simple to get the AOD with a wallpaper when we get the file from the Pixel 3 XL. But then again, I'm not a developer, so maybe not. But I'm glad this is still working for now!
APKs are posted by various users here, once I get access to my PC I'll be sure to post them in chronological order every time a update is put out.
Magisk module here https:/forum.xda-developers.com/pixel/themes/mod-display-enabler-magisk-module-t3857034
But doesn't magisk not work?
muppetmaster916 said:
But doesn't magisk not work?
Click to expand...
Click to collapse
That's what I thought, it seems it's just a Magisk manager issue, root works but not in all apps. Worked fine with a file manager for me.
Doesn't work for me. Everytime I navigate to root folder, it comes up blank
dictionary said:
Doesn't work for me. Everytime I navigate to root folder, it comes up blank
Click to expand...
Click to collapse
Did you install Magisk via TWRP? Only other thing I can think of, is going back to 8.1, rooting and giving the file manager root permissions, then flashing P (as a update, without wiping data) then flashing Magisk again. Then opening the file manager, it will already be able to use root permissions. It seems like it's just the Magisk app that is broken, not root itself.
YTSec said:
Did you install Magisk via TWRP? Only other thing I can think of, is going back to 8.1, rooting and giving the file manager root permissions, then flashing Oreo (as a update, without wiping data) then flashing Magisk again. Then opening the file manager, it will already be able to use root permissions. It seems like it's just the Magisk app that is broken, not root itself.
Click to expand...
Click to collapse
Yeah. It's not so serious to do all that work lol. I'm sure a real solution will come soon, but thank you
What's the battery hit? Negligible?
nadiros said:
What's the battery hit? Negligible?
Click to expand...
Click to collapse
It's just a disclaimer they have, I have been using AOD since early December with no battery issues.
Tried this on Android O March 2018, extracted the file from Pixel 2 XL factory images, but I'm not getting the option in setting.
Do I have to do anything else other than copy file and set permissions?
Edit: Read your other thread, and did it through TWRP file manager as I don't have root. I guess it only works using a file manager with root while booted.
Sent from my Pixel XL using Tapatalk
Couldn't get Android P to boot after this. Anyone installed on DP1 ?
nadiros said:
Couldn't get Android P to boot after this. Anyone installed on DP1 ?
Click to expand...
Click to collapse
The system isn't booting or you are having other issues?
Any way to enable this without root? Like for Oreo installing the Substratum and Andromeda plugin?
nadiros said:
Couldn't get Android P to boot after this. Anyone installed on DP1 ?
Click to expand...
Click to collapse
Yeah I'm up and running. I moved the file, rebooted, got into ES file (after a few tries) and was able to fix the permissions. I'm on Dev preview with magisk and a few modules + this mod now.
muppetmaster916 said:
Yeah I'm up and running. I moved the file, rebooted, got into ES file (after a few tries) and was able to fix the permissions. I'm on Dev preview with magisk and a few modules + this mod now.
Click to expand...
Click to collapse
Great, glad it worked out. I'm having issues with Magisk though, no modules seem to work. Did you do anything different to get them working?
jidccruz said:
Any way to enable this without root? Like for Oreo installing the Substratum and Andromeda plugin?
Click to expand...
Click to collapse
I don't think so, unfortunately. I tried via TWRP and nothing stuck until I rooted.
YTSec said:
I don't think so, unfortunately. I tried via TWRP and nothing stuck until I rooted.
Click to expand...
Click to collapse
Will try your workaround. Hopefully it works. I'm already in Android P? Any way to install TWRP and Magisk without clearing data?
jidccruz said:
Will try your workaround. Hopefully it works. I'm already in Android P? Any way to install TWRP and Magisk without clearing data?
Click to expand...
Click to collapse
As long as you have a unlocked bootloader (which you should if you are on the first P preview, even though it is insanely stable) it won't wipe your device. Magisk was actually updated to work with P.
YTSec said:
As long as you have a unlocked bootloader (which you should if you are on the first P preview, even though it is insanely stable) it won't wipe your device. Magisk was actually updated to work with P.
Click to expand...
Click to collapse
Thanks for the info. Will try it now!
Magisk has just been updated to support Android P
YTSec said:
Great, glad it worked out. I'm having issues with Magisk though, no modules seem to work. Did you do anything different to get them working?
Click to expand...
Click to collapse
Choose download rather than install, within magisk, then use twrp to flash.