Database Users

Issues with smn910w8 - Rooting

After i got my note 4 i rooted it and everything was going fine until i installed the xposed framework app, i didn't install the framework itself but the phone got messed up. I flashed the stock firmware which fixed the issues but now whenever i try to root the phone again using cf auto root it goes into an endless boot cycle which can be fixed by flashing stock firmware. The worst part is all my contacts were backed up with titanium backup which requires root. Also I'm wondering about cyanogen mod and if there are any working builds since the Canadian bell isn't listed.

Sprint SPH-L720 CM 12.1 MMS Problems

I'll try to be as thorough as possible.
I started out with the stock S4. Everything worked, minus a terribly damaged screen which I replaced. It was originally on 4.4.2 the NG2 build. I rooted with CF-Auto Root through Odin 3.09. I flashed PhilZ recovery through Rashr's Recovery Tools. It says 6.15 something, but when it boots in recovery mode it just says 6 and CWRM 6.0.4.7 (not sure if this matters or not). I then installed the latest snapshot for CM 11-20141112-snapshot-m12-jflte.zip and gapps-kk-20140606 which was fine. I got LTE service, but no SMS/MMS at all. I then tried CM 12.1-20151116-snapshot-yog7dao1jn-jfltespr.zip with gapps-5.1-arm-2015-07-17-13-29.zip which looks and works great (LTE works) minus the SMS/MMS again.. I tried the same with the latest nightlies of both CM 11 and 12.1 to no avail. I wipe phone, cache and dalvik before flashing every ROM.
I have tried changing the "Bearers" to LTE for all of the n.ispsn options under APN which I'm not even sure is a valid solution anymore. My preferred network is set to LTE. I am rooted through developer options both app and adb. I have come across other Sprint SMS/MMS workaround threads, but they seem dated; it's hard to sift through what is still relevant.
My baseband still shows up as the NG2 version with Android version 5.1.1 (I am currently on CM 12.1). Does this matter? Am I using the correct versions of what I should be?
My goal is to have CM 12.1 running so I can use mobile hotspot among other features. I don't necessarily need CM, but mobile hotspot is my biggest wanted feature. And obviously SMS/MMS needs to work.
As a last ditch effort, can I go back to stock rom/does it have to be an NG2 one?
I have temporarily reactivated my previous phone (HTC One M7) until I have a sure way of accomplishing my goal with the S4.
Thanks in advance!

