VPNDialogs fix for Nightbreed813's 6.0.1 Slim Rom - Desire 626 General

For those who prefer nightbreed813's 6.0.1 slim rom version, I uploaded 601VPNDIALOGSFIX.zip to fix the issue with authorizing VPN clients, but first you have to create the directory /system/priv-app/VpnDialogs in Root Explorer or any other root filesystem browser, then reboot to TWRP recovery and flash the zip.

Related

Sideload apk

Just updated the nexus player to marshmallow. Flashed the alternative boot.img by Chainfire and also flashed twrp.
How can I sideload the root zip file that needs to be flashed in twrp? The new version of ES Explorer doesn't find the NAS connected to the player and the root zip is saved onto a folder on the NAS.

[Root] Phoenix OS x86/x64 v2.1.0 (20 July) Rooted Images

Hey guys, here are the rooted and original system images for you to download. I don't like this release because Google Play Services doesn't want to update, but I made rooted images just in case a solution to this problem is found.
Instructions:
Download the correct correct system.img.7z file provided in the Download section and extract it
Install Phoenix OS.
Go to C:\Phoenix OS (or wherever your Phoenix OS installation is) and replace the system.img file with the one you just downloaded
Boot into Phoenix OS and finish the system initialization wizard.
Install the latest version of SuperSU by going to the Play Store and clicking the Update button.
-(Optional) If you for some reason cannot use the Play Store, you can find SuperSU on the official thread. Download the flashable zip, extract Superuser.apk from the common folder, and install it in Phoenix OS by opening the .apk file with the default file manager that comes with the OS. You don't have to do this step if SuperSU updated successfully in the Play Store.
Update the binary by choosing Normal and your Phoenix OS should now be fully rooted
Optional/Recommended:
Download Google Play Services v11.0.55 APK (Google Drive | APKMirror)
This will fix the "Google Play Services" can't be installed Error code: -501 message.
Download:
Phoenix OS x86 v2.1.0 Rooted Image + backups
https://drive.google.com/open?id=0B_UTWXKFnZoNdGVzOXRZdDFVTXc
Phoenix OS x64 v2.1.0 Rooted Image + backups
https://drive.google.com/open?id=0B_UTWXKFnZoNNU5jcHZjV0haUHc
Download Phoenix OS v2.1.0 here (original thread):
http://bbs.phoenixstudio.org/en/showthread.php?tid=6511
History:
N/A

Exploring TWRP and root directory bugged?

I'm running stock Moto G4 plus firmware (Android 7.0, Nougat) on my XT1644 with TWRP 3.1.1-0 recovery, ElementalX 1.04 kernel and root with SuperSU 2.82. I'm not sure how relevant the android version is because I've noticed the same thing on every build of stock android version with root that I've tried so far.
When I go into the TWRP directory within android using a file explorer (I've tried Root Browser File Manager, ES File Explorer, Root Explorer), I can never see any of the contents of the TWRP folder. I can get into the TWRP folder, but it is just empty. The only way I can get access to the contents of the TWRP folder is to mount the phone's drive in TWRP. Also, when an OTA update downloads, I go to the cache folder in root to look for it but it is not there. I'm guessing it's the same issue that's preventing me from seeing the OTA file. However, I can't access the root directory through TWRP's mounting so I cannot grab the OTA file at all.
Is this the intended behaviour? I can see the contents of these folders on my Nexus 5. Is there any way to change/fix this?

OP5 upgraded to Android 10 and rooted with Magisk, system changes don't stick

Hi,
Just upgraded my OP5 to Android 10 official stable version. Rooted successfully with Magisk 20.4
Now I'm trying to do some changes to the system folder but they revert back when I reboot.
1- Trying to replace the emoji with another ttf file, as I always did in Pie but the file gets reverted upon restart.
2- Trying to apply hosts file for ad blocking, same issue the file gets reverted as soon as I restart.
it looks like my system partition is reverting itself for some reason, does anyone know why this happens and how to make the changes stick?
PS: I don't want to enable (Systemless hosts in Magisk) because I'm planning to unroot after doing these changes.
thanks..
medo159 said:
Hi,
Just upgraded my OP5 to Android 10 official stable version. Rooted successfully with Magisk 20.4
Now I'm trying to do some changes to the system folder but they revert back when I reboot.
1- Trying to replace the emoji with another ttf file, as I always did in Pie but the file gets reverted upon restart.
2- Trying to apply hosts file for ad blocking, same issue the file gets reverted as soon as I restart.
it looks like my system partition is reverting itself for some reason, does anyone know why this happens and how to make the changes stick?
PS: I don't want to enable (Systemless hosts in Magisk) because I'm planning to unroot after doing these changes.
thanks..
Click to expand...
Click to collapse
Just forget to change hosts file manualy, use the better Adbloacker Rootless, Blokada
medo159 said:
QUOTE
Click to expand...
Click to collapse
Hi Mate,
Ensure to give proper permissions as follows: rw-r--r-- (0644) to the file. If it is a folder, the permissions are: rwxr-xr-x (0755)
medo159 said:
Hi,
Just upgraded my OP5 to Android 10 official stable version. Rooted successfully with Magisk 20.4
Now I'm trying to do some changes to the system folder but they revert back when I reboot.
1- Trying to replace the emoji with another ttf file, as I always did in Pie but the file gets reverted upon restart.
2- Trying to apply hosts file for ad blocking, same issue the file gets reverted as soon as I restart.
it looks like my system partition is reverting itself for some reason, does anyone know why this happens and how to make the changes stick?
PS: I don't want to enable (Systemless hosts in Magisk) because I'm planning to unroot after doing these changes.
thanks..
Click to expand...
Click to collapse
You can't mount the system partition as rw directly in Android 10. Here's a thread by topjohnwu (slightly technical, but give it a read) on why: https://twitter.com/topjohnwu/status/1259039809361739776

Magisk 22101 (22.+) not detected by Manager, but SU still working on Android 6.0 Marshmallow with Samsung Note 4 SM-N910F TouchWiz,

- Target image: /dev/block/
- Device platform: armeabi-v7a
- Installing: 22.0 (22000)
! Unable to check signature
! Installation failed
this is the message inside of magisk manager when i try to install with recommended way. but i have root after flashing zip not showing anything else in the app not magisk hide not modules etc
ant solution?
I do not quite understand what you want, but I think I understand some of it. You want to install a new version of magic and can not do it from the magic app, it was properly understood. If it was I can help. Try using another file explorer if you need to patch for it, or download the zip file and install it from recovery.
i have tried all when flashing the latest magisk the manager doesnt recognize the version but i have root rights nor appears su hide modules etc in the manager
Im running a 6.0 Custom ROM and noticed Magisk isnt working well but does give me SU access. I you need to run an earler version of Magisk (16?) in order to run it smoothly.

Categories

Resources