Hi,
Is there anyway to edit build.prop and enable the HAL3 flag from 0 to 1 without unlocking bootloader and installing TWRP? I want to get GCam for this device.
please help
Editing system files as build.prop requires you have superuser rights, means Android is rooted.
FYI: You don't have to flash TWRP at all, simply booting into it does it.
Thanks for the info, I'm guessing there's no way to edit that one solimple line without rooting or loading Into TWRP. And since it's like impossible to unlock bootloader for Huawei, I'm not gonna chance it.
Related
Ok so I have a friend that bought the pixel via verizon, and took it onto Tmobile. Trying to unlock the hotspot tether via build.prop edit.
The Pixel (Was on Android 7.1) has been unlocked via dePixel8 and rooted via Chainfire. Root Checker also verifies this.
However, whenever we try to access the build.prop through Root Explorer, ES File Manager, and the like, SuperSU prompts and gives root access but no way to save an edited build.prop.
I tried mounting /system as R/W via multiple adb commands which were unsuccessful, I think due to the new partition scheme. I don't remember the commands I used, I googled for them and have since closed those tabs.
Thought that maybe the root messed up somehow so re-did the Chainfire root with no change to the system, in fact it even seems like root is even more broken with ES File Manager no longer able to view the root directory.
We are currently downloading the google edition NDE63V Factory Image in hopes of getting rid of any hidden Verizon security "features" that may be causing this issue along with getting rid of the Verizon bootloader.
All OTAs will be sideloaded after we put on NDE63V Image to protect from a Verizon bootloader being placed back onto the phone.
Has anyone else with Verizon Pixel had issues with root features and troubles mounting anything as R/W? Any ideas on a possible fix without needing to flash NDE63V?
There's no Verizon-specific build.prop security feature to my knowledge. The command "mount -o rw,remount /system_root" should work. If it fails, can you post the error you get?
dnbonds said:
Ok so I have a friend that bought the pixel via verizon, and took it onto Tmobile. Trying to unlock the hotspot tether via build.prop edit.
The Pixel (Was on Android 7.1) has been unlocked via dePixel8 and rooted via Chainfire. Root Checker also verifies this.
However, whenever we try to access the build.prop through Root Explorer, ES File Manager, and the like, SuperSU prompts and gives root access but no way to save an edited build.prop.
I tried mounting /system as R/W via multiple adb commands which were unsuccessful, I think due to the new partition scheme. I don't remember the commands I used, I googled for them and have since closed those tabs.
Thought that maybe the root messed up somehow so re-did the Chainfire root with no change to the system, in fact it even seems like root is even more broken with ES File Manager no longer able to view the root directory.
We are currently downloading the google edition NDE63V Factory Image in hopes of getting rid of any hidden Verizon security "features" that may be causing this issue along with getting rid of the Verizon bootloader.
All OTAs will be sideloaded after we put on NDE63V Image to protect from a Verizon bootloader being placed back onto the phone.
Has anyone else with Verizon Pixel had issues with root features and troubles mounting anything as R/W? Any ideas on a possible fix without needing to flash NDE63V?
Click to expand...
Click to collapse
Might as well use the latest factory image. (7.1.1 build NMF260)
I updated to the latest build with a clean install. Installed TWRP. Rooted with SR5. Then did the build.prop edit and it's working fine for me. (Verizon Pixel on Verizon's network)
Hi Guys,
I was planning to root my phone but I don't want to do a factory reset. Is there any possibility to edit the build.prop without root? The only reason I wanted to root is to enable on screen navbar and disable the hw buttons. I hate them
If anyone has any solution for this, i would forever be in debt to you
Thank you!
Dan
No, build.prop is a system file and thus requires root to edit
Hello I would like to know if there is a way to spoof in Android Oreo I have recently purchased a Verizon Google pixel 2 (5 inches) I have already unlocked bootloader, rooted with magisk, I have pass the app to priv-app with the right permissions.
At the appninjas help from Fake GPS Joystick says Oreo users have to edit 2 xml files one you have to create and the another edit from Permissions folder. I already did but I still can't use it. Maybe I'm doing something wrong.
The app launchs but I can't enable the private mode and I get the GPS error at game and nothing appears when I activate the Fake GPS already cloned of course with the own apk tool privacy.
I upload the xml files already edited I don't know if I made it correctly
I faced this problem after updating to 8.1 on my Oneplus 5T. I used Magisk module App systemizer terminal to succesfully move Gps Joystick app to /system/private app. So now spoofings working again without location errors and without smalipatcher (not compatible yet with 8.1).
I think this will work on other 8.1 roms too.
I just got a OnePlus 5t and updated to Oreo. I just want to check a few steps:
1. Unlock bootloader
2. Install twrp
3. Root with magisk
4. Move to system / priv-app with twrp (or should I use the magisk module?)
5. Run the game
Is that correct?
I have a note 3 working properly with the steps I mentioned above. Is it all I need?
I'm quite new to using a phone without root, so is there a possibilty to add apks to system without rooting?
I tried ADBFastbootTools but it seems like it won't add anything. No apk and also no new folder.
Impact7 said:
I'm quite new to using a phone without root, so is there a possibilty to add apks to system without rooting?
I tried ADBFastbootTools but it seems like it won't add anything. No apk and also no new folder.
Click to expand...
Click to collapse
System partition is write protected. Not only Root is needed, you need a systemlees system like Magisk for example to not break dm-verify. Another option should be a rooted phone with dm-verify disabled.
In both cases, you will need a unlocked bootloader and root
I want to edit hosts file in my non-rooted Android device.
Since flashing a Custom ROM is basically installing a new OS, I was wondering,
Is a hosts file already present in a Custom ROM or is it generated later and at what point?
If it is preincluded in the ROM, is it possible to edit that hosts file and then flash the ROM, basically editing the hosts file without rooting?
parker_04 said:
I want to edit hosts file in my non-rooted Android device.
Since flashing a Custom ROM is basically installing a new OS, I was wondering,
Is a hosts file already present in a Custom ROM or is it generated later and at what point?
If it is preincluded in the ROM, is it possible to edit that hosts file and then flash the ROM, basically editing the hosts file without rooting?
Click to expand...
Click to collapse
Some custom ROMs do include custom hosts files, and you could potentially edit it before flashing the ROM. I'm not sure why you'd want to use a custom ROM without root, though - with root access, you can use a hosts manager like AdAway to update your hosts file on the fly.
V0latyle said:
Some custom ROMs do include custom hosts files, and you could potentially edit it before flashing the ROM. I'm not sure why you'd want to use a custom ROM without root, though - with root access, you can use a hosts manager like AdAway to update your hosts file on the fly.
Click to expand...
Click to collapse
(I am a newbie in rooting and flashing Custom ROM so please correct me)
Well my main objective is to edit the hosts file.
I understand it generally require root privileges but I want to use rooting as a last resort.
I am already going to flash Xiaomi Eu ROM in my Redmi Note 11. And if it is possible to edit the hosts via the ROM, wouldn't it be a better alternative than rooting? As with rooting, there also comes some consequences like tripping SafetyNet which I would gladly like to avoid.
parker_04 said:
(I am a newbie in rooting and flashing Custom ROM so please correct me)
Well my main objective is to edit the hosts file.
I understand it generally require root privileges but I want to use rooting as a last resort.
I am already going to flash Xiaomi Eu ROM in my Redmi Note 11. And if it is possible to edit the hosts via the ROM, wouldn't it be a better alternative than rooting? As with rooting, there also comes some consequences like tripping SafetyNet which I would gladly like to avoid.
Click to expand...
Click to collapse
SafetyNet is no longer relevant; it has been replaced by Play Integrity. See this thread. Even so, it is possible to pass Play Integrity BASIC and DEVICE attestation using the Universal SafetyNet Fix Magisk module.
I'm rooted with Magisk 25.2 on my Pixel 5. I use AdAway to manage my hosts file, and USNF 2.3.1 MOD 2, and I have zero issues with Play Integrity.
O
V0latyle said:
SafetyNet is no longer relevant; it has been replaced by Play Integrity. See this thread. Even so, it is possible to pass Play Integrity BASIC and DEVICE attestation using the Universal SafetyNet Fix Magisk module.
I'm rooted with Magisk 25.2 on my Pixel 5. I use AdAway to manage my hosts file, and USNF 2.3.1 MOD 2, and I have zero issues with Play Integrity.
Click to expand...
Click to collapse
I see.
But SafetyNet/Play Integrity is only one of the consequences of rooting. In Xiaomi devices, the warranty remains intact even after unlocking bootloader unless the device is rooted.
I am happy with flashing Custom ROM with edited hosts file without rooting.
I can always root my device later if this doesn't work.
Unless there is some other drawback which I am not aware of. If there is, please inform me so I don't end up in a mess.
parker_04 said:
I see.
But SafetyNet/Play Integrity is only one of the consequences of rooting. In Xiaomi devices, the warranty remains intact even after unlocking bootloader unless the device is rooted.
Click to expand...
Click to collapse
How would they know whether you rooted the device?
I can see how flashing custom firmware could void the warranty, like Samsung...So I suppose I've answered my own question as rooting would ostensibly involve either patching the boot image or installing SU to system. But, if you're editing a hosts file, you're also changing the system image, so I would assume that this would do the same thing.
parker_04 said:
I am happy with flashing Custom ROM with edited hosts file without rooting.
I can always root my device later if this doesn't work.
Unless there is some other drawback which I am not aware of. If there is, please inform me so I don't end up in a mess.
Click to expand...
Click to collapse
Well, as I pointed out above, you're making modifications to the software. If you're concerned about the warranty, don't use ANY modified software on your device, and keep your bootloader locked. You can't have your cake and eat it too.