Just did a full wipe and installed latest TWRP as my recovery. I flashed the Optimized CM 12.1 from here:
http://forum.xda-developers.com/gal...lop/exclusive-antaresone-alucard24-s-t3066696
and the latest gapps from 11/29/15 (nano fwiw).
Still have LTE. Still no MMS/SMS. I changed the same APN bearers to LTE. I tried Textra (APN settings seemed correct) and Google Messenger to no avail. I even did this dialer fix method found here (post #3):
http://forum.xda-developers.com/not...int-note-4-t2973257/post57613217#post57613217
What am I missing?

If it was MMS only that you were having issues with, then fiddling with the APN settings would make more sense to me.
However, since you have neither SMS nor MMS, it suggests something other than the APN settings.
Some potential things to try:
Turn off mobile data and see if SMS works.
Turn off LTE and drop down to 2G or 3G and see if SMS/MMS work.
Try updating your profile (hiding somewhere in the Update Software in the Settings menu) and then trying to see if SMS/MMS work.
I have had reasonable functionality on the NG2 baseband with the Dirty Unicorns ROM (v9.7) on the L720, though I did not explicitly verify that hotspot was working.

fireguy85 said:
I'll try to be as thorough as possible.
I started out with the stock S4. Everything worked, minus a terribly damaged screen which I replaced. It was originally on 4.4.2 the NG2 build. I rooted with CF-Auto Root through Odin 3.09. I flashed PhilZ recovery through Rashr's Recovery Tools. It says 6.15 something, but when it boots in recovery mode it just says 6 and CWRM 6.0.4.7 (not sure if this matters or not). I then installed the latest snapshot for CM 11-20141112-snapshot-m12-jflte.zip and gapps-kk-20140606 which was fine. I got LTE service, but no SMS/MMS at all. I then tried CM 12.1-20151116-snapshot-yog7dao1jn-jfltespr.zip with gapps-5.1-arm-2015-07-17-13-29.zip which looks and works great (LTE works) minus the SMS/MMS again.. I tried the same with the latest nightlies of both CM 11 and 12.1 to no avail. I wipe phone, cache and dalvik before flashing every ROM.
I have tried changing the "Bearers" to LTE for all of the n.ispsn options under APN which I'm not even sure is a valid solution anymore. My preferred network is set to LTE. I am rooted through developer options both app and adb. I have come across other Sprint SMS/MMS workaround threads, but they seem dated; it's hard to sift through what is still relevant.
My baseband still shows up as the NG2 version with Android version 5.1.1 (I am currently on CM 12.1). Does this matter? Am I using the correct versions of what I should be?
My goal is to have CM 12.1 running so I can use mobile hotspot among other features. I don't necessarily need CM, but mobile hotspot is my biggest wanted feature. And obviously SMS/MMS needs to work.
As a last ditch effort, can I go back to stock rom/does it have to be an NG2 one?
I have temporarily reactivated my previous phone (HTC One M7) until I have a sure way of accomplishing my goal with the S4.
Thanks in advance!
Click to expand...
Click to collapse
I would suggest flashing latest stock and make sure everything works, the CM builds you were flashing may be having issue with the fact you were in NG2. Go to sammobile.com get latest OH1,flash that via Odin, make sure everything is working, then flash TWRP via Odin. Now you will be stock with custom recovery, then you can flash your latest CM in TWRP and everything should work.

mattzeller said:
I would suggest flashing latest stock and make sure everything works, the CM builds you were flashing may be having issue with the fact you were in NG2. Go to sammobile.com get latest OH1,flash that via Odin, make sure everything is working, then flash TWRP via Odin. Now you will be stock with custom recovery, then you can flash your latest CM in TWRP and everything should work.
Click to expand...
Click to collapse
Thank you (both of you guys). I am downloading the stock OH1 rom from sammobile right now (1 hr+ download though..). I'll try to post up later if I get the chance.
Download is complete; however I can only find TWRP 2.8.7.0 as a .img file, even on their official site. I can download 2.8.4.0 as a .tar file, but I'm pretty sure I have to be rooted to flash an .img. We'll see I guess..

fireguy85 said:
Thank you (both of you guys). I am downloading the stock OH1 rom from sammobile right now (1 hr+ download though..). I'll try to post up later if I get the chance.
Download is complete; however I can only find TWRP 2.8.7.0 as a .img file, even on their official site. I can download 2.8.4.0 as a .tar file, but I'm pretty sure I have to be rooted to flash an .img. We'll see I guess..
Click to expand...
Click to collapse
Just Odin the 2.7.4.0

mattzeller said:
Just Odin the 2.7.4.0
Click to expand...
Click to collapse
Yeah, I Odined the 2.8.4.0 after installing the stock rom which was successful after a factory wipe. I reactivated the S4 with Sprint and have just tested SMS and MMS-both of which work. Now to flash CM (fingers crossed!).
TWRP didn't take over my recovery.. Guess I'll reodin it.
Reflashing TWRP 2.8.4.0 didn't seem to work.. Do I need to go back through the CF-Auto Root process?
I think I got it. I had to hold up immediately after odining TWRP. I am backing up now.

Success so far! I have SMS and MMS working correctly and LTE working. Thank you!
However; I lost my backed up apps + data from Titanium Backup Am I able to restore a backup from this ROM earlier today to somehow recover this information?
Apparently flashing the stock ROM via Odin wiped out everything on my internal storage. I do have a backup from the 29th I made on CM 12.1 with CWM. Can I flash/Odin CWM and then restore this backup to get back my app data? Or can TWRP restore this backup as well? I also see an "extract from nandroid" option in Titanium Backup, but it is a paid option. I don't have a problem with this if it is my only option, but why would TB back up my apps/data internally by default? Backing up to SD card makes way more sense to me.

fireguy85 said:
Success so far! I have SMS and MMS working correctly and LTE working. Thank you!
However; I lost my backed up apps + data from Titanium Backup Am I able to restore a backup from this ROM earlier today to somehow recover this information?
Apparently flashing the stock ROM via Odin wiped out everything on my internal storage. I do have a backup from the 29th I made on CM 12.1 with CWM. Can I flash/Odin CWM and then restore this backup to get back my app data? Or can TWRP restore this backup as well? I also see an "extract from nandroid" option in Titanium Backup, but it is a paid option. I don't have a problem with this if it is my only option, but why would TB back up my apps/data internally by default? Backing up to SD card makes way more sense to me.
Click to expand...
Click to collapse
Should always make your backups on external SD card. By default TB backs up to internal because a lot of phones either don't have external SD card capability, or they just don't have one. TB is worth the couple of bucks, try googling to see if there are any free options to restore apps from nandroid

There are apps that should be able to pull apks from the nandroid backups, but I'm unsure if they can pull the data as well.
The long and tedious way to do it is to just reload your previous CM12.1, rerun Titanium backup, then restore your current firmware.
Make a nandroid back up of your current working OH1 from TWRP and copy it to your SD card or somewhere else. I believe the backup resides in a directory called TWRP on the sdcard.
Use TWRP to restore your backup of CM12.1 (copy your backup directory into a corresponding folder in the TWRP directory). I believe it should be a standard nandroid backup if you used CWM to back it up. If it doesn't work, then flash CWM recovery with odin and then use CWM to restore your backup.
Then boot into your CM12.1, run Titanium Backup, then copy the Titanium Backup directory on to an SD card. Copying might not be necessary since you won't need to use odin to get back to stock OH1 firmware. You could probably also check to see if MMS/SMS is working.
Once you are done making the new backup of your apps/data with Titanium Backup, then use TWRP to restore your working OH1.
When restoring your apps, just be careful to choose just the ones you need. I have never tried it, but I would expect that there would be some incompatibilities between apps in CM12.1 and apps for TouchWiz (i.e. funny things may happen if the cLock screen lock app got restored).
Now that you have SMS/MMS working, do you have mobile hotspot working yet?

So good news/bad news I guess. I installed paid version of Titanium Backup and chose extract from nandroid. None of the apps I'm looking for were in there. I must have made nandroid after installing gapps but before other apps which is my fault. I'm guessing I'm SOL on this issue now.
I did test mobile hotspot and that seems to work though :/
And now SMS/MMS doesn't work through stock messaging app.. It does in Hangouts though thankfully..

I got my app data from the nandroid after all! I had to reinstall the app from the play store and then install the app data afterwards. The app data was named something completely different than the app name and from what I was looking for. $6 well spent

I am still on the 11/1 optimized build. I still have issues with MMS. I won't receive them at all in stock messaging app. I experience major delay (and no notification unless I am in the app) if I use Hangouts. And I cannot receive them at all through Google Voice. SMS is also very much delayed except through Google Voice (with Sprint Integration). Is there anyone here that is using a CM 12.1 ROM with Sprint and having success with MMS and MMS? All of the research I have found seems to just go nowhere. I hear Hangouts and Sprint together don't work and you're not supposed to integrate GV with Sprint either (although it is the only way I can use SMS consistently and get notifications). Apparently GV isn't even compatible with MMS?
BTW, the 11/30 build destroys my Bluetooth. I can't even enable it successfully. Didn't even bother to try SMS/MMS. Flashed right back to 11/1.
I'm wondering if I can/should just flash to a rooted stock ROM. Not having reliable SMS/MMS is rather annoying..

fireguy85 said:
I am still on the 11/1 optimized build. I still have issues with MMS. I won't receive them at all in stock messaging app. I experience major delay (and no notification unless I am in the app) if I use Hangouts. And I cannot receive them at all through Google Voice. SMS is also very much delayed except through Google Voice (with Sprint Integration). Is there anyone here that is using a CM 12.1 ROM with Sprint and having success with MMS and MMS? All of the research I have found seems to just go nowhere. I hear Hangouts and Sprint together don't work and you're not supposed to integrate GV with Sprint either (although it is the only way I can use SMS consistently and get notifications). Apparently GV isn't even compatible with MMS?
BTW, the 11/30 build destroys my Bluetooth. I can't even enable it successfully. Didn't even bother to try SMS/MMS. Flashed right back to 11/1.
I'm wondering if I can/should just flash to a rooted stock ROM. Not having reliable SMS/MMS is rather annoying..
Click to expand...
Click to collapse
Have you tried Google Messenger?

mattzeller said:
Have you tried Google Messenger?
Click to expand...
Click to collapse
I did and it did not initially work either. I did not spend much time troubleshooting this as the general workaround seems to be just using Hangouts.
I am now in the process of switching to T-Mobile. I could not pass up on their $200/line deal for being a Sprint customer (I have 5 lines). I'm sure I'm going to have to go back to stock for awhile on this device and then maybe flash a different CM ROM to get back to where I am now. Idk, maybe not. I guess I have to have Sprint unlock my device first. If it doesn't go smoothly, I'll just sell my S4 and get a T-Mobile one. T-Mobile says this one is compatible with their network though..
EDIT: Probably not going to be fully compatible. Likely going to have to get a T-Mobile S4. I'm guessing the CF-Auto Root is still valid for rooting being it is the same device? Thank you for the help!

Issues with Snapchat

So I have completely wiped the phone. Internal storage, sd card and all and I still get the error from snapchat. I do not have Xposed installed, or anything for that matter.
So I've installed and ran Nougat (AICP) and snapchat ran perfectly. Reverting to 6.1 (TruePure) to see if this has fixed my problem.

ive also, returned to stock and since then got error msg and not being able to log snap

the-light said:
ive also, returned to stock and since then got error msg and not being able to log snap
Click to expand...
Click to collapse
So, I'm not completely sure how it worked but I got a reccomedation to use Magisk. After a clean install of TruePure 2.9 (remember in aroma to set root to systemless) I installed Magisks, and somehow it just worked. I was able to sign in.
http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

kspreco said:
So, I'm not completely sure how it worked but I got a reccomedation to use Magisk. After a clean install of TruePure 2.9 (remember in aroma to set root to systemless) I installed Magisks, and somehow it just worked. I was able to sign in.
http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
thx. might give it a shot

problem installing magisk

I've tried a few times to install magisk on my s4 but it doesn't work
I have twrp 3.2.3 installed
android 5.01
sgh-i337m
seems to say it installs, but when it reboots I get a message like
"Unfortunately the phone has stopped working"
If I click ok, the message just comes back and I can do next to nothing. I have once or twice seen a message after this about the samsung keyboard not working. I've tried wiping caches, but I have to do a restore before the phone will work again.
I've tried magisk 18.0 and 17.3 same result.
I'd use an old version of supersu (that I get to work without problems), but I wanted to use a backup utility that requires magisk. I only need the backup for call logs/sms/contacts etc. I can lose the calendar.
Any ideas on installing magisk?
Or if you know of some other way of installing logs/sms/contacts that doesn't require magisk, that would work also.
I want to try a custom rom, but I don't really want to lose the history of this stuff.
Thx
Edit: I should add that at the time I have tried this, the phone was NOT rooted. Supersu had been removed

Cannot open SIM & Network settings / com.android.phone crashes after uptdate to OO10

Cannot open SIM & Network settings / com.android.phone crashes after uptdate to OO10
Device:
Rooted OP 6t, OxygenOS 10.3, stock recovery, Magisk 20.2, Magisk Manager 7.5.0
What did I do:
I updated from the last OxygenOS 9 Version to OxygenOS 10.3 by uninstalling magisk, restoring images and doing the manual update through the downloaded full image. Reinstall magisk. It all went well. First boot took a while but went through.
SIM was not recognised at all.
I've reset all network settings and cleared cache and data of com.android.phone.PhoneApp.
Found out here that its due to a call record magisk module which I uninstalled. Mobile data is working just fine since then.
I tried to uninstall magisk and reinstall it before rebooting in order to keep the possibility to keep root as I do not have twrp installed. (suggested here). I guess this is unrelated.
Issue:
I cannot access the SIM & Network Settings. When I try, the app com.android.phone crashes instantly.
Logs throw these warnings:
Code:
Unable to launch app com.android.phone/99901001 for broadcast Intent { act=android.telephony.action.CARRIER_CONFIG_CHANGED flg=0x15000010 (has extras) }: process is bad
Is there a way to check the carrier config or renew it?
Code:
Unable to launch app com.android.phone/99901001 for broadcast Intent { act=android.intent.action.SIM_STATE_CHANGED flg=0x5000010 (has extras) }: process is bad
Hows the SIM state changing?
and this Error:
Code:
Sending non-protected broadcast com.android.internal.telephony.ACTION_IMS_CAPABILITY_STATUS_CHANGE from system 1102:system/1000 pkg android
java.lang.Throwable
at com.android.server.am.ActivityManagerService.checkBroadcastFromSystem(ActivityManagerService.java:15963)
at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:16666)
at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:15980)
at com.android.server.am.ActivityManagerService.broadcastIntent(ActivityManagerService.java:16808)
at android.app.ContextImpl.sendStickyBroadcastAsUser(ContextImpl.java:1422)
at com.android.server.TelephonyRegistry.broadcastImsCapabilityStatusChangeForPhoneId(TelephonyRegistry.java:2644)
at com.android.server.TelephonyRegistry.notifyImsCapabilityStatusChangeForPhoneId(TelephonyRegistry.java:2636)
at com.android.internal.telephony.ITelephonyRegistry$Stub.onTransact(ITelephonyRegistry.java:964)
at android.os.Binder.execTransactInternal(Binder.java:1032)
at android.os.Binder.execTransact(Binder.java:1005)
I am not sure what to do. But I do want to avoid a full factory reset.
Thanks for your hints.

