So I have ls997 as most may know already.
We all know it is not root able past ZV7.
Now to the question...
Since we are stuck for full root stock on 7.0, would it be possible just to flash the required SDK/ Libs from Oreo+ in order to be able to run Oreo+ required apks?
Sure there are manipulation apks that allow value changes, but those are half ass lol.
If this is doable, this would be an awesome work around.
Lineage is nice, but it has issues.
Related
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.
Hi, after over a year without unlocking my Moto G 5 Plus I'm eager to make the move to unlock and root it. But I've seen that things have changed quite a bit since the last time I rooted my old phone.
As far as I know unlocking the bootloader wipes the DRM keys for ever. What implications does that have? Is there any way to back them up before unlocking to restore them later? What won't work without them?
Will it influence Netflix and Banking apps like Mobilepay (Denmark)? From what I could find out Magisk can help to patch the system without being detected. How does Safety net detect system changes? How to prevent an accidental system change that would break SafetyNet? What about future updates to SaftyNet?
I'm mainly planning to unlock Camera2 API and Miracast. And also install XPosed and some audio enhancement mod if possible. Would any of these break SafetyNet? Would a 64bit ROM break SafetyNet?
Any information is highly appreciated.
My factory unlocked and rooted US996 USA is still running the original 10d firmware. I have Xposed framework with several mods and MK2000 kernel installed. I also have an unreliable USB C port connection that makes wired communication with my Windows 10 PC very iffy, especially for long procedures. I want to jump to Oreo and need some ideas on the best way to do it given the hardware problem. I absolutely must retain root or it's stay on Nougat. I would also very much like to reinstall the Xposed modules but will consider sacrificing them if necessary. Are there any viable update options or will the phone eventually die on Nougat 7.0?
hi, I've been happy with stock f/w since my first 2015 unit to current 2019 pro unit but going to root my 2019 pro to get smb r/w access. (as far as I know, official system support is limited to read only and only few apps which has its own smb mounter support write access. to find out this was a bummer because I settled with local smb setup to avoid rooting to get rclone! what a...)
so, after hours spent with google-fu, I learned few things and would like to see if I'm ready.
0. I'm on experience 9.1.1 with 2019 pro(mdarcy)
1. there's a magisk module which support what I want, but not sure if it still works. (probably will, but it was written 3 years ago.)
GitHub - dnfm/shield_samba_rw_mounter: Shield TV SAMBA R/W mounter.
Shield TV SAMBA R/W mounter. Contribute to dnfm/shield_samba_rw_mounter development by creating an account on GitHub.
github.com
2. to run that module, I need root priviledge for apps > magisk installed
3. to accomplish #2,
3.1. first have to unlock bootloader, then
3.2. flash twrp recovery or patched bootloader.
4.1. with root, I'll lose ota and ai upscaling in return.(although unrooting and revert back to stock won't hard too much, its not sure you can get ai upscaling back.)
4.2. widevine or safetynet won't be affected by bl unlocking or rooting.
but most articles I found was more than a year old and mentioning experience 8 with 2017 pro, so its not 100% sure.
I'm still not sure which is better and safer way to go, twrp or patched bootloader.
developer image(pre root, adb only) was considered in the first place but dropped because it seems there's no real benefit over consumer image but only could make conflict with magisk.
do you think I'm ready to go? or any advice?
shiree1 said:
hi, I've been happy with stock f/w since my first 2015 unit to current 2019 pro unit but going to root my 2019 pro to get smb r/w access. (as far as I know, official system support is limited to read only and only few apps which has its own smb mounter support write access. to find out this was a bummer because I settled with local smb setup to avoid rooting to get rclone! what a...)
so, after hours spent with google-fu, I learned few things and would like to see if I'm ready.
0. I'm on experience 9.1.1 with 2019 pro(mdarcy)
1. there's a magisk module which support what I want, but not sure if it still works. (probably will, but it was written 3 years ago.)
GitHub - dnfm/shield_samba_rw_mounter: Shield TV SAMBA R/W mounter.
Shield TV SAMBA R/W mounter. Contribute to dnfm/shield_samba_rw_mounter development by creating an account on GitHub.
github.com
2. to run that module, I need root priviledge for apps > magisk installed
3. to accomplish #2,
3.1. first have to unlock bootloader, then
3.2. flash twrp recovery or patched bootloader.
4.1. with root, I'll lose ota and ai upscaling in return.(although unrooting and revert back to stock won't hard too much, its not sure you can get ai upscaling back.)
4.2. widevine or safetynet won't be affected by bl unlocking or rooting.
but most articles I found was more than a year old and mentioning experience 8 with 2017 pro, so its not 100% sure.
I'm still not sure which is better and safer way to go, twrp or patched bootloader.
developer image(pre root, adb only) was considered in the first place but dropped because it seems there's no real benefit over consumer image but only could make conflict with magisk.
do you think I'm ready to go? or any advice?
Click to expand...
Click to collapse
I've tried for hours! I don't think it's possible to root experience 9. Followed and tried all examples( they are all old using version 8) but failed everytime, even the so called rooted Dev files appear to be normal unrooted os. Good luck, advise if you succeed.
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.