Related
I flashed CM when it first arrived and encrypted my phone. How do I unencrypt it again? Thanks in advance.
jdub251 said:
I flashed CM when it first arrived and encrypted my phone. How do I unencrypt it again? Thanks in advance.
Click to expand...
Click to collapse
I don't think you can decrypt without formatting the area.
jdub251 said:
I flashed CM when it first arrived and encrypted my phone. How do I unencrypt it again? Thanks in advance.
Click to expand...
Click to collapse
You need a kernel that does not force encryption. I believe ex kernel is an option. I run benzo rom which does not force encryption. Make sure yo backup any data you want to keep. The process should go as follows:
Flash rom
Flash gapps
Flash kernel
Select wipe
Format data
Reboot Recovery
Reboot system
n.halepat said:
You need a kernel that does not force encryption. I believe ex kernel is an option. I run benzo rom which does not force encryption. Make sure yo backup any data you want to keep. The process should go as follows:
Flash rom
Flash gapps
Flash kernel
Select wipe
Format data
Reboot Recovery
Reboot system
Click to expand...
Click to collapse
Ok! Will try this! Thanks! I believe this will work!
Sent from my Nexus 6P using Tapatalk
jdub251 said:
Ok! Will try this! Thanks! I believe this will work!
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Just make sure you format data, not wipe.
n.halepat said:
You need a kernel that does not force encryption. I believe ex kernel is an option. I run benzo rom which does not force encryption. Make sure yo backup any data you want to keep. The process should go as follows:
Flash rom
Flash gapps
Flash kernel
Select wipe
Format data
Reboot Recovery
Reboot system
Click to expand...
Click to collapse
Heisenberg said:
Just make sure you format data, not wipe.
Click to expand...
Click to collapse
Have you noticed any speed difference after decrypting?
Also is it possible to decrypt using a kernel that doesn't force encryption and then switch to a kernel that may not have that? I would still have to turn encryption on via Settings -> Encrypt is what I'm thinking.
exSD said:
Have you noticed any speed difference after decrypting?
Also is it possible to decrypt using a kernel that doesn't force encryption and then switch to a kernel that may not have that? I would still have to turn encryption on via Settings -> Encrypt is what I'm thinking.
Click to expand...
Click to collapse
I've seen some testing regarding encrypted vs decrypted, the performance gain is so small it's negligible. If you switch to a kernel that forces encryption, it'll encrypt automatically on boot.
Heisenberg said:
I've seen some testing regarding encrypted vs decrypted, the performance gain is so small it's negligible. If you switch to a kernel that forces encryption, it'll encrypt automatically on boot.
Click to expand...
Click to collapse
Have you read http://www.anandtech.com/show/9820/the-google-nexus-6p-review ?
The difference in storage speeds is drastic.
Encrypted: 75.7MB/s seq read, 40.6MB/s seq write, 7.4MB/s rand read, 1.0MB/s rand write.
Unencrypted: 179.7MB/s seq read, 52MB/s seq write, 14.73MB/s rand read, 6.3MB/s rand write.
exSD said:
Have you read http://www.anandtech.com/show/9820/the-google-nexus-6p-review ?
The difference in storage speeds is drastic.
Encrypted: 75.7MB/s seq read, 40.6MB/s seq write, 7.4MB/s rand read, 1.0MB/s rand write.
Unencrypted: 179.7MB/s seq read, 52MB/s seq write, 14.73MB/s rand read, 6.3MB/s rand write.
Click to expand...
Click to collapse
No I hadn't seen that particular article. I guess the results must vary, the results I saw showed performance gains in the order of less than a percent.
Heisenberg said:
No I hadn't seen that particular article. I guess the results must vary, the results I saw showed performance gains in the order of less than a percent.
Click to expand...
Click to collapse
In terms of power consumption, the CPU is processing an extra step for every instruction it has passed to it. I would think that with the inefficient chip the 810 already is that this would impact battery life more than real world opening apps type speed.
I think I'll decrypt to see if I can notice any power differences.
so if i copy all my files to my PC before following these steps, I would still be able to use them afterwards? ie pictures, sounds, images, and titanium backup files? i'm wanting to try benzorom and it sounds like it doesn't get along with encryption very well.
glhelinski said:
so if i copy all my files to my PC before following these steps, I would still be able to use them afterwards? ie pictures, sounds, images, and titanium backup files? i'm wanting to try benzorom and it sounds like it doesn't get along with encryption very well.
Click to expand...
Click to collapse
Yeah, as long as you back up everything to your PC you can just transfer them all back to your phone after you do this.
if i do a nandroid backup (from TWRP) of an encrypted system then create backup of /sdcard, wipe userdata than restore /sdcard and restore backup with a non forcing kernel will i get a decrypted device with all data restored?
answering my own question:
- twrp backup data
- copy /sdcard to pc
- fastboot format userdata
- copy from pc to /sdcard
- restore data in twrp
are the needed steps to decrypt without losing any data.
A bit of a necro, so I apologize for that.
@ratson: I am attempting to do exactly what you have mentioned here, although I am not an experienced user. Can I get some clarification on the following:
TWRP backup: Done. It keeps wanting to restrict my permissions on this folder, but I was able to get it off the device (Nexus6p Huawei) and backed up onto my PC.
copy the /sdcard to the PC. Man, what a problem I am having with this. First off, when it gets to a folder called /kick it fails because it says it's not a directory. It does this on some long hex named file that actually isn't a directory, but it seems to want to recognize it as one anyway, and then fail the pull because of this.
So, I cut the entire /kick folder through ES Explorer, and temporarily pasted it into my dropbox. Restarted the adb pull through my shell. It seemed to be working ok, until it got to the TWRP folder. While backing that up (I already did this, but it is still on the device as I only copied it. Should I be deleting this before backing up the rest of the /sdcard?) it fails because it says permission denied when it tries to pull some of the backup files.
At this point I've restarted the pull, and tried different things for several hours. Before I continue to bang my head against the wall, I'd like to get some advice.
How do you pull the /sdcard to your pc? what method? what commands? do you do it from TWRP recovery mode, from the system? Pretend I'm an android toddler (I kind of am). Is there anyway to not start from scratch every time the pull fails? Is there ways to pre-empt the failures?
Once this is complete, when you restore the data, can you please also list the commands for that?
I greatly appreciate your, or anyone elses help to reads this.
Thanks,
For the record:
Make sure battery is charged!
On PC: adb reboot recovery
In TWRP: select BACKUP, select DATA, swipe
When finished
On PC:
mkdir DATA-BACKUP
adb pull /data/media/0/TWRP/BACKUPS
fastboot reboot bootloader
fastboot format userdata
On Phone:
arrow down to select recovery, power to enter
cd DATA-BACKUP
adb push * /data/media/TWRP/BACKUPS
When finished
In TWRP: Restore, select the backup, swipe
rchtk said:
For the record:
Make sure battery is charged!
On PC: adb reboot recovery
In TWRP: select BACKUP, select DATA, swipe
When finished
On PC:
mkdir DATA-BACKUP
adb pull /data/media/0/TWRP/BACKUPS
fastboot reboot bootloader
fastboot format userdata
On Phone:
arrow down to select recovery, power to enter
cd DATA-BACKUP
adb push * /data/media/TWRP/BACKUPS
When finished
In TWRP: Restore, select the backup, swipe
Click to expand...
Click to collapse
This will backup and restore the nandroid backup, but not the sdcard, correct? Or am i getting it wrong?
Kalamos said:
This will backup and restore the nandroid backup, but not the sdcard, correct? Or am i getting it wrong?
Click to expand...
Click to collapse
It will restore what you backed up: the complete data partition: app settings, contacts, media,.. All your datas..
rchtk said:
It will restore what you backed up: the complete data partition: app settings, contacts, media,.. All your datas..
Click to expand...
Click to collapse
I was under the impression that a nandroid backup didnnot include apps, user settings, etc. Otherwise, what is the use of Titanium Backup? Perhaps I'm jist confused.
I'm curious if 7.1 still has a huge performance hit with encrypted partitions.
Anyone know of a good app for checking performance of the data partition? All I've seen is internal/external storage.
Thanks.
Hi all,
has anyone been able to do this? Following the guide here, no longer works for Android N. The phone boots, but ignores all changes to system. How do I modify both build.prop and hosts? It seems that there are now possibly two system partitions?
Thanks!
Same issue on Nexus 5X
No answer on this? How is it that nobody else seems to be having this issue?
What I've done
It looks to me like everyone has moved to systemless and the /system partition cannot be adequately modified in this way anymore.
Maybe this will help others:
I was modifying the system directory for two reasons: 1. modify /system/etc/hosts to remove ads and modifying build.prop to increase lcd.density. I found that here are the alternatives for each:
Removing Ads
Using something similar to AdAway_systemless_hosts_v2.zip (google it for a copy) and modifying the hosts file in that zip file to be the one I use (and rezipping, deploying on the Android device). This basically mounts over /system/etc/hosts with a custom hosts file instead of actually modifying the system specific hosts file which is no longer writable.
The alternative is to use Netguard which routes non https network traffic through a private VPN where you can block ads according to a hosts file. This seems to work OK, but I have noticed that websites seem to take longer to load.
Modifying lcd.density
You can use the same trick as AdAway_systemless_hosts_v2.zip uses, but modify it to also mount a modified copy of build.prop. Alternatively just use the Android N Display settings that are small (what I did anyhow).
I have been able to edit build.prop and still maintain systemless root.
Sent from my Nexus 6P using XDA-Developers mobile app
I was able to modify my system partition; by installing busy box to /su/xbin and running "su busybox mount -o rw,remount system" (no quotes) in material terminal with root
ArminasAnarion said:
I was able to modify my system partition; by installing busy box to /su/xbin and running "su busybox mount -o rw,remount system" (no quotes) in material terminal with root
Click to expand...
Click to collapse
Have you been able to do this with simply fastboot boot <twrp-image>, mounting system in rw mode and modifying it? I did that as I didn't want to root the phone, and while it looks like it did the write, it does not affect the system partition that is used by the phone after boot. I think there are two system partitions, and twrp mounts only one in rw mode. It does seem like it may be possible to do what you say using adb though after the phone is fully booted up. I'll try that!
dontblinkwatchout said:
Have you been able to do this with simply fastboot boot <twrp-image>, mounting system in rw mode and modifying it? I did that as I didn't want to root the phone, and while it looks like it did the write, it does not affect the system partition that is used by the phone after boot. I think there are two system partitions, and twrp mounts only one in rw mode. It does seem like it may be possible to do what you say using adb though after the phone is fully booted up. I'll try that!
Click to expand...
Click to collapse
I had the same problem. I don't want to root but I do make a few changes to my /system partition through adb in recovery such as the hosts file and some font files (namely the Emoji font file). I had modified stock boot image to not enforce encryption. I would boot back up into the system and couldn't see any changes made. The only thing I found that worked was installing a custom kernel (I use ElementalX). After that, changes I made to /system in TWRP were reflected in the OS. I don't know enough about kernel development to understand why on (mostly) stock kernel my changes couldn't be seen but on a custom one they were.
I never had this "problem" prior to Nougat.
Same issue here. Something has changed with how this is handled in Nougat.
I don't want to root just to overwrite the hosts file...
I'll keep debugging but my capability in this is definitely limited!
I use a similar approach as described in the OP's linked guide except I use my own recovery image that I compiled as an engineering build from source, and I am also experiencing the same behavior. Modifying the hosts file seems to have no impact on the system though the changes persist. Comparing the host file I installed and the host file from the latest Nexus 5X image with 'ls -lZ' the SELinux info looks to be the same. The only information that appears to differ is the modified date and one additional line in the file itself for testing. I thought I was doing something wrong with my hosts file, even though I have been using this approach since Android 6.0. However, I agree, it appears that changes to system are being ignored. Further, changing the system partition no longer shows the red warning at boot about the system being corrupted.
---------- Post added at 09:58 PM ---------- Previous post was at 09:38 PM ----------
DanRyb;68654939 I would boot back up into the system and couldn't see any changes made.[/QUOTE said:
Oooh. You're right. Neither /etc/hosts or /system/etc/hosts is modified in the booted OS after I modify it from live image, but the change is retained when I reboot into live image and mount system. Hmm, so either:
1) Need to figure out where the the system files are being loaded from and modify them from live image if possible
2) Use a mechanism similar to what dontblinkwatchout described AdAway is using of having a custom mount setup (have to reverse engineer AdAway I guess to see what it's doing)
3) ?
Click to expand...
Click to collapse
There's absolutely no way to modify or mount system partition r+w unless you disable dm-verity
Enviado desde mi Nexus 6P mediante Tapatalk
alexiuss said:
There's absolutely no way to modify or mount system partition r+w unless you disable dm-verity
Enviado desde mi Nexus 6P mediante Tapatalk
Click to expand...
Click to collapse
dm-verity has been around since Android 4.4. Are you saying there is something new around this in Android 7.0?
You can modify the system partition by compiling an engineering build of Android and booting it, then mounting the system partition and modifying it. I've been doing this to update the hosts file since Android 6.0 for every OTA update (since more recently OTA updates bomb out unless you reflash the clean "uncorrupted" system.img first). Changing the system image before Android 7.0 did result in an extra screen with a red warning about a corrupted something or other (I'm sure because dm-verity checking failed). Regardless, you can still change the system partition, the information just no longer seems to be used, which is a bit perplexing to me atm.
crashenx said:
dm-verity has been around since Android 4.4. Are you saying there is something new around this in Android 7.0?
Click to expand...
Click to collapse
Android 7.0 introduced redundant bits for reed solomon forward error correction into the system and vendor partitions and code in the kernel to perform the error correction.
Your changes are being written to emmc but when you boot with 7.0 kernel with dm-verity enabled your changes are being treated as data corruption and on-the-fly error corrected back to original.
You can see your changes if you boot into twrp because it has dm-verity disabled. However if you boot into android with dm-verity enabled it will look like original image again even though your changes are technically still there.
It took me a day to figure out what was really going on because i initially had no idea they added this feature to Android N.
The simple way to disable dm-verity is to install SuperSU, but you can also accomplish the same patching your own kernel, installing pre-patched kernel, installing custom kernel, etc.
sfhub said:
Android 7.0 introduced redundant bits for reed solomon forward error correction into the system and vendor partitions and code in the kernel to perform the error correction.
Your changes are being written to emmc but when you boot with 7.0 kernel with dm-verity enabled your changes are being treated as data corruption and on-the-fly error corrected back to original.
You can see your changes if you boot into twrp because it has dm-verity disabled. However if you boot into android with dm-verity enabled it will look like original image again even though your changes are technically still there.
It took me a day to figure out what was really going on because i initially had no idea they added this feature to Android N.
The simple way to disable dm-verity is to install SuperSU, but you can also accomplish the same patching your own kernel, installing pre-patched kernel, installing custom kernel, etc.
Click to expand...
Click to collapse
That's good info and makes total sense. Thanks! Pretty neat actually, just a bummer for me.
Yeah so SuperSU path is not really one I want to pursue. I could learn how to update the dm-verity shas used for verification. That'd probably be the most secure, but it's gonna be a PITA I bet. I imagine I'd need to compile my own image similar to how I made my live image and update a few things. Might have to deal with encryption which is probably an even bigger headache. Also, I bet it would break OTA and have to reflash to update, though that's true now.
I'm really curious what AdAway is doing. Maybe I should pursue reverse engineering that.
I really appreciate you pointing us in the right direction.
I am glad found this thread..willing to assist here without permanent root..
Ericarthurc said:
I was able to modify my system partition; by installing busy box to /su/xbin and running "su busybox mount -o rw,remount system" (no quotes) in material terminal with root
Click to expand...
Click to collapse
I was trying to create a /system/xbin/post-boot but couldn't remount /system, and so I added busybox to the front of my command. I am not using adb so I cut that part off. Thanks a lot!
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.
I have here, two packages.
The twrp one is meant for those who have already flashed twrp, the other is for first time root via EDL.
Both flash System RW, updated TWRP and magisk.
TWRP package will not wipe Data, You will loose no data
NOTE - You may have to mount the system RW.
NOTE - The above will be fixed via a future custom rom.
Without further ado, here are the instructions.
Initial Root Instructions
Prep: You must have a Pin screen lock set on your device to prevent data loss.
On your phone go to
Settings>Security>Screen Lock>PIN
and set a pin.
USB Debugging and OEM Unlocking have to be enabled to make this work.
On Your phone go to
Setting>About phone
Then tap on build number 10 time to unlock Developer Settings
Now go to
Settings>Developer Options
Then toggle usb debugging and oem unlocking.
1. Download this package B20 Via QFIL
2. Unzip the file to your desktop.
3. Right click on RunasAdmin_TestSignON.bat and run as administrator.
4. Let your machine reboot.
5. Run Run This.bat
6. Install everything it tells you to install.
NOTE Select WWAN-DHCP when asked
7. RTFM and flash (All the files your need for qfil are in the B20 Folder!!!!)
8. Profit
Then
9.Press and hold Vol+ and Power
10.Once the ZTE screen shows, let go of power while continuing to hold vol+
This will get you into twrp
11.Plug you phone into your computer and from your adb directory, run these commands.
12.adb shell
13.setenforce 0
14.exit
Now on your phone, in twrp
15.Swipe to allow midification
16.Tap Backup
17.check data
18.tap select storage
19.Select microsdcard
20.tap ok
21.Swipe to backup
22.Tap home
23.Tap wipe
24.Tap Format Data
25.Enter yes and tap the blue checkmark
26.Tap home
27.Tap Power off
28.Turn your phone on.
For those who have TWRP already on their device, follow these instructions.
1. Download this package. B20 via TWRP
2. Extract it to your desktop
3. Run "Flash full B25.bat"
4. Profit
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Update 5/253/19
Updated boot.img z982_boot_magisk.img
Update Magisk root "Already obsolete"
Fixes ADB not authorized issues
Update twrp recovery.img z982_recovery_twrp.img
Fixes selinux enforcing related issues related to /data folder
Fixes backup related issues
Fixes zip install related issues
Do you think this will work with my hard bricked phone?
so if our system is still ro, all we have to do is mount rw every time? I was hoping that we would only need to mount it like one time, because im basically doing the same thing I was doing before.
https://drive.google.com/file/d/1YsOFbKcca2GTc6K77vD6-hh4qtk5O3mv/view?usp=sharing
test this. you might need to rename the zip file to bootanimtion.zip.
Chickenaa said:
https://drive.google.com/file/d/1YsOFbKcca2GTc6K77vD6-hh4qtk5O3mv/view?usp=sharing
test this. you might need to rename the zip file to bootanimtion.zip.
Click to expand...
Click to collapse
will do. are all the files already in place.
bootanimation worked, but sound still didnt
evtoofly said:
will do. are all the files already in place.
bootanimation worked, but sound still didnt
Click to expand...
Click to collapse
Upload the build.prop
Chickenaa said:
Do you think this will work with my hard bricked phone?
Click to expand...
Click to collapse
As long as you get the driver working, it should no problem.
xxMoon said:
As long as you get the driver working, it should no problem.
Click to expand...
Click to collapse
Im thinking about reinstalling windows. Do you think i should give it a try?
Chickenaa said:
Im thinking about reinstalling windows. Do you think i should give it a try?
Click to expand...
Click to collapse
I would.
Before you reinstall.. if ur able try on another PC.
xxMoon said:
1. Download this package. B20 via TWRP
2. Extract it to your desktop
3. Run "Flash full B25.bat"
4. Profit
Click to expand...
Click to collapse
Appreciate the update, same problem as before though RO /system and a mount -o rw,remount /system command results in the phone freezing and then restarting.
JasonSec said:
Appreciate the update, same problem as before though RO /system and a mount -o rw,remount /system command results in the phone freezing and then restarting.
Click to expand...
Click to collapse
thought I was the only one, I just stopped trying, if I need to go mount rw, i just use root explorer . Even that freezes sometimes though smh. Some people just got it better than we do
B25
Hello sir,
My phone is running B25. Will this cause issues? Do I need to downgrade?
AjtheLAF said:
Hello sir,
My phone is running B25. Will this cause issues? Do I need to downgrade?
Click to expand...
Click to collapse
No issues for me.
Emerl said:
No issues for me.
Click to expand...
Click to collapse
Did your system become rw?
evtoofly said:
Did your system become rw?
Click to expand...
Click to collapse
I use ES File Explorer. Open the app, wait for su to grant it access, then change the system to RW. I've noticed that the phone will freeze if I tried to switch to RW before the File Explorer was granted su access.
Emerl said:
I use ES File Explorer. Open the app, wait for su to grant it access, then change the system to RW. I've noticed that the phone will freeze if I tried to switch to RW before the File Explorer was granted su access.
Click to expand...
Click to collapse
I noticed that too. I also tried to see if root explorer would mount rw after I used es to mount rw, and it turns out that u still have to mount system separately in both file managers. Bummer because I was looking for a way to always have my system mounted as rw between both file managers.
evtoofly said:
I noticed that too. I also tried to see if root explorer would mount rw after I used es to mount rw, and it turns out that u still have to mount system separately in both file managers. Bummer because I was looking for a way to always have my system mounted as rw between both file managers.
Click to expand...
Click to collapse
I'm guessing once a custom rom is available, the whole system RW situation will be situated. Is there an advantage of root explorer over es explorer?
Emerl said:
I'm guessing once a custom rom is available, the whole system RW situation will be situated. Is there an advantage of root explorer over es explorer?
Click to expand...
Click to collapse
I personally use root explor to chmod files, I dont think es can do it, however es has its own perks as well, so I just keep both just in case
Emerl said:
I'm guessing once a custom rom is available, the whole system RW situation will be situated. Is there an advantage of root explorer over es explorer?
Click to expand...
Click to collapse
Lol, actually you can put init.d scripts in /sbin/.magisk/img/.core/service.d/ and they will do it on boot.
Try my attachment.
I
I've looked all over and I'm unable to find a solution or even what's stopping me from modifying the /system folder in the root directory. I can remove files from that folder and all of it's subfolders but I'm unable to add any files into that directory. I am rooted on the T-mobile OnePlus 6t that has been converted to the international ROM. I know my root works cause I can perform other root functions. I also cannot modify the /system folder from TWRP either which is really strange to me. Also, when TWRP prompts me to install the app, it just reboots recovery since it's trying to install it as a system app which I can't do for this odd reason I have yet to find out. This issue all of a sudden showed up after an OTA update and re-rooting after. I have tried reinstalling TWRP, Magisk and Oxygen OS itself but the issue persists. I have also tried running "reboot disemmcwp" as root in a terminal window AND using adb but I guess that command no longer works. Any suggestions welcome as this is the last place I can find an answer to this issue.
Edit: found out I'm unable to uninstall system apps for some reason. So the issue isn't space related.
Toilet Clauger said:
I've looked all over and I'm unable to find a solution or even what's stopping me from modifying the /system folder in the root directory. I can remove files from that folder and all of it's subfolders but I'm unable to add any files into that directory. I am rooted on the T-mobile OnePlus 6t that has been converted to the international ROM. I know my root works cause I can perform other root functions. I also cannot modify the /system folder from TWRP either which is really strange to me. Also, when TWRP prompts me to install the app, it just reboots recovery since it's trying to install it as a system app which I can't do for this odd reason I have yet to find out. This issue all of a sudden showed up after an OTA update and re-rooting after. I have tried reinstalling TWRP, Magisk and Oxygen OS itself but the issue persists. I have also tried running "reboot disemmcwp" as root in a terminal window AND using adb but I guess that command no longer works. Any suggestions welcome as this is the last place I can find an answer to this issue.
Click to expand...
Click to collapse
Known issue that in the Newer OxygenOS versions there is no free space in /system. I'd download Solid Explorer and check the Free Space in the Root Directory.
Sent from my OnePlus6T using XDA Labs
Mannan Qamar said:
Known issue that in the Newer OxygenOS versions there is no free space in /system. I'd download Solid Explorer and check the Free Space in the Root Directory.
Click to expand...
Click to collapse
I've thought about that before. I use root explorer and can see there's more space than needed for the files I want to insert. Is there some buffer space needed in there and how much?
Toilet Clauger said:
I've thought about that before. I use root explorer and can see there's more space than needed for the files I want to insert. Is there some buffer space needed in there and how much?
Click to expand...
Click to collapse
Well, if you go to magisk and select core only mode then reboot you will be able to modify system
toolhas4degrees said:
Well, if you go to magisk and select core only mode then reboot you will be able to modify system
Click to expand...
Click to collapse
I was actually able to find the issue. Space was the issue. I guess there's a space buffer needed from what a file explorer says is left and what's actually left. I uninstalled a couple system apps I disable anyway and was able to insert files/apps into system again.
I made space easy I have the new OnePlus camera apk 125mb the old one is 67mb