Alternatively is it possible to access the settings of this submenu through a different app or way?

hey_malik said:
Alternatively is it possible to access the settings of this submenu through a different app or way?
Click to expand...
Click to collapse
Sounds like a bad flash, or you didn't factory reset. If you update from 9 to 10 without wiping data, **** can happen

True, I did not because I don't want to set up the whole phone afterwards.
Could it be a solution to flash the ROM again through the integrated update system? Or would I then need to install twrp? I haven't done this in ages

Have you got any magisk module active?

estapagu said:
Have you got any magisk module active?
Click to expand...
Click to collapse
I uninstalled magisk for the update. Reinstalled it, forgot the call recording module. Removed that.
I still have systemless hosts, viper and YouTube vanced active.

hey_malik said:
I uninstalled magisk for the update. Reinstalled it, forgot the call recording module. Removed that.
I still have systemless hosts, viper and YouTube vanced active.
Click to expand...
Click to collapse
I had some SIM problems at the beginning related to a magisk module but I can't remember which. And another problem with WiFi after OTA update using magisk OTA udapte method, so finaly I deleted Magisk completely and updated from TWRP

Just to get this straight:
I may in a first step boot a twrp image (just boot) dirty flash the latest stock image, flash magisk (or not and lose root for the moment which is no issue because I have an unlocked boot loader) and see if the issue is still present. If yes a clean wipe and install is in order?!

