Database Develop

Removed Dialer (I know...) No data, please assist.

So upon removing some of the bloat on my Droid 3, I broke mms and contacts. I successfully installed AOSP 2.3.5 mms so I thought I'd try to install stock contacts. I ended up backing up BlurPhone and BlurContacts and then deleting them and replacing them with the AOSP .apks... Now I have no data, and I can't restore the backups I made. I even pulled BlurPhone and BlurContacts from the Droid 3 system dump and pushed them to /system/app to no avail. Any ideas how to unbork my phone? Thanks.

Androidsims said:
So upon removing some of the bloat on my Droid 3, I broke mms and contacts. I successfully installed AOSP 2.3.5 mms so I thought I'd try to install stock contacts. I ended up backing up BlurPhone and BlurContacts and then deleting them and replacing them with the AOSP .apks... Now I have no data, and I can't restore the backups I made. I even pulled BlurPhone and BlurContacts from the Droid 3 system dump and pushed them to /system/app to no avail. Any ideas how to unbork my phone? Thanks.
Click to expand...
Click to collapse
Factory Reset perhaps? Honestly, I'm a bit confused why you would do that to your device when we don't even have an SBF to restore to. Do you want an expensive new paper weight?

I had a temporary lapse of intelligence. I'm at work right now but I will attempt to push all system files back to the phone and do a restore. If that doesn't work, I've heard of people successfully flashing an Atrix SBF so I'll try that next. IF neither of those work, I'll beg Verizon to exchange it or I make an insurance claim, lol.

Yep I did the same thing. This could help, its a backup of the entire /system/app folder
media fire ...../?xntww3x2h2xow24
I can't figure out what I'm supposed to push back there to get functionality back. I know you have to repair perms after pushing.

Androidsims said:
I had a temporary lapse of intelligence. I'm at work right now but I will attempt to push all system files back to the phone and do a restore. If that doesn't work, I've heard of people successfully flashing an Atrix SBF so I'll try that next. IF neither of those work, I'll beg Verizon to exchange it or I make an insurance claim, lol.
Click to expand...
Click to collapse
I believe what you may have heard about was people flashing the Atrix preinstall partition in an effort to find a root exploit (which ultimately turned out to be a dead end). This is entirely different from flashing an Atrix SBF. If you attempt to do this, you're almost certain to brick your phone.
Sent from my DROID3 using xda premium

RandomEncounter said:
I believe what you may have heard about was people flashing the Atrix preinstall partition in an effort to find a root exploit (which ultimately turned out to be a dead end). This is entirely different from flashing an Atrix SBF. If you attempt to do this, you're almost certain to brick your phone.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
That is what i meant, the root.img. Sleepy, sorry.
Still no headway with this thing... might be stopping by Verizon tomorrow.

First off, did you push the odex files for those 2 apks as well? I don't know the significance of them, but if they were in the system dump, it's probably a good idea to put them in the /system/app directory.
Second, did you fix the permissions and owner of the files you pushed?

Javier78 said:
First off, did you push the odex files for those 2 apks as well? I don't know the significance of them, but if they were in the system dump, it's probably a good idea to put them in the /system/app directory.
Second, did you fix the permissions and owner of the files you pushed?
Click to expand...
Click to collapse
Yes and yes.

...Huh. Well, I'm not entirely sure what to do then (I've never dealt with the dialer). My best advice would be to play dumb when you go exchange it.
Sorry!

For me I think I'm going to just leave it like it is until the first custom ROM appears.

There are some bloatware that is ok to remove. I removed most of the ones that you can just re-download from the Market like: NFLMobile, ZumoCast, GuidedTours, Slackerradio, Citrix, BlockBuster, and MyVerizon. I did not touch a lot of the main VZW apps that they put on out of fear of some other part of android being tied to them. But random apps like the BlockBuster and SlackerRadio are fine to remove.

Why not just install a 3rd party dialer such as GoDialer or something until we get an sbf?
Sent from my DROID X2 using XDA App

You might check to see if they were disabled with package manager. Enter pm list packages -d from the command line.
Sent from my DROID3 using Tapatalk

