So I'm currently on 6.0 w/ system root (SuperSU 2.52), and I'm preparing to upgrade to 6.0.1.
However I just read the following post by Chainfire:
http://forum.xda-developers.com/showpost.php?p=64208563&postcount=3393
It seems like editing the build.prop is hit or miss, and may potentially cause a boot loop. I rely on editing my build.prop so I can enable tethering on my grandfathered AT&T unlimited plan. (net.tethering.noprovisioning=true)
Has anyone on 6.0.1 + SuperSU 2.61 had success editing their build.prop?
flash stock 6.0.1 boot, system and vendor images, boot into recovery without rebooting phone, flash 2.61.... then reboot normal (if twrp asks to root, say no)
u would have root, and should be fine editing ur build prop after that
Well to follow up, I installed 6.0.1, SuperSU 2.62 (which came out today), and I was able to modify my build.prop successfully using the FX File Browser app.
Before editing, I tried to make space using Chainfire's advice, and I tried to use Titanium Backup to uninstall a system app first to make room, but it failed. Next I tried SD Maid and it succeeded, which gave me plenty of room in the /system partition.
ChrisG683 said:
So I'm currently on 6.0 w/ system root (SuperSU 2.52), and I'm preparing to upgrade to 6.0.1.
However I just read the following post by Chainfire:
http://forum.xda-developers.com/showpost.php?p=64208563&postcount=3393
It seems like editing the build.prop is hit or miss, and may potentially cause a boot loop. I rely on editing my build.prop so I can enable tethering on my grandfathered AT&T unlimited plan. (net.tethering.noprovisioning=true)
Has anyone on 6.0.1 + SuperSU 2.61 had success editing their build.prop?
Click to expand...
Click to collapse
I have the same plan as well. Are you sure at&t won't be able to detect the hotspot though? So all you do is add that line to the build.prop and it should enable it now natively?
Planning to update to 6.0.1 this weekend, thanks for the heads up.
Sent from my Nexus 6P using Tapatalk
I don't think they can really tell, other than by checking what kind of traffic is going. I've been using tethering hacks for years on my S4 & S6 with not even a warning text.
build.prop edit causes bootloop for me
ChrisG683 said:
Well to follow up, I installed 6.0.1, SuperSU 2.62 (which came out today), and I was able to modify my build.prop successfully using the FX File Browser app.
Before editing, I tried to make space using Chainfire's advice, and I tried to use Titanium Backup to uninstall a system app first to make room, but it failed. Next I tried SD Maid and it succeeded, which gave me plenty of room in the /system partition.
Click to expand...
Click to collapse
I have a Nexus 6P 6.0.1 MMB29P with SuperSU-sysytemless-v2.66. My carrier is Net10.
I also have a Nexus 5. The tethering hotspot works on my Nexus 5 but not on my 6P.
I have used root explorer to copy build.prop to a new location and then I added net.tethering.noprovisioning=true to it and moved it back to sytem. After I did this my phone got stuck on the google logo during boot. I was able to fix it by flashing the system partition back to stock.
I need help getting tethering working on my Nexus 6P.
shiznoroe88 said:
I have a Nexus 6P 6.0.1 MMB29P with SuperSU-sysytemless-v2.66. My carrier is Net10.
I also have a Nexus 5. The tethering hotspot works on my Nexus 5 but not on my 6P.
I have used root explorer to copy build.prop to a new location and then I added net.tethering.noprovisioning=true to it and moved it back to sytem. After I did this my phone got stuck on the google logo during boot. I was able to fix it by flashing the system partition back to stock.
I need help getting tethering working on my Nexus 6P.
Click to expand...
Click to collapse
Interesting, I haven't had any problems with my 6P, but to be fair I never moved the file. All I did was create a duplicate backup file in the same location as the original, and then I edited the original. Did you make sure to uninstall a decently large system app before editing the file? Chainfire said due to the low amount of space available on the partition, there may be issues if you don't free up some space before editing your build.prop file (it may not save properly, possibly corrupting your build.prop file). I uninstalled Chrome via SD Maid since I use Chrome beta/Firefox, so that freed me me up about 20-30 MB, more than enough space.
Can someone give me very detailed instructions on how to add net.tethering.noprovisioning=true to build.prop please. This is kicking my ass. I have done it a few different ways and it keeps causing a bootloop.
Thanks.
shiznoroe88 said:
Can someone give me very detailed instructions on how to add net.tethering.noprovisioning=true to build.prop please. This is kicking my ass. I have done it a few different ways and it keeps causing a bootloop.
Thanks.
Click to expand...
Click to collapse
I've got a Nexus 6 (no P) and samething thing is happening to me as well.
If anyone stills needs help with this
If anyone stills needs help with this, I installed the BuildProp Editor by JRummy from the play store. I was able to use it with root privileges to edit my build.prop file and I added the no provisioning and the multi window edits. Now I am able to use tethering and multi window on my Nexus 6P on android 6.0.1.
The only reason I even use tethering is to send files via ES File Explorer to my Nexus 4 & 5 over a WiFi direct connection. I think it is crap that I have to edit the build.prop just to be able to do that. It even blocked tethering when I turned off mobile data or removed my sim card, so it wasn't even a carrier issue, it was a Nexus 6P issue.
I just flashed android 7.0 and am going to update my post afterwards whether or not the edit still works on 7.0.
Related
I have successfully edited build prop on Android N Preview to allow tethering. My setup is as follows: I was originally rooted on Pure Nexus. I reflashed stock 6.0.1 MM and unrooted my device. I took the Android N OTA and rooted via CF Auto Root by Chainfire ( I had to manually fastboot the CFAR image as the program provided kept failing). I tried various root file managers that did not work. Finally FX Explorer with the root add-on worked. I had to change the file manager to open files in R/W mode via the menu settings. After that I was able to open the build prop file in text editor and added "net.tethering.noprovisioning=true" (without quotes) at the bottom or end of the file. I rebooted and am able to tether without the subscription check. I am on an unlimited data plan. Hope this helps.
hsomnus said:
I have successfully edited build prop on Android N Preview to allow tethering. My setup is as follows: I was originally rooted on Pure Nexus. I reflashed stock 6.0.1 MM and unrooted my device. I took the Android N OTA and rooted via CF Auto Root by Chainfire ( I had to manually fastboot the CFAR image as the program provided kept failing). I tried various root file managers that did not work. Finally FX Explorer with the root add-on worked. I had to change the file manager to open files in R/W mode via the menu settings. After that I was able to open the build prop file in text editor and added "net.tethering.noprovisioning=true" (without quotes) at the bottom or end of the file. I rebooted and am able to tether without the subscription check. I am on an unlimited data plan. Hope this helps.
Click to expand...
Click to collapse
Worked for me, but I used Root Browser. Glad to have tethering on N.
Edit: Scratch that, I added the net.tethering line to build.prop, but when I go into settings and turn tethering on, it tries for a few seconds and fails.
Fvolfrine said:
Worked for me, but I used Root Browser. Glad to have tethering on N.
Edit: Scratch that, I added the net.tethering line to build.prop, but when I go into settings and turn tethering on, it tries for a few seconds and fails.
Click to expand...
Click to collapse
What I did and always do is to modify my APN; where it says APN type i just add DUN and save the file.
Like this: default,supl,mms,dun
After you hit save your internet connection will reset itself, then everything should be good.
n3ck0man said:
What I did and always do is to modify my APN; where it says APN type i just add DUN and save the file.
Like this: default,supl,mms,dun
After you hit save your internet connection will reset itself, then everything should be good.
Click to expand...
Click to collapse
Sorry, no luck with that. I added the dun, now my APN type reads "default,mms,supl,fota,hipri,dun" and the net.provisioning line is in, but when I toggle the tethering switch it fails. I wonder if this is like the dark theme toggle, which requires several attempts before it works.
Fvolfrine said:
Sorry, no luck with that. I added the dun, now my APN type reads "default,mms,supl,fota,hipri,dun" and the net.provisioning line is in, but when I toggle the tethering switch it fails. I wonder if this is like the dark theme toggle, which requires several attempts before it works.
Click to expand...
Click to collapse
Try the fx explorer and its root add on...both are free. You just have to change it to open files in r/w in menu before opening the build prop file.
Mine has been working fine and i didnt have to make several attempts...it worked after the first try. Didnt change to DUN either. Only did exactly what i listed in OP...nothing more.
hsomnus said:
Try the fx explorer and its root add on...both are free. You just have to change it to open files in r/w in menu before opening the build prop file.
Mine has been working fine and i didnt have to make several attempts...it worked after the first try. Didnt change to DUN either. Only did exactly what i listed in OP...nothing more.
Click to expand...
Click to collapse
That worked! I thought that using Root Explorer, which also has R/W capability, would be just the same, but I guess I was wrong.
Fvolfrine said:
That worked! I thought that using Root Explorer, which also has R/W capability, would be just the same, but I guess I was wrong.
Click to expand...
Click to collapse
Yeah...i tried root explorer first as well as a few others. This was the only one that worked.
Worked for me. Thanks!
hsomnus said:
I have successfully edited build prop on Android N Preview to allow tethering. My setup is as follows: I was originally rooted on Pure Nexus. I reflashed stock 6.0.1 MM and unrooted my device. I took the Android N OTA and rooted via CF Auto Root by Chainfire ( I had to manually fastboot the CFAR image as the program provided kept failing). I tried various root file managers that did not work. Finally FX Explorer with the root add-on worked. I had to change the file manager to open files in R/W mode via the menu settings. After that I was able to open the build prop file in text editor and added "net.tethering.noprovisioning=true" (without quotes) at the bottom or end of the file. I rebooted and am able to tether without the subscription check. I am on an unlimited data plan. Hope this helps.
Click to expand...
Click to collapse
thanks! thinking about trying this for 6.0.1 until N and after. I'm on project fi tho and don't know if that's a jinx
Erik Rye said:
thanks! thinking about trying this for 6.0.1 until N and after. I'm on project fi tho and don't know if that's a jinx
Click to expand...
Click to collapse
Isn't tethering allowed on Project Fi?
Sent from my Nexus 6 using Tapatalk
Fvolfrine said:
Isn't tethering allowed on Project Fi?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yes, tethering is allowed on project fi. I was hoping that no subscription check = no data charges but not sure that's possible..
What providers is this succeeding on? Anyone on TMO?
Sent from my Nexus 6 using Tapatalk
wideasleep1 said:
What providers is this succeeding on? Anyone on TMO?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I've successfully unlocked tethering on Sprint but I get a DNS error when I try to load websites on my PC.
Anyone tried sending the tether command just like on m?
5ghz tethering
blitzerking1 said:
I've successfully unlocked tethering on Sprint but I get a DNS error when I try to load websites on my PC.
Click to expand...
Click to collapse
I'm currently sprint, I input the dun_required 0 by terminal emulator and net.tethering by fx explorer. My tethering wouldn't stay active until I switched to 5ghz frequency in tether settings. I connected my ipad and searched pages to verify.
For some reason when I try to mount build.prop as read/write I get an "error: this action could not be completed" within FX Explorer. I can however, mount the system folder with no problems. Seems to be an issue mounting just the build.prop. Any ideas?
ForeverZ3RO said:
For some reason when I try to mount build.prop as read/write I get an "error: this action could not be completed" within FX Explorer. I can however, mount the system folder with no problems. Seems to be an issue mounting just the build.prop. Any ideas?
Click to expand...
Click to collapse
I tried all of the suggestions in this thread until I found one. I can't remember which one worked.
kwdan said:
I tried all of the suggestions in this thread until I found one. I can't remember which one worked.
Click to expand...
Click to collapse
Ummmm... ok. I've looked through all of the posts in this thread and can't find any with my issue. Not sure how you got it to work.
ForeverZ3RO said:
Ummmm... ok. I've looked through all of the posts in this thread and can't find any with my issue. Not sure how you got it to work.
Click to expand...
Click to collapse
I used terminal emulator to add the tethering_dun_required 0
And fx explorer, or root explorer or root browser (not sure which one) to add provisioning line. Then rebooted. Tethering would still turn on and off until I went into tethering settings and switched it to 5ghz.
kwdan said:
I used terminal emulator to add the tethering_dun_required 0
And fx explorer, or root explorer or root browser (not sure which one) to add provisioning line. Then rebooted. Tethering would still turn on and off until I went into tethering settings and switched it to 5ghz.
Click to expand...
Click to collapse
Any chance you could post the steps for doing it with the terminal emulator?
Also, didn't you still have to mount the system folder as R/W? That's where it's failing at for me.
hello im getting the following message everytime i try and download the lists "copying of host file failed! please read help for more information"
ive just updated to the android 7.0 through the developer program, twrp custom recovery installed with root access build number NRD90M
just wondering what could be causing this and if i can do anything to try and fix it thanks
Is your /system set to read only, or read/write? If read only, adaway will not be able to update /system/etc/hosts
dratsablive said:
Is your /system set to read only, or read/write? If read only, adaway will not be able to update /system/etc/hosts
Click to expand...
Click to collapse
i have it set to read write im gonna try to flash the systemless hosts right now ill update how it goes
flashing the AdAway_systemless_hosts_v2.zip in the recovery, then unistalling and reinstalling the app seems to have worked
you can also use Magisk now to enable complete systemless root and then the hosts file /system/etc will be forwarded to the systemless version
I didn't even install Adaway, I just downloaded a host file and replaced it in /etc/
Works good enough for me and one less app running...
kennehh said:
hello im getting the following message everytime i try and download the lists "copying of host file failed! please read help for more information"
ive just updated to the android 7.0 through the developer program, twrp custom recovery installed with root access build number NRD90M
just wondering what could be causing this and if i can do anything to try and fix it thanks
Click to expand...
Click to collapse
In the exact same boat. Frustrating. Tried Adfree, to no avail. Adaway, to no avail. Tried the adaway bind zip file, making hosts writable, and even System to writable. Nothing.
treoo0_1 said:
In the exact same boat. Frustrating. Tried Adfree, to no avail. Adaway, to no avail. Tried the adaway bind zip file, making hosts writable, and even System to writable. Nothing.
Click to expand...
Click to collapse
i have fixed this by converting adaway from user apps to system apps using Link2SD, reboot and adaway working properly again
Very old thread, but I've had exactly the same problem installing AdAway on the last 3 or 4 phones -- all but one running Nougat 7.0, the other on Oreo 8.1. This was when trying to install AdAway versions 3.1 and 3.3.something.
I finally got it to write hosts file updates using one of the following, not sure which was the key:
-- Installed version 3.2 which had been running problem-free on an old phone for years. The biggest difference is this older phone is running Resurrection Remix 5.8.3 (Nougat 7.1.2).
-- Before trying to update the hosts file on this fresh install, I went straight to AdAway preferences and set "Check for updates daily", "Enable webserver", and "Start webserver on boot". After making those settings I tapped Download Files and Apply Ad Blocking, and it successfully wrote to the hosts file.
Again I don't know which was the fix. It seems weird that version 3.2 would work when a version just before and after it didn't work for me. But of course it is possible that the version is the difference. It seems even more weird that those 3 little preference settings make any difference at all . . . unless it's just the act of writing changes to the AdAway app itself.
Before installing 3.2, using Root Explorer I checked permissions on the working phone and one non-working phone, for the systems and etc folders, and for the hosts file itself. (In all cases AdAway is/was set to use /systems/etc/hosts.) I also checked Android permissions in the Apps list. All permissions were exactly the same on both phones: 0755 for system, 0755 for etc, and 0644 for hosts. No permissions assigned via Android.
Hoping this bump will also get fresh attention from somebody who might know the details of a real answer.
@Moondroid
Why the hell you trying to make some really old ass version of it work instead of installing the newest version? Lol
I've been using 4.2.7 and though its kind of weird on a fresh install I need to update and apply the hosts twice before searching for newer hosts comes back its up to date. But at least it works.
Hi so I just got OnePlus 5. Bootloader unlocked.
Using official twrp 3.1.1.
Did a full wipe without wiping internal storage.
Installed freedom os 1.8. I had official oos 4.5.11 installed before.
Got rom setup. Magisk working fine. Adaway installed and updated. Rebooted phone
But ads are not being blocked. Not on websites (using Samsung internet browser ) not in apps (speed test).
I keep seeing ads.
What is going on here?
Yes adaway has root access double checked.
I am using Magisk 14.0 and Adaway without any problems.
So are you using same rom?
I'm on cellular network..4G
try enabling systemless hosts option in magisk settings. Might adjust some behaviors for you.
LimitsX said:
So are you using same rom?
Click to expand...
Click to collapse
I have used lineage, asop and oos. Right now I'm on oos 4.5.11. Never had a problem.
depends on what app you are using and host you have.
In my case, original host didn't do much.
I add this one : http://winhelp2002.mvps.org/hosts.txt
And most ads are blocked for my usage. (just copy this url host in adaway)
oVeRdOsE. said:
depends on what app you are using and host you have.
In my case, original host didn't do much.
I add this one : http://winhelp2002.mvps.org/hosts.txt
And most ads are blocked for my usage. (just copy this url host in adaway)
Click to expand...
Click to collapse
Lol, i tried most apps and every single website, its not being able to block. Could it be the FreedomOS related?
Thank you, I will definitely try that!
So I tested it again.
As long as I am on WiFi, ads are being blocked. Once I am off Wifi, im on cellular Data - 4G/4G+ or 3G+, there is no ad blocking.
Never had problem, regardless of app or room, will or not. It might be your device or carrier where you live since it works on wifi for you, but not on cellular data.
@LimitsX I've had this problem with AdAway hosts file not sticking after reboot since marshmallow. The way I fix it is to use a file manager to move the hosts file, /system/etc/hosts over to sdcard and back again to where it was originally, /system/etc/ , set permissions rwrr, and open AdAway, update the hosts file, and hot reboot. It should stick then. I don't why but it might have something to do with permissions and system integrity protections. The file manager app I use is Mixplorer from here at xda and no, I haven't had any issues with safety nut. I also use the AdAway from F-Droid. I haven't tried others. As always, make sure you have a current backup before touching anything in /system/ . You can also copy the updated hosts file to the sdcard from twrp. Boot straight into twrp after you update and copy to sdcard, reboot and delete /system/etc/hosts, grab /sdcard/hosts and move it to /system/ect/ set permissions: root root 00644 (rw-r-r-) and hot reboot. From then on, you will be able to just update thru the app
Hope that helps.
ElwOOd_CbGp said:
@LimitsX I've had this problem with AdAway hosts file not sticking after reboot since marshmallow. The way I fix it is to use a file manager to move the hosts file, /system/etc/hosts over to sdcard and back again to where it was originally, /system/etc/ , set permissions rwrr, and open AdAway, update the hosts file, and hot reboot. It should stick then. I don't why but it might have something to do with permissions and system integrity protections. The file manager app I use is Mixplorer from here at xda and no, I haven't had any issues with safety nut. I also use the AdAway from F-Droid. I haven't tried others. As always, make sure you have a current backup before touching anything in /system/ . You can also copy the updated hosts file to the sdcard from twrp. Boot straight into twrp after you update and copy to sdcard, reboot and delete /system/etc/hosts, grab /sdcard/hosts and move it to /system/ect/ set permissions: root root 00644 (rw-r-r-) and hot reboot. From then on, you will be able to just update thru the app
Hope that helps.
Click to expand...
Click to collapse
yeah, I saw this how-to aswell.
But, enter hosts manually should do the trick also, but not sure if he rejected this idea or just don't understand what I meant.
it worked for me.
if it was a how-to, I would have just linked to it. This is just the explanation of how I was able to get it to work. Entering the hosts data manually would take a year or more, so whatever you are referring to probably meant applying it manually with a file manager.
@LimitsX you might want to try a solution to change your dns settings (there's several) on mobile to see if that solves it. It's possible your carrier is putting your data thru a proxy, effectively killing your adblock capabilities
ElwOOd_CbGp said:
@LimitsX I've had this problem with AdAway hosts file not sticking after reboot since marshmallow. The way I fix it is to use a file manager to move the hosts file, /system/etc/hosts over to sdcard and back again to where it was originally, /system/etc/ , set permissions rwrr, and open AdAway, update the hosts file, and hot reboot. It should stick then. I don't why but it might have something to do with permissions and system integrity protections. The file manager app I use is Mixplorer from here at xda and no, I haven't had any issues with safety nut. I also use the AdAway from F-Droid. I haven't tried others. As always, make sure you have a current backup before touching anything in /system/ . You can also copy the updated hosts file to the sdcard from twrp. Boot straight into twrp after you update and copy to sdcard, reboot and delete /system/etc/hosts, grab /sdcard/hosts and move it to /system/ect/ set permissions: root root 00644 (rw-r-r-) and hot reboot. From then on, you will be able to just update thru the app
Hope that helps.
Click to expand...
Click to collapse
ElwOOd_CbGp said:
if it was a how-to, I would have just linked to it. This is just the explanation of how I was able to get it to work. Entering the hosts data manually would take a year or more, so whatever you are referring to probably meant applying it manually with a file manager.
@LimitsX you might want to try a solution to change your dns settings (there's several) on mobile to see if that solves it. It's possible your carrier is putting your data thru a proxy, effectively killing your adblock capabilities
Click to expand...
Click to collapse
Hey bro, Thank you for taking the time to helping me out. I didn't get a chance to reply earlier.
I've actually looked into this, apparently OOS doesn't properly setup APN for my Canadian sim card. I had to manually correct it, thus now blocking works . When I realized, wifi blocking works, I had to look into my sim card and APN settings. The proxy was incorrectly setup by the rom, when my carrier doesnt even use it lol..
Also, I noticed OOS doesn't properly setup GPS / Navigation for high accuracy. I had to manually open it lol.
Thank you to everyone who helped me. I really appreciate your kind help!
Hopefully this will be useful to others as well!
cool glad you got it. the internet is horrible without a good filter
Adaway acts like a proxy between the app and the ad network. I'm guessing the problem with ads not being block is caused by your cellular provider himself using a proxy to deliver content. Try another APN for mobile internet.
I've installed the latest version of adaway from here
https://androidfilehost.com/?w=files&flid=249276
And it works now
Sent from my ONEPLUS A5010 using Tapatalk
Poppeye0 said:
Adaway acts like a proxy between the app and the ad network. I'm guessing the problem with ads not being block is caused by your cellular provider himself using a proxy to deliver content. Try another APN for mobile internet.
Click to expand...
Click to collapse
alessandro_xda said:
I've installed the latest version of adaway from here
https://androidfilehost.com/?w=files&flid=249276
And it works now
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
Guys, post is old of more 1 year...
Pho3nX said:
Guys, post is old of more 1 year...
Click to expand...
Click to collapse
and???
still working on and off.
no later than this morning I searched for new host since few apps got ads back
oVeRdOsE. said:
and???
still working on and off.
no later than this morning I searched for new host since few apps got ads back
Click to expand...
Click to collapse
Huuuuuuuu..... Keep cool, keep calm
Okay, I'll leave you in your host file lol
Hey,
I've rooted my A1 using this guide:
https://www.youtube.com/watch?v=tRcYUMBgvaI
I have magisk 13.4 installed, and passing Root checker verification.
When I try to edit build.prop file using solid explorer or buidprop editor app I get an error, "can't save the file"
even tough both of them has been granted "superuser accesses" using magisk.
Any ideas?
On another matter, I just received November OTA, I have TWRP installed,
Will it be possible to install the update at all? in particularity will I be able to install it right after I manage to edit the build.prop file, and still "have" the edited file after the OTA in order to keep using GCAM? I don't care about root access, all I want is GCAM, and updated phone if possible.
Thanks!
You need to change ur system permission for writing!
Tip:- use es file explorer to change it
Or get the app BuildProp Editor from the playstore.
I can't get the Nov update with TWRP installed.
I think there's a magisk module to enable google camera
Build prop app and solid explorer failed changing permission. Any ideas?
WishMonster said:
Build prop app and solid explorer failed changing permission. Any ideas?
Click to expand...
Click to collapse
Maybe you should try magisk 14.4
Everything just work like a charm in my devices, root woth magisk 14.4
Update:
I reinstalled magisk, and updated to v 14.5.
tried GCAM ports from here:
https://www.xda-developers.com/google-camera-hdr-customization-raw-support/
& here:
https://www.xda-developers.com/google-camera-updated-zero-shutter-lag-xiaomi/
all keep crashing. should I do something other then installing the apk and editing the build prop?
Second update:
The "enabled" keyword vs "enable" made the difference. Everything works like a charm. Picture quality is dramatically improved.
Thanks!
BTW:
Anyone has good configuration for GCAM port from here:
https://www.xda-developers.com/google-camera-hdr-customization-raw-support/
I copied the configuration from post.
I believe there is a better one since the picture is size is significantly smaller (~1.7mb vs 2.5 - 3mb usually),
- Note that although the smaller size picture quality is definitely better.
WishMonster said:
Hey,
I've rooted my A1 using this guide:
https://www.youtube.com/watch?v=tRcYUMBgvaI
I have magisk 13.4 installed, and passing Root checker verification.
When I try to edit build.prop file using solid explorer or buidprop editor app I get an error, "can't save the file"
even tough both of them has been granted "superuser accesses" using magisk.
Any ideas?
On another matter, I just received November OTA, I have TWRP installed,
Will it be possible to install the update at all? in particularity will I be able to install it right after I manage to edit the build.prop file, and still "have" the edited file after the OTA in order to keep using GCAM? I don't care about root access, all I want is GCAM, and updated phone if possible.
Thanks!
Click to expand...
Click to collapse
Please refer my guide... maybe it will help u
https://forum.xda-developers.com/mi-max-3/themes/problem-fixed-failed-to-enabled-t3913133
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