Hi there.
I was wondering if anyone could help me. I have installed Lineage 18.1 onto my S7 as I am trying to modernise my S7 since I have to downgrade to it for a while. However the Wear app doesn't work (system modified in an unauthorised way.)
I have seen a couple of threads on how to deal with this. I have rooted the device with magisk 25.2.
I have attempted to edit the build.prop folders as per post 7 in this guide: https://forum.xda-developers.com/t/galaxy-wearable-app-on-rooted-phone-help.3838503/
However the wear app wont even install now. I think it is picking up that the device is rooted even though I have set magisk to hide itself and I have added samsung apps to the deny list. I am not sure what I am doing wrong.
Alternatively I have see a thread here https://forum.xda-developers.com/t/...-for-samsung-phones-with-custom-roms.4208143/ that describes how to patch samsung apps. From what I can tell I am unable to do this as I am on a Windows system and not Linux. Is it possible someone could patch the GALAXY FIT 2 plug ins and the latest wear apk? The patched wear apk installs on my device but refuses to run without an update and the update never completes. It errors out. Again I have a feeling the update is picking up the device is rooted.
Any assistance with this would be much appreciated.
Related
Hi & thanks in advance for reading.
I over looked part of the post by rovo89. It states in large Red font that said Stock Samsung ROMS will almost always end in a boot loop.
I'm fairly new still to XDA and modular application.
So here's what happened.
I rooted my Galaxy S5 SM-G900P 6.01 then installed Xposed Installer and began to download a few modulars. Everything downloaded fine, my SuperSU worked just as it should. Then I noticed I didn't have Framework fully installed so through reading the XDA forums and my research on the web. Seemed that my only option was to option was to test the Xposed Installer Alpha 3.0 which brings me to my question.
(I understand the risks involved and blame no one but myself, but any advice would be great because I'm a noob.)
My situation - I installed the Xposed Framework zip for lollipop 5.0 ,5.1 & Marshmello 6.0 with my factory Samsung ROM then I downloaded the amv.87 patch because I assumed it was AMv7 and then I flashed it via FlashFire into my system and during the reboot I got BootLooped. Now I was foolish enough to not set up a backup or uninstall Xposed framework or Xposed disabled on my SD card... Now
My question what can I do to attempt to fix this, I have Odin 13.11 & I downloaded my factory ROM from Samsung & I downloaded the Xposed framework uninstalled zip on my laptop for a possible fix.
Is it possible I remove my SD card and transfer the Xposed uninstalled or Xposed disabled to my SD card on my laptop then boot up Recovery on my Galaxy S5 then try updating via my SD card?
I just don't want to ruin my phone since I feel like this is a possible fix even if it involves a format.
Thanks in advance I'm gonna keep trying to figure it out.:fingers-crossed::laugh:
I've come from owning iPhones my entire life. To bypass Jailbreak checks within apps all we did was install a .deb package from a repo (in most cases).
For Pokemon GO we had PokePatch.
For Snapchat we had Phantom (Phantom Lite nowadays).
And that was it.. you resprang your phone and your tweaks/apps were working. But after buying an S7 Edge (my first Android device ever) I've been getting super confused with getting Pokemon GO and Snapchat both working while being rooted. People are talking about systemless SuperSU which I understand, but also Magisk, but also suhide, but also pph super.
Could someone help me figure out how to get apps working (pass the Safetynet check) as of today? Coming from iPhone.. this is very confusing.
Note: I have latest TWRP installed for Recovery and adb is working perfectly. I also do not need Xposed. It would be nice to have, but if it makes things harder I can do without it.
You might want to check this link out.
Hey All,
I just got a new S7E from T-Mobile with Nougat pre-installed. I tried to root it using the method in this YOUTUBE Vid: https://www.youtube.com/watch?v=iC9wpPUl7A0
When I go to update the Binaries in SuperUSer, it fails and then everytime i try and start SuperUser after that, i get a message that says the Binaries are occupied. If i repeat the entire process and skip the updating of the binaries, then the device gets rooted though obviously the binaries are not getting updated. I wonder if anyone has any ideas what is happening?
Anyhow, the main question is, I want to install a Stable ROM without Bloatware and also would like to install TWRP. It appears that TWRP does not play fair with the Snapdragon versions of this phone, is that correct?
Can you guys and gals recommend which ROMS are the cleanest and most stable for this device,
Thanks,
Danny
Im hoping someone can help me or possibly direct me to a youtube video to achieve what im looking to achieve
I struggled with, but finally managed to upgrade my device to stock 7.0, but rooted with magisk. When i tried to install xposed it forced a bootloop, so i restored a backup i had just made prior, and all has been well. I had wanted to install and use "Root cloak" as, at least so far thats been working on my 8.0 device (also Samsung, also stock but rooted but with SU method in that case, i couldnt get SU alone to work on my 7.0, for whatever reason)
I left it alone, but I'm noticing more and more that apps Id like to use come up saying "device is incompatible", which at first i thought it was weird as the play store itself allowed the install... but then upon some basic looking around, it seems that the apps have a way of detecting root, even through "magisk hide" - the feature directly included in magisk manager.
currently when i try to test for safetynet directly in the magisk manager, it doesnt actually properly test at all, no pass or fail, it just said unable
the rather peculiar part is that some of these apps arent all even banking apps, theyre for games. I cant figure out why gaming apps have issues with root access, especially when these apps themselves dont have root access, but thats kind of an aside
Any simplified help anyone can offer would be great! i am slightly familiar with editing the build prop, but i wouldnt know which values to change or even if that method is still effective. i used to use that on a quite older device (captivate glide) to spoof which version of android i was on in order to download app updates (which did work just fine, so why my older version wasnt supported is beyond me, lol)
thank you in advance for any help you can offer!
I was bored one evening, so I started poking around on XDA Forums, and found a way to fix the battery issue I had with OnePlus 3T that made me switch to another device years ago! I was surprised how usable 3T is to this day. I thought I would breathe some life into it with LineageOS 18.1 that continues to receive security updates and patches. This way I will have a backup phone ready in case something happens to my OnePlus 6. It is unlikely that 3T will receive LOS 19, so this guide should stay relevant for a long time.
1) Get back to the latest version of Oxygen OS if you are on a custom ROM. Use something like MSM Download tool and then upgrade to 9.0.6 with the built-in updater.
2) Follow the instructions on los website to install LineageOS 18.1 and google apps via MindTheGapps. If you do not need google apps, then you probably do not care about SafetyNet and do not need this guide
Now the main issue is the SafetyNet. If you install YASNAC - Yet Another SafetyNet Attestation Checker you will see that the phone is not passing the SafetyNet verification, meaning that Google Pay will not work and some other apps, like banking apps, might not work either. We are going to fix that with Magisk and MagiskHideProps. Feel free to poke around on your own. I will just present that have worked for me.
3) Go to Magisk's Github, download the latest release and follow the installation instructions. (Notes: 3T has RAM Disk, there is no separate vbmeta, boot.img is inside lineage-18.1-xxxx.zip)
4) Once you have Magisk working, got to MagiskHidePropsConf and get the latest release there. Go to Force Basic Attestation Post and follow the installation instructions under the spoiler.
5) Now, let's get Basic Integrity to pass. Go to Basic Attestation Post and make sure to add both com.google.android.gms.unstable and com.google.android.gms to deny list. Reboot. Go to YASNAC. It should say that Basic Integrity is passing. CTS profile match is not, but that's okay.
6) Install terminal app like Termux. Open it, and run su to get superuser privilages. Then run props. Follow the instructions to Edit device fingerprint (option 1).
Edit Device Fingerprint (1)
Pick a certified fingerprint (f)
Pick vendor (OnePlus is 21 at the time of writing)
Pick device (3T is 5 at the time of writing)
Pick the one with Android 9. (It does not matter that the android versions are mismatched)
Follow the instructions to apply changes and reboot.
7) Check YASNAC, everything should be passing now!
Some other suggestions:
GCam is pretty nice alternative to the original camera. I would recommend this one. (It is recommended to also install Google Photos. It is a google camera after all.)
OpenWeather is a nice weather provider.
I would also recommend going to Google's Keyboard, Messages, Phone, and Calendar Apps. AOSP ones are not great, in my opinion.
Hope somebody finds it useful! Good luck!
Ah nicely done, thanks for the effort and work you put into this. How is your 3T performing?
AndyC76 said:
Ah nicely done, thanks for the effort and work you put into this. How is your 3T?
Click to expand...
Click to collapse
Hi, thanks! I was planning to use it as a development device to pick up android app development, but life got in the way and that never got off the ground
My 3T has developed a battery issue which ultimately led to me retiring it. The battery is extremely unreliable. It can be at 1% but work for 3 hours, sometimes the phone refuses to charge and the battery percentage tends to get stuck at 50% regardless of the actual charge level. I tried replacing the battery but the same behavior persisted. I think it is something either with the motherboard or the battery connector on it :/ Still a pretty snappy phone though!