Block OTAs? (possible upcoming 4.4.4)

Heya guys. I couldn't find much info on this for the X, and certainly not anything about this particular update.
I'm not too fond of jumping on board a new ship before I get a good look at it.
Has anyone before successfully blocked an incoming OTA update? I'm particularly interested in VZW moto Xs, though any info is helpful.
In a nutshell, I'm aiming to block the 4.4.4 OTA on a non-dev, non-rooted VZW moto X.
I'm sure it may not be possible without root, but I'm interested in opinions.

Just hit no when it tells you havê a new update
Sent from my XT1058 using XDA Free mobile app

chrisp6825 said:
Heya guys. I couldn't find much info on this for the X, and certainly not anything about this particular update.
I'm not too fond of jumping on board a new ship before I get a good look at it.
Has anyone before successfully blocked an incoming OTA update? I'm particularly interested in VZW moto Xs, though any info is helpful.
In a nutshell, I'm aiming to block the 4.4.4 OTA on a non-dev, non-rooted VZW moto X.
I'm sure it may not be possible without root, but I'm interested in opinions.
Click to expand...
Click to collapse
using titanium backup or some program like it just freeze Motorola ota that should stop all ota notifications

kelvinmorcillo said:
Just hit no when it tells you havê a new update
Click to expand...
Click to collapse
Ah, I wasn't aware OTAs on this phone were optional. Some devices force them ASAP on a boot-up if available. Good to hear, and I hope it stays true.
adm1jtg said:
using titanium backup or some program like it just freeze Motorola ota that should stop all ota notifications
Click to expand...
Click to collapse
I'm not able to do this. Otherwise, I would. Root free, dev free, that's the life for me... for the time being at least...

chrisp6825 said:
Ah, I wasn't aware OTAs on this phone were optional. Some devices force them ASAP on a boot-up if available. Good to hear, and I hope it stays true.
I'm not able to do this. Otherwise, I would. Root free, dev free, that's the life for me... for the time being at least...
Click to expand...
Click to collapse
To stop the updates, this will do it but you will have to redo this everytime you reboot until you are rooted in stone not temp like Pie.. but this will stop any updates from coming to the phone and stop you from forcing an update. the two files Ive changed the name of the first two in the pic, it's the root / system / pri apps folder, I added .bak to the name, you have to do both of them.
If you don't rename them after every boot when you lose Pie they revert back to original and you will get the notice again and you might accidentally hit install when the notice pops up.. so just re Pie and change them.. I use FX explorer with root addon. It's a great app and free and takes less than a minute to rename the files.

