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.
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?
Anyone else having an issue with Android Pay. I am rooted (systemless) and finally decided to add a card to Android Pay. I've been able to get into Android Pay and tap the plus button to add the card just to test that it would work. I'm just now getting around to setting it up now. This time however tapping the plus button, I get the error message when you are rooted the traditional way. I didn't install any new apps that weren't directly from the Play store or that use root in any way.
I checked and noticed Android Pay was updated though. I went ahead and rebooted and was now able to add a card. But in the middle of adding another card I got the same error message. I dismissed it and was able to add another card. For some reason I could not add my Bank of America Visa though. So I haven't used it yet at a terminal. Anybody seen this issue?
synnyster said:
Anyone else having an issue with Android Pay. I am rooted (systemless) and finally decided to add a card to Android Pay. I've been able to get into Android Pay and tap the plus button to add the card just to test that it would work. I'm just now getting around to setting it up now. This time however tapping the plus button, I get the error message when you are rooted the traditional way. I didn't install any new apps that weren't directly from the Play store or that use root in any way.
I checked and noticed Android Pay was updated though. I went ahead and rebooted and was now able to add a card. But in the middle of adding another card I got the same error message. I dismissed it and was able to add another card. For some reason I could not add my Bank of America Visa though. So I haven't used it yet at a terminal. Anybody seen this issue?
Click to expand...
Click to collapse
Ugh. I was going to post that I hadn't seen this before, but before doing so I removed my discover card from AP and tried to add it again - got that dang error message you're referring to. Then rebooted my phone and tried to re-add it, and this time got further to where it says "contacting your bank" before again failing. Ugh Google why! Might try side loading the old version of AP see if that makes a difference.
EDIT: Very, very odd. I rolled back to the previous 1.1.1 version and tried adding the card again. The first time it failed instantly, but the 2nd time I tried (immediately after) it went through fine.
EDIT2: Just tried adding a completely different card after RE-updating to the latest version and it added perfectly fine right away the first time I tried. No idea what's going on here.
I might try going to a terminal later today to see if it works with the cards I already have added and I want that free Chromecast
I can't seem to add any more cards. They both say failed to verify info.
I was able to use Android Pay at the grocery store today. I still haven't been able to add any other cards thoug,even though I've waited 24 hours since adding the last two.
Decided to root today for the first time on this phone and I am also having this issue, so I went back to stock. I am on MMB29P. I had installed twrp, then flashed the systemless root version 2.66. Root was working fine, but the safteynet checker failed and I tried adding a card and got the Android Pay error. I have not tried the old method of installing the modified boot / SU... I just let 2.66 patch the boot image for me. I really just wanted to use Adaway too.
Edit: I guess adaway modifies the system partition, so that is probably why this wasn't working for me. Since that was the main reason for me to root, guess I'm staying on stock.
Read this thread on systemless root.
http://forum.xda-developers.com/nexus-6p/themes-apps/systemless-root-themed-apps-t3292105
If it were me though I would just flash the /unSU zip, then flash SuperSU 2.61 http://download.chainfire.eu/746/SuperSU/BETA-SuperSU-v2.61-20151207213702.zip . Then AP should just work without having to run any terminal commands. I've done it this way numerous times and it worked every time.
As for Adaway, if you flash the systemless hosts zip before installing Adaway AP will be unaffected.
Adaway thread http://forum.xda-developers.com/showthread.php?t=2190753
systemless hosts download https://www.androidfilehost.com/?fid=24269982087016285
I only ever add one card though.
And I don't have busybox installed (although I did install it previously and AP worked without issue)
So I can't add my Bank of America card because it can't verify my system, but I can still use android pay with the card I already have added. Not sure what to do at this point. Also want to point out the safety net app passes.
I recently updated to 10.3.1 from android 9 i was rooted using magisk and edxposed installed so after installing i didn't reboot i went to magisk manager and installed to other slot and rebooted.
Everything's fine but both sim shows emergency calls only so i downloaded offline package and installed it locally. Root is removed and both Sim are working fine but when i go to settings and open Sim & network it says com.android.phone keeps stopping.
I'm unable to send messages and check balance using ussd code. I don't know what to do.
haidermiz said:
I recently updated to 10.3.1 from android 9 i was rooted using magisk and edxposed installed so after installing i didn't reboot i went to magisk manager and installed to other slot and rebooted.
Everything's fine but both sim shows emergency calls only so i downloaded offline package and installed it locally. Root is removed and both Sim are working fine but when i go to settings and open Sim & network it says com.android.phone keeps stopping.
I'm unable to send messages and check balance using ussd code. I don't know what to do.
Click to expand...
Click to collapse
Hello bud,
this is the third time (including me) that I see such a thing.
Here i posted my experience, quite same like yours.
Here how i solved. (see posts below)
Backup all your stuff and good luck.. :fingers-crossed:
Cheers
Stock out of box Samsung Galaxy S6 From Boost Mobile.
Disclaimer >>>Might Work With the Sprint S6, since Boost is just the prepay of Sprint, the same phone I think...
First to say this is a rare find (2015 Release) but if you can get your hands on this awesome handset it has, 8Cores, 32Gb of Memory, 16mp.Cam, and as far as i know the Last Samsung Galaxy With the iR Blaster. So I take No-Responsibility to any Malfunctions or Broken Devices. Personally Had Little to Zero Problems Achieving this I would say This is the Best, Most stable Rooted Device i'v ever owned.
Im Posting here expecting that everyone knows what ROOT, TWRP, CWM, SuperSU is, Developer Mode/How to activate, how to reboot to recovery/Download Mode, Flash via Odin, and use TWRP.
I'll try to put this whole thing in chronological order. so out of box... or anyone who can restore their device back to this build BOL1It Works Flawlessly, Very-Fast/ResponsiveSystem Wide Equalizer>V4A-starts on boot, Xposed FW, Xprivacy, Lightning Wall, and The Google PlayStore still works.
Take Phone out of box [UNACTIVATED/NOSIM/AIRPLANE] LoL... Turn on at home alone... DO NOT CONNECT TO WiFi/DATA it will force update BOL1. Dont sign in google Acc. or Samsung Acc. SET UP http://wakasoftware.com/app-freezer-setup/ Once Completed With Freezer App Set up Reboot and Freeze The following Apk.'s
Search (Update) in Freezer app. You should find [com.sec.android.fotaclient, com.wssyncmldm, com.sec.fwservice, com.sprint.ce.updater, and [NOT100%ON com.policydm] Disable them. Next search sprint in Freezer; Disable every apk. listed under sprint search [com.sprint.zone, com.sprint.psdg.sw, com.samsung.sprint.chameleon, com.sprint.w.installer, com.sprint.ce.updater, com.sprint.w.prefact, com.sprint.dsa, com.samsung.sprint.setupwizard, and com.sprint.voicemail]
You can probably leave voicemail enabled boost has theirs installed anyways. Not sure if sprint-Vmail works or not. Go ahead and freeze any bloat ware or apps you don't want. Disable at own risk. If something messes anything up, reboot to recovery, factory reset, then start over lol
THIS WILL TRIP KNOX
Alright now go developer options and turn on OEM unlocking (allow the Bootloader to be unlocked) Now im going to thank (spammy l) XDA Member for this post https://forum.xda-developers.com/sp...ainfire-autoroot-stock-custom-kernel-t3294308
Follow That Root Method-Just USE THE LATEST SuperSU & TWRP instead. Im on [SU 2.82-SR3] & [twrp-3.3.1-0-zerofltespr] Once obtained Root, an have installed TWRP&BUSYBOX; Create a Custom Recovery backup-TWRP BEFORE you go on to install XposedFW.
You can connect to WiFi/Data, set up google, samsung accounts, and activate wireless services/put SiM Card Back/Disable-airplane-mode now that you have the sprint apps disabled. WARNING if you root this without sprint apps disabled sprint will detect root on the phone and try to force update and continuously restart the phone only 10seconds or so after bootup. I did not know this when i first activated my services. Even after i turned off wifi and pulled the sim card out it was still rebooting only 10seconds after bootup. Giving me only moments to navigate to freezer app and search ''sprint'' and freeze freeze freezze.... so thats why we freeze them first. Also by disabling the sprint Apk. s it Removed the Boost Mobile Boot Animation not sure which one but just FYI just see stock samsung boot.img cool still.
Next have to Thank (wanam Contributor/Developer) For Their Forum( https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960 ) on how to install XposedFW For [5.1/6.0]Lollipop/Marshmallow. Follow That to get Xposed Installed properly. Once flashed it dose take a few minuets to startup, it will boot cycle a couple times, be patient.
Last but my personal favorite piece of software to place in to the system, ViPER4Android-FX 2.5.0.5
My last shout-out goes to (kevintm78 Senior Member) for his method on installing V4A The Proper Way. Here (https://forum.xda-developers.com/note-4/themes-apps/how-to-viper4android-install-proper-t3691597) after all that you should make a new custom recovery point to save your work. Thanks to all just wanted to put all that into one place for this specific build of phone.
A Few Apk. s to Mention
--Galaxy Universal Remote Version 4.1.3 out there on the web<<aptoid
--XBooster-Free Version 5.1.2 PlayStore
--Physical Button Music Control Version 4.0 beta6 Xposed Module
--lightningWall Version 3.9.2 Xposed Module
--APM+ (Advanced Power Menu) Version 17.12 Xposed Module
--XPrivacy Version 3.6.19 Xposed Module
--Flappy Bird Version 1.3 lol...
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.