[Q] Mail.apk auto-restores wrong version - AT&T HTC One (M8)

I backed up my mail.apk before replacing it with a modified version. But the mod didn't work, so I've tried storing the old one. And it won't stay.
When I copy it over, via TWRP or manually, clear cache/dalvik, and reboot, a different file is there after reboot. And I cannot create Exchange accounts - neither those using office365 nor my own server which does not require admin rights.
The original file was dated 18 April 2014. The file I was replacing it with was from June 2014. The auto-restored file is from 01 Aug 2008 and is .5.05MB.
The ODEX is restored also, as 18 April 2014, regardless of what I put down or delete.
Where is the invalid /system/priv-apps/ getting the backup it's putting on from? How can I prevent this?

You should make sure you have system write protection off first

Related

[Q] Editing /data/system/packages.xml

Hi guys,
I'm currently trying to manipulate the file /data/system/packages.xml in order to make Android start one of my apps with another user id. However, this doesn't work because it seems that Android recreates the file completely when shutting down the system which means the old user id is being written back into the file.
Without rebooting, changing the file's contents (or even deleting it completely) doesn't do anything either, it seems that the contents are being loaded into the memory on boot.
What I need are your ideas on how I can make my app run as another user (or edit the file permanently) I need this because I want to access another app's non-exported service.
Thanks in advance!
edit: Even if I try editing the file and then shutting down the system unexpectedly (One X, holding down power for like 10 seconds without using the software shutdown), the file is being restored after reboot. When I check the file in CWM after a normal shutdown, it's also back to normal. So I guess Android rebuilds it on shutdown AND on boot.. or something?
edit2: I just tried the following: Rebooting into CWM, editing /data/system/packages.xml from there, checking file contents (worked), rebooting system - file contents restored. I'm starting to think that this isn't the file I have to edit. But which one is it?
edit3: Tried editing /data/system/packages.list instead, didn't work either. The file is also being restored to the original state.
- Android 4.1.1, CM10, German
did u managed anything?got same issue

Download & Install The Unreleased Gmail 4.2 APK With Pinch-To-Zoom And More

You will find here the new Unreleased Gmail 4.2.apk - Thanks to Android Police for this news
The Gmail 4.2 APK is signed by Google, but with a different key than the one in the Play Store (we checked the signatures - they differ). One is probably the test key and the other the production key. For this reason, you can't simply install it as an update and therefore need to be rooted with the ability to mount the /system directory for writing in order to remove the existing Gmail APK.
Important: Once Google updates Gmail in the Play Store, you will want to revert this process or at the very least delete the Gmail 4.2 APK you installed here if you want to update it from the Play Store.
OK, let's get down to it. You'll probably need ADB installed on your computer (here's an easy way that doesn't require downloading the Android SDK). There is a chance that this might work without ADB by just removing the APKs mentioned below and installing the new one, but it didn't seem to work reliably for everyone. This should, though:
- Download Gmail 4.2 from the download link above.
- Rename it to Gmail2.apk.(already renamed )
- Make a Nandroid backup in case something goes wrong (this is always a good thing to do before messing with your device).
- Remount /system for writing (via your favorite root-aware file explorer).
- Delete (or move if you want to save the APKs) all other versions of Gmail.
- Update: We've seen multiple successful reports of simply uninstalling Gmail using Titanium Backup or ROM Toolbox instead of performing this and the next step. If that works for you, go directly to step 7. If not, proceed below.
- Usually there are 2 or 3 copies. One will be in /system/app (that's the original Gmail that was pre-installed on the device) and there may be a few in /data/app (these are the updates installed from the Play Store). They'll be called "Gmail.apk," or "com.google.android.gm-[number].apk," An easy way to tell is to look for the Gmail icon.
- You may need to delete the .odex files matching the APKs in step 5 too, if you have them. Neither I nor Artem had to do this, but there are many different ROMs out there, and we're trying to cover all bases. Ignore this step and only come back to it if something doesn't work later.
- Reboot. Once you do, you should have no Gmail as far as Android is concerned.
- You can try to install the Gmail 4.2 APK you downloaded at this point by tapping it in your favorite file explorer (move the APK to your device first, of course). If that doesn't work, or if you prefer ADB, fire up a command line and type adb install Gmail2.apk.
If you get an error message, you probably didn't delete all copies of Gmail. If you don't feel like playing with ADB for Step 8, I've also gotten it to work by just copying the APK to /data/app, but that's not as fool proof as "ADB install".
Click to expand...
Click to collapse
Gmail 4.2.apk - download link - MD5 Sum: 2e5dbfccea5fca470d1e669fc0f431ba - Size: 2.77 MB (2906222 bytes)
Source [androidpolice]

[Q] editing .so file

Howdy.
I'm trying to modify a .so file (libflashplayer.so), but have run into a few problems:
I first tried editing the file after it was installed from an .apk. This appears to work at first, but the edited file is quickly replaced with the original.
I then tried editing the file in the .apk package. This causes the package to fail to install (I'm guessing because the md5 in the certificates no longer matches)
Aldo tried moving a folder with the .so files from the .apk (com.adobe.flashplayer-1 which is what is created when the .apk installs correctly) directly into /data/app-lib/.The directory was created successfully but appears to be immediately deleted.
Is there a way to accomplish what I'm trying to do? If so how?
Other possibly relevant info:
My device is rooted
I did not write the code for anything in the .apk, I got it from a link on xda (pretty dubious i know but I couldn't find another option)
I'm using cyanogenmod 10.2 (based on android 4.2 I believe).
I'm editing the file with a hex editor to change a a few characters ("AND" to "WIN")

I don't have smart manager app

Ok guys, I bought galaxy alpha in october 2015 and I received android 5.0.2 in december 2015. I haven't received ANY update since that day. I don't have smart manager and I want to know why! Because battery sucks and even galaxy s4 has received it. Any solution ?
Here you go. Simply copy both folders SmartManager and SmartManagerSDK with all the files within to: system/priv-app, set permitions: drwxr-xr-x for all folders, -rw-r--r-- for apk
files and lib files. Reset the handset and that's it.

Delete extra-TWRP backup post-root on Leagoo T5c

Hi everyone,
This weekend, I rooted my Leagoo T5c using the excellent tutorial posted here, and everything went well.
However, while I was in Recovery mode in TWRP, I decided to backup the factory image AND the system image, thinking it would add an extra-layer of safety in case my rooting plan went south.
Thing is, I now have only 10GB of free space left on the device, though I have installed only a few of the apps I had prior to rooting the phone, and I still have to transfer my music (about 10GB worth) on it, something I'll do when I've decided to try and install a custom ROM or not (things are not entirely clear on that front).
When I go to the TWRP folder in File Explorer, after sorting by size, I see the following:
- One file named system.ext4.win001 (size: 1.50GB)
- One file named system.ext4.win000 (size: 1.50GB)
- One file named data.f2fs.win001 (size: 1.50GB)
- One file named data.f2fs.win000 (size: 1.49GB)
- One file named system_image.emmc.win (size: 3.61GB)
I take it the latter is the actual factory image backup of the last ROM I flashed on the device; the other four seem to be duplicates of one another, and *should* be safe to delete, but I don't want to do something I'll regret later.
I'd like your advice on this, because I sorely need to reclaim some free space on this device, and from the look of it, there are almost 6GB of data I can do without now that my phone is up and running, considering the fact that I'll leave the factory image as is.
What do you think?
EDIT: I decided, to Hell with it, I went and deleted the four files of 1.5GB in size, and rebooted. Everything is OK.

Categories

Resources