Hello,
I am trying to edit the build.prop on my AT&T Note 4 in order to trick the Oculus software into allowing me to connect a GearVR wireless controller by setting the model to be an S6 of some variant.
However, some research on the XDA forums suggests that this variant of the Note 4 is not permanently rootable. However, there was a few temporary root suggestions. As I only want to do this one specific thing, if I were to do a temporary root that was lost after reboot, would the changes to my build.prop persist through the reboot or would that also be reset when root access was lost?
Also if there is some better way to edit build.prop without needing root access (some people suggest that I could use a custom recovery but my understanding is that requires an unlocked bootloader which the SM-N910A does not have?)
Thanks
Related
Well today I was doing my root via Odin and used the auto root kernal that was provided for my phone, so I followed every step and it didn't work at all, besides the root not working I now got this problem on my wifi which you can solve via build.prop, the thing is that you need root to access this files as far as i'm concerned, there is no root for my phone else than the one I already tried, meaning I cannot fix my problem, I need help please!
Hi All
I was wondering whether someone could tell me whether this is likely to work before I spend hours trying...
My situation is that the echo / muffled voice issue is a CONSTANT issue for me - I bought on a contract rather than through Google, so would have to return to Huawei directly for "repair" - which I've already done once and pretty sure they just sent the phone back to me. Besides, I don't have a spare phone and setting up the phone again every time is a pain, especially as I use it for work and need to involve our IT to register and install [email protected]
It's this latter point which prevents me from rooting - the software audits and reports on rooting - so it'd get blocked and I'd get a slap on the wrist. Using RootCloak or similar is also not an option I'm willing to go down (my company deals in security things so this wouldn't go down well at all!).
So what I'm aiming to do is:
Modify build.prop to turn the noise cancelling mic off
Without wiping my device and having to install all my apps again
Without rooting
I've come across this: How to edit build.prop without root and I'm interested in whether the approach without root would work?
In short, it would involve booting into a custom recovery (TWRP?) temporarily through fastboot (without unlocking the bootloader as that wipes all my data), and then modifying the file via adb.
So - does anyone know whether this is a feasible option on the 6P?
Thanks!
What you may be able to do is unlock the bootloader. Once unlocked you can flash twrp recovery on the device (however do not root it when it asks if you want to). Then from there you should be able to pull and push a modified build.prop. However you will have to wipe your device in order to make it happen. That is the only way I could think of since the bootloader has to be unlocked in order to edit files on the nexus.
This won't work, even using adb to modify system files requires root.
Long story short: you can't do it. I'm pretty sure even using adb to modify system files requires root.
Grr - So I'm either stuck with a phone that I can use for emails / calendar for work, but doesn't work as a phone - or I have to root to make it work as a phone, but not use it for work
I'm not sure I have the energy or desire to keep sending this back for repair, only for them to not fix anything - it seems that some units just work, others don't.
OP, were you ever able to resolve this issue?
I have the same problem, got a replacement from Huawei for the bootlooping issue (same IMEI as before) and have the horrible microphone issue and don't want to root it.
I want to try the build.Prop quora.com thing as well but that is the only reference I have seen that claims to allow modification without root.
I have a Zenfone 3 ZC520TL US model phone (apparently there are multiple versions of the ZC520TL).
First question: Is there a LineageOS available for this phone? Or any plans for it? I don't see it listed on LineageOS's website. But there was a thread here a few months ago about it, although I'm not sure if that was specifically for the ZC520TL or the US specific ZC520TL.
Second question: Is it possible to root this phone? From the best I can tell, the only way to do this is with Magisk Manager, creating a patched boot image. Although, I'm not sure what the probability of bricking the phone is by doing this. I would assume you could always manually install the stock firmware, but I'm not sure if that would work.
Third: Is root even needed? The only reason I think I'd really need root is to enabling tethering on the phone. I'm currently with an MVNO that doesn't specifically allow tethering. I'm not sure how providers go about detecting tethering these days, I'm sure they probably could detect it regardless of whether the phone is rooted or not. But I rarely tether, in fact I rarely use over 1GB of data a month period. But the last thing I really want is to be stuck out some where when I have to be away from home for a few days and not being able to tether to my laptop for work. Or when I'm sitting outside an arm's length away from my home's wifi signal.
Do you still need to add the net.tethering.noprovisioning=true line to the build.prop file in order to tether?
Fourth: I used Asus's UnlockTool from their website. But I don't know if it truely unlocked the phone. When entering fastboot mode, I no longer see the message about CSC, I see a message that says FASTBOOT mode... But fastboot getvar unlocked still shows no. Although, I'm not sure if there is a TWRP for this phone or a LineageOS or alternative that would really necessitate any of this anyway.
To preface this I'm relatively new to this bootloader unlocking, in the past of i've rooted a galaxy s4, Note 2, S3, S4 mini, galaxy nexus, galaxy note 8.0 (tablet), and a galaxy tab 3. This is first device Ive had with a locked bootloader.
So we know that both old methods of unlocking the google pixel/XL no longer work:
dePixel8 is only supported up to android 7.1.0 http://theroot.ninja/depixel8.html
and the newer method of resetting the phone and connecting to the internet seems to be patched by Google/Verizon as well https://forum.xda-developers.com/pi...lock-bootloader-verizon-pixel-t3796030/page80
My ideas:
1. Is it possible to trick the the Verizon bootloader into thinking that android 10 is being flashed via adb sideload when in reality its android 7.1.0, perhaps by modifying the ota certificate, meta data and payload properties files? And then from use the dePixel8 method.
2. Has anybody given any thought into using the Qualcomm flashing software to flash a older version of the Verizon firmware or a non Verizon firmware version?
3. Is it possible to unlock the bootloader using a Sim from a certain provider?
Hi!
I have issue with app on my S7 Edge that demands me to unroot. I rooted my phone 5 years ago or more and I don't remember a thing about it. I did this to permanently remove bloatware. Only way I know to unroot is to flash stock-rom again but I don't want to loose my hard effort on debloating + data and so on. Is there any tricks for that? Like hide/remove su binary? I really don't remember where to start. Also with factory reset or something I cant remember I lost root access partially - that is apps can still tell that phone is rooted (root checker tells that root access is available but then also orange warning that root access is not properly installed on this device). But they can't request root privilege for some reason. But I still have this custom recovery rom installed where I have basically root access to phone - do you think I could use this to somehow hide temporarily root from my app that is complaining about it and then later restore root to the full - that is to make apps able to request root access again? I would like to keep my apps/data and I remember them getting lost in process of rooting due to some samsung encryption crap - not sure how to check data/app loss would be case now since I did it so long time ago. Could anyone help me out?
For documentation purposes. So in my case I had lost root with factory reset. I had to boot into TWRP and re-flash super su. Difference from official tutorial: https://forum.xda-developers.com/t/...ial-twrp-for-galaxy-s7-edge-hero2lte.3334084/ was that in step 9 my phone did not complain about dm-verity,. I did not have to disable encryption and I did not loose my data. Someone may correct me but it was because I had already rooted in past and the most likely cause for "loosing" root was doing factory reset. PS I have european model so I am not sure how much it makes this tutorial different.
Now what is left to do is come up with ideas how to hide root from 1 specific app in Android 7.