Hello everyone,
We have developed an apk, and we need a definitive timestamp in order to determine the time that the device was last flashed. This timestamp should be unique only for flash, and not factory reset. Any ideas on how this could be achieved?
Related
I had not realized that the aGPS fix uses data, so I have been researching how to undo the fix. So far I've wrote the original QPST settings back to the phone (that I saved in step 9 of the XDA AGPSfix Tutorial). Everything appears in order with those settings, and my question for the forum (specifically gc14 ) is,
What else is required to restore the pre-aGPS fix settings on my phone?
Note that I've flashed a new ROM twice since I first performed the fix late last week, so I'm not sure if the VZ aGPS Provisioning Cab is still lingering somewhere. I've searched the forums abit (the 67 page discussion and the wiki), but I'm not finding exactly what I'm looking for on this subject.
Any help or input is appreciated!
I've done everything I can think of to determine if this is a question that has been posed elsewhere - to no avail. Nothing quite seems to fit my predicament exactly (that I've found anyway - please feel free to flame/educate me if I have overlooked anything or am in the wrong thread) I am hoping you 1337 pros here on xda devs can help this poor self-loathing n00b. Apologies for the lengthy post - but it is necessary to explain my question.
I am attempting to develop an app (open source for personal use [no ads] - with enterprise edition available for a fee) that can remotely secure/locate an Android device - tablets, phones, etc -- targeted for anything running Froyo or better.
The problem I am running into is that I am unable to prevent a would-be thief from initiating a factory reset and removing the app (and it's configuration settings). I have device admin setup so that the permissions must be revoked after signing in with a username and password before the app can be uninstalled - but factory restore still wipes it.
As this would be a theft deterrent/recovery tool - relying on a thief to connect the device back to the original Google account and reinstall the apps is out of the question. I understand that if the ROM is replaced with a custom ROM (e.g. Cyanogen, etc.) it would not be able to prevent the app from being wiped - but negating the factory reset from removing the app would still be very beneficial.
Short of including the app in the manufacturer's ROM image - is there any work around to be found here? I'm at my wit's end (however limited that may be).
I am most grateful for any information you can provide - even if its bad news.
After playing around with rooting and different CF kernels, Kies have started having troubles when performing a full system backup - most notably with elements such as "Call Log" and "Others". This is however not a unique problem as I have found threads with people having the same problem, although without any solution.
I have tried fixing permissions, different Samsung firmwares (4.0.3, 4.0.4), removing root with SuperSU, wiping dalvik cache..
So I have decided to take matters into my own hands and try to track down where the specific problem lies. And for that I need log. I need to know:
1) If Kies produce any sort of log when a system backup is commenced, either on my computer or telephone?
2) If not, can it be enforced with some sort of verbose command?
3) The location of the logs
Thank you in advance.
I've spent the whole night trying to figure this out so hopefully the information is useful for some of of you
The usual scenario is that the phone is encrypted due to using Exchange email (eg. Corporate email) and now you can't upgrade or root it. The first thing to do is to delete that email account and hopefully the phone will decrypt itself or the option appears when you go to phone security settings. You can also try to access the corporate email via a browser and delete the mobile connection.
This worked for me previously but it doesn't now - I don't know if its because I'm using a non-stock rom. Either way a lot of people seems to be stuck with a Samsung rom as well. So you now have a phone with the exchange account gone and its restriction so you should in theory be able to removing the decryption but no it doesn't work. I don't know why as this is a basic OS stuff.
At this stage you can try to full wipe it - but this doesn't work, both through settings or CWM. The only way to sort this out is to copy / backup all your information then flash it to factory state and this means using odin and a stock rom. I've done this several times and there is no lasting issues.
I''m by no mean an expert and would be happy for anyone to correct me
Hello guys,
this is my first post on this forum (sorry for my poor English, I'll try to write my best), and I'd really like to ask you some advice about my situation.
I used to have an Android 2.3.3 device and Whatsapp installed on it, regularly updated (I still have it, but I'm not using it).
Almost a month ago I bought a new device, with Android 4.4.4 installed, and I immediately put WhatsApp on it.
Before removing SD from the old phone, i saved my backup file OLD.db.crypt8, in order to let the "new" whatsapp restore my messages. Unfortunately, a month passed before i could be able to think about restoring my old messages.
Thus, i have accumulated (?) a month of messages, and i "backup-ed" them in a MIDDLE.db.crypt8 file.
I already managed to decrypt the "middle" db.crypt8 file (extracting the key file from my android 4.4.4), but don't know how to decrypt the OLD.db.crypt8 file.
OLD, in fact, comes from Android 2.3.3, as said, and i got no key file
My final goal is, after decrypting all three databases (OLD, MIDDLE and "NEW" - provided that NEW is the database i'm "growing up" on my phone at the moment), merging the three databases in an only database (and this is possible with the XDA guide i already have read)
Can anyone help me?
Thank you very much
Up! Please help
No chance for me?