[REQ] Stock System App list - X 2014 Q&A, Help & Troubleshooting

So after rooting I used TiBu to uninstall several system apps. I thought I was quite careful, only deleting things I know I don't need (face unlock, live wallpapaers, etc), but it seems I've done something that borked the stock camera. The hardware works fine, I normally use Google Camera anyway, but the stock camera app crashes on opening either from lockscreen, launcher icon, or wrist twist.
Is there a list of the stock system apps available for perusal to contrast my setup against to try to find what's missing?
Again, I use Google Camera 90% of the time, but until there's a mod for making the double twist trigger other operations, it'd be nice to have some functionality there.
Thanks in advance y'all!

I was in the same situation, go unto Moto X (2014) android development and there's a thread there with a system.img with root, download and fast boot flash that and you'll get all the system apps back. Let me know if you have questions or problems.

antnyhills said:
I was in the same situation, go unto Moto X (2014) android development and there's a thread there with a system.img with root, download and fast boot flash that and you'll get all the system apps back. Let me know if you have questions or problems.
Click to expand...
Click to collapse
Thanks for the advice! However, I would much rather just push the system app(s) manually rather than start over with a fresh system. I've been tinkering with this too long to start over now! Maybe one day when I get bored.
I'm mostly wondering if anyone knows any apps that the camera depends on, especially ones that aren't named in such a way that it's obvious.

It will not wipe your phone tried it my self, all my settings apps everything still there

antnyhills said:
It will not wipe your phone tried it my self, all my settings apps everything still there
Click to expand...
Click to collapse
Hmm, I guess I should've known the system.img wouldn't erase data...
So it looks like all I'll lose is Xposed and root? I can handle that.
Edit: It's got root too! Zoinks!

Won't lose either

antnyhills said:
Won't lose either
Click to expand...
Click to collapse
Wait, seems that system.img is for xt1095, I'm xt1093...
We don't even have official firmware yet...
Boo!

I'll get you titanium backups of the apps you need, list them please
---------- Post added at 01:32 PM ---------- Previous post was at 01:22 PM ----------
Or the apks

antnyhills said:
I'll get you titanium backups of the apps you need, list them please
---------- Post added at 01:32 PM ---------- Previous post was at 01:22 PM ----------
Or the apks
Click to expand...
Click to collapse
I appreciate your assistance very much!
I first must find the apps that are missing. If that is even my issue, could be any number of things. I currently have a system dump of all the stock system apps, but thanks for your offer of TiBu files!
Since the camera hardware is functional and the only issue is the stock camera app, I think it's more worth everyone's time for me to wait until official firmware is released, then I can create system.img and flash over.
Unless someone else has a similar issue and resolves it somehow, or knows any strange apps that the camera depends on......?

Related

Blocking update?

