Im rooted stock att s5 usa and i can not send pics in messages
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Did you use xposed, or did you do any modifications. I haven't found a post yet where the phone was broke after towel root, where towel root itself broke the phone.
Agree. There's no reason the root itself would cause this. Give us some more info so we can help you better. MMS can be finicky anyway on this phone. I've had some message delay issues (which are mms), but I've found a restart helps stuff come and go faster.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
The only thing i used from xposed was the fake system
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
I know i have trouble sending pictures vis WiFi but not via LTE
Sent from my SAMSUNG-SM-G900A using Tapatalk
lrmdaddy said:
The only thing i used from xposed was the fake system
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've noticed pretty much every one of the "my phone's not acting right after towel root" in some way has xposed involved.
Meangean said:
I know i have trouble sending pictures vis WiFi but not via LTE
Sent from my SAMSUNG-SM-G900A using Tapatalk
Click to expand...
Click to collapse
There is a reason for this. It is the network not the phone. Picture messaging is not sent through as normal data on the default text app it has to go through the towers.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
I've found that mms doesn't work when using adblock plus. If you're using that, delete it and switch to Adaway. Fixed the problems I was having with mms messages.
DI'm having this same issue. A reboot causes a pending one to download but can't sent out. Uninstalled add block plus and still have issue. I did install add away
For clarification. I installed and successfully ran towellroot. Installed xposed and then the xposed framework. Installed wanam xposed. Changed a few things in the notification bar like battery. Put symbols back into keyboard.
Strange it worked for a few days just perfectly fine... now it does not work.
That's all I've done.
sent from my Galaxy S 5
Since you're rooted, maybe you should do a full backup in TiBu, wipe clean, and restore. It might fix whatever broke.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
I think I may have got it working last night. Adblock Plus did not an uninstall the first time I did it properly so it over wrote the settings again no I didn't know it. After a couple reboots with adAway install it seems to be now working
sent from my Galaxy S 5
Related
I saw this in another Note 3 forum. I tried it out and hot through most steps but it shows an error in sqlite which I can't get past. I am trying to figure it out but has anyone managed this?
http://forum.xda-developers.com/showthread.php?t=2342370
Sent from my SAMSUNG-SM-N900A using xda app-developers app
ekerbuddyeker said:
I saw this in another Note 3 forum. I tried it out and hot through most steps but it shows an error in sqlite which I can't get past. I am trying to figure it out but has anyone managed this?
http://forum.xda-developers.com/showthread.php?t=2342370
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
I was able to get it to work.
Are you rooted. Did you use sqlite? I keep getting error 14 when I try to edit settings.db
Sent from my SAMSUNG-SM-N900A using xda app-developers app
I am rooted and used the exact same method, and everything worked for me.
Very odd. Its like the db is open so I can't open it.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
i got it to works too! thanks!
Do you have Wanam running?
Sent from my SAMSUNG-SM-N900A using xda app-developers app
ekerbuddyeker said:
Do you have Wanam running?
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
yep, Wanam running.
try to download sqlite again.
or reset phone and try again.
Sqlite opens other databases but it says error 14 when I try to open this one.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
I have the same error. Anyone know the path to that database so I can edit the permissions in root Explorer?
Sent from my Galaxy Note 3
I found it on root Explorer. Data/data/ com. Android. Providers. Settings. But all the permissions are already checked!
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Weird, IDK enough about sql to figure it out! Oh well lol
Sent from my Galaxy Note 3
I get error 14 also when trying to open settings.db. I tried shutting off Xposed installer and wanman rebooted and still no go, also tried downloading the app a few different times and still no go.
scoot05redss said:
Weird, IDK enough about sql to figure it out! Oh well lol
Sent from my Galaxy Note 3
Click to expand...
Click to collapse
Help us out here. What did you do.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
I even hard reset but still had same problem.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
ekerbuddyeker said:
Help us out here. What did you do.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
I wish I could help, I continue to get the error, I just gave up! lol
scoot05redss said:
I wish I could help, I continue to get the error, I just gave up! lol
Click to expand...
Click to collapse
I wonder why we got this error and others didn't, especially after I hard reset the device. Must be something to do with rooting? I also had the 'custom' sign on bootup which i removed using wanam. Could it be connected?
Also, when I hard reset and tried to SQLite it was the TASK MANAGER that blocked the editing of a system file. came up with a shield logo, but it wasn't Lookout. When I clicked on the message, which said it was safe to delete SQLITE, there was no option to 'ignore' or bypass it.
ekerbuddyeker said:
I wonder why we got this error and others didn't, especially after I hard reset the device. Must be something to do with rooting? I also had the 'custom' sign on bootup which i removed using wanam. Could it be connected?
Also, when I hard reset and tried to SQLite it was the TASK MANAGER that blocked the editing of a system file. came up with a shield logo, but it wasn't Lookout. When I clicked on the message, which said it was safe to delete SQLITE, there was no option to 'ignore' or bypass it.
Click to expand...
Click to collapse
I'm pretty sure that was knox. Did it say "prevention information"? I disabled it according to designgears' second post in his rooting thread, but still get the code 14 error, just no shield this time --
"I am getting a "Prevention Information" popup after running a root app, how do I disable it?
From terminal emulator or adb shell as root, run; pm disable com.sec.knox.seandroid
Or freeze the Knox apps with Titanium Backup."
I have all the knox stuff and lookout deleted and still get the error message 14. I also tried the app from the play store and still get error. I really want to figure this out cause turning data on and off in settings is a pita. I'd even settle for the data toggle in the power off menu.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
We are in parallel. I froze knox and it didn't help.
What's odd to me is that other people did not have this problem...
Sent from my SAMSUNG-SM-N900A using xda app-developers app
For the first time today my phone gave me this prompt when I tried to open my camera while on a bluetooth call. I also tried it with just the speaker phone and regular call and still got this prompt. I can open it with camerazoom fx btw.. I cleared cache and data in the camera app and did a system wipe of dalvik cache and still no luck.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Cojam1 said:
For the first time today my phone gave me this prompt when I tried to open my camera while on a bluetooth call. I also tried it with just the speaker phone and regular call and still got this prompt. I can open it with camerazoom fx btw.. I cleared cache and data in the camera app and did a system wipe of dalvik cache and still no luck.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I believe thats by default. Not sure if its a Samsung thing or what. If you're rooted, Wanam has an option to allow that.
theorioles33 said:
I believe thats by default. Not sure if its a Samsung thing or what. If you're rooted, Wanam has an option to allow that.
Click to expand...
Click to collapse
I am rooted and have Wanam installed. But I can assure I have in the past been able to take pictures while on a bluetooth call. I also had a coworker while on a bluetooth call on his note 3 open his camera without issue.Thanks anyway.Will check out Wanam features.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Cojam1 said:
I am rooted and have Wanam installed. But I can assure I have in the past been able to take pictures while on a bluetooth call. I also had a coworker while on a bluetooth call on his note 3 open his camera without issue.Thanks anyway.Will check out Wanam features.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hmmm. Sounds unusual. Never tried it myself. I figured since there was a Wanam mod for it that it was normal.
I'm fully stock and I can open my camera while in a phone call
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
kufusoto said:
I'm fully stock and I can open my camera while in a phone call
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah. I'm going to unroot and factory reset to see what's causing this. Appreciate the reply.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Cojam1 said:
For the first time today my phone gave me this prompt when I tried to open my camera while on a bluetooth call. I also tried it with just the speaker phone and regular call and still got this prompt. I can open it with camerazoom fx btw.. I cleared cache and data in the camera app and did a system wipe of dalvik cache and still no luck.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's funny you brought this up. I've noticed on stock Samsung phones sometimes I can't do that either, then on others I can. I know with Wanam Xposed you can enable it though if you want to try that route.
Agent said:
That's funny you brought this up. I've noticed on stock Samsung phones sometimes I can't do that either, then on others I can. I know with Wanam Xposed you can enable it though if you want to try that route.
Click to expand...
Click to collapse
The orioles33 suggested Wanam and I did use it, but it worked before and after root. I'm just trying to figure out why it stopped all of a sudden.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
I wish I could tell you but I don't know about this one
Sent from my SAMSUNG-SGH-I467 using Tapatalk
Its a Samsung thing. They put so many stupid restrictions on their phones. Like not being able to use the camera if your battery is low. Fnck you samsung. Let me kill my battery however I want.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Well today I took my phone to an AT&T service center for for call issues and they gave me a new sim and reflashed MJ5 to my phone. I'm bone stock again and my stock camera opens during phone calls. So I think root broke it somehow, maybe, I will reroot with kingo 1.1.8 to see if there is a relation to this situation with root. Thanks all.
Ok, So I rerooted with 1.1.8 and camera now works with calls. This is crazy. Lol
It started yesterday. The biggest changes I can think of are
1. adding Gear Manager and connecting Gear 2 Neo to it which happened one week ago. No issues till now
2. putting in and taking out a microSD card. Shortly after this action, the random reboots started. I don't think I messed up the related hardware. I did it carefully, not forcing anything. I even shut down the device and popping the battery before inserting and removing the microSD.
I'm scratching my head what could have triggered the random reboots. I have shut down Bluetooth to trouble-shoot what is causing the random reboots. Any insight is greatly appreciated. Thanks
What firmware are you on? Are you rooted? Have you tried another sd card? Maybe try a factory reset
Sent from my SAMSUNG-SM-N900A using xda app-developers app
It is possible that the power button is failing.
Sent from my SM-N900A using XDA Premium 4 mobile app
graydiggy said:
It is possible that the power button is failing.
Sent from my SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Diggy that might be also I had that happen to me on my s3 I used a mod (can't remember from where either wanam or gravitybox) to double tap notification bar to lock screen
Sent from my SAMSUNG-SM-N900A using xda app-developers app
ryant100 said:
Diggy that might be also I had that happen to me on my s3 I used a mod (can't remember from where either wanam or gravitybox) to double tap notification bar to lock screen
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
I believe it is in gravity box. But it is possible that wanam has that feature as well.
Sent from my SM-N900A using XDA Premium 4 mobile app
My Note 3 isn't rooted. It's running stock KitKat. It doesn't have a microSD. I put one in to copy files and took it out right away. I don't know if it was a coincident. The reboots started shortly after I put in and took out the microSD. I think it's more a coincident because I was super careful with the microSD slot.
I just did a reset. I'll observe if reboots happen again.
I know it sounds crazy but try going into Settings>Wifi>Advanced and unchecking "Always Allow Scanning". Once I used a SD in it and have that checked my phone randomly reboots no matter what ROM or MODs I use and I have met other people on here that have had the same issue and unchecking that setting fixed it. Something about the way some SD cards work and that setting not playing nice with each other. Hope this helps you, I know it nearly drove me mad until someone suggested I try unchecking it.
I did a reset and restored my all apps backed up by Helium. I got random reboots still. But may be because I also restored Gear Manager and its associated plugins and apps, I was still getting random reboots. I have reset again and restored all my apps without the Gear Manager etc. So far it's been 20 hours, no random reboots. I'll observe some more. I just have the feeling Gear Manager etc have something to do with the reboots.
@zacharyt86: I'll remember your tip too. Thanks
My N3 used to do that a lot so i rooted the phone and now i have no issues. I did have issues with some roms and when i was using a rom slot on ss but no issues on the stock slot.
Im on JB though but my note had the same issue. I think its a memory issue... I was also using a cache cleaner then that i just havent used since i changed roms
Ya think it just could be one if those weird things I see others having issues that I'm not having if it keeps doing it I would call Samsung or take it back to att
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
Mayonesa said:
My N3 used to do that a lot so i rooted the phone and now i have no issues. I did have issues with some roms and when i was using a rom slot on ss but no issues on the stock slot.
Im on JB though but my note had the same issue. I think its a memory issue... I was also using a cache cleaner then that i just havent used since i changed roms
Click to expand...
Click to collapse
Root alone does nothing. All it does is allow administrative access to everything.
Sent from my SM-N900A using XDA Premium 4 mobile app
graydiggy said:
Root alone does nothing. All it does is allow administrative access to everything.
Sent from my SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am aware root alone does nothing lol i have been rooting phones for a while. A different rom is what helps
Is there any root procedures for the latest kit kat update on the att galaxy note 3 yet?
Sent from my SAMSUNG-SM-N900A using Tapatalk
bongra80 said:
Is there any root procedures for the latest kit kat update on the att galaxy note 3 yet?
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
Google or the search function will answer your question.
Highjacking a thread will not.
Sent from my SM-N900A using XDA Premium 4 mobile app
It's been 60+ hours. No reboots. I'm inclining to conclude it's Gear Manager and its associated plugins and apps that caused the reboots. I'll install Gear Manager again, not install any Gear app, just connect phone calling and default notifications, i.e.all default stuff. Will report back.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Make sure you watch if you are unsure on how to do it!
http://youtu.be/nWqTIXf5kUs
Thanks for making this. It's like people literally couldn't read the instructions on the site. It was really frustrating to watch how many people asked how to do this yesterday in the release thread.
Does this work on s5 active?
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
No has not been reported to work yet
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
DO NOT USE ULTRA POWER SAVING MODE AFTER ROOTING AS OF YET... myself and a few others are left with a black white att logo onscreen after enabling ULTRA POWER SAVING MODE just a heads up....
UnhoIy said:
Thanks for making this. It's like people literally couldn't read the instructions on the site. It was really frustrating to watch how many people asked how to do this yesterday in the release thread.
Click to expand...
Click to collapse
I was trying to do it through my computer as I have everything in the past. The video showed me how to do it on my phone.
Holy Fuc!ing sh!t! There's root now!
Sent from my SM-G900A using XDA Premium 4 mobile app
sholsten said:
I was trying to do it through my computer as I have everything in the past. The video showed me how to do it on my phone.
Click to expand...
Click to collapse
I was hesitant to make a video, but thanks for the feedback!!
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
This is done from the phone?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Yes you do it all from the phone
DO NOT REMOVE THE LAUNCHERS AS I STATED IN THE VIDEO THIS WILL SCREW THE PHONE IF YOU TRY TO USE ULTRA POWER SAVING...
LEAVE THE LAUNCHERS IN
Thanks
Sent from my SAMSUNG-SM-G900A using Tapatalk
Worked for me! Thanks Guys
Samsung Galaxy S5 Active
I can confirm that this worked to root the S5 Active. I had issues with Google services not functioning properly, but once I installed SuperSU, and it disabled Knox, everything seemed to be working fine again. Based on comments from others, I have not enabled ultra power save mode.
MSStranger said:
I can confirm that this worked to root the S5 Active. I had issues with Google services not functioning properly, but once I installed SuperSU, and it disabled Knox, everything seemed to be working fine again. Based on comments from others, I have not enabled ultra power save mode.
Click to expand...
Click to collapse
Im on S5 AND3 rooted ans debloat i tried the UPSM and its working great just do not uninstall any stock launcher or stock samsung keyboard
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
I removed the launchers lol but that's because I have never used the ultra power saver in the 2 months I've nd this
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
MSStranger said:
I can confirm that this worked to root the S5 Active. I had issues with Google services not functioning properly, but once I installed SuperSU, and it disabled Knox, everything seemed to be working fine again. Based on comments from others, I have not enabled ultra power save mode.
Click to expand...
Click to collapse
How did you go about installing SuperSU, and disabling Knox?
UPDATE: I see in his thread about SuperSU. Does it automatically disable Knox? Or do I have to go about Titanium Backup and disable all the appropriate apps?
MercilessLTD said:
How did you go about installing SuperSU, and disabling Knox?
UPDATE: I see in his thread about SuperSU. Does it automatically disable Knox? Or do I have to go about Titanium Backup and disable all the appropriate apps?
Click to expand...
Click to collapse
SuperSU automatically prompts and asks if you want to disable Knox. The first time I ran it, it hung. Rebooted, and ran again, and it disabled right away. Was golden after that point.
V2 didn't work for me. Just tried V1 and it worked with no issue. Awesome! Just got the S5 today as well.
Sent from my SAMSUNG-SM-G900A using Tapatalk
lol a 10min video on how to root by dling an apk in 1 click.. you should title it root and titanium and xposed etc lol.. did you show in video how to update su?
Sent from my SM-G900V using XDA Premium HD app
---------- Post added at 02:48 AM ---------- Previous post was at 02:39 AM ----------
elliwigy said:
lol a 10min video on how to root by dling an apk in 1 click.. you should title it root and titanium and xposed etc lol.. did you show in video how to update su?
Sent from my SM-G900V using XDA Premium HD app
Click to expand...
Click to collapse
or one of them was 10mins.. u should teach how to set up supersu or at least say sll they gotta do is go in play store to get it lol
Sent from my SM-G900V using XDA Premium HD app
I just rooted my phone with Towelroot (all hail Geohot) and installed the XPosed framework. Everything seemed to work fine until I activated the first couple modules (Rootcloak and Wanam) and then texts stopped sending from my phone. Worked fine after just rooting and fine once i disabled the modules, so it's probably something having to do with the installed modules.
Anyone else run into this issue?
jtguf87 said:
I just rooted my phone with Towelroot (all hail Geohot) and installed the XPosed framework. Everything seemed to work fine until I activated the first couple modules (Rootcloak and Wanam) and then texts stopped sending from my phone. Worked fine after just rooting and fine once i disabled the modules, so it's probably something having to do with the installed modules.
Anyone else run into this issue?
Click to expand...
Click to collapse
i have both of those modules on my phone and texting is working fine. i know this doesnt help your particular phone, just wanted to say that those together do work with no texting problems.
Had a similar issue yesterday with mms. Thought it was xposed but it turned out to be Adblock blocking port 80.
Sent from my SAMSUNG-SM-G900A using XDA Premium HD app
dcd17 said:
Had a similar issue yesterday with mms. Thought it was xposed but it turned out to be Adblock blocking port 80.
Sent from my SAMSUNG-SM-G900A using XDA Premium HD app
Click to expand...
Click to collapse
Interesting, I'll disable adblock and see if that helps.
Any way to keep ab from blocking that port?
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
You were absolutely right, that did it.
Glad to see it, I wanted Wanam and Root Cloak more than ab
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app