Looks like the OTA reached me. It creates a permanent notification from the MotoOTA app.
Without write-protection enabled, you can't disable this app permanently. Most likely in a temp-root instance, freezing it in titanium backup may not take effect on the app til reboot, or possibly a hot-reboot.
I just un-enabled notifications for the app, though I'm hoping it won't auto download during idle.
And apparently (I'm) not able to freeze it. See screen shots.
tapa'd on my moto x

chrisp6825 said:
Looks like the OTA reached me. It creates a permanent notification from the MotoOTA app.
Without write-protection enabled, you can't disable this app permanently. Most likely in a temp-root instance, freezing it in titanium backup may not take effect on the app til reboot, or possibly a hot-reboot.
I just un-enabled notifications for the app, though I'm hoping it won't auto download during idle.
And apparently (I'm) not able to freeze it. See screen shots.
tapa'd on my moto x
Click to expand...
Click to collapse
It won't install automatically...almost guaranteed.
But why can't you freeze it? You should be able to click it, opening up a menu with a freeze option. My guess is that it will revert back to 'unfrozen' after the next reboot, but I HAVE seen a post or two that suggests otherwise (not sure how reputable, if at all).
I have several system apps frozen (mostly the google play music/movies/games/etc. bloat, along with a couple others). The fact that it is red just indicates it is a system app. You might have to mount /system r/w in order to be able to freeze it, but once again, I've read some posts suggesting that mounting r/w was tricky with the temp-root (and of course, will revert all changes upon reboot).
I would give you more definitive answers, but since I'm unlocked, its difficult for me to test...
Good Luck! If you can just put up with the nag, you'll be fine. As you well know, once you accept it, it's game-over for root.

Chris forget about that freeze crap do what I said to do and you won't have any issues I did it yesterday.. rebooted the phone lost towelpie got the 4.4.4 notice started downloading because wanted to know what it was.. than ran towelpie, went to a root/system/priv-apps and deleted the 3c ota files and it stopped that download as it was downloading. i wanted to download it to see what it was so i had to reboot the phone to get rid of towelpie and that got the 3c ota files back and then it rebegan the download I don't use Titanium Backup I just manually delete. I did it Verizon 4.4.2 non dev locked boot
now after I downloaded 4.4.4 and rooted with towelPie.. it did cause the root to act kind of funny I went into FX root explorer tried to rename the 3c ota files after mounting Fx Explorer in write mode it still told me the files were not writable that must have had something to do with the new download.. so my corrective action was to go into fx root explorer cashe folder send that new update into outerfreakin space then reboot the phone retowelpie and then mount fx Explorer in write mode again and deleted 3c ota files and had no problem after rebooting.. but once you download that file it permanently does something to your phone until you delete it from the cashe folder and reboot.

samwathegreat said:
It won't install automatically...almost guaranteed.
But why can't you freeze it?
Click to expand...
Click to collapse
In that screen shot, I had just attempted to freeze it 3 times. It's as if I haven't even tried though.
As long as it won't auto download, I'm cool with it. Kit Kat or jelly bean introduced the option to disable notifications from apps, so that gets it out of my way.
tapa'd on my moto x

Once you delete the 3c_ota.apk and 3c_ota.odex files your phone is NOT capable of checking for or downloading an OTA.
And towelPie root allows you to delete these files if you use FX explorer with root add-on, its available in playstore, and explains how to mount in write mode allowing you to rename or delete any file, it takes all of 10 seconds.
FX file explorer
https://play.google.com/store/apps/details?id=nextapp.fx&hl=en
Root add-on for for FX explorer to access root files
https://play.google.com/store/apps/details?id=nextapp.fx.rr&hl=en

Right, but this is something that obviously has to be done every boot, and I imagine may need to be soft-rebooted after to take effect, so the app won't load during boot.
I may do that our write a quick script to take care of it each rooted boot for me in a while. Thanks for the info
tapa'd on my moto x

So I just renamed the system files... So much for not trying to auto update. Then next screen after I hit later asked me to select a time of day for the next reminder.
Silly.
I'll see if I still get this after the files are renamed.
tapa'd on my moto x

Renamed my files. So far, no notification. Thx.

chrisp6825 said:
So I just renamed the system files... So much for not trying to auto update. Then next screen after I hit later asked me to select a time of day for the next reminder.
Silly.
I'll see if I still get this after the files are renamed.
tapa'd on my moto x
Click to expand...
Click to collapse
you have to go into system root cashe folder and send the downloaded file to kingdome come than you wont get the install prompt. the phone is not capable of downloading the update if you rename the files

the file in cashe is that the Verizon ghost zip?delete then re name the other ota in priv folder?
Thanks

gmmurphy said:
the file in cashe is that the Verizon ghost zip?delete then re name the other ota in priv folder?
Thanks
Click to expand...
Click to collapse
that is it. either delete it, rename it, or move someplace else (like /sdcard)

I froze MotorolaOTA 1.0 in Titanium Backup using Towel Root. (Also works using Pie Root). Blocks of obedience obnoxious update requests.
Sent from my Nexus 7

[Q] Replace Build.prop In TWRP

Hey all,
Today is not my day...just not paying attention. I accidentally replaced my build.prop file with a modified version but forgot to change the permissions so now I am boot looping. I can still access TWRP, so I was curious if there is any way to get a new build.prop file onto the phone so I do not have to do a full wipe. Any help would be appreciated.
Also, if its possible to flash onto the phone, does anyone have the build.prop file I can use? Thanks in advance.

I guess I can also access the bootloader for fastboot, if that makes a difference. Thanks.

JustROLLIN said:
I guess I can also access the bootloader for fastboot, if that makes a difference. Thanks.
Click to expand...
Click to collapse
You can either use mfastboot to flash the entire system. IMG for the rom you are using (easiest). Or use adb from within recovery to fix permissions on the build.prop....
Good luck :good:
Edit: re flashing just system will not affect you data. Only any modifications made to /system. For instance: if you are using xposed, it will need to be reinstalled. All other apps will be unaffected.

samwathegreat said:
You can either use mfastboot to flash the entire system. IMG for the rom you are using (easiest). Or use adb from within recovery to fix permissions on the build.prop....
Good luck :good:
Edit: re flashing just system will not affect you data. Only any modifications made to /system. For instance: if you are using xposed, it will need to be reinstalled. All other apps will be unaffected.
Click to expand...
Click to collapse
Your idea spurred me to use a method I used the other day, from this thread:
http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
Worked great and saved all data, thank you!

Looking for clean 4.4.2 RW backup or SBF

Does anybody here have a link to a clean and unrooted 4.4.2 backup or the RW 4.4.2 SBF for the Moto X?
I'm trying to gather all the files I need to prep for the coming 4.4.4 and my thumb drive with all my clean files corrupted.
Sent from my XT1049 using XDA Free mobile app

There are a few sites that host the Stock SBF files. I have them listed in -> http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347

Thanks! It seems motofirmware.com has the file listed but is not able to locate it.
http://sbf.droid-developers.org has been down for quite some time. This was my usual hunting ground and I know that they had the files I needed until they had multiple hard drive failures.
Filefactory did the trick though.

CF-Auto-Root

CF-Auto-Root's installing SuperSU are available for the Moto Z2 from https://desktop.firmware.mobi/
Search for nash in the search bar!
Thanks to @ac1dx for testing.

Chainfire said:
CF-Auto-Root's installing SuperSU are available for the Moto Z2 from https://desktop.firmware.mobi/
Search for nash in the search bar!
Thanks to @ac1dx for testing.
Click to expand...
Click to collapse
Root is there. Just as buggy as Magisk with this dual partition phone. Can't remove system apps with Titanium Backup. Can't set some things as r/w with root browser. Besides flashing the boot.img, is there anything else that needs to be done as some parts of system are r/o still or do we need twrp for full system access with this device?
Edit: as explained later in thread, this isn't an issue with CFAR, it's an issue with apps not working correctly with our boot partitions and directories.

Uzephi said:
Root is there. Just as buggy as Magisk with this dual partition phone. Can't remove system apps with Titanium Backup. Can't set some things as r/w with root browser. Besides flashing the boot.img, is there anything else that needs to be done as some parts of system are r/o still or do we need twrp for full system access with this device?
Click to expand...
Click to collapse
I have full system access. I have deleted both bootanimation zips to get the stock Android boot animation going. I have deleted some of the T-Mobile bloat. This was done with root explorer. All rooted apps work as they did with any other phone. I even flashed BusyBox with flashfire. But I think BusyBox is a little buggy on here. Not 100% sure lol.
Sent from my Moto Z (2) using Tapatalk

ac1dx said:
I have full system access. I have deleted both bootanimation zips to get the stock Android boot animation going. I have deleted some of the T-Mobile bloat. This was done with root explorer. All rooted apps work as they did with any other phone. I even flashed BusyBox with flashfire. But I think BusyBox is a little buggy on here. Not 100% sure lol.
Click to expand...
Click to collapse
I wish mine was that easy. You use Sprint model?. Below are attached images. Flashed stock removed Magisk then flashed CF.
One is TB showing root access. One is the error can't find APK. Then SU screen shot showing root. And the last one is the error when trying to move (not copy, but cut/paste) a system app to SD.
Edit: Chainfire, it seems the method for T-mob either isn't working the same for sprint or with dual boot.imgs there is some odd issue after updating. If you need logs, let me know how to help

Deleted.
Please see below.

ac1dx said:
I tried for the heck of it and it worked.
Oh, your on Sprint. No I'm on Tmobile. Wonder if it's boot image specifically to gsm and cdma.
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
I would think Chainfire did the same edits to T-Mob img as Sprint. (using their corresponding boot images) did yours flash boot_a or Boot_b? Mine flashed Boot_b
Edit:
C:\Users\Uzephi\Downloads>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_b' (20457 KB)...
OKAY [ 0.506s]
writing 'boot_b'...
OKAY [ 0.408s]
finished. total time: 0.918s
C:\Users\Uzephi\Downloads>fastboot reboot
rebooting...
finished. total time: 0.003s
C:\Users\Uzephi\Downloads>

Uzephi said:
I wish mine was that easy. You use Sprint model?. Below are attached images. Flashed stock removed Magisk then flashed CF.
One is TB showing root access. One is the error can't find APK. Then SU screen shot showing root. And the last one is the error when trying to move (not copy, but cut/paste) a system app to SD.
Edit: Chainfire, it seems the method for T-mob either isn't working the same for sprint or with dual boot.imgs there is some odd issue after updating. If you need logs, let me know how to help
Click to expand...
Click to collapse
It is different. Judging by the Magisk thread, you guys have a boot image for Sprint and one for TMobile.
Sent from my Moto Z (2) using Tapatalk
---------- Post added at 12:57 AM ---------- Previous post was at 12:54 AM ----------
Uzephi said:
I would think Chainfire did the same edits to T-Mob img as Sprint. (using their corresponding boot images) did yours flash boot_a or Boot_b? Mine flashed Boot_b
Edit:
C:\Users\Uzephi\Downloads>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_b' (20457 KB)...
OKAY [ 0.506s]
writing 'boot_b'...
OKAY [ 0.408s]
finished. total time: 0.918s
C:\Users\Uzephi\Downloads>fastboot reboot
rebooting...
finished. total time: 0.003s
C:\Users\Uzephi\Downloads>
Click to expand...
Click to collapse
Yes. It is boot_b. I know it's weird and we are all gonna have to get used to it lol. Hopefully roms are easy.
Sent from my Moto Z (2) using Tapatalk

ac1dx said:
It is different. Judging by the Magisk thread, you guys have a boot image for Sprint and one for TMobile.
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
Yes, We have different boot images and I downloaded the one specifically made for sprint by Chainfire per the linked website.

Uzephi said:
Yes, We have different boot images and I downloaded the one specifically made for sprint by Chainfire per the linked website.
Click to expand...
Click to collapse
I'm stumped then.
Sent from my Moto Z (2) using Tapatalk

ac1dx said:
I'm stumped then.
Click to expand...
Click to collapse
I found it out. Titanium Backup cannot find app due to it being in oem and not /sys. Removed Chrome and it worked and is a system app. All apps in system/app can be removed besides the one app I tried:Translate. Bug on my phone? Maybe... Attached images of the issue. One showing oem/app being Amazon, audible, etc. Second showing only translate not having correct perms in root browser. Odd.....

Uzephi said:
I found it out. Titanium Backup cannot find app due to it being in oem and not /sys. Removed Chrome and it worked and is a system app. All apps in system/app can be removed besides the one app I tried:Translate. Bug on my phone? Maybe... Attached images of the issue. One showing oem/app being Amazon, audible, etc. Second showing only translate not having correct perms in root browser. Odd.....
Click to expand...
Click to collapse
I have the same issue.
Sent from my Moto Z (2) using Tapatalk

filthyfnj24 said:
I have the same issue.
Click to expand...
Click to collapse
When all else fails, use lucky patcher. Just be sure the stock image will flash for you. It won't back up apps, but it removed all my bloat I wanted to remove...
Edit: tried removing Translate. The one System/app that has wrong permissions. Lucky Patcher was about to remove it, hard reboot and it's still there with the wrong permissions. I guess translate is a must on stock?

Uzephi said:
When all else fails, use lucky patcher. Just be sure the stock image will flash for you. It won't back up apps, but it removed all my bloat I wanted to remove...
Edit: tried removing Translate. The one System/app that has wrong permissions. Lucky Patcher was about to remove it, hard reboot and it's still there with the wrong permissions. I guess translate is a must on stock?
Click to expand...
Click to collapse
hey for all those that have root i use a program called root uninstaller pro..i do not have any of the permissions issues that you guys have with titanium backup i was able to very easily completely de bloat the phone..

Uzephi said:
Root is there. Just as buggy as Magisk with this dual partition phone. Can't remove system apps with Titanium Backup. Can't set some things as r/w with root browser. Besides flashing the boot.img, is there anything else that needs to be done as some parts of system are r/o still or do we need twrp for full system access with this device?
Click to expand...
Click to collapse
This is not an issue with SuperSU (or Magisk). This is an issue with Titanium Backup (and many other tools) not being fully able to cope with the partition setup on newer devices yet.
Uzephi said:
Edit: Chainfire, it seems the method for T-mob either isn't working the same for sprint or with dual boot.imgs there is some odd issue after updating. If you need logs, let me know how to help
Click to expand...
Click to collapse
I don't understand what you mean, please elaborate.
The T-Mobile and Sprint images do the same thing. CFAR/SuperSU uses a different method than Magisk. The Magisk images are pre-rooted, while the CFAR images patch the boot image present on your device when you boot it. In other words, if both the T-Mobile and Sprint root images are able to boot on your device, what they do is identical, and you'd end up with an identical root.
In case of any issues, try 'fastboot flash'ing back the stock boot image, before 'fastboot boot'ing the CFAR.

Chainfire said:
This is not an issue with SuperSU (or Magisk). This is an issue with Titanium Backup (and many other tools) not being fully able to cope with the partition setup on newer devices yet.
I don't understand what you mean, please elaborate.
The T-Mobile and Sprint images do the same thing. CFAR/SuperSU uses a different method than Magisk. The Magisk images are pre-rooted, while the CFAR images patch the boot image present on your device when you boot it. In other words, if both the T-Mobile and Sprint root images are able to boot on your device, what they do is identical, and you'd end up with an identical root.
In case of any issues, try 'fastboot flash'ing back the stock boot image, before 'fastboot boot'ing the CFAR.
Click to expand...
Click to collapse
I figured it out. The apps I was testing root with were exactly what you describe. TB and an odd permission error with translate. Root works. My later posts go into detail. It's just the oddities with possibly two boot partitions or just an idiosyncrasy on our phone why translate has different permissions than all other files.
Thanks for getting CFAR working on our phone.

raver445 said:
hey for all those that have root i use a program called root uninstaller pro..i do not have any of the permissions issues that you guys have with titanium backup i was able to very easily completely de bloat the phone..
Click to expand...
Click to collapse
Can you remove Translate? for some reason on my Sprint model it doesn't have correct permissions to remove it on any root app.

Uzephi said:
Can you remove Translate? for some reason on my Sprint model it doesn't have correct permissions to remove it on any root app.
Click to expand...
Click to collapse
I have the T-Mobile variant but but I do remember being able to remove all bloatware applications except for one of the Google applications and it wasn't translate that wasn't able to be removed it was Google Sheets. But yes translate should be able to be removed
Sent from my LGLS992 using Tapatalk

raver445 said:
I have the T-Mobile variant but are you talking about Google Translate?
Sent from my LGLS992 using Tapatalk
Click to expand...
Click to collapse
Yes. If you see my last post on page 1 you will see translate has different permissions than other system/ apps causing it to not be removed by any root app on my Sprint model. I wonder if it's sprint only, Z2 Force only or something just with my phone with the dual boot partition causing oddities.

I'm figuring it's probably just Sprint Sprint version causing the problems can you send me some screenshots please
Sent from my LGLS992 using Tapatalk

raver445 said:
I'm figuring it's probably just Sprint Sprint version causing the problems can you send me some screenshots please
Sent from my LGLS992 using Tapatalk
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=73858447&postcount=10 Post 10 has the screenshot of what the issue is. Check rw permissions in root browser. All system/app folders have drwxr-xr-x while only the translate folder has drw-------- meaning there is something causing translate to not be able to be written over/deleted. I tried with console commands and root browser to modify permissions of the file but access denied error. When I tried to remove with another app, Lucky Patcher, it was about to remove then the phone rebooted and the system/app was still there.