@hey_malik
dude when i upgraded from 9.0.17 to 10.3.0 occurred same issue...
Backup all your stuff and MSM your device.
Look for '[OP6T][LATEST 10.3.0] Collection of unbrick tools' thread,
posts #83 - #86 and see how i solved.
Good luck :fingers-crossed:
Cheers

Dadditz said:
@hey_malik
dude when i upgraded from 9.0.17 to 10.3.0 occurred same issue...
Backup all your stuff and MSM your device.
Look for '[OP6T][LATEST 10.3.0] Collection of unbrick tools' thread,
posts #83 - #86 and see how i solved.
Good luck :fingers-crossed:
Cheers
Click to expand...
Click to collapse
I don't really get what you mean. What's msm? Magisk? And what am I supposed to do? Remove magisk completely? I've read the posts 83-86 but it's a bit cryptic for me.

hey_malik said:
I don't really get what you mean. What's msm? Magisk? And what am I supposed to do? Remove magisk completely? I've read the posts 83-86 but it's a bit cryptic for me.
Click to expand...
Click to collapse
Sorry, sometimes I take certain things for granted.
By MSM I meant (incorrectly) the unbrick / downgrade package
posted on the first page of the thread I indicated to you.
If you have not solved that problem and want to try,
I recommend using the Android 10-based package.
Back up all your stuff, be sure you have installed the OP6T drivers on your PC.
All information is already described in the aforementioned thread
or in the link posted on the first page that reports to that of iaTa.
All the credits go to these fantastic guys.
Cheers

