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
Related
Every time I submit a post in the XDA application I get a pop up that says I need to force close the application. The post goes through but I need to force close the application to get it working again.
Very confused on why this is happening. I have the kernel dump log saved but not sure which part to post. The log file is just a hair over 1 megabyte, not sure why it's so large. Any way someone can point me to the relevant part to help figure this out?
Same on mine.
Same
Sent from my SAMSUNG-SGH-I897 using XDA App
Mine did that too. I uninstalled and reinstalled the app, fixed it.
I think there was another thread about that issue.
I had a thread like this. I just uninstall and re install when it starts doing that.
Sent from my SAMSUNG-SGH-I897 using XDA App
madjsp said:
I had a thread like this. I just uninstall and re install when it starts doing that.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
That's deff does not help. As many times as i've installed this app after restoring it STILL has this issue. It almost makes the app useless if your going to do anything but read. (And hear goes a force close as I post this lol)
Sent from my GT-I9000 using XDA App
I had this issue as well. I uninstalled it for a while, then reinstalled. Haven't experienced the problem since.
Sent from my SAMSUNG-SGH-I897 using XDA App
same same same same
Is there a fricken fix to this problem? Getting really pissed. Every time i post i got to log in. Prob will be forced out again after j make this post. Lol.
How about the actual tapatalk? Does that app force close too?
Sent from my GT-I9000 using XDA App
Edit: wow, no force close. Maybe its my lucky day.
Been having the same problem on mine, just uninstalled and reinstalled. Posting to test.
*Edit: No FC... Guess uninstalling/reinstalling worked.
Sent from my SAMSUNG-SGH-I897 using XDA App
I reinstalled it like 5 times and I finally don't get any FC's.
Sent from my GT-I9000 using Tapatalk
Does anyone know why if I freeze the att update stuff in TB it shows up when looking at the battery stats for android systems under included packages? Don't want an update forced on me and I'm trying to make sure I did it right.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
monte97z said:
Does anyone know why if I freeze the att update stuff in TB it shows up when looking at the battery stats for android systems under included packages? Don't want an update forced on me and I'm trying to make sure I did it right.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
Did you reboot by any chance?
Yes, rebooted a few time both reboot and power off and back on. If I go into "about device" and hit "software update" it won't even load, button clicks but that's all it does. So I assume it's at least disabled at this point, I just don't want to assume wrong and get stuck with a secret att update and loose root.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Mine still lists it as well even though it is frozen with Titanium Backup.
Ok maybe it's normal then. Thank you for checking.
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
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
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