Hopefully there is a way to fix it...
I recently installed M and I attmpted to root it but got the root partially somehow-I was able to install busybox and delete app from the system folder, however I did not have rights to write to the system folder for some reason-I was attempting to edit build.prop to hide the navigation bar and I deleted the Build.Prop in error. I have a back up of it on my phone but I am unable to push it back to the system folder.
I am afraid to reboot and try factory reset since I am at work and I cannot connect my phone to the PC here...I hope I haven't screwed it permanently.
Any help is much appreciated....
Yeah, don't reboot.
You'll need to download a rom and flash it, or a working build.prop.
Pecata said:
Hopefully there is a way to fix it...
I recently installed M and I attmpted to root it but got the root partially somehow-I was able to install busybox and delete app from the system folder, however I did not have rights to write to the system folder for some reason-I was attempting to edit build.prop to hide the navigation bar and I deleted the Build.Prop in error. I have a back up of it on my phone but I am unable to push it back to the system folder.
I am afraid to reboot and try factory reset since I am at work and I cannot connect my phone to the PC here...I hope I haven't screwed it permanently.
Any help is much appreciated....
Click to expand...
Click to collapse
permanently, no. stupid, yes. you wont ever boot up without a build.prop btw. if you have it backed up on your phone, just use a root file explorer and copy/paste it back(you might need to set your SElinux to be permissive). if you reboot, youre going to have to reflash your rom. if youre stock, youll be flashing a factory image.
danarama said:
Yeah, don't reboot.
You'll need to download a rom and flash it, or a working build.prop.
Click to expand...
Click to collapse
I have my build.prop I saved in the downloads folder. I was able to push it back to system with total commander-it worked and it's now back there and it even has the line to disable the software keys. I have to reboot to test it though. I have set the permissions as -rw-r--r-- is that correct?
simms22 said:
permanently, no. stupid, yes. you wont ever boot up without a build.prop btw. if you have it backed up on your phone, just use a root file explorer and copy/paste it back(you might need to set your SElinux to be permissive). if you reboot, youre going to have to reflash your rom. if youre stock, youll be flashing a factory image.
Click to expand...
Click to collapse
Yeah I have never done something that dumb...thanks for replaying...I was able to mount system as rw with total commander...it wouldn't do it with any other file manager for some reason...
Pecata said:
Yeah I have never done something that dumb...thanks for replaying...I was able to mount system as rw with total commander...it wouldn't do it with any other file manager for some reason...
Click to expand...
Click to collapse
ive done it before, more than once. one time i even deleted all of /system/(a long time ago), lol. we learn from our mistakes
simms22 said:
ive done it before, more than once. one time i even deleted all of /system/(a long time ago), lol. we learn from our mistakes
Click to expand...
Click to collapse
That is true-we do....
One last question are the permissions for the build.prop correct as -rw-r--r--?
Pecata said:
That is true-we do....
One last question are the permissions for the build.prop correct as -rw-r--r--?
Click to expand...
Click to collapse
honestly, i have no idea. ive never ever changed any permissions(but always change files), i use root explorer. but, this is what they are set to here..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
simms22 said:
honestly, i have no idea. ive never ever changed any permissions(but always change files), i use root explorer. but, this is what they are set to here..
Click to expand...
Click to collapse
yes, it's the same-644....Thank you so much! Hopefully I will be fine to reboot...
Pecata said:
yes, it's the same-644....Thank you so much! Hopefully I will be fine to reboot...
Click to expand...
Click to collapse
it will, now
Related
This is a pretty easy process. I went in to Root Explorer - dbdata - databases - com.android.providers.settings, copied settings.db to my sd card, edited it on my pc with a db editor changed 0 to a 1 next to non market apps. Copied it back to the original directory, rebooted and installed a non market app.
Please use caution. If you want to make sure the db save properly open it on your sd card before you copy and replace the original. It should open up as a readable table. If it opens up in a txt editor its corrupt. This permanently enables non market apps. You can not toggle it on and off.
I will try and post pictures soon.
**If this has helped you please consider a donation.**
Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Which DB Editor did you use?
clubtech said:
Which DB Editor did you use?
Click to expand...
Click to collapse
Actually its just called Data Base Editor. Program Files says is by ACID/ODE. I will post a link.
Here
Captivate Help
kirbo20 said:
Actually its just called Data Base Editor. Program Files says is by ACID/ODE. I will post a link.
Here
Click to expand...
Click to collapse
Does it mean th after this you are able to install any 3rd party application with no restrictions?
Thanks
You can actually do it through firefox too. There's a firefox addon called 'SQLite manager' that you can use to edit the file, if you don't want to download a separate program.
Root Explorer is the pay program on the market? Any free alternitives?
Are you just trying to install non-market apps on the Captivate? If so, then just download the usb driver for the Captivate and then Droid Explorer (may also need SDK installed; not sure). With Droid Explorer, you can easily load non-market apps within seconds. Good solution for a non tech guy like me.
Being brand spanking new to Android, still have question. I like very specific instructions.
Do you download files to whatever directory you want to make and put the files in? Then is there an option to select, and do install? My background is WinMO, so on that you can just use a file explorer and double click or tap, and it installs.
Muhamadabdelaall said:
Does it mean th after this you are able to install any 3rd party application with no restrictions?
Thanks
Click to expand...
Click to collapse
Yes
(too short)
Confirmation
kirbo20 said:
Yes
(too short)
Click to expand...
Click to collapse
So if I installed "PDAnet" for tethering it will work after rooting?
Thanks for the answer
PDA Net will work without rooting. Just put your phone on airplane mode and enable wifi. Go to the market and download it. Once it is downloaded you can turn off airplane mode and you're good to go.
kirbo20 said:
PDA Net will work without rooting. Just put your phone on airplane mode and enable wifi. Go to the market and download it. Once it is downloaded you can turn off airplane mode and you're good to go.
Click to expand...
Click to collapse
oh, thanks alot man for that I was unaware of.
will flashing a new rom when they start coming out also allow you to do this or do i have to do this regardless?
kirbo20 said:
This is a pretty easy process. I went in to Root Explorer - dbdata - databases - com.android.providers.settings, copied settings.db to my sd card, edited it on my pc with a db editor changed 0 to a 1 next to non market apps. Copied it back to the original directory, rebooted and installed a non market app.
Please use caution. If you want to make sure the db save properly open it on your sd card before you copy and replace the original. It should open up as a readable table. If it opens up in a txt editor its corrupt. This permanently enables non market apps. You can not toggle it on and off.
I will try and post pictures soon.
Click to expand...
Click to collapse
Where do you see the 0, the one you recommend to change to a 1? I only see lots of squares.
So... Thank you so much for this info. I downloaded your file and put it into the correct DIR and have non market apps installing with no problem. However I can not get Titanium backup to work correctly. =/ When I try to restore an app it says installing and I have to force close titanium to get it to stop. Probably about half the apps I try and do this for install the other backups do not. Is any one else having any issues like this or know how to fix it?
seriouslyjeff said:
So... Thank you so much for this info. I downloaded your file and put it into the correct DIR and have non market apps installing with no problem. However I can not get Titanium backup to work correctly. =/ When I try to restore an app it says installing and I have to force close titanium to get it to stop. Probably about half the apps I try and do this for install the other backups do not. Is any one else having any issues like this or know how to fix it?
Click to expand...
Click to collapse
Where did you see the number to change? Mine just looks like a bunch of gibberish
When into this dir dbdata - databases - com.android.providers.settings and cant find any files. Using linda
I used this DB editor instead
http://sqlitestudio.one.pl/index.rvt
connect to the settings.db file, on the left side click Tables, and then click Secure. It will show a grid on the right with _id, name, value etc. Click the Data tab, in the search box type market. And there should be only one value that shows up as "install_nonmarket_apps". Set the value to one. Refersh it and then copy it back to your phone.
iJITSU said:
Are you just trying to install non-market apps on the Captivate? If so, then just download the usb driver for the Captivate and then Droid Explorer (may also need SDK installed; not sure). With Droid Explorer, you can easily load non-market apps within seconds. Good solution for a non tech guy like me.
Click to expand...
Click to collapse
How the heck do you do this? I have Droid Explorer installed but not BusyBox. I have Windows 7 and can't figure out how to get BusyBox on my phone. I have rooted the phone but that's about it. in Droid Explorer when I connect to my phone it shows nothing!
I was a bit hesitant to flash originally, due to the large number of threads that talked about getting one's Android ID or IMEI wiped clean. But as I go back and scan the threads, they are all from more than a couple months ago. I never saw a definitive answer about what causes you to lose these "quite important" numbers. Did someone figure it out? Or was it just that the earliest ROM's were flashing things they weren't supposed to, and now everything is fine. Or was it something in Odin? (I have to say I'm a bit hesitant to Master Clear).
I hesitate to flash much, not knowing yet if there is still a problem that I'd have trouble recovering from. I did back up my efs folder to the computer, and supposedly that will allow me to recover things, but I'd still prefer the option that doesn't wipe out any chance of me getting the phone back to initial conditions, just in case...
Did this get solved, or is there still a vague, tiny but non-zero risk of wiping out the wrong thing in the flash process? Or can Odin always get you back if you can get into download mode?
To my knowledge it's not really an issue, as long as you backed up your efs folder, which you said you did. So you should be good to go.
Your product code will be changed if you flash an i9000 rom, but your IMEI number should still be intact. Your product code should not effect the function of your phone unless your using kies.
For some strange reason your IMEI number does change, well, that's why we have a backup of your efs folder. You'll copy over your nv_data.bin file over with root explorer or similar program, and delete .nv_data.bak, .nv_data.bak.md5 and the nv_data.bin.md5 files.
I'm still running a generic IMEI number on my phone with no issues, and do have a backup of my efs folder. Just lazy, I guess, in not restoring the original IMEI number
so where is this backup located?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i've searched in my internal SD in the sgstoolbox folder, it's blank... most likely because i've master cleared since that backup and gone to stock, but it's gotta be somewhere, if the program is reporting so... thanks...
B-Naughty said:
so where is this backup located?
i've searched in my internal SD in the sgstoolbox folder, it's blank... most likely because i've master cleared since that backup and gone to stock, but it's gotta be somewhere, if the program is reporting so... thanks...
Click to expand...
Click to collapse
Those .bak files are contained within the live /efs. You should be able to use those to get back to the correct product code as they seem to have the correct captivate product ID. Make a backup immediately and move it off of the phone. The backup was probably put on your internal SD card but your master clear for sure wiped them.
z28james said:
Those .bak files are contained within the live /efs. You should be able to use those to get back to the correct product code as they seem to have the correct captivate product ID. Make a backup immediately and move it off of the phone. The backup was probably put on your internal SD card but your master clear for sure wiped them.
Click to expand...
Click to collapse
sweet, i have the correct product code and a backup now... thanks man, thanks button hit
Soccer_Dad said:
I was a bit hesitant to flash originally, due to the large number of threads that talked about getting one's Android ID or IMEI wiped clean. But as I go back and scan the threads, they are all from more than a couple months ago. I never saw a definitive answer about what causes you to lose these "quite important" numbers. Did someone figure it out? Or was it just that the earliest ROM's were flashing things they weren't supposed to, and now everything is fine. Or was it something in Odin? (I have to say I'm a bit hesitant to Master Clear).
I hesitate to flash much, not knowing yet if there is still a problem that I'd have trouble recovering from. I did back up my efs folder to the computer, and supposedly that will allow me to recover things, but I'd still prefer the option that doesn't wipe out any chance of me getting the phone back to initial conditions, just in case...
Did this get solved, or is there still a vague, tiny but non-zero risk of wiping out the wrong thing in the flash process? Or can Odin always get you back if you can get into download mode?
Click to expand...
Click to collapse
It's all a pain in the ass as I am sure you have found out. Such a pain that it really isn't even worth worrying about. Close eyes, flash... maybe back something up first...
Long time forum fan, first post! I'm a little scared from that registration video, but here we go: After rooting my phone, I did a complete backup with Titanium Backup before deleting all kinds of Verizon and Motorola bloat. Now my Droid 3 is experiencing the hardware keyboard repeating space thing described in many other threads. One of the solutions I read about was to try the new OTA update, but I also read that this requires all the bloatware to be back where it was when I got the phone. So, I went in to Titanium Backup and managed to restore a few of the files, but most of the time, when I try to restore a file, I get the little spiny animation forever. I've tried a couple different Busybox versions, direct access and indirect access. Nothing seems to help. In the future I plan to explore other backup solutions, but for now, I'm stuck with all these backups I can't restore. So, now I guess I need to know a way to manually restore the backed up files. Any ideas?
Try Pete's Root Tools and there is a restore system app option
So that app will use the titanium backups? Happen to have a link for that app?
Its not an app, you connect your D3 to the computer and run the batch script. I cant post links cuz I'm on my phone but i believe Pete posted it in a thread called "unroot" i'll edit my post if i can find it.
morse coded via my DROID 3
http://forum.xda-developers.com/showthread.php?p=17137213
Unroot?
Thats the thread the .exe file is located in. Its not an app, you connect your d3 to the computer and run the batch script. It'll provide you with instructions to restore missing system apps.
morse coded via my DROID 3
Download Pete's Motorola Root Tools:
http://dl.dropbox.com/u/6643359/Software/Android/PetesMotorolaRootTools_v1.06.zip) <-- for win 7/vista
Download DROID3 original system apps (5.5.959):
http://www.fileserve.com/file/M5jnR7X/DROID3_original_system_app.zip
Extract the DROID3_original_system_app.zip to a folder called system that's in the same location you extracted PetesMotorolaRootTools too.
Then connect your phone to your computer and run the tool. Click this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It gets stuck on the first step
SEARCHING FOR THE PHONE (connect it now if you haven't yet)... found!
Running fix step 1 of 4 (setting up symlink)...
Click to expand...
Click to collapse
Played around with it some more and got it to work. Thanks everyone!
LaTropa64 said:
Download Pete's Motorola Root Tools:
http://dl.dropbox.com/u/6643359/Software/Android/PetesMotorolaRootTools_v1.06.zip) <-- for win 7/vista
Download DROID3 original system apps (5.5.959):
http://www.fileserve.com/file/M5jnR7X/DROID3_original_system_app.zip
Extract the DROID3_original_system_app.zip to a folder called system that's in the same location you extracted PetesMotorolaRootTools too.
Then connect your phone to your computer and run the tool. Click this:
Click to expand...
Click to collapse
Hi there,
How do I execute the tool?
Thanx
Edit- I get a message saying the files must be saved in a /restore/ folder but I can't figure out why my windows XP (32 bit) wont let me use a "/" to create a file??
Am I missing something?
Help??
/ indicates file path. You dont need to type it into the file name. Just place the restore folder inside of the main folder, and extract all the apk's to it.
morse coded via my DROID 3
Lars1967 said:
Hi there,
How do I execute the tool?
Thanx
Edit- I get a message saying the files must be saved in a /restore/ folder but I can't figure out why my windows XP (32 bit) wont let me use a "/" to create a file??
Am I missing something?
Help??
Click to expand...
Click to collapse
The directory you run the tool from to restore the system apps should look like this:
Also, if you are on XP, make sure you are using the file for XP (found here: http://www.psouza4.com/droid3/) and not the one for Vista/7 that I linked to in my original post.
Thanks for the reply.
The Win 7/Vista version installed and launches on my XP machine and gives me the restore option pictured in your post.
The XP version you linked me to does not include the restore function (as far as I can tell).
Can I try using the 7/Vista file or will it bork my phone.
Also, will this wipe my phone?
TIA
Please, cant download DROID3_original_system_app.zip anyone has it??
So what happened is that update 5.11.401.10 rolled out today, so I went ahead and started installing the update but I didn't have enough time since I was going out to work so I cancelled the update and decided to start again once I reach the office... But when I tried to restart the update in the office I kept getting a massage saying that update is corrupted, so i restarted the phone, cleared the update cach but I still same problem.
I read somewhere that the only way to solve this is by a phone rest, and since my phone isn't rooted I cant manually go and delete the system update folder..
So is there a way to fix this..
Flash your nandroid backup & then you can start fresh.
Sent from my HTC One using Tapatalk
Element x said:
So what happened is that update 5.11.401.10 rolled out today, so I went ahead and started installing the update but I didn't have enough time since I was going out to work so I cancelled the update and decided to start again once I reach the office... But when I tried to restart the update in the office I kept getting a massage saying that update is corrupted, so i restarted the phone, cleared the update cach but I still same problem.
I read somewhere that the only way to solve this is by a phone rest, and since my phone isn't rooted I cant manually go and delete the system update folder..
So is there a way to fix this..
Click to expand...
Click to collapse
Delete the OTA file from downloads folder
Delete ota file
Delete updater app & download app data in applications
Wipe cache in stock recovery reboot
from HTC One
ghostryder12 said:
Flash your nandroid backup & then you can start fresh.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
can I do a nandroid backup now and then reset...or will it backup the corrupted file and install it later??
Sent from my HTC One using Tapatalk
SaHiLzZ said:
Delete the OTA file from downloads folder
Click to expand...
Click to collapse
I can't see the ota file in the downloads folder, I am using Es file explorer.
btw I am viewing the local download folder on the phone storage..
Sent from my HTC One using Tapatalk
It wont be in the download folder yet as you didn't finish downloading it, it will be somewhere like data/local/tmp, must be a temp folder somewhere until its completed, im surprised it doesn't give you the option to redownload if its informing you the download is corrupt.
If you don't have a nandroid from a previous Rom, you can't do one now. A nandroid is a "copy" of a Rom. Doing one now will save the screwed up Rom.
When you get your phone back working correctly, then make a nandroid. I update my nandroid at least once a week. I keep 2 nandroids on my SD card and delete the oldest after making a new one.
As far as the download folder not displaying the OTA file, do you see anything in that file?
Sent from my HTC One using Tapatalk
Seanie280672 said:
It wont be in the download folder yet as you didn't finish downloading it, it will be somewhere like data/local/tmp, must be a temp folder somewhere until its completed, im surprised it doesn't give you the option to redownload if its informing you the download is corrupt.
Click to expand...
Click to collapse
I'll poke around the temp folder see if I find anything, as for asking to download once press download it just shoes the same massage again doesn't matter how many tries I do... I attached a screenshot wonder if it will work..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HTC One using Tapatalk
Ever since I updated to the latest firmware (magisk rooted) my Galaxy Tab S8+ can no longer use Smart View or second screen. It worked fine on the previous firmware version even when rooted.
I've seen a suggestion to add "wlan.wfd.hdcp = disable" to the build.prop file, but I can't seem to edit build.prop even using a root explorer, or not even by using the twrp file manager. I've tried using various buildprop editors, granted them root access yet they still don't seem to be able to change anything in the file.
Is there any other possible fix?
The open source Material Files file manager has been repeatedly and highly recommended in my phone's XDA section for true root file management. https://github.com/zhanghai/MaterialFiles
It's also available through F-Droid, and the Play Store. https://play.google.com/store/apps/details?id=me.zhanghai.android.files
A lot of root file manager either haven't been updated (or aren't allowed to be - not sure what the story is) to really do full root file management.
Hope this helps. Note, I've installed this app but haven't really done anything with it yet.
Thanks for suggestion, but even using Material Files I still get the same error. I granted file access permission and root access to the app, I clicked Remount as RW but it still gives me an error saying read-only file system.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That is probably because root permissions have been lost. When you root the device and then flash new update it will usually revoke the root access and you have to re-root again with updated root method. Reason is becuase update affects the root access by reseting it. Since if root method has edited any system files to gain root access then update writes over those files which is why root access becomes revoked.
So my suggestion is to re-root your device and try editing same file again and I bet issue you got will be gone.
emko7 said:
Thanks for suggestion, but even using Material Files I still get the same error. I granted file access permission and root access to the app, I clicked Remount as RW but it still gives me an error saying read-only file system.
View attachment 5651197
Click to expand...
Click to collapse
I get the exact same thing when I tried to save the modified boot.prop with Material Files, so you're not alone.
Jake.S said:
That is probably because root permissions have been lost. When you root the device and then flash new update it will usually revoke the root access and you have to re-root again with updated root method. Reason is becuase update affects the root access by reseting it. Since if root method has edited any system files to gain root access then update writes over those files which is why root access becomes revoked.
So my suggestion is to re-root your device and try editing same file again and I bet issue you got will be gone.
Click to expand...
Click to collapse
I definitely have root access, I granted root permissions to Material Files, but I got the same result when trying to save an edited boot.prop.
@emko7
Edit 1: I just remembered that there is a Magisk Module out there folks have used on Android 12 (at least on the Pixel 6 Pro, which I have) that "emulates" having full root access. i.e. to my understanding, you don't actually do anything permanant to the files that require root, but it effectively acts as if you did. If you edit the boot.prop, technically it doesn't save to the actual original location, but your changed version is remembered and substituted when you boot/reboot.
I haven't re-located what the name of the Magisk Module is - I know it's been mentioned many times in the Pixel 6 Pro section, but I'm not sure if I can come up with the correct search terms to find the posts.
*Some* Android FIle Managers, like my preferred one X-Plore File Manager, makes it look like saving an edited boot.prop worked, but after a reboot I saw that the boot.prop edit clearly wasn't permanent. It's possible and probable that if I just re-loaded the edited boot.prop, I would've seen that my changes weren't saved, either.
Edit 2: After a tiny bit of research, I think it's possible this is the reason full root access doesn't give us r/w access to everywhere is the information presented in this Twitter thread (read the additional comments by Magisk's creator):
https://twitter.com/i/web/status/1170404631865778177
Click to expand...
Click to collapse
If battery cpu limit is enabled smartview probably won't work
Catmobile said:
If battery cpu limit is enabled smartview probably won't work
Click to expand...
Click to collapse
How exactly would you disable the "cpu battery limit"?