Dadditz said:
Sorry, sometimes I take certain things for granted.
By MSM I meant (incorrectly) the unbrick / downgrade package
posted on the first page of the thread I indicated to you.
If you have not solved that problem and want to try,
I recommend using the Android 10-based package.
Back up all your stuff, be sure you have installed the OP6T drivers on your PC.
All information is already described in the aforementioned thread
or in the link posted on the first page that reports to that of iaTa.
All the credits go to these fantastic guys.
Cheers
Click to expand...
Click to collapse
I suggest you boot to Twrp, then flash the Twrp. Get inside twrp and flash these > OOS, Twrp, Magisk Then reboot again to twrp repeat > OOS, Twrp, Magisk. And for the last time reboot again to twrp and flash the Magisk.
You will be good to go. :good:

Is there any risk involved concerning the encryption?

hey_malik said:
Is there any risk involved concerning the encryption?
Click to expand...
Click to collapse
As you already mentioned, you are in Android 10, and if you are using the correct Twrp. There won't be any.
Still it's always better to take a back up just in case if something goes wrong.

Stuck with the same issue. Did you manage to get it fixed somehow?

Actually the latest available oo update to 10.3.1 fixed it.

hey_malik said:
Actually the latest available oo update to 10.3.1 fixed it.
Click to expand...
Click to collapse
Lucky you. I got this issue when switching to 10.3.1 from 9. I tried flashing 10.3.1 once again. Didn't work.