Just received my Moto X AT&T shipped from Costco, system version is 139.9.51.ghost_ATT.en.US -so would appear I can root? (and then hopefully take the update without losing root? I recall seeing a thread, hopefully for the version I have)
Can the update be "pushed" onto the device without my accepting it, as to whether I would need to root (if I wanted to root) quickly to block it?
Thanks
M973 said:
Just received my Moto X AT&T shipped from Costco, system version is 139.9.51.ghost_ATT.en.US -so would appear I can root? (and then hopefully take the update without losing root? I recall seeing a thread, hopefully for the version I have)
Can the update be "pushed" onto the device without my accepting it, as to whether I would need to root (if I wanted to root) quickly to block it?
Thanks
Click to expand...
Click to collapse
no but you will get continual pop ups unless you the phone then disable motorola ota 1.0 and updater.apk (i think just updater.apk will suffice) with Titanium back up.
jayboyyyy said:
no but you will get continual pop ups unless you the phone then disable motorola ota 1.0 and updater.apk (i think just updater.apk will suffice) with Titanium back up.
Click to expand...
Click to collapse
Thanks, I thought that was the case, but wanted to confirm quickly (with some, SGS4, it's pushed to the phone whether you accept or not, unless you're rooted.)
Thanks for the quick reply
M973 said:
Thanks, I thought that was the case, but wanted to confirm quickly (with some, SGS4, it's pushed to the phone whether you accept or not, unless you're rooted.)
Thanks for the quick reply
Click to expand...
Click to collapse
not sure if it downloads it automatically or not (i don't think it does but it may). Even if it does download automatically it won't update it unless you click ok when it prompts you. I would root and disable OTiA until you figure out what you are going to do about it.
rooting
looks like it's either with PwnMyMoto, or Motoroot, appears the first is better? Looks like both are done with ADB which was a bit difficult, have only used it once, used it to remove safestrap from the SGS4 I had so I could return it
M973 said:
looks like it's either with PwnMyMoto, or Motoroot, appears the first is better? Looks like both are done with ADB which was a bit difficult, have only used it once, used it to remove safestrap from the SGS4 I had so I could return it
Click to expand...
Click to collapse
You can just install pwnmymoto on your device and run it. Make sure to have unknown sources checked
---------- Post added at 05:56 PM ---------- Previous post was at 05:55 PM ----------
Also it is wise to get familiar with adb and fastboot!
shane1 said:
You can just install pwnmymoto on your device and run it. Make sure to have unknown sources checked
---------- Post added at 05:56 PM ---------- Previous post was at 05:55 PM ----------
Also it is wise to get familiar with adb and fastboot!
Click to expand...
Click to collapse
Cool, thanks!

Block Verizon/OTA Update?

Not sure if wrong forum section but was wondering if there was a way to block all Verizon updates without root. I keep getting notifications to install the latest update (the one that gives Advanced Calling 1.0) but I don't want to install it in case it causes issues. Is there a way to remove/block this update feature without root?
You can disable all the Verizon's apps. In the app section in settings I don't get any notifications.
mdcowby said:
You can disable all the Verizon's apps. In the app section in settings I don't get any notifications.
Click to expand...
Click to collapse
Dont think you understood my question mdcow. I wasnt talking about stopping Verizon app updates like Navigator, Visual Voicemail, Text App, etc. I was talking about the system firmware updates
jgowell said:
Dont think you understood my question mdcow. I wasnt talking about stopping Verizon app updates like Navigator, Visual Voicemail, Text App, etc. I was talking about the system firmware updates
Click to expand...
Click to collapse
Not without root unfortunately. You can only keep declining the install and that's it but eventually your phone will bend to big red's will when you're not paying attention
jgowell said:
Dont think you understood my question mdcow. I wasnt talking about stopping Verizon app updates like Navigator, Visual Voicemail, Text App, etc. I was talking about the system firmware updates
Click to expand...
Click to collapse
I've never gotten those update notifications so my disabling a lot of stuff from Verizon and moto must of prevented something.
Just curious then what is your current firmware version? Want to see if you unknowingly updated already or if your update was actually blocked
mdcowby said:
I've never gotten those update notifications so my disabling a lot of stuff from Verizon and moto must of prevented something.
Click to expand...
Click to collapse
Is your system 21.44.8 or 21.21.15?
jgowell said:
Is your system 21.44.8 or 21.21.15?
Click to expand...
Click to collapse
221.44.8 if it updated it did it without me knowing. I'm getting rid of this phone anyway. Came from insurance cause they didn't have any razr maxx in Stock. I really don't like it.
Okay it sounds like it didn't update as your firmware version matches as one without the update Advanced Calling feature. Still curious to know what you disabled so I could get rid of my notification too
I think this newer ota app came from the Turbo, it stops it on the ultras. Check the md5 against yours. Pull it with Super Manager, apk manager, bAPK. Use Explorer free to read the md5.
I posted the md5 on my Op.
http://forum.xda-developers.com/showpost.php?p=56708101&postcount=1
---------- Post added at 01:13 PM ---------- Previous post was at 01:11 PM ----------
I wanted to check where it came from anyway. If not from Turbo then you may be able to benefit too.
aviwdoowks said:
I think this newer ota app came from the Turbo, it stops it on the ultras. Check the md5 against yours. Pull it with Super Manager, apk manager, bAPK. Use Explorer free to read the md5.
I posted the md5 on my Op.
http://forum.xda-developers.com/showpost.php?p=56708101&postcount=1
---------- Post added at 01:13 PM ---------- Previous post was at 01:11 PM ----------
I wanted to check where it came from anyway. If not from Turbo then you may be able to benefit too.
Click to expand...
Click to collapse
What? Not sure what you are trying to say. Can you reword?
lafont28 said:
Not without root unfortunately. You can only keep declining the install and that's it but eventually your phone will bend to big red's will when you're not paying attention
Click to expand...
Click to collapse
actually you can block OTA's without root.
go here and use this method. without root
http://forum.xda-developers.com/showpost.php?p=57436867&postcount=26
jgowell said:
What? Not sure what you are trying to say. Can you reword?
Click to expand...
Click to collapse
I still have the old Maxx. I found that installing a newer moto ota app (my link) I could stop the ota. I have yet to determine which new moto system dump I got it from. If not from the Turbo then it may stop it too.
Md5 is unique to any app. I posted it for the unknown app.
When you boot your phone, wait until the download notification comes up then go into settings and force stop MotorolaOTA. It'll cancel the download and it won't try again until you reboot.
Cobra04 said:
When you boot your phone, wait until the download notification comes up then go into settings and force stop MotorolaOTA. It'll cancel the download and it won't try again until you reboot.
Click to expand...
Click to collapse
Look two post above by me. you can block without root
the_rooter said:
Look two post above by me. you can block without root
Click to expand...
Click to collapse
A few questions about this. Let me know if it is easier to PM you or post here
the_rooter said:
Look two post above by me. you can block without root
Click to expand...
Click to collapse
jgowell said:
A few questions about this. Let me know if it is easier to PM you or post here
Click to expand...
Click to collapse
Try this blocking method out, I believe it will work for the Turbo. It's easier than using the script. http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
Misterxtc said:
Try this blocking method out, I believe it will work for the Turbo. It's easier than using the script. http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
Click to expand...
Click to collapse
thanks MisterXTC. The tool seems to work like a charm, esp with the search function.
One question: the OTA is already downloaded on my phone and i keep getting a notification to install it but I have been been 'delaying' the install. When I block the "MotoralOTA" but then reboot the phone the phone, the notification comes back. Is there a way to permanently block the OTA or will I have to block it each time the phone restarts?
jgowell said:
thanks MisterXTC. The tool seems to work like a charm, esp with the search function.
One question: the OTA is already downloaded on my phone and i keep getting a notification to install it but I have been been 'delaying' the install. When I block the "MotoralOTA" but then reboot the phone the phone, the notification comes back. Is there a way to permanently block the OTA or will I have to block it each time the phone restarts?
Click to expand...
Click to collapse
Try entering recovery mode and wipe the cache. That will delete the downloaded update file. As for permanently blocking the OTA it should stay blocked until you factory reset. It's probable nagging you because of the downloaded update file. You might have to re-block the OTA after clearing cache, I'm not positive. You might need to enter your app manager and manually stop the OTA, try that first.
Misterxtc said:
Try entering recovery mode and wipe the cache. That will delete the downloaded update file. As for permanently blocking the OTA it should stay blocked until you factory reset. It's probable nagging you because of the downloaded update file. You might have to re-block the OTA after clearing cache, I'm not positive. You might need to enter your app manager and manually stop the OTA, try that first.
Click to expand...
Click to collapse
I went ahead and cleared cache and it seems to have worked. No notifications to install so far despite reboot.
Thanks again for the link and help afterwards!

[Q&A] MoFo IMG AT&T XT1097 (root, tether, xposed)

Q&A for MoFo IMG AT&T XT1097 (root, tether, xposed)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for MoFo IMG AT&T XT1097 (root, tether, xposed). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
My /data directory is empty. Can I assume I don't need to follow the steps to delete the two folders?
busybox
Any chance on getting busybox baked in as well?
AlwaysHere said:
Any chance on getting busybox baked in as well?
Click to expand...
Click to collapse
Do you know anyone with an XT1095? If so it is really easy to do and they can make a nandroid of their system and just restore it when they are done.
JulesJam said:
Do you know anyone with an XT1095? If so it is really easy to do and they can make a nandroid of their system and just restore it when they are done.
Click to expand...
Click to collapse
Sadly I don't know anyone around that has one. Looks like I'll have to wait until it's released somewhere on here. Thanks JulesJam.
Newbie questions
I've received my Moto X yesterday (bought a used one on Amazon). Unfortunately I haven't ask the seller which exact model of MotoX it was and it turned out that it is AT&T one and bootloader can't be unlocked.
Tried to go through all topics connected to MotoX but still have a couple of questions. If this this is wrong topic please tell my where to post.
1. Using MoFO, should I be able to install debloated firmwares (without AT&T bloatware) on my phone? I don't need root but I wan't pure stock Android without carrier-specific apps.
2. If I use MoFo and don't like it, can I go back to official stock and receive OTA updates?
3. Do we have any hope that someday (say, in one year) someone (like Sunshine) finds a way to unlock bootloader? Is that hardware-impossible or just such an exploit wasn't found yet?
4. Assuming that such exploit probably will need KitKat, will I be able to downgrade to 4.4.4 later if I update 5.0.2 OTA now?
qyron said:
1. Using MoFO, should I be able to install debloated firmwares (without AT&T bloatware) on my phone? I don't need root but I wan't pure stock Android without carrier-specific apps.
Click to expand...
Click to collapse
Yes but to make it you have to either use another device with an unlocked bootloader like a Nexus 9 or a Moto X 2013, or if you know someone with an XT1095 they can make it for you. Or if you know linux you can make it.
---------- Post added at 08:56 PM ---------- Previous post was at 08:55 PM ----------
qyron said:
I've received my Moto X yesterday (bought a used one on Amazon). Unfortunately I haven't ask the seller which exact model of MotoX it was and it turned out that it is AT&T one and bootloader can't be unlocked.
Click to expand...
Click to collapse
Can you return and buy an XT1095 instead? That is what I would do.
---------- Post added at 08:57 PM ---------- Previous post was at 08:56 PM ----------
qyron said:
2. If I use MoFo and don't like it, can I go back to official stock and receive OTA updates?
Click to expand...
Click to collapse
Yes read my noob guide in the General forum (it is linked to in the OP of the MoFo thread).
---------- Post added at 09:00 PM ---------- Previous post was at 08:57 PM ----------
qyron said:
3. Do we have any hope that someday (say, in one year) someone (like Sunshine) finds a way to unlock bootloader? Is that hardware-impossible or just such an exploit wasn't found yet?
Click to expand...
Click to collapse
I don't have any hope. No one is working on it. jcase and beaups aren't interested in motorola phones anymore and they were the only ones pretty much working on it who have the skillz needed to do it.
And maiko1 hasn't been responding to questions about MoFo via the forum or by email. He hasn't been on XDA since 5/27/15 so I don't know what is going on. It is like he abandoned MoFo. Maybe he is sick or in the hospital and can't respond, idk, but he hasn't been responding to anyone in awhile. When 5.1 drops, the copy of MoFo you have now won't work on it. He would need to update the MoFo site and I worry that he isn't interested anymore.
If you have the ability to return the XT1097 and get an XT1095, that is what I would do.
---------- Post added at 09:02 PM ---------- Previous post was at 09:00 PM ----------
qyron said:
4. Assuming that such exploit probably will need KitKat, will I be able to downgrade to 4.4.4 later if I update 5.0.2 OTA now?
Click to expand...
Click to collapse
There is no reason to think that the exploit will be found on KK. jcase and beaups looked for one and didn't find one and gave up.
And no, you will never be able to downgrade your bootloader to 4.4.4 once you upgrade to 5.0.2.
JulesJam said:
Yes but to make it you have to either use another device with an unlocked bootloader like a Nexus 9 or a Moto X 2013, or if you know someone with an XT1095 they can make it for you. Or if you know linux you can make it.
---------- Post added at 08:56 PM ---------- Previous post was at 08:55 PM ----------
Can you return and buy an XT1095 instead? That is what I would do.
---------- Post added at 08:57 PM ---------- Previous post was at 08:56 PM ----------
Yes read my noob guide in the General forum (it is linked to in the OP of the MoFo thread).
---------- Post added at 09:00 PM ---------- Previous post was at 08:57 PM ----------
I don't have any hope. No one is working on it. jcase and beaups aren't interested in motorola phones anymore and they were the only ones pretty much working on it who have the skillz needed to do it.
And maiko1 hasn't been responding to questions about MoFo via the forum or by email. He hasn't been on XDA since 5/27/15 so I don't know what is going on. It is like he abandoned MoFo. Maybe he is sick or in the hospital and can't respond, idk, but he hasn't been responding to anyone in awhile. When 5.1 drops, the copy of MoFo you have now won't work on it. He would need to update the MoFo site and I worry that he isn't interested anymore.
If you have the ability to return the XT1097 and get an XT1095, that is what I would do.
---------- Post added at 09:02 PM ---------- Previous post was at 09:00 PM ----------
There is no reason to think that the exploit will be found on KK. jcase and beaups looked for one and didn't find one and gave up.
And no, you will never be able to downgrade your bootloader to 4.4.4 once you upgrade to 5.0.2.
Click to expand...
Click to collapse
You say we can make images using linux, can you make a guide or at least explain quickly how this is done? I'm moderately proficient in linux and I'm thinking about being the guinea pig who tries to make a rom for the XT1097.
darknessrise1234 said:
You say we can make images using linux, can you make a guide or at least explain quickly how this is done? I'm moderately proficient in linux and I'm thinking about being the guinea pig who tries to make a rom for the XT1097.
Click to expand...
Click to collapse
If you're moderately proficient I won't go into too much detail, you basically just use the mount command to mount the ext4 image then modify then unmount then flash.
G4 Man2 said:
If you're moderately proficient I won't go into too much detail, you basically just use the mount command to mount the ext4 image then modify then unmount then flash.
Click to expand...
Click to collapse
So I'm right it has to be an installed image, not a fxz? I have a 5.1 fxz and I was looking to attempt a 5.1 image for our 1097.
Does gravitybox work with on this image?
Sent from my XT1097 using XDA Premium 4 mobile app
QA Bot said:
Q&A for MoFo IMG AT&T XT1097 (root, tether, xposed)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its !
Click to expand...
Click to collapse
JulesJam said:
Do you know anyone with an XT1095? If so it is really easy to do and they can make a nandroid of their system and just restore it when they are done.
Click to expand...
Click to collapse
For some reason the xposed doesn't work for me.
See screenshot from attachment
I got a ATT xt1097
My flash procedure:
1. enter recovery and wipe data/cache
2. flash stock image with just root
3. wipe cache(If I don't do this there will be a bootloop)
4. enter system, turn on Unknown Sources (read from another website), Install Xposed Installer (tried both 2.7 experimental1 and 2.6.1), delete everything in dalvik-cache
5. fastboot flash your mod
6. wipe cache
7. enter system, there is a long updating app process.
8. open Xposed installer and it doesn;t work
lihanchen said:
For some reason the xposed doesn't work for me.
See screenshot from attachment
I got a ATT xt1097
My flash procedure:
1. enter recovery and wipe data/cache
2. flash stock image with just root
3. wipe cache(If I don't do this there will be a bootloop)
4. enter system, turn on Unknown Sources (read from another website), Install Xposed Installer (tried both 2.7 experimental1 and 2.6.1), delete everything in dalvik-cache
5. fastboot flash your mod
6. wipe cache
7. enter system, there is a long updating app process.
8. open Xposed installer and it doesn;t work
Click to expand...
Click to collapse
Are you using mofo?
JulesJam said:
Are you using mofo?
Click to expand...
Click to collapse
Yes. otherwise I can't flash. AT&T sucks
---------- Post added at 01:20 AM ---------- Previous post was at 01:01 AM ----------
JulesJam said:
Are you using mofo?
Click to expand...
Click to collapse
And one thing I notice is that every time there is a 10-second starting app process before loading the launcher after the Moto Earth animation. Similar dialog as updating apps
lihanchen said:
Yes. otherwise I can't flash. AT&T sucks
And one thing I notice is that every time there is a 10-second starting app process before loading the launcher after the Moto Earth animation. Similar dialog as updating apps
Click to expand...
Click to collapse
You need to follow the instructions in the OP exactly as written, by what you posted you aren't doing that. There is no need for instance to enable Unknown Sources.
JulesJam said:
You need to follow the instructions in the OP exactly as written, by what you posted you aren't doing that. There is no need for instance to enable Unknown Sources.
Click to expand...
Click to collapse
I tried turning on/ not turning on unknown sources
Also use ES file explorer/ adb shell to delete dalvik cache
Also wipe cache/ not wipe cache after flashing the mod.zip (second zip)
Can't get it working anyway
JulesJam said:
You need to follow the instructions in the OP exactly as written, by what you posted you aren't doing that. There is no need for instance to enable Unknown Sources.
Click to expand...
Click to collapse
Let's discuss in this post. I accidentally sent a post on the original thread instead of Q&A and can't delete it.
I googled "xposed installer" and clicked the first link, tried both 2.7 experimental 1 and 2.6.1, installed with adb
Also, for last step, I installed "APM+" module and it didn't work.
lihanchen said:
Let's discuss in this post. I accidentally sent a post on the original thread instead of Q&A and can't delete it.
I googled "xposed installer" and clicked the first link, tried both 2.7 experimental 1 and 2.6.1, installed with adb.
Click to expand...
Click to collapse
But what version of the Xposed installer was used when the dev made the image? That may be the issue as the installer has been updated but I am not sure if the image was. Idk the anwer - the dev would know.
JulesJam said:
But what version of the Xposed installer was used when the dev made the image? That may be the issue as the installer has been updated but I am not sure if the image was. Idk the anwer - the dev would know.
Click to expand...
Click to collapse
From the release date, I believe 2.6.1 is the correct one.
Plus, in another post about mofo image of motoX gen1 of the same author, he mentioned explicitly of xposed installer 2.6.1
lihanchen said:
From the release date, I believe 2.6.1 is the correct one.
Plus, in another post about mofo image of motoXat gen1 of the same author, he mentioned explicitly of xposed installer 2.6.1
Click to expand...
Click to collapse
Well if you are using the correct version of the installer and following the instructions in the OP for the image as written it should work. I would flash back to stock system and start again from scratch if it isn't working for you making sure you are following the instructions.

Getting rid of Sprint/LG Bloatware

Does anyone have a list or a link to a list that we can refer to for removing/cleaning bloatware that comes with stock Sprint LG G4?
I've tried bloatware tool but that doesn't remove anything, it simply hides it so its not visible.
Thanks!
chirayu said:
Does anyone have a list or a link to a list that we can refer to for removing/cleaning bloatware that comes with stock Sprint LG G4?
I've tried bloatware tool but that doesn't remove anything, it simply hides it so its not visible.
Thanks!
Click to expand...
Click to collapse
Seconded, we should have a community list of apps that are safe to remove from the Sprint version of the G4 without breaking anything vital, now that we have root. OP if you haven't, I'd suggest you go and root your sprint G4.
elsamuraiguapo said:
Seconded, we should have a community list of apps that are safe to remove from the Sprint version of the G4 without breaking anything vital, now that we have root. OP if you haven't, I'd suggest you go and root your sprint G4.
Click to expand...
Click to collapse
It was rooted within 10 minutes of public release I am on the fence about debloating tool until someone compiles a proper list.
chirayu said:
It was rooted within 10 minutes of public release I am on the fence about debloating tool until someone compiles a proper list.
Click to expand...
Click to collapse
Debloating tool is obsolete if you have root because you can directly freeze or even uninstall unwanted apps with root apps like Titanium Backup. There was a list floating around somewhere of apps to use the debloating tool on, but now that we have root I'd rather see someone compile a list of apps or apks safe to completely uninstall.
Running list of apps safe to remove.
elsamuraiguapo said:
Debloating tool is obsolete if you have root because you can directly freeze or even uninstall unwanted apps with root apps like Titanium Backup. There was a list floating around somewhere of apps to use the debloating tool on, but now that we have root I'd rather see someone compile a list of apps or apks safe to completely uninstall.
Click to expand...
Click to collapse
It isn't much yet since I'm trying to be safe about it, but I started a list here:
http://forum.xda-developers.com/spr...itial-list-removable-apps-using-root-t3168299
Testing LG apps with freezing and disabling intents so far has either broken something or caused a dramatic impact on battery life. But I have only just begun!
elsamuraiguapo said:
Debloating tool is obsolete if you have root because you can directly freeze or even uninstall unwanted apps with root apps like Titanium Backup. There was a list floating around somewhere of apps to use the debloating tool on, but now that we have root I'd rather see someone compile a list of apps or apks safe to completely uninstall.
Click to expand...
Click to collapse
@elsamuraiguapo quick question. I have Titanium used it on my Nexus 5 and I suppose I got spoiled not having bloatware. I'm kind of fuzzy on the freeze option in Titanium since I've never needed it. What does it do? I know you can uninstall apps with it even though I never needed to.
Waiting till tomorrow to root this phone! I can't live without root!
MrBiggzz said:
@elsamuraiguapo quick question. I have Titanium used it on my Nexus 5 and I suppose I got spoiled not having bloatware. I'm kind of fuzzy on the freeze option in Titanium since I've never needed it. What does it do? I know you can uninstall apps with it even though I never needed to.
Waiting till tomorrow to root this phone! I can't live without root!
Click to expand...
Click to collapse
I would personally hold off on rooting the device until we have a KDZ/TOT file to return to stock in case of a soft brick. I have personally bricked 2 devices now trying to freeze/uninstall via titanium backup.
Just a word of waring!
---------- Post added at 09:59 PM ---------- Previous post was at 09:50 PM ----------
Also this might be of some use - http://www.andromods.com/apps-mod/how-to-safely-disable-bloatware-lg-g4-no-root.html
elsamuraiguapo said:
Debloating tool is obsolete if you have root because you can directly freeze or even uninstall unwanted apps with root apps like Titanium Backup. There was a list floating around somewhere of apps to use the debloating tool on, but now that we have root I'd rather see someone compile a list of apps or apks safe to completely uninstall.
Click to expand...
Click to collapse
thetruejay20 said:
I would personally hold off on rooting the device until we have a KDZ/TOT file to return to stock in case of a soft brick. I have personally bricked 2 devices now trying to freeze/uninstall via titanium backup.
Just a word of waring!
---------- Post added at 09:59 PM ---------- Previous post was at 09:50 PM ----------
Also this might be of some use - http://www.andromods.com/apps-mod/how-to-safely-disable-bloatware-lg-g4-no-root.html
Click to expand...
Click to collapse
Is this post what your are talking about?
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
I've been spoiled so far having a Nexus devices. Had Wug Fresh's Nexus Root Toolkit. Everything was a breeze. So if you'd be as so kind to tell me what KDZ/TOT is. I've see that acronym quite a bit the past couple of days.
Using Titanium I would more likely freeze rather than remove. I don't see how that could soft brick the phone. Mind you I'm no expert so try to understand my ignorance in the matter.
So is this just a matter of the phone being really new and if I just sit on it for a few more months rooting and recover may change?
I just saw that URL you left about the Debloater. I'll have to check that out.
MrBiggzz said:
Is this post what your are talking about?
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
I've been spoiled so far having a Nexus devices. Had Wug Fresh's Nexus Root Toolkit. Everything was a breeze. So if you'd be as so kind to tell me what KDZ/TOT is. I've see that acronym quite a bit the past couple of days.
Using Titanium I would more likely freeze rather than remove. I don't see how that could soft brick the phone. Mind you I'm no expert so try to understand my ignorance in the matter.
So is this just a matter of the phone being really new and if I just sit on it for a few more months rooting and recover may change?
I just saw that URL you left about the Debloater. I'll have to check that out.
Click to expand...
Click to collapse
Yes that's the post about KDZ, and Basically KDZ/TOT lets you re-flash your phone back to stock like you just bought the phone from the store.
And evening freezing them may cause an issue, not 100% sure haven't been able to play with it much lol. Because yes the phone is so new, not a lot of development going on.

Nexus 6 on AT&T - Major MMS issues since upgrading to 6.0

Hey guys - I have a Google-bought Nexus 6 running on AT&T. I have never had MMS issues until now. I clean-flashed 6.0 and have had no problems except with MMS...most of they time they won't send/receive.
The APN settings are currently the default, set to nxtgenphone.
I have spoken to AT&T and verified that the settings are correct. I just received a new SIM card from AT&T and it hasn't changed anything.
Anyone have any suggestions or similar experience?
Thanks!
No problems here...unlocked N6 running on AT&T. You might check your MMS settings as to the file size. Maybe it's set too small. Also - make sure you have set your app to be the default sms/mms app.
I have run several message apps with no problem...currently using Next SMS (formerly Handcent)
OKAstro said:
No problems here...unlocked N6 running on AT&T. You might check your MMS settings as to the file size. Maybe it's set too small. Also - make sure you have set your app to be the default sms/mms app.
I have run several message apps with no problem...currently using Next SMS (formerly Handcent)
Click to expand...
Click to collapse
I don't believe there are MMS settings for size in the Messenger app...and it is set to default...not sure how that would help though.
The size is only a factor if the mms is over 600 kb. Att has that as their max limit. As long as your apns are correct you should be good.
zelendel said:
The size is only a factor if the mms is over 600 kb. Att has that as their max limit. As long as your apns are correct you should be good.
Click to expand...
Click to collapse
Well my APN is correct and I am not good :crying: lol
If the SIM card is good, the APN is correct...and now I've tried Hangouts instead of Messenger and it has the same problem...then it must either be something on my account on AT&T's side or perhaps I need to try and do a clean flash and test MMS with no modifications (not that I have many...just TWRP and root).
jeffreii said:
Well my APN is correct and I am not good :crying: lol
If the SIM card is good, the APN is correct...and now I've tried Hangouts instead of Messenger and it has the same problem...then it must either be something on my account on AT&T's side or perhaps I need to try and do a clean flash and test MMS with no modifications (not that I have many...just TWRP and root).
Click to expand...
Click to collapse
You don't have data disabled on your account do you?
If all is good then it has to be att that is the issue.
Delete all apn's except for the one your using by default had the same issue a while back in also on the n6 at&t
---------- Post added at 04:11 PM ---------- Previous post was at 04:10 PM ----------
jeffreii said:
Hey guys - I have a Google-bought Nexus 6 running on AT&T. I have never had MMS issues until now. I clean-flashed 6.0 and have had no problems except with MMS...most of they time they won't send/receive.
The APN settings are currently the default, set to nxtgenphone.
I have spoken to AT&T and verified that the settings are correct. I just received a new SIM card from AT&T and it hasn't changed anything.
Anyone have any suggestions or similar experience?
Thanks!
Click to expand...
Click to collapse
Delete all APN'S except the one you are currently using my guess is your gonna have about 5 in there you only need the one that is already selected when you first open the apn section
zelendel said:
You don't have data disabled on your account do you?
If all is good then it has to be att that is the issue.
Click to expand...
Click to collapse
Thanks - I use lots of data so definitely not that. I'm going to contact AT&T again and have them thoroughly look through my account.
galaxy s4 nutjob said:
Delete all apn's except for the one your using by default had the same issue a while back in also on the n6 at&t
---------- Post added at 04:11 PM ---------- Previous post was at 04:10 PM ----------
Delete all APN'S except the one you are currently using my guess is your gonna have about 5 in there you only need the one that is already selected when you first open the apn section
Click to expand...
Click to collapse
I saw this tip somewhere else and have already tried deleting the other APNs to no avail
jeffreii said:
Thanks - I use lots of data so definitely not that. I'm going to contact AT&T again and have them thoroughly look through my account.
I saw this tip somewhere else and have already tried deleting the other APNs to no avail
Click to expand...
Click to collapse
Have you tried using a different apn?
galaxy s4 nutjob said:
Have you tried using a different apn?
Click to expand...
Click to collapse
Yes I've tried both the default nxtgenphone and the second one: phone. The only one I didn't try is the third one: wap.cingular.
From everything I've read, there's no reason why nxtgenphone shouldn't work fine.
jeffreii said:
Yes I've tried both the default nxtgenphone and the second one: phone. The only one I didn't try is the third one: wap.cingular.
From everything I've read, there's no reason why nxtgenphone shouldn't work fine.
Click to expand...
Click to collapse
I feel like such a noob. All this random fix trying, and we don't even have a logcat.
Grab a logcat and post it up. This will tell use just what's going on.
Sorry. Should have suggested this before. Troubleshooting 101
I have the same thing on my oneplus one on all 6.0 roms with AT&T.
If I turn off mobile data and turn it back on, my group MLS send/receive fine for a little while.
Meanwhile I am streaming Netflix on the train endlessly without interruption.
jeffreii said:
Hey guys - I have a Google-bought Nexus 6 running on AT&T. I have never had MMS issues until now. I clean-flashed 6.0 and have had no problems except with MMS...most of they time they won't send/receive.
The APN settings are currently the default, set to nxtgenphone.
I have spoken to AT&T and verified that the settings are correct. I just received a new SIM card from AT&T and it hasn't changed anything.
Anyone have any suggestions or similar experience?
Thanks!
Click to expand...
Click to collapse
Try disabling Google hangouts and uninstalling Google hangouts updates
---------- Post added at 07:53 PM ---------- Previous post was at 07:47 PM ----------
jeffreii said:
Yes I've tried both the default nxtgenphone and the second one: phone. The only one I didn't try is the third one: wap.cingular.
From everything I've read, there's no reason why nxtgenphone shouldn't work fine.
Click to expand...
Click to collapse
Or you can freeze the Google hangouts temporarily with this
https://play.google.com/store/apps/details?id=ccc71.at.free
And see if that helps
---------- Post added at 07:58 PM ---------- Previous post was at 07:53 PM ----------
Or flash cataclysm works great for me full 6.0 experience and very close to stock
https://www.androidfilehost.com/?w=files&flid=40894
zelendel said:
I feel like such a noob. All this random fix trying, and we don't even have a logcat.
Grab a logcat and post it up. This will tell use just what's going on.
Sorry. Should have suggested this before. Troubleshooting 101
Click to expand...
Click to collapse
Ok - I started a CatLog recording session and then attempted to send an MMS through Messenger. I waited until it failed...then waited another 20 seconds...then deleted the message and stopped the recording. Hopefully that got everything. See attached.
Thanks!
SchmilK said:
I have the same thing on my oneplus one on all 6.0 roms with AT&T.
If I turn off mobile data and turn it back on, my group MLS send/receive fine for a little while.
Meanwhile I am streaming Netflix on the train endlessly without interruption.
Click to expand...
Click to collapse
I'm willing to try anything so I disabled data...turned it back on 15 seconds later and tried to send an MMS. Same failure.
galaxy s4 nutjob said:
Try disabling Google hangouts and uninstalling Google hangouts updates
---------- Post added at 07:53 PM ---------- Previous post was at 07:47 PM ----------
Or you can freeze the Google hangouts temporarily with this
https://play.google.com/store/apps/details?id=ccc71.at.free
And see if that helps
---------- Post added at 07:58 PM ---------- Previous post was at 07:53 PM ----------
Or flash cataclysm works great for me full 6.0 experience and very close to stock
https://www.androidfilehost.com/?w=files&flid=40894
Click to expand...
Click to collapse
I froze Hangouts with TiBu, rebooted the phone, and tried to send an MMS with Messenger. Failed again.
Are you connected to Wifi? Can you send any MMS with WiFi off? Right now Cricket is having some sort of MMS Proxy DNS issue. Just a thought, given Cricket runs on AT&T, maybe some AT&T users are affected too.
Reference: https://www.reddit.com/r/NoContract...y_with_cricket_wireless_mms/cw655vx?context=9
BinaryW01f said:
Are you connected to Wifi? Can you send any MMS with WiFi off? Right now Cricket is having some sort of MMS Proxy DNS issue. Just a thought, given Cricket runs on AT&T, maybe some AT&T users are affect too.
Reference: https://www.reddit.com/r/NoContract...y_with_cricket_wireless_mms/cw655vx?context=9
Click to expand...
Click to collapse
Thanks but this has been happening for a few weeks now...in all situations, including no wifi. I just tried it again just in case!
jeffreii said:
Ok - I started a CatLog recording session and then attempted to send an MMS through Messenger. I waited until it failed...then waited another 20 seconds...then deleted the message and stopped the recording. Hopefully that got everything. See attached.
Thanks!
I'm willing to try anything so I disabled data...turned it back on 15 seconds later and tried to send an MMS. Same failure.
I froze Hangouts with TiBu, rebooted the phone, and tried to send an MMS with Messenger. Failed again.
Click to expand...
Click to collapse
Wow there were a ton of errors in that logcat. Many dealing with package manager. I would advise you to do a clean flash. When I say clean I mean wipe the whole device. Then flash the stock image, there are errors all over the place with some system files. I also see you have push bullet installed. Try removing it.
Here is the main mms error.
11-04 22:30:09.664 E/MmsService( 2311): [[email protected]] HTTP: IO failure
11-04 22:30:09.664 E/MmsService( 2311): java.net.UnknownServiceException: CLEARTEXT communication not supported: []
The best advise I could give you is start from scratch. This way it will remove some of those other errors that may or may not be messing with other system apps.
Did you happen to restore some system app settings?
zelendel said:
Wow there were a ton of errors in that logcat. Many dealing with package manager. I would advise you to do a clean flash. When I say clean I mean wipe the whole device. Then flash the stock image, there are errors all over the place with some system files. I also see you have push bullet installed. Try removing it.
Here is the main mms error.
11-04 22:30:09.664 E/MmsService( 2311): [[email protected]] HTTP: IO failure
11-04 22:30:09.664 E/MmsService( 2311): java.net.UnknownServiceException: CLEARTEXT communication not supported: []
The best advise I could give you is start from scratch. This way it will remove some of those other errors that may or may not be messing with other system apps.
Did you happen to restore some system app settings?
Click to expand...
Click to collapse
Thanks for taking a look. When upgrading to 6.0, I wiped my device multiple times with TWRP - wiped everything, not just system. I then flashed 6.0 with ADB. The only modification I made were with Chainfire's boot.img to achieve root...and left TWRP in place as well. I also wiped the device again after flashing 6.0. I then clean installed everything and redid settings for 90% of my apps manually...only a few were restored via in-app restore process or TiBu - as always I would never restore data for any system apps.
I will try removing Pushbullet and see if that helps...perhaps another Logcat without Pushbullet, in case that's the culprit of these errors?
I can wipe and redo everything, but I don't see myself performing it any differently.
Thanks again!
jeffreii said:
Thanks for taking a look. When upgrading to 6.0, I wiped my device multiple times with TWRP - wiped everything, not just system. I then flashed 6.0 with ADB. The only modification I made were with Chainfire's boot.img to achieve root...and left TWRP in place as well. I also wiped the device again after flashing 6.0. I then clean installed everything and redid settings for 90% of my apps manually...only a few were restored via in-app restore process or TiBu - as always I would never restore data for any system apps.
I will try removing Pushbullet and see if that helps...perhaps another Logcat without Pushbullet, in case that's the culprit of these errors?
I can wipe and redo everything, but I don't see myself performing it any differently.
Thanks again!
Click to expand...
Click to collapse
Ok. Wait you wiped after flashing as well? This may cause an issue. only a small chance but a chance none the less.
Ok to trouble shoot this here is what I would do step by step.
1. Fully wipe the device, system, data, both caches, internal storage (back it up of course) (this is also a perfect time to remove encryption if desired)
2.Flash The stock rom and let it load. Try MMS
3.Flash Chains files for root, test mms again.
4.Keep going one by one until it breaks.
If it doesnt work on pure stock set up. Then grab another logcat and we can see where the error is then.
This is not something that will be done right away so set plenty of time aside for it. This way you dont get rushed and maybe just maybe we can figure this out.
Feel free to look at the logcat. I know it seems intimidating but it really isnt. You can see errors by just looking for the E/ after the time. While you might not completely understand what your looking at it will give hints on the issue and if you look at them enough times they kinda start to make sense.
zelendel said:
Ok. Wait you wiped after flashing as well? This may cause an issue. only a small chance but a chance none the less.
Ok to trouble shoot this here is what I would do step by step.
1. Fully wipe the device, system, data, both caches, internal storage (back it up of course) (this is also a perfect time to remove encryption if desired)
2.Flash The stock rom and let it load. Try MMS
3.Flash Chains files for root, test mms again.
4.Keep going one by one until it breaks.
If it doesnt work on pure stock set up. Then grab another logcat and we can see where the error is then.
This is not something that will be done right away so set plenty of time aside for it. This way you dont get rushed and maybe just maybe we can figure this out.
Feel free to look at the logcat. I know it seems intimidating but it really isnt. You can see errors by just looking for the E/ after the time. While you might not completely understand what your looking at it will give hints on the issue and if you look at them enough times they kinda start to make sense.
Click to expand...
Click to collapse
So after flashing all the files, I booted the system to make sure it was up and running fine. Then I went back to TWRP and wiped it for good measure.
Chainfire's boot.img was flashed with the rest of the 6.0 package (never flashed the standard boot.img) to insure that it didn't encrypt the device on first boot.
I just ran another Logcat after uninstalling Pushbullet and there are still a massive number of errors and the same failure to send the MMS...I guess I have a full wipe in my future again...I'll probably wait until we have images for the latest security fixes to do it all at once.
Thanks again!

Categories

Resources