NFC - NFC Hacking

I would like to program a nfc tags to do system options, such as reset the phone and wipe all the data. I have a understanding that I can write a script to the tags to make them do commands, is this possible?

lifebound said:
I would like to program a nfc tags to do system options, such as reset the phone and wipe all the data. I have a understanding that I can write a script to the tags to make them do commands, is this possible?
Click to expand...
Click to collapse
I suppose tasker should do that, but wipe data... I don't think so

xaxoo said:
I suppose tasker should do that, but wipe data... I don't think so
Click to expand...
Click to collapse
why not? from my understanding and learning, you can program tasker to do any phone command, which should included wiping data. I cannot confirm because I'm new at this as well. Tasker is all about automation of tasks.

lifebound said:
I would like to program a nfc tags to do system options, such as reset the phone and wipe all the data. I have a understanding that I can write a script to the tags to make them do commands, is this possible?
Click to expand...
Click to collapse
In principle I thing that's possible, but I'm pretty sure that it would be more secure to do it other ways, as the automation of such sensitive tasks can lead to catastrophic results. So, be careful.

Related

Question about rooting

I'm trying to root GN but it seems that we MUST unlock bootloader to root.
I know how to do it but just worrying about what will be wipe with unlock, I've just spent whole afternoon setting up this phone and don't want to do it again?
Will I loss:
-Launcher setting? ADW setting?
-Downloaded application? and their setting?
-Do I have to redo all the widget?
I just want to use juicedefender and RE but don't want go through all the trouble again
I think unlocking the boot loader wipes the device. Make a titanium backup first an extract the back up from the sdcard then restore once complete.
dannyfly said:
I'm trying to root GN but it seems that we MUST unlock bootloader to root.
I know how to do it but just worrying about what will be wipe with unlock, I've just spent whole afternoon setting up this phone and don't want to do it again?
Will I loss:
-Launcher setting? ADW setting?
-Downloaded application? and their setting?
-Do I have to redo all the widget?
I just want to use juicedefender and RE but don't want go through all the trouble again
Click to expand...
Click to collapse
As far as I've seen, Google has programmed the device to wipe the /data partition when the unlock command is executed.
This will wipe all application settings including downloaded applications, widgets and the Launcher as they are all stored on the /data partition.
If you dislike this, Google is the place to file the complaint as this is their standard procedure on all their Google "Nexus" devices.
The only upside will be, once you've unlocked, you'll be able to gain root access and be able to have complete control over the device including full backups of all settings to prevent ever having to re-set them again. Unless of course you start flashing lots of custom ROMs which are imcompatible with each other, but that is perhaps another story.
Hope that helps!
mklass said:
I think unlocking the boot loader wipes the device. Make a titanium backup first an extract the back up from the sdcard then restore once complete.
Click to expand...
Click to collapse
I've never used Titantium backup, but many people seem to say a lot of positive things about it. I've also read Titantium backup requires root access.
The Android security structure ONLY allows the root user full unlimited access to the /data partition. Otherwise, each application is assigned a linux UID/GID and only allowed access to their respective directory. According to the Android security structure, no application should be able to access another aplication's directory w/o sharing the same signing key or having root access.
I could be wrong, but I'm definitely certain regarding Android's security structure for "sandboxing" the applications.
Hope that helps clarify!

[Q] Titanium Backup: restoring after wiping

I have the premium version of Titanium Backup which I have been using for over a year with much success.
I have one query which would make it really awesome if it can be accomplished.
I normally only use it when doing a ROM upgrade. When I am getting ready to upgrade, I delete all my old backups, do a new set of backups on all user apps + system data, and wipe and flash the ROM. Then, when I'm back inside, I go into the Market and download Titanium plus the Pro unlock, and restore the backup.
(First of all, is this what you guys do? restoring all system data shouldn't screw up the features of the new ROM from the old one, right?)
The question is: Is there any way to have Titanium run without having to first go into the Market, find the app plus the unlock, download it, and install it? i.e. If I could just run it straight off the SD card, or install it straight off the SD card without having to use the Market.
Ideally, it would be even better if I could have a startup script on first run where it just restores the full set of apps + system data after I've flashed the ROM.
Is this at all possible?
download or extract from a rom the titanium.apk, put it on sd-card an install the apk after flashing new rom and it´s done.
Ozzah said:
I have the premium version of Titanium Backup which I have been using for over a year with much success.
I have one query which would make it really awesome if it can be accomplished.
I normally only use it when doing a ROM upgrade. When I am getting ready to upgrade, I delete all my old backups, do a new set of backups on all user apps + system data, and wipe and flash the ROM. Then, when I'm back inside, I go into the Market and download Titanium plus the Pro unlock, and restore the backup.
(First of all, is this what you guys do? restoring all system data shouldn't screw up the features of the new ROM from the old one, right?)
The question is: Is there any way to have Titanium run without having to first go into the Market, find the app plus the unlock, download it, and install it? i.e. If I could just run it straight off the SD card, or install it straight off the SD card without having to use the Market.
Ideally, it would be even better if I could have a startup script on first run where it just restores the full set of apps + system data after I've flashed the ROM.
Is this at all possible?
Click to expand...
Click to collapse
Never restore system data as it can and has causes issues. It is only advised to restore user apps and data never system data.
As for your other question no not that I know of. Most roms worth anything already include TIBU so all you have to do is install the pro key and run it.
Start Titanium backup
Goto menu/more/create update>zip
scroll down and hit "create update.zip"
when you install a new Rom just use "add another zip" when in Rom manager or 4EXT recovery
Goto SD card and select "update.zip" from root of SD card
Hope that helps
alchopop said:
Start Titanium backup
Goto menu/more/create update>zip
scroll down and hit "create update.zip"
Click to expand...
Click to collapse
Thanks, that's great!
Do you know if it is smart enough to bundle the Pro unlock into the update.zip? I opened the zip file up and there only appears to be 1 APK in there.
Would it be difficult (or even possible?) to manually adjust the update.zip so that it includes the Pro unlock APK?
Ozzah said:
Thanks, that's great!
Do you know if it is smart enough to bundle the Pro unlock into the update.zip? I opened the zip file up and there only appears to be 1 APK in there.
Would it be difficult (or even possible?) to manually adjust the update.zip so that it includes the Pro unlock APK?
Click to expand...
Click to collapse
Pro unlock is stored on the SD card, no need to worry about it
Sent from my Desire HD using xda premium
restoring
So I'm returning my nexus for a replacement today. Some kind of battery issue that makes it keep turning off every night:
http://forum.xda-developers.com/showthread.php?p=34923533#post34923533
On restoring, if I understand right, I'm going to move my titanium folder back to the new nexus to the SD card area.
Run my TiBU apk and just restore my apps and associated files.
If I understand right, I Should Not restore my system files right? (Although i did a lot of customizing i was hoping could come right over).
Then when i have it all customized again, I'll back up the new system and hopefully it won't have any issues anymore.
Just an android noob talking it through, sound good?
I'll be installing the rom and CM10 again of course before doing this.
zelendel said:
Never restore system data as it can and has causes issues. It is only advised to restore user apps and data never system data.
Click to expand...
Click to collapse
Sorry, i take this opportunity to ask a question i had in mind for a long time: what exactly do you mean by "system data"?
I mean, can i restore stuff like "Settings", or "Wireless network", "Bluetooth associations", "SMS", "Wallpaper" and stuff like this? Is really annoying to have to re-customize from scratch the CyanogenMod settings and similar stuff, everytime i do a full wipe...
sberla54 said:
Sorry, i take this opportunity to ask a question i had in mind for a long time: what exactly do you mean by "system data"?
I mean, can i restore stuff like "Settings", or "Wireless network", "Bluetooth associations", "SMS", "Wallpaper" and stuff like this? Is really annoying to have to re-customize from scratch the CyanogenMod settings and similar stuff, everytime i do a full wipe...
Click to expand...
Click to collapse
You can restore these, they're not system level files (i.e. make the system run)
GuyInTheCorner said:
You can restore these, they're not system level files (i.e. make the system run)
Click to expand...
Click to collapse
Thank you!
So....what's the stuff i DON'T have to restore, because messes up my system?
sberla54 said:
Thank you!
So....what's the stuff i DON'T have to restore, because messes up my system?
Click to expand...
Click to collapse
Do not restore data from SYSTEM apps.
dalanik said:
Do not restore data from SYSTEM apps.
Click to expand...
Click to collapse
Could you tell me a couple of examples?
I'm sorry but i really can't figure out which ones are the system apps. In my opinion, even Settings and Wireless networks are system apps.
Do you mean all the services, frameworks, sms and contacts apps and stuff like this?
sberla54 said:
Could you tell me a couple of examples?
I'm sorry but i really can't figure out which ones are the system apps. In my opinion, even Settings and Wireless networks are system apps.
Do you mean all the services, frameworks, sms and contacts apps and stuff like this?
Click to expand...
Click to collapse
I think he's talking about app names that are red-colored while you're doing the backup in Titanium BackUp.
Am I right?
Cheers
Please delete

[Q] ADB Backup

Quick noob question
Is making a ADB backup using
adb backup -all
The same as a nano backup? Or is the adb one better?
GhostSamuraiX said:
Quick noob question
Is making a ADB backup using
adb backup -all
The same as a nano backup? Or is the adb one better?
Click to expand...
Click to collapse
Uhh wow I don't know. I usually just make a nandroid backup through recovery. I looked it up on Google and this guy seems to provide a very good explanation: http://android.stackexchange.com/qu...e-between-a-nandroid-backup-and-an-adb-backup
Sent from my SGH-M919 using XDA Premium 4 mobile app
xdapowerapps said:
Uhh wow I don't know. I usually just make a nandroid backup through recovery. I looked it up on Google and this guy seems to provide a very good explanation: http://android.stackexchange.com/qu...e-between-a-nandroid-backup-and-an-adb-backup
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wow that's perfect just what I was looking for! I searched Google too but all I kept getting was how to make adb backups an different commands. Thanks a lot for the link bro.
GhostSamuraiX said:
Wow that's perfect just what I was looking for! I searched Google too but all I kept getting was how to make adb backups an different commands. Thanks a lot for the link bro.
Click to expand...
Click to collapse
No problem mate! I learned something as well!
Sent from my SGH-M919 using XDA Premium 4 mobile app
xdapowerapps said:
No problem mate! I learned something as well!
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Indeed friend we both learned something
About backup
What is a backup?
In information technology, a backup or the process of backing up is making copies of data which may be used to restore the original after a data loss event. In Android, this affects applications, settings and documents.
Which types of backups do we have for Android?
Basically, we can distinguish three types:
Nandroid
A Nandroid backup (as it's done by e.g. ClockworkMod) basically creates full images of all your device's partitions, without any abstraction. This does not necessarily mean one could not pick single items out of a Nandroid backup, but its not that trivial. If you restore a single partition only (such as /data), it must fit the other parts of the system. The /data partition also holds the /data/dalvik-cache, for example, which consists of the byte-code for all installed apps, optimized for the ROM which created it. If you would restore only the /data partition from a backup of ROM-X to a device with ROM-Y, those DEX (Dalvik EXecutables) would not fit. Also ROM-Y might use different directory structures for several things, which are not reflected here. As a result, you might have a unstable system (which might not even be able to complete its boot process), see apps crashing, and the like.
Doing this would not be such a good idea. So for the average user, a Nandroid restore is rather an all-or-nothing: Either restore it completely, or not at all. Unless you know exactly what you're doing, of course.
ADB Backups
Backups created with the adb backup command are a different case: they are "abstracted". If you look into such an archive, you will not find the directory structure reflected. Thus, at least in theory, an app backup (including the apps' data) created on ROM-X should restore fine on ROM-Y, as the ADB daemon on the device should take care of what belongs where.
App-based backups
There are several apps available for Android that create backups of apps, their data, or both. Some only cover system data available via so-called "data providers" (contacts, call logs, bookmarks, SMS/MMS, and the like). Others can capture/extract the .apk app installation archives. A few can backup apps, their data, and even system data—which before Android 4.0 required root permissions. Two of the powerful apps shall be mentioned here:
Titanium Backup is one of the best-known, most-powerful, and most recommended Backup solutions. It is able to backup apps, their data, data available via data-providers, system data, and more. And it can read (and restore) things from Nandroid and ADB backups as well. But it requires your device to be rooted.
Helium - App Sync and Backup (previously called Carbon) creates backups compatible with ADB backups (in fact, it is a front-end to the adb backup and adb restore commands). It can backup apps and their data, plus some other system data and stuff available via some data-providers. More to come, we hope. Helium Backup does not require root.
Source-http://android.stackexchange.com/tags/backup/info

Ok, have bumped phone... TWRP, and working great, but have question

So I restored my phone from a TWRP backup, very nice, very fast.
However, I discovered I have to (re)setup my Cal account options, and other apps accounts/options as well.
Is the restore supposed to be an 'exact' copy of my phone?
Thanks.
1. Questions go in Q&A forum not General.
2. Whenever I have restored using TWRP it has been an exact copy of what I backed up.
samorgs said:
1. Questions go in Q&A forum not General.
2. Whenever I have restored using TWRP it has been an exact copy of what I backed up.
Click to expand...
Click to collapse
Hum. My backups include boot, system and data. No cache or EFS. They are all restored.
Am I missing a setup thing or ?
samorgs said:
1. Questions go in Q&A forum not General.
2. Whenever I have restored using TWRP it has been an exact copy of what I backed up.
Click to expand...
Click to collapse
Hum. My backups include boot, system and data. No cache or EFS. They are all restored.
Am I missing a setup thing or ?
I am unable to move this thread to QA
JeffDC said:
Hum. My backups include boot, system and data. No cache or EFS. They are all restored.
Am I missing a setup thing or ?
Click to expand...
Click to collapse
In order to have an "exact" copy you would have to restore the "cache" too, but since you didn't back up your cache your only choice would be is to redo your settings.
Please post questions in the Q&A section
Thread moved
Amb669 said:
In order to have an "exact" copy you would have to restore the "cache" too, but since you didn't back up your cache your only choice would be is to redo your settings.
Click to expand...
Click to collapse
Excellent, thank you.
JeffDC said:
Excellent, thank you.
Click to expand...
Click to collapse
Okay well your cache has nothing to do with settings saved on your phone. Your cache can be deleted at any time while running any ROM and it wont change settings in your phone, unless for some odd reason your phone has not written the data to storage yet before a reboot. Your cache is used to temporarily store files that your phone will need in the future to help open apps quicker without having to look up the required files each time for the operation. Instead, the phone can look to the cache to quickly load commonly used files back into the RAM.
acparker18 said:
Okay well your cache has nothing to do with settings saved on your phone. Your cache can be deleted at any time while running any ROM and it wont change settings in your phone, unless for some odd reason your phone has not written the data to storage yet before a reboot. Your cache is used to temporarily store files that your phone will need in the future to help open apps quicker without having to look up the required files each time for the operation. Instead, the phone can look to the cache to quickly load commonly used files back into the RAM.
Click to expand...
Click to collapse
Thanks. Any thoughts on why my restore did not have my 'accounts' setup, like my default google account for 'Cal(anded)", and others? I had to spend a bit of time re-setting up a number of 'accounts and preferences.
JeffDC said:
Thanks. Any thoughts on why my restore did not have my 'accounts' setup, like my default google account for 'Cal(anded)", and others? I had to spend a bit of time re-setting up a number of 'accounts and preferences.
Click to expand...
Click to collapse
I noticed you said that you also didn't backup the EFS partition. That shouldn't have anything to do with your accounts but I always backup and restore the EFS partition each time and I have never lost any account info. It could have to do with the fact that your EFS partition contains carrier and device-specific info like your device ID number that could have caused your backup to not recognize the device once you restored it. This probably lead to your phone erasing your account info out of security in case someone else had gotten a hold of your backup and restored it to their phone. This way, the person who hijacked your backup couldn't access sensitive information like account login credentials. I'm not sure if this is the case, but it seems to be the only explanation I have. Next time you do a backup, include the EFS partition and see if that fixes it on the next restore. Either way, I hope it doesn't erase it on you again man. I know it can be frustrating to have to manually fix little details like that every time. Best of luck!
acparker18 said:
I noticed you said that you also didn't backup the EFS partition. That shouldn't have anything to do with your accounts but I always backup and restore the EFS partition each time and I have never lost any account info. It could have to do with the fact that your EFS partition contains carrier and device-specific info like your device ID number that could have caused your backup to not recognize the device once you restored it. This probably lead to your phone erasing your account info out of security in case someone else had gotten a hold of your backup and restored it to their phone. This way, the person who hijacked your backup couldn't access sensitive information like account login credentials. I'm not sure if this is the case, but it seems to be the only explanation I have. Next time you do a backup, include the EFS partition and see if that fixes it on the next restore. Either way, I hope it doesn't erase it on you again man. I know it can be frustrating to have to manually fix little details like that every time. Best of luck!
Click to expand...
Click to collapse
Thanks for the detailed response. Good info to understands.
Following the loss of the accounts, and everyone's help, I am backing up everything in the list, EFS as well.

How to copy the system 1:1 to a new device by using TWRP

I got a new device by RMA and now I want to copy my nandroid backup made with TWRP to the new one.
Which partitions do I have to copy?
Most of the partitions are system based, so don't touch them. All you would want to copy is data, but I am not even sure that would work, without a boot loop? I keep all my data backed up with Titanium. And Google drive would restore most of what you had on your phone as long as you were allowing setting>system>backup.
Sui77 said:
I got a new device by RMA and now I want to copy my nandroid backup made with TWRP to the new one.
Which partitions do I have to copy?
Click to expand...
Click to collapse
Data, as it is the one where your settings and app updates are stored. Just be sure the new device is running the same version of Android as the old.
Droid_Nut said:
Most of the partitions are system based, so don't touch them. All you would want to copy is data, but I am not even sure that would work, without a boot loop? I keep all my data backed up with Titanium. And Google drive would restore most of what you had on your phone as long as you were allowing setting>system>backup.
Click to expand...
Click to collapse
Restoring a nandroid backup of the data partition to another, identical, device will work without causing a bootloop given the precautions I describe above. Do note however that Google's backup only restores items acquired through the Play Store. Alternative app stores such as Amazon will not be restored, apps acquired through Amazon will not be restored, and any apps sideloaded will not be restored. Since Google's restore function doesn't restore everything, any backup solution - like a nandroid backup - is going to be a better alternative.
Strephon Alkhalikoi said:
Data, as it is the one where your settings and app updates are stored. Just be sure the new device is running the same version of Android as the old.
Restoring a nandroid backup of the data partition to another, identical, device will work without causing a bootloop given the precautions I describe above. Do note however that Google's backup only restores items acquired through the Play Store. Alternative app stores such as Amazon will not be restored, apps acquired through Amazon will not be restored, and any apps sideloaded will not be restored. Since Google's restore function doesn't restore everything, any backup solution - like a nandroid backup - is going to be a better alternative.
Click to expand...
Click to collapse
Thanks for the clarification that you can restore data as long as you are on the same version, does it have to be at the same security update level as well?
That is why I use Titanium for apps I got off of Fdroid and other sources. I will make sure I try the Nandroid data backup next time.
Security level shouldn't make a difference, but that is not something I have attempted. The pair of identical tablets I have here are running the same security update.
Thanks, data did the trick.
I had to delete 2 files due to a non working finger printer by using TWRP files explorer, but now the phone is fine.
Last thing pending are customer ringtones, but this is a nasty one.
Any idea how to do it?
Sui77 said:
Thanks, data did the trick.
I had to delete 2 files due to a non working finger printer by using TWRP files explorer, but now the phone is fine.
Last thing pending are customer ringtones, but this is a nasty one.
Any idea how to do it?
Click to expand...
Click to collapse
I am having the same problem with the fingerprint reader after restoring data from one phone to another, what files did you delete in TWRP file manager?
Solution for fingerprinter:
1. Boot into TWRP
2. Go to advanced>filemanager to acces the files in your phone.
3. Enter the folder /data/system/user/0
4. Delete following files: ./fpdata/user.db, settings_fingerprint.xml
5. Reboot to system and set up new fingerprints with the fingerprint wizard
6. Everything should work normal
Was not easy to find, but it's easy to do
Sui77 said:
Solution for fingerprinter:
1. Boot into TWRP
2. Go to advanced>filemanager to acces the files in your phone.
3. Enter the folder /data/system/user/0
4. Delete following files: ./fpdata/user.db, settings_fingerprint.xml
5. Reboot to system and set up new fingerprints with the fingerprint wizard
6. Everything should work normal
Was not easy to find, but it's easy to do
Click to expand...
Click to collapse
I didn't think it would be easy to find, but thanks for the tips. :good:
I am just putting this phone online with Q Beta 3 today, I have no notifications for text, and all options are greyed out?
Droid_Nut said:
I am just putting this phone online with Q Beta 3 today, I have no notifications for text, and all options are greyed out?
Click to expand...
Click to collapse
Turns out this is a bug in Android Q. With Pie there were some many notifications that I set my sound to none, so I just set my sound to Gibbon Call, and now I get text notifications. :good:

Categories

Resources