You need to uninstall Magisk then factory reset, it will get rid of all Magisk modules ghost residues. Then flash Magisk again with fastboot twrp method. I had this and going back to factory state was the only fix. No need to flash again and again the rom it doesn't touch Magisk data in /data partition.

hey_malik said:
Actually the latest available oo update to 10.3.1 fixed it.
Click to expand...
Click to collapse
Just an update, this worked for me too. Thanks for posting that tip else I would have went ahead and reset the phone. You saved me a hell lot of trouble.
Additionally, I figured out a solution which might work for people still having this issue. I haven't tested this myself since I found this after my issue was solved.
The reason why the issue happened to us is because the system app "Phone Services" was missing, or not installed properly while dirty flashing. There is an alternative hidden activity for sim settings called "com.android.settings.network.telephony.MobileNetworkActivity", which is not a part of Phone Services app, but a part of the Settings app itself. This could be invoked using any activity launcher apps available in the Play Store.
Also, this activity gives more advanced sim settings too. So, probably worth a look if interested.

Same problem here, but fixed!!
Sim not working anymore after update to Magisk 21.2. nothing would change it.
After installing previous version (21.1) the problem persisted. After almost giving up, I found this thread. Simply uninstalled the OOS Native Call Enabbler module and everything workes like a charm again!!!
So it was an easy fix (once you know) and I am very thankful, because I would never have thougt of it! Unfortunately I cannot record Calls anymore, nor find the module now that I am successfully running on 21.2 again with working SIM. Though the choice between being able to use my SIM or record calls was easy
Hope someone finds use of this info.
As mentioned before Encryption is not a problem if the right TWRP version is used.
Put in you password (or pin) and all is nicely decrypted and reachable in TWRP Recovery.
Good luck to all!
PS: still hoping for a new (compatible) call recorder module though