Hello masters,
I am here with a simple question, since Pixel 2 XL I have been unlocking boot loader, rooting with Magisk, and then editing the System/Build.prop file in order to enable Wifi Hotspot Native tethering. I got a new Pixel 6 and am wondering if I can edit the System/Build.prop file without unlocking boot loader or rooting the pixel 6 currently running android 13 with the latest patch as of Sep 2022.
Thank you in advance for your suggestions.
Sincerely,
Nope, no read/write access without root.
Cheers
@tom1807 ,
I actually don't agree with that, I believe it might be possible to write to the Build.prop without rooting. Especially if you can install a custom recovery image such as TWRP, because it will allow me to mount the system/Build.prop file and that way make the changes on the file save it and then unmount the system/Build.prop file?
Has anyone else experienced this scenario?
I tested it before I wrote my comment.
Filemanager without root access, saw the build.prop, but opening stated "Unable to read file." Access the build.prop with the same filemanager with root access was able to open the build.prop and show the content incl. editing.
There is no TWRP (yet) available for the Pixel 6-series, but installing that would require to unlock the bootloader.
Cheers
@tom1807 ,
Noted, if I am not able to install a custom recovery on the Pixel 6 with Android 13 then I am definitely out of luck, I wanted to avoid unlocking the bootloader because it will wipe/erase all the current data apps, etc on the Pixel 6 and I really want to avoid that.
Thank you very much for the information.
Sincerely,
Lol os13 even not possible with root access
Its depends on brands too
Like in oneplus os12 not even possible with root access twrp and also many other things to get rw
I'll pay to you or any other person if you or he can get rw in os12
So don't even think about without root edit build or modifications
@Mr Hassan,
OS 12 and OS 13 I am guessing you mean Android 12 and Android 13, in any device, not just the Pixel 6 (which is the device I am working on at the moment)?
Thank you,
Mr Hassan said:
Lol os13 even not possible with root access
Its depends on brands too
Like in oneplus os12 not even possible with root access twrp and also many other things to get rw
I'll pay to you or any other person if you or he can get rw in os12
So don't even think about without root edit build or modifications
Click to expand...
Click to collapse
No idea about OS12 on OnePlus, but I can assure you, that I was able to edit my build.prop with root access.
Maybe you use the wrong filemanager (I use FX) or don't have root access.
FX is able to switch to R/W access.
Cheers
jairunet said:
@Mr Hassan,
OS 12 and OS 13 I am guessing you mean Android 12 and Android 13, in any device, not just the Pixel 6 (which is the device I am working on at the moment)?
Thank you,
Click to expand...
Click to collapse
Op have very bad partitions table its on RO its blocks not sys parts to edits
The matter is not about editor
I can also try with pull then edit via pc notepad++ and try push but error not enough space
Or su not found or not accessible etc
tom1807 said:
No idea about OS12 on OnePlus, but I can assure you, that I was able to edit my build.prop with root access.
Maybe you use the wrong filemanager (I use FX) or don't have root access.
FX is able to switch to R/W access.
Cheers
Click to expand...
Click to collapse
Build prop edits still work ?
JazonX said:
Build prop edits still work ?
Click to expand...
Click to collapse
The system partition is read only and not even Root Explorer was able to fix that. With Magisk however I believe some files can be copied into a particular folder and run from there in place of the originals. Build.prop is almost certainly one of them.
I am rooted and I can't freaking access the damn thing either.
I'm thinking of downgrading the os to twelve. Won't give me read write access even with root.
dragonsouce said:
I am rooted and I can't freaking access the damn thing either.
I'm thinking of downgrading the os to twelve. Won't give me read write access even with root.
Click to expand...
Click to collapse
I haven't tried it, but there's this...
GitHub - HuskyDG/magic_overlayfs: Make system partition become read-write (it is also possible without Magisk)
Make system partition become read-write (it is also possible without Magisk) - GitHub - HuskyDG/magic_overlayfs: Make system partition become read-write (it is also possible without Magisk)
github.com
Related
alright so i know what rooting is , my understanding is that before rooting i won't have administrative access to parts of the file system i think that means that
i'll only have access to "/mnt/sdcard" and not to "/"
after rooting i'll have full access to the entire filesystem
i know why manufacutures dont want people playing around in there ,my understanding - many things break easily deleting something or changing some permison can "f" it up
i've been with android for 1 year and roughly 6 months ,been through an x10 a DHD
other various devices currently on the Mopho so im not a complete nub
i know how to root ,you install this ,push this ,do this , that etc
my question is how is the root part blocked and how is root acheived i dont mean how to root a certain device, i mean how do the exploits do what do they change ?
J35US said:
alright so i know what rooting is , my understanding is that before rooting i won't have administrative access to parts of the file system i think that means that
i'll only have access to "/mnt/sdcard" and not to "/"
after rooting i'll have full access to the entire filesystem
i know why manufacutures dont want people playing around in there ,my understanding - many things break easily deleting something or changing some permison can "f" it up
i've been with android for 1 year and roughly 6 months ,been through an x10 a DHD
other various devices currently on the Mopho so im not a complete nub
i know how to root ,you install this ,push this ,do this , that etc
my question is how is the root part blocked and how is root acheived i dont mean how to root a certain device, i mean how do the exploits do what do they change ?
Click to expand...
Click to collapse
Basically, the root section is blocked since it is set to r/o which normal user permissions cannot change. Rooting exploits change the system permissions and pushes the su binary in to give you superuser access which will then allow you full access to the system.
J35US said:
alright so i know what rooting is , my understanding is that before rooting i won't have administrative access to parts of the file system i think that means that
i'll only have access to "/mnt/sdcard" and not to "/"
after rooting i'll have full access to the entire filesystem
i know why manufacutures dont want people playing around in there ,my understanding - many things break easily deleting something or changing some permison can "f" it up
i've been with android for 1 year and roughly 6 months ,been through an x10 a DHD
other various devices currently on the Mopho so im not a complete nub
i know how to root ,you install this ,push this ,do this , that etc
my question is how is the root part blocked and how is root acheived i dont mean how to root a certain device, i mean how do the exploits do what do they change ?
Click to expand...
Click to collapse
as far as I know, Stock rom's don't have a root function implemented at all.
to get root access, people use exploits to change permissions of the folders to gain access to the System partition, and then the SU (superuser) binaries are put into /system/xbin , and then install the superuser.apk (to make use of the su binary)
EDIT:
Damn ninjas
so rooting is basically changing a few permisions of folders that i wont normally have access to in order to put the SU binary into the fore mentioned path
just re itarating to make sure i understand
additionally if i won't normally have access to these folders then how do they change the permissions <-- maybe pushing it but ask an you shall receive
J35US said:
so rooting is basically changing a few permisions of folders that i wont normally have access to in order to put the SU binary into the fore mentioned path
just re itarating to make sure i understand
additionally if i won't normally have access to these folders then how do they change the permissions <-- maybe pushing it but ask an you shall receive
Click to expand...
Click to collapse
You could say it like that but it grants you far more access and unlocks many possibilities making you the superuser. Rooting uses exploits which bypass these set permissions.
hi all,
I'm on a rooted nexus 7 running Lollipop and I'm trying to move some apps to the priv-app folder however I seem to be unable to create or copy any files in the system folder (or subfolders) at all. I can for instance create a folder in root but not in system. Always says 'failed', I tried ES, and Root explorer, including the built in scripts of those apps which try to move the apk themselves. Screenshot attached. Any ideas? Thanks
@bthere79,
It seems to me that you probably don't have Hidden Files and/or Root Explorer enabled in ES File Explorer. Check out my post here, and click on the two "here" links for complete instructions on how to accomplish that.
:good:
thenookieforlife3 said:
@bthere79,
It seems to me that you probably don't have Hidden Files and/or Root Explorer enabled in ES File Explorer. Check out my post here, and click on the two "here" links for complete instructions on how to accomplish that.
And don't forget to hit "Thanks!" on the bottom-right of this post! :good:
Click to expand...
Click to collapse
thanks for the answer but doesn't really help, that was all enabled already and I was mainly using Root Explorer anyway.
Anyone can help? thanks
You do know that the new security updates in android 5.0 has far stricter root restrictions. That folder may no longer be able to be edited by 3rd party apps
zelendel said:
You do know that the new security updates in android 5.0 has far stricter root restrictions. That folder may no longer be able to be edited by 3rd party apps
Click to expand...
Click to collapse
no i did not know.... surely there's a way round that? If that's the case I'd imagine other people would want to override that? That would mean you can't uninstall bloatware etc.
bthere79 said:
no i did not know.... surely there's a way round that? If that's the case I'd imagine other people would want to override that? That would mean you can't uninstall bloatware etc.
Click to expand...
Click to collapse
Could be why Google is trying to make them install them so they can be removed.
It could be just that the root apps need to be updated. Many 3rd party apps are having issues with stock things. Like heads up. So it could just be the apps need to be updated
Probably has something to do with SELinux Mode. I'm using an unofficial version of CM12 on my 1+1 and it was already set to permissive, but I tried the SELinux Mode Changer and it did work to change it back to Enforcing, so seems like it does work on Lollipop, despite that it doesn't technically support it (it also says it doesn't work with Samsung devices with Knox, though I have used it on dozens without issues). I would try and use that to change to permissive, and then you should be able to make changes to the system easier.
https://play.google.com/store/apps/details?id=com.mrbimc.selinux
es0tericcha0s said:
Probably has something to do with SELinux Mode. I'm using an unofficial version of CM12 on my 1+1 and it was already set to permissive, but I tried the SELinux Mode Changer and it did work to change it back to Enforcing, so seems like it does work on Lollipop, despite that it doesn't technically support it (it also says it doesn't work with Samsung devices with Knox, though I have used it on dozens without issues). I would try and use that to change to permissive, and then you should be able to make changes to the system easier.
https://play.google.com/store/apps/details?id=com.mrbimc.selinux
Click to expand...
Click to collapse
thanks i'll give it a go
es0tericcha0s said:
Probably has something to do with SELinux Mode. I'm using an unofficial version of CM12 on my 1+1 and it was already set to permissive, but I tried the SELinux Mode Changer and it did work to change it back to Enforcing, so seems like it does work on Lollipop, despite that it doesn't technically support it (it also says it doesn't work with Samsung devices with Knox, though I have used it on dozens without issues). I would try and use that to change to permissive, and then you should be able to make changes to the system easier.
https://play.google.com/store/apps/details?id=com.mrbimc.selinux
Click to expand...
Click to collapse
didn't make any difference any other ideas?
I'm new to Android on PC, so the question. (I'm somewhat versed in Linux, though.)
Why the need to root Remix OS for PC, if we can become root by pushing Alt+F1?
When I open the Terminal, I get [email protected] /$, while Alt+F1 gives me [email protected]_86_64:/#
I couldn't become root by writing su in the Terminal, but would be root in Alt+F1. Additionally, what are the commands in Android/Remix OS?
What advantages you get by rooting the hard disk installation?
There are a lot of different apps out there that require root permissions to function. While many of them would not really be applicable to RemixOS, or at least could be worked around using the root console, others still have their uses. For one, I'd rather trust Titanium Backup to backup my app data rather than manually copying things with the root console.
Granted, the root console is a very useful feature and does allow for a lot of tweaking, but without app access it's not the full story.
Actually, I want to, that what is the benefit if I am using root console
atiqursumon said:
Actually, I want to, that what is the benefit if I am using root console
Click to expand...
Click to collapse
Being able to take ota's without returning to the stock system.img. But you can tweak more if you have a rooted system.img.
Remix OS is a "desktop" user experience, and anywhere in the desktop's i want my Administrator rights .
The idea to root our phones/tablets came from the experience from the desktop era.
Personally, i think Root should be at least a choice officially for RemixOS
PlutoDelic said:
Remix OS is a "desktop" user experience, and anywhere in the desktop's i want my Administrator rights .
Personally, i think Root should be at least a choice officially for RemixOS
Click to expand...
Click to collapse
I would also like to have Administrator rights. If I root the system.img, rename it from root.img to system.img, would I be able to become root in the Terminal? If so, what would be the command? Is it su? Can I make a user, or rename the user from u0_a77 and can I change localhost to some other name? What would be my root password?
Right now, I can get to root terminal by Alt+F1, but I feel as the root is at Jide, and they can do whatever without my knowing it. The password for root is there, not with me. I am thinking the Linux way here. Android is anyway Linux, most probably Gentoo.
I don't use a tablet, only an android phone, and the only time I go to internet is to check the bus timetable. Never thought of rooting the phone. Now with Remix OS, and Phoenix OS, I'd like to dig in. Hopefully, with you guys help.
ostrolk said:
I would also like to have Administrator rights. If I root the system.img, rename it from root.img to system.img, would I be able to become root in the Terminal? If so, what would be the command? Is it su? Can I make a user, or rename the user from u0_a77 and can I change localhost to some other name? What would be my root password?
Right now, I can get to root terminal by Alt+F1, but I feel as the root is at Jide, and they can do whatever without my knowing it. The password for root is there, not with me. I am thinking the Linux way here. Android is anyway Linux, most probably Gentoo.
I don't use a tablet, only an android phone, and the only time I go to internet is to check the bus timetable. Never thought of rooting the phone. Now with Remix OS, and Phoenix OS, I'd like to dig in. Hopefully, with you guys help.
Click to expand...
Click to collapse
Yes, root is su; no there isn't a password (conditional access to SU is what apps like SuperSU are for - you could password protect apps if you really wanted to).
The u0_a* is the owner/group of the app itself, every app gets its own owner/group (I think this is part of the selinux security measures; despite RemixOS running with SELinux off (permissive)).
I have systemless root working if anyone wants to try; just writing a short how to atm.
HypoTurtle said:
Yes, root is su; no there isn't a password (conditional access to SU is what apps like SuperSU are for - you could password protect apps if you really wanted to).
The u0_a* is the owner/group of the app itself, every app gets its own owner/group (I think this is part of the selinux security measures; despite RemixOS running with SELinux off (permissive)).
I have systemless root working if anyone wants to try; just writing a short how to atm.
Click to expand...
Click to collapse
Being in permissive mode means SELinux allow more access to the system. Sometimes having SELinux enforcing affects performance because it will deny the system access to certain modules like Bluetooth, WiFi, etc. Also you can set a password in SuperSU and set apps so they always ask for permission before granting root access you have to enter the master password.
HypoTurtle said:
I have systemless root working if anyone wants to try; just writing a short how to atm.
Click to expand...
Click to collapse
Yes, I would like that. If you could write about the commands, it would be much nicer.
ostrolk said:
Yes, I would like that. If you could write about the commands, it would be much nicer.
Click to expand...
Click to collapse
I've posted it here at the top; it will take me a while to get a 32bit setup built though...
Not sure my question in subject is clear, so here's the thing...
I have dual-boot tablet with Android 5.0.1 and Windows 10 installed, and the model is Onda V80 Plus (32GB), if that matters at all.
I'm really having hard time rooting this device using standard methods (even with much of background knowledge and experience), so I was about to take a different route.
I installed Paragon ExtFS windows app which gives me read/write access to /system and /data android partitions (which have ext4 filesystem).
I was wondering if anyone knows if it's possible to gain root access in Android just by copying some files and changing some permissions or whatever from within Windows OS?
Basically, for those not familiar with ExtFS app, I can assign a drive letter to /system and /data partitions, and do whatever I want with them just like with any other drive or volume.
I'm aware that modifying ext4 partitions can render my Android OS unbootable, but I have a backup and would like to try it anyway as this is my last option.
When I look into SuperSU.zip file (which I always flashed through CWM/TWRP recovery to gain root access), I see many files which some lengthy script is copying all around, so I stopped after analyzing about hundred lines of code lol.
I really didn't find any method like this on the internet, so I wonder if that's even possible, and if it is, how would I go about it?
Thanks everyone.
Burs said:
Not sure my question in subject is clear, so here's the thing...
I have dual-boot tablet with Android 5.0.1 and Windows 10 installed, and the model is Onda V80 Plus (32GB), if that matters at all.
I'm really having hard time rooting this device using standard methods (even with much of background knowledge and experience), so I was about to take a different route.
I installed Paragon ExtFS windows app which gives me read/write access to /system and /data android partitions (which have ext4 filesystem).
I was wondering if anyone knows if it's possible to gain root access in Android just by copying some files and changing some permissions or whatever from within Windows OS?
Basically, for those not familiar with ExtFS app, I can assign a drive letter to /system and /data partitions, and do whatever I want with them just like with any other drive or volume.
I'm aware that modifying ext4 partitions can render my Android OS unbootable, but I have a backup and would like to try it anyway as this is my last option.
When I look into SuperSU.zip file (which I always flashed through CWM/TWRP recovery to gain root access), I see many files which some lengthy script is copying all around, so I stopped after analyzing about hundred lines of code lol.
I really didn't find any method like this on the internet, so I wonder if that's even possible, and if it is, how would I go about it?
Thanks everyone.
Click to expand...
Click to collapse
Root needs a custom kernel. Not something you are gonna do with a Windows setup the way you have it. Also you will most likely not find anything as that is most likely not an official version of Android as Google doesn't allow dual booting.
Thanks for a reply. But I don't see what does custom kernel have to do with what I try to achieve? If I could, in my Windows environment, replicate the modifications that script inside SuperSU zip does to /system partition, I should gain root access, right? In theory that is, since I'm aware lots of things can go wrong. I was hoping someone could explain a bit what SuperSU script is doing when run inside custom recovery, so I try to do the same thing. Again, if it's possible, and if it's worth the time spent. But I have time, and I'm always willing to learn something new.
Burs said:
Thanks for a reply. But I don't see what does custom kernel have to do with what I try to achieve? If I could, in my Windows environment, replicate the modifications that script inside SuperSU zip does to /system partition, I should gain root access, right? In theory that is, since I'm aware lots of things can go wrong. I was hoping someone could explain a bit what SuperSU script is doing when run inside custom recovery, so I try to do the same thing. Again, if it's possible, and if it's worth the time spent. But I have time, and I'm always willing to learn something new.
Click to expand...
Click to collapse
what su is doing is pulls the kernel and patches it. root access is defined in the kernel. what itnis doing in system is flashimg just the apk
Ok, I see. So if I ask someone who rooted the same model successfully to send me patched kernel, I could easily flash it in fastboot mode (my bootloader is unlocked). So only thing left to do would be to copy apk inside /system/app, and cross my fingers? I'll post my findings if I manage to do something worth writing about. Thanks.
I have same problem with you. I can't root my Onda V80 plus. I unlock bootloader, flash recovery for my device. Then, i put it into recovery mode and install supersu.zip over recovery. When i reboot this onda, it has stopped in onda logo.
bahuy2003 said:
I have same problem with you. I can't root my Onda V80 plus. I unlock bootloader, flash recovery for my device. Then, i put it into recovery mode and install supersu.zip over recovery. When i reboot this onda, it has stopped in onda logo.
Click to expand...
Click to collapse
I managed to root my Onda few days after my last post, but forgot to post my findings, sorry. I didn't used any of my hacker's skills lol, but I researched a bit more and found out what I was missing. The same issue is with you, so you have to disable verity before flashing recovery by typing in these commands:
Code:
adb root
adb remount
adb disable-verity
adb reboot
After rebooting install supersu.zip, and the next boot won't hang on Onda logo anymore. Hope this helps you.
btw, note that not just any adb version has verity command line switch. You have to download newer adb version!
Thank you! I trie a lots times, but i can't make successfully!
Basic root procedure would be: unlock BL -> disable verity -> flash (temp) recovery -> install SuperSU
Here are the links containing all the files neccessary for rooting Onda V80 Plus: Mega | MediaFire
Note the ReadMe.txt inside archive. It contains list of adb/fastboot commands needed to be executed in order to successfully root the device.
Thank you very much! I download your file and root successfully my Onda V80 plus! It works well for me.
hello ...
back for more question about pixel 6 : how do we mount system partition to r/w using any file explorer apps ? i have root access.
thank you !
I think you can't. Make a Magisk module and replace/edit things you want to
mailistman said:
hello ...
back for more question about pixel 6 : how do we mount system partition to r/w using any file explorer apps ? i have root access.
thank you !
Click to expand...
Click to collapse
As mentioned already, you can't and haven't been able to since Android 10. System partitions have the RO_COMPAT_SHARED_BLOCKS flag set. This is nicknamed the "dedup" flag, and the flag's behavior only works if the partition is read only. Not only that, the flag cannot be disabled due to insufficient space remaining in the partition. The lack of space has the side effect of making it impossible to ever set the partition as r/w.
thank you for the answers. i came from android Pie. so much learning curve & surprises with the 12.
Also wanted this. Thanks to community.
some system directory's can be mounted r/w if you have a root enabled file explorer. like root explorer. im not sure exactly which ones.
Rooting didn't harm the devices?
xikal12 said:
Rooting didn't harm the devices?
Click to expand...
Click to collapse
define harm?
AFAIK the pixel can always be put back to complete stock by flashing the factory rom back and re-locking the bootloader
Harm means the capability of the device. But got the point. Thanks.
So, did you got the point about harm?
physically no. as for software wise you will need to research.
i don't use my phone to pay for things or banking apps so i have never had any loss of use i find valuable.
security wise if you don't have your phone you don't have any security left anyways.
as for what damage you can do once you mount a system partition or other partitions, everything should be fixable with a fresh flash.
but then you take your chances with anything you do.
If you wanna listen all bulshitt about harm and so on - listen .If you wanna enjoy real root and debloat your phone I can drop to you all files (system,system_ext,product) with rw enable form may 5. Drop request in conversation.
Drop all of the files.
The best forum for information and sharing knowledge.
XDA forum is best.
cori12 said:
Drop all of the files.
Click to expand...
Click to collapse
Right now I'm on GrapheneOS Android 13 and have only stock Android 13 September update files with rw, no more android 12.