So recently, I had to unroot my phone because I need snapchat working. I was using Magisk with the newest update and EdXposed. Everything was fine until I got struck by a suprise 12 hour ban, yeah no big deal, I wasn't even using root for much else but changing the boot animation at the time.
This is where it gets interesting, after multiple restarts disabling modules and then finally uninstalling Magisk, I get struck by a mesagge that the phone is corrupted and can't be trusted. I got a mini heartattack from this but after starting my phone, nothing is weird or out of place, bootloader is still unlocked and updating the phone works.
My question is, what will this affect that I haven't realised yet and is there any way to prevent that message from appearing?
I think Magisk Hide can do something. Just turn on Magisk Hide and in its section turn on Snapchat.
Related
I've had my Note 4 for a while and after a few Lollipop update incidents I finally after a lot of hesitation decided to root my phone (with the TWRP bootloader) and disable the update notifier. Since then, I've always stuck to the latest stock version of KitKat 4.4.4.
Since I've rooted my phone, I made the following modifications that require root priviliges: I installed XPrivacy mod, YouTube AdAway mod, NoSafeVolumeWarning mod, PlayPermissionsExposed mod, and CrappaLinks mod for the Xposed framework. I also installed Titanium backup to freeze/uninstall the updater and AdAway. After XPosed was installed I had to change a line in /system/build.prop to 'ro.securestorage.support=false' to make 'S Health' work again. I did that with the 'FX' app.
That's it, I had made no more modifications and the phone seemed to work quite well for a month or so.
Two days ago I decided to try out Instagram, I've been quite wary with social apps but figured Instagram shouldn't hurt and everything was fine. Then I installed a bunch of dating apps, I started with Match.com and Tinder. Tinder didn't work because it required FB and Match didn't work because it refused to, probably because of denied permissions with XPrivacy so I gave up on them and uninstalled them.
But I also installed OkCupid and Motesplatsen and enjoyed playing around with these apps. They didn't seem to interfere with XPrivacy and worked rather fine. Motesplatsen was rather intense with sending me notifications of girls who watched my profile and sent me (rather strange) messages whereas OkCupid was rather calm.
Then something strange happened.
Yesterday I started noticing that the battery was draining considerably faster than normal during normal day. It was almost empty whereas it usually is half full after a full day, I also noticed that the phone was unusually warm. I forgot to put it on the charger and woke up today with a dead phone. I put it on charge and after about an hour the battery was full again.
When I tried to turn on the phone it was stuck on boot loop. I first tried disabling XPosed by "touch /data/data/de.robv.android.xposed.installer/conf/disabled" using the 'terminal' tool in the TWRP bootloader. It didn't help. I tried flushing the cache/dalvik cache but it didn't work either. Then I did a total factory reset, but that didn't work. I noticed that during boot, the phone froze so hard that it doesn't even respond to button pushes. I had to take out the battery to reboot (that's one reason why I never will buy S6).
So then I decided to flash the phone with stock KitKat once again using Odin and that finally restored the phone.
Now, here's one of my questions, how can things go so bad with a phone that not even a factory reset will fix it? We're talking stock firmware here, albeit it is rooted.
What boot logs could be worth looking into when such a thing occurs and what is the easiest way to extract them? The terminal tool in the bootloader seems promising, plus I saw a 'copy log to SD' option which I neglected this time.
I'm puzzled, does anyone know what happened? I made no root modifications in the process of installing these apps and they don't advertise themselves as needing root privileges. How can a seemingly inconspicuous app directly from Google play **** a phone up like that?
Some history with the phone. I've gone back and forth a few times with this phone. At one point the bootloader was unlocked, I was rooted, etc etc. This was quite a while ago. Since then I have flashed the factory rom, locked the bootloader and ran 100% pure stock until this morning and everything worked just fine. Android Pay worked, etc. Today I decided I'd do a factory reset and not bother restoring data. Prior to doing that, I decided to give Magisk a quick try just for the heck of it. I flashed the current Oreo factory image (With Sept security patches) left the bootloader unlocked, flashed TWRP, installed Magisk via TWRP. Didn't really give it much of a chance but either way, after a quick check safetynet failed. So I figured, whatever no big deal. I flashed the factory image again, then relocked the bootloader, and eventually rebooted and signed back into my account and didn't bother restoring any backup. Let all the stock apps install/update, checked Android Pay.....and it wouldn't allow me to add a card. I checked the Safetynet tests and it fails the CTS Profile match. I'm pretty much at a loss now as to what in the world the problem is. The phone is fresh off of a factory reset and the bootloader is locked. No magisk, no root, nothing.
Another REALLY strange thing is, during boot up, I have to unlock the phone, then it continues booting up and eventually finishes the boot up process, although I think I recall reading about this being some new security thing. Either way, don't think it relates to my issue.
Well I unlocked the bootloader again, flash the August 7.1.2, relocked the bootloader, and after updating apps and Google Play Services, all is well again. Guess I'll just grab the OTA and go from there.
Wow, so sideloading the OTA broke it again.
Ug...found out there's a build 019. Apparently there's a problem with build 017. Sideloaded 019 and now I have no issues with safetynet.
glad someone else is seeing this, sideloaded OTA build 017 and Android Pay stopped working with it failing Safetynet's CTS Profile check
ParadingLunatic said:
Ug...found out there's a build 019. Apparently there's a problem with build 017. Sideloaded 019 and now I have no issues with safetynet.
Click to expand...
Click to collapse
Where is this 019 OTA? I'm having this same problem. I thought I was the Andromeda I tried but I knew that was rootless.
Thanks for shedding light on this.
---------- Post added at 07:45 PM ---------- Previous post was at 07:35 PM ----------
Did some more digging. Found it. Gonna see if it works.
Sent from my Nexus 6P using XDA-Developers Legacy app
ParadingLunatic said:
... Another REALLY strange thing is, during boot up, I have to unlock the phone, then it continues booting up and eventually finishes the boot up process, although I think I recall reading about this being some new security thing. Either way, don't think it relates to my issue.
Click to expand...
Click to collapse
This is because when you set the screen lock you checked the box to ask for the lock code when the system boots up. It's a good security measure that insures that if the phone is lost or stolen, a reboot will not allow someone to bypass the screen lock.
stevemw said:
This is because when you set the screen lock you checked the box to ask for the lock code when the system boots up. It's a good security measure that insures that if the phone is lost or stolen, a reboot will not allow someone to bypass the screen lock.
Click to expand...
Click to collapse
Yup I figured that out. I knew it was an added security feature but I couldn't recall where it was set. It seems that in Oreo, when you enroll in the fingerprint setup during the initial phone config, when it forces you to create a PIN it automatically sets that option without asking unlike how before, it used to ask.
ParadingLunatic said:
Yup I figured that out. I knew it was an added security feature but I couldn't recall where it was set. It seems that in Oreo, when you enroll in the fingerprint setup during the initial phone config, when it forces you to create a PIN it automatically sets that option without asking unlike how before, it used to ask.
Click to expand...
Click to collapse
Didn't realize it was automatically set in Oreo. I went thru 7 and the preview, so this option was already set. I will be getting the Pixel 2 XL, so it's something for me to check on.
So, I got my A1 yesterday. I let it live for a night but that's the most I can do without root. Anyway, no dice.
I tried Magisk on Stock. Bootloop.
I tried Magisk on Google Experience. Bootloop.
I tried SuperSU on Google Experience. Bootloop.
The interesting part is that it acts exactly the same every time no matter the ROM: first it'll ask for the PIN, then crash and reboot. Then it does it again *sometimes*. But sure as hell it'll end up at the boot animation ad infinitum. What gives? Anyone had more luck?
dancress said:
So, I got my A1 yesterday. I let it live for a night but that's the most I can do without root. Anyway, no dice.
I tried Magisk on Stock. Bootloop.
I tried Magisk on Google Experience. Bootloop.
I tried SuperSU on Google Experience. Bootloop.
The interesting part is that it acts exactly the same every time no matter the ROM: first it'll ask for the PIN, then crash and reboot. Then it does it again *sometimes*. But sure as hell it'll end up at the boot animation ad infinitum. What gives? Anyone had more luck?
Click to expand...
Click to collapse
Did you by any chance disable a service, like location services for example?
Flash stock using miflash.
Then again try magisk on stock??
Hm. Looks like I have it. Suddenly worked. I have no explanation. I sound like my mom now - but I didn't do anything!
Well restarted my phone on the weekend and when it started up a notification showed it was being updated. I had automatic updates turned off. I checked and see I am now on July update.
Magisk manager is still installed but it says Magisk has been uninstalled. The strange this is that the Google Camera is still working.
Has anyone else had something similar happen?
Yes magisk and twrp has been removed
Yes it has happened to me too.
Twrp got removed from boot and also magisk was uninstalled.
Gcam app is also not working
Can anyone help me remove the gcam app from boot.
Thanks in advance
ludditefornow said:
Well restarted my phone on the weekend and when it started up a notification showed it was being updated. I had automatic updates turned off. I checked and see I am now on July update.
Magisk manager is still installed but it says Magisk has been uninstalled. The strange this is that the Google Camera is still working.
Has anyone else had something similar happen?
Click to expand...
Click to collapse
No, had updates turned off since early Oreo and its never updated 'automatically'.
Happened to me also. As it didn't behave like a normal update, I am wary of reinstalling magisk/twrp. Has anyone done it, can they post a link to the guide they used?
Thanks all
Sent from my Mi A1 using Tapatalk
I didnt have twrp installed, but i dontbthink i will bother with Magisk reinstall because gcam is still working.. only problem is that my Viper i stall has gone.. so if i get sick of the low volume through headphones, i will install magisk again
Have installed magisk - or at least have root acess, but magisk manager says it's not installed. Maybe I am doing something wrong. or is it a version release issue. Also is Cosmic Dan's twrp the best way to go with July release
Thanks
M
Not sure whether to post here or under ROMs.
Phone was working fine this morning, had a couple of missed calls. I update Magisk and noticed both of my sim cards are showing a square icon w a line through it. When I go to settings, sim card, the app keeps crashing.
I am hoping I have overlooked something stupid and simple. Airplane mode is off, cycled it off and on just in case. Google play services was checked under Magisk Hide, unchecked it and rebooted. Still no phone modem.
I have XXX no limits installed and elemental kernel.
Only change I have made was updating Magisk. Thought I would post here before I uninstall Magisk.
***UPDATE****
I have the patience of a 2 yr old.
So this is what I did:
Unistalled all my Magisk modules
rebooted
phone is working
added my 3 modules back in 1 at a time and rebooted each time.
Got a weird reboot about a minute after my last reboot ( after I added XXX back in ).
I am using OS14 Laucher and got a couple of weird restarts there also.
But the phone and both sims are working.
This last update has been strange. After I updated my phone passed safety net for the 1st time in ages. My banking app still detected root and I can't use it, but I passed safety net.
After removing then re installing each of my modules I no longer pass safety net.....but that is a whole other post.