Database Develop

[Q] Backup entire custom rom and settings via Clockwork or other

Hello!
I have a new european HTC One with Trickdroid v8 installed and Clockwork 6.0.3.3
How to backup entire rom with settings ? I have used the backup function in Clockwork recovery, but I cant find the back file on my internat memory - i want to copy it to my computer just in case.
What is best solution to make backup of my entire phone with rom ? Using clockwork recovery software or some other function ?

cavist said:
Hello!
I have a new european HTC One with Trickdroid v8 installed and Clockwork 6.0.3.3
How to backup entire rom with settings ? I have used the backup function in Clockwork recovery, but I cant find the back file on my internat memory - i want to copy it to my computer just in case.
What is best solution to make backup of my entire phone with rom ? Using clockwork recovery software or some other function ?
Click to expand...
Click to collapse
The CWM backup is located in '/data/media/clockworkmod/backup/' (from root) and is not visible from the pc.
Using ES file explorer or root explorer copy the folder in the '/data/media/clockworkmod/backup/' directory to '/data/media/0/' and then you'll be able to see it from your pc and copy across....... remember to delete the copy from '/data/media/0/' afterwards

rider5512 said:
The CWM backup is located in '/data/media/clockworkmod/backup/' (from root) and is not visible from the pc.
Using ES file explorer or root explorer copy the folder in the '/data/media/clockworkmod/backup/' directory to '/data/media/0/' and then you'll be able to see it from your pc and copy across....... remember to delete the copy from '/data/media/0/' afterwards
Click to expand...
Click to collapse
Unfortunately, i do not have such directory path like you specified.
I installed Clockwork Rom Manager and it tells me the backup is in inaccesible area, path: Device: mnt/shell/emulated/clockworkmod/backup
But the mnt/shell folder is empty and I cant find clockword folder. Any solution to this ?

cavist said:
Unfortunately, i do not have such directory path like you specified.
I installed Clockwork Rom Manager and it tells me the backup is in inaccesible area, path: Device: mnt/shell/emulated/clockworkmod/backup
But the mnt/shell folder is empty and I cant find clockword folder. Any solution to this ?
Click to expand...
Click to collapse
When navigating to root with a file explorer are you unable to see the directories I listed?

rider5512 said:
When navigating to root with a file explorer are you unable to see the directories I listed?
Click to expand...
Click to collapse
Using your path, I can only go for: Device: /data/ and it is empty

cavist said:
Using your path, I can only go for: Device: /data/ and it is empty
Click to expand...
Click to collapse
No it can't be empty.... check your file explorer is root enabled, if you're using ES then settings>tools>root explorer

rider5512 said:
No it can't be empty.... check your file explorer is root enabled, if you're using ES then settings>tools>root explorer
Click to expand...
Click to collapse
Now it works like a charm. Thank you very much for your help!

TWRP recovery copy issue

Friends....I have two TWRP backup on my HTC ONE. I want to transfer them on my PC so hat i can save 4 GB of disk space but for some reason i cannot copy the main file which is around 1.5 gb and is named 'system.ext4.win'. I tried copy/cut both but of no use. When i copy and paste in same location it gives error that cannot copy 'system.ext4.win'. Plz help :crying::crying:. Just for added info I can copy all other things like Titanium backup

Older versions of TWRP incorrectly set the permissions. Use root explorer or ES File Explorer to set the permissions properly.

BenPope said:
Older versions of TWRP incorrectly set the permissions. Use root explorer or ES File Explorer to set the permissions properly.
Click to expand...
Click to collapse
Thanks, but I can't locate the option to edit 'permission'. I'm using ES explorer. Can you plz guide ?

[Q] SD Card files only viewable in recovery?

Hello everyone,
I just upgraded to 4.3 from 4.1.2 for the first time.
When in recovery I can view all of my original SD card files (prior to upgrade) when I select the "choose zip from SD card" option. However, when I plug my phone through USB to view my SD card contents there's an entirely fresh file structure which does not include my personal files. I also tried through ES File Explorer and I still cannot view my old files. It only works through recovery.
Can someone please point me in the right direction to get my old files back? I know the file structure changed but I'm not sure how to go about migrating my old files.
I'm running InsertCoin with the latest T-Mobile Radio if it helps.

Toshinobu said:
Hello everyone,
I just upgraded to 4.3 from 4.2.2 for the first time.
When in recovery I can view all of my original SD card files (prior to upgrade) when I select the "choose zip from SD card" option. However, when I plug my phone through USB to view my SD card contents there's an entirely fresh file structure which does not include my personal files. I also tried through ES File Explorer and I still cannot view my old files. It only works through recovery.
Can someone please point me in the right direction to get my old files back?
I'm running InsertCoin with the latest T-Mobile Radio if it helps.
Click to expand...
Click to collapse
Use a program like ES file explorer or root explorer
Navigate to /data/media/0 and see if you see your files in there or data/media/emulated something like that

CharliesTheMan said:
Use a program like ES file explorer or root explorer
Navigate to /data/media/0 and see if you see your files in there or data/media/emulated something like that
Click to expand...
Click to collapse
Thanks for the reply Charlie. I'm using ES File Explorer. There are no files or folders inside /data/. I checked /storage/emulated/0/ and /storage/emulated/legacy (not sure if that's what you meant) and they are not there either.

Nevermind, found it. ES File Explorer had hidden files turned off and root explorer off as well.
Thanks again!

Toshinobu said:
Nevermind, found it. ES File Explorer had hidden files turned off and root explorer off as well.
Thanks again!
Click to expand...
Click to collapse
If you have two TWRP folders, delete the TWRPs file that's in the empty one (not the one that's got your backups in)

CharliesTheMan said:
If you have two TWRP folders, delete the TWRPs file that's in the empty one (not the one that's got your backups in)
Click to expand...
Click to collapse
I'm actually on CWM not TWRP.

[Q] How can I change the hangouts emoticons (emoji) back to Google ones?

Hi,
I have updated my HTC One to android 4.4, sense 5.5 (latest update from HTC). After the update I see that the emoticons in the Google hangouts app have been changed to HTC emoticons.
I was used to the emoticons in my hangouts app and now they have been changed and I am very disappointed.
Is there a way to get the Google emoticons back? I don't like the ones that HTC provides.
I have attached a screen shot.
If I could also change the emoticons/emojis to Google system-wide I would be more glad.

183.amir said:
Hi,
I have updated my HTC One to android 4.4, sense 5.5 (latest update from HTC). After the update I see that the emoticons in the Google hangouts app have been changed to HTC emoticons.
I was used to the emoticons in my hangouts app and now they have been changed and I am very disappointed.
Is there a way to get the Google emoticons back? I don't like the ones that HTC provides.
I have attached a screen shot.
If I could also change the emoticons/emojis to Google system-wide I would be more glad.
Click to expand...
Click to collapse
I'd like to know this as well. I much prefer the Google emoticons in Hangouts.

imminentwill said:
I'd like to know this as well. I much prefer the Google emoticons in Hangouts.
Click to expand...
Click to collapse
I think this should either be provided by Google Hangouts app or we need to use a custom framework.

Finally figured it out myself and thought I should share! You need root for this to work.
Get a file browser app that can browse system files. I suggest Root Browser or ES File Explorer.
Navigate to /system/fonts/
While in the fonts folder, you should see a font named "AndroidEmoji-htc.ttf" and a "AndroidEmoji.ttf".
Rename "AndroidEmoji-htc.ttf" to "AndroidEmoji-htc.ttf.nothankyou" or whatever file extension you prefer. Just make sure it's not .ttf or any other font file extension or the system will still read it.
Doing this will make the system fall back to "AndroidEmoji.ttf" which contains the hangous emojis.
Reboot and you will see the results.
Enjoy!

Okay, so you changed the Emoji in your conversation to match your keyboard. What if I wanted to go the other way ’round and skin my keyboard Emoji to match what’s in the conversation?

Musenkishi said:
Finally figured it out myself and thought I should share! You need root for this to work.
Get a file browser app that can browse system files. I suggest Root Browser or ES File Explorer.
Navigate to /system/fonts/
While in the fonts folder, you should see a font named "AndroidEmoji-htc.ttf" and a "AndroidEmoji.ttf".
Rename "AndroidEmoji-htc.ttf" to "AndroidEmoji-htc.ttf.nothankyou" or whatever file extension you prefer. Just make sure it's not .ttf or any other font file extension or the system will still read it.
Doing this will make the system fall back to "AndroidEmoji.ttf" which contains the hangous emojis.
Reboot and you will see the results.
Enjoy!
Click to expand...
Click to collapse
do you think there is a way to get the emoticons used in whatsapp for hangouts also?

herwegan said:
do you think there is a way to get the emoticons used in whatsapp for hangouts also?
Click to expand...
Click to collapse
Well... I don't know. In my post, I basically just remove the emojis that HTC put in the Android system and let it fall back on the original emojis in KitKat, which is the same as the Hangouts.
If there is an emoji font inside the whatsapp APK, then it might be possible to rename it to "AndroidEmoji-htc.ttf", and put it in /system/fonts/. This way, your phone would think it's loading the HTC emojis, but in reality it would be the whatsapp emojis. Might be possible with any emoji font pack actually.

thank you this worked perfectly!

Musenkishi said:
Finally figured it out myself and thought I should share! You need root for this to work.
Get a file browser app that can browse system files. I suggest Root Browser or ES File Explorer.
Navigate to /system/fonts/
While in the fonts folder, you should see a font named "AndroidEmoji-htc.ttf" and a "AndroidEmoji.ttf".
Rename "AndroidEmoji-htc.ttf" to "AndroidEmoji-htc.ttf.nothankyou" or whatever file extension you prefer. Just make sure it's not .ttf or any other font file extension or the system will still read it.
Doing this will make the system fall back to "AndroidEmoji.ttf" which contains the hangous emojis.
Reboot and you will see the results.
Enjoy!
Click to expand...
Click to collapse
is there a way to do this without having root?

Any ideas on making this work without root?
Sent from my HTC One using Tapatalk

robgee789 said:
Any ideas on making this work without root?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I'd love to find a non rooted solution as well. Anyone got any ideas?

IIIMik3 said:
I'd love to find a non rooted solution as well. Anyone got any ideas?
Click to expand...
Click to collapse
I also need a non rooted solution for my HTC One M8. This is driving me crazy.

Musenkishi said:
Finally figured it out myself and thought I should share! You need root for this to work.
Get a file browser app that can browse system files. I suggest Root Browser or ES File Explorer.
Navigate to /system/fonts/
While in the fonts folder, you should see a font named "AndroidEmoji-htc.ttf" and a "AndroidEmoji.ttf".
Rename "AndroidEmoji-htc.ttf" to "AndroidEmoji-htc.ttf.nothankyou" or whatever file extension you prefer. Just make sure it's not .ttf or any other font file extension or the system will still read it.
Doing this will make the system fall back to "AndroidEmoji.ttf" which contains the hangous emojis.
Reboot and you will see the results.
Enjoy!
Click to expand...
Click to collapse
Obviously I have not rooted yet. What type of root does this require to have permissions to do this? Thanks in advance.

Musenkishi said:
Finally figured it out myself and thought I should share! You need root for this to work.
Get a file browser app that can browse system files. I suggest Root Browser or ES File Explorer.
Navigate to /system/fonts/
While in the fonts folder, you should see a font named "AndroidEmoji-htc.ttf" and a "AndroidEmoji.ttf".
Rename "AndroidEmoji-htc.ttf" to "AndroidEmoji-htc.ttf.nothankyou" or whatever file extension you prefer. Just make sure it's not .ttf or any other font file extension or the system will still read it.
Doing this will make the system fall back to "AndroidEmoji.ttf" which contains the hangous emojis.
Reboot and you will see the results.
Enjoy!
Click to expand...
Click to collapse
I have a rooted M7, I've granted ES File Explorer SuperUser, and I get "task failed" when i try to rename it, and "Read only file system" when I try to delete it. Nothing is working
EDIT: Using Root Explorer instead of ES File Explorer worked. Not sure why, but I'm glad I know Root Explorer will work for me.

JMB2772 said:
I have a rooted M7, I've granted ES File Explorer SuperUser, and I get "task failed" when i try to rename it, and "Read only file system" when I try to delete it. Nothing is working
EDIT: Using Root Explorer instead of ES File Explorer worked. Not sure why, but I'm glad I know Root Explorer will work for me.
Click to expand...
Click to collapse
still hoping for a non-root solution to this. :fingers-crossed:

Me too mate but I don't think it's gonna happen
Sent from my HTC One using Tapatalk

Just run the weaksauce root for your HTC One M8 guys and you'll have no problems following the OP's instructions- literally takes 1 minute to root, 30 seconds to change the emoticons and you are good to go!
I rooted on my first day picking up the M8 and it's been awesome since

JMB2772 said:
I have a rooted M7, I've granted ES File Explorer SuperUser, and I get "task failed" when i try to rename it, and "Read only file system" when I try to delete it. Nothing is working
EDIT: Using Root Explorer instead of ES File Explorer worked. Not sure why, but I'm glad I know Root Explorer will work for me.
Click to expand...
Click to collapse
Just an FYI for anyone else who gets the "read only file system error" in ES File Explorer. There are actually two steps required to configure ES to be able to access and modify files on the system partition.
Step one, you've done, is grant ES superuser access. But all this does is give ES read-only access to the protected system partition. In order to actually make changes to any files on system, you also need to enable read-write access to system.
Step two, In the same place you enable superuser access in ES, you can tap the option to open up another menu, choose Mount R/W, and then select /system.
Now you will be able to actually modify files on the system partition. This is essentially what root explorer does in the background, it just starts up with system mounted as readwrite. But since ES can be used by users without root, it defaults to read-only for system, and must be specifically configured for read-write.
---------- Post added at 02:23 PM ---------- Previous post was at 02:15 PM ----------
IIIMik3 said:
still hoping for a non-root solution to this. :fingers-crossed:
Click to expand...
Click to collapse
Well, there's no way for a non-root device to modify files on the system partition. This is what root gives you, access to modify /system. So without root, there's just no way to accomplish this modification. If the emoji files were stored on /data, then you'd be able to make some changes. But they're stored on /system, which the user on a non-root device is blocked from accessing.
A little background on the "why" this is:
If the user had full read-write to /system by default on a stock device, then any app in the Play Store or sideloaded could compromise your security and make unauthorized changes to your device. This is why /system is protected. By rooting your device, you are removing this protection. You the user are essentially taking on the responsibility to ensure that anything you install from that point forward is safe and trusted. If you install something and grant it root access, it then has access to every file on your device. Because of the very real security dangers involved with rooting, no device will ever come rooted from the factory, and no Play Store app will be able to access /system without being rooted.

trjlive said:
Just an FYI for anyone else who gets the "read only file system error" in ES File Explorer. There are actually two steps required to configure ES to be able to access and modify files on the system partition.
Step one, you've done, is grant ES superuser access. But all this does is give ES read-only access to the protected system partition. In order to actually make changes to any files on system, you also need to enable read-write access to system.
Step two, In the same place you enable superuser access in ES, you can tap the option to open up another menu, choose Mount R/W, and then select /system.
Now you will be able to actually modify files on the system partition. This is essentially what root explorer does in the background, it just starts up with system mounted as readwrite. But since ES can be used by users without root, it defaults to read-only for system, and must be specifically configured for read-write.
---------- Post added at 02:23 PM ---------- Previous post was at 02:15 PM ----------
Well, there's no way for a non-root device to modify files on the system partition. This is what root gives you, access to modify /system. So without root, there's just no way to accomplish this modification. If the emoji files were stored on /data, then you'd be able to make some changes. But they're stored on /system, which the user on a non-root device is blocked from accessing.
A little background on the "why" this is:
If the user had full read-write to /system by default on a stock device, then any app in the Play Store or sideloaded could compromise your security and make unauthorized changes to your device. This is why /system is protected. By rooting your device, you are removing this protection. You the user are essentially taking on the responsibility to ensure that anything you install from that point forward is safe and trusted. If you install something and grant it root access, it then has access to every file on your device. Because of the very real security dangers involved with rooting, no device will ever come rooted from the factory, and no Play Store app will be able to access /system without being rooted.
Click to expand...
Click to collapse
Ah, thanks for this! I'm glad I was able to get it to work with root explorer before this, but I'm glad I know how ES works now.

Hello everyone
I just want to get feedback on something... I use Go SMS Pro, but people using hangouts that I speak with, because I use the emoji provided by the app (iPhone emoji), they don't get most of them, which is very annoying... has anyone faced this? Is this happening just because of the emojis not being integrated? (If I press the button for emojis on the app, I get iPhone' s emojis, but not if i use the SwiftKey shortcut...)
Btw, I tried sending about 50 emoji. Hangouts got 25... :S
Sent from my GT-N5110 using XDA Free mobile app

[Q] TWRP Nandroid Backup/Lollipop Issue...

I have a T-Mobile HTC M7 converted to GPE, recently flashed to Lollipop from KK 4.4.4. I use Tasker and OpenRecoveryScript to automate Nandroid backups through TWRP, then use FolderSync to upload said backup to my server over WiFi. My method worked perfectly until I flashed to Lollipop.
Since flashing to Lollipop, whether through Tasker or manually, I get an error in FolderSync saying the Nandroid files can't be read or copied. If I use TWRP's file manager, I can view the Nandroid folders/files, but those same files are not viewable using ES File Explorer in Lollipop. When I navigate to TWRP\BACKUPS\{Serial Number} folder in ES File Explorer, the {Serial Number} folder (where the TWRP backups are) is listed as a 0k(zero) file that can't be read or copied. When I try to create a new folder (in the BACKUPS folder) using ES File Explorer I get an error saying the operation failed.
Just this morning I restored a Nandroid backup using TWRP, and now in ES File Explorer my entire SDcard folder is blank (not true, as all my apps still function), but in TWRP file manager the SDcard folder is fine. At first I thought the problem was with ES File Explorer, but I tried a few different file explorers with the same result (FX File Explorer tells me 'Access was Denied' when trying to view the sdcard folder. ) All file managers I've tried have root access.
I thought Lollipop fixed the sdcard problems from KK, but this is a whole new one for me. Is there an issue with Lollipop not being able to read files that are written through recovery/TWRP? Any help would be greatly appreciated.

lords8n said:
I have a T-Mobile HTC M7 converted to GPE, recently flashed to Lollipop from KK 4.4.4. I use Tasker and OpenRecoveryScript to automate Nandroid backups through TWRP, then use FolderSync to upload said backup to my server over WiFi. My method worked perfectly until I flashed to Lollipop.
Since flashing to Lollipop, whether through Tasker or manually, I get an error in FolderSync saying the Nandroid files can't be read or copied. If I use TWRP's file manager, I can view the Nandroid folders/files, but those same files are not viewable using ES File Explorer in Lollipop. When I navigate to TWRP\BACKUPS\{Serial Number} folder in ES File Explorer, the {Serial Number} folder (where the TWRP backups are) is listed as a 0k(zero) file that can't be read or copied. When I try to create a new folder (in the BACKUPS folder) using ES File Explorer I get an error saying the operation failed.
Just this morning I restored a Nandroid backup using TWRP, and now in ES File Explorer my entire SDcard folder is blank (not true, as all my apps still function), but in TWRP file manager the SDcard folder is fine. At first I thought the problem was with ES File Explorer, but I tried a few different file explorers with the same result (FX File Explorer tells me 'Access was Denied' when trying to view the sdcard folder. ) All file managers I've tried have root access.
I thought Lollipop fixed the sdcard problems from KK, but this is a whole new one for me. Is there an issue with Lollipop not being able to read files that are written through recovery/TWRP? Any help would be greatly appreciated.
Click to expand...
Click to collapse
I'm still looking forward to automating my backups and syncing them to my server, but I had a similar problem on my OnePlus One today - the TWRP folder was marked as being a zero byte FILE instead of being a folder. Using Solid Explorer for file management on my devices, and the OPO is running a Lollipop ROM as well. Never saw this on KK ROM or on my Samsung Tablet (KK as well)
So - I'd say it's a good observation that this is likely to be ROM related, not device.
BTW: Would you mind telling me how you automated nandroid and syncing?

lords8n said:
I have a T-Mobile HTC M7 converted to GPE, recently flashed to Lollipop from KK 4.4.4. I use Tasker and OpenRecoveryScript to automate Nandroid backups through TWRP, then use FolderSync to upload said backup to my server over WiFi. My method worked perfectly until I flashed to Lollipop.
Since flashing to Lollipop, whether through Tasker or manually, I get an error in FolderSync saying the Nandroid files can't be read or copied. If I use TWRP's file manager, I can view the Nandroid folders/files, but those same files are not viewable using ES File Explorer in Lollipop. When I navigate to TWRP\BACKUPS\{Serial Number} folder in ES File Explorer, the {Serial Number} folder (where the TWRP backups are) is listed as a 0k(zero) file that can't be read or copied. When I try to create a new folder (in the BACKUPS folder) using ES File Explorer I get an error saying the operation failed.
Just this morning I restored a Nandroid backup using TWRP, and now in ES File Explorer my entire SDcard folder is blank (not true, as all my apps still function), but in TWRP file manager the SDcard folder is fine. At first I thought the problem was with ES File Explorer, but I tried a few different file explorers with the same result (FX File Explorer tells me 'Access was Denied' when trying to view the sdcard folder. ) All file managers I've tried have root access.
I thought Lollipop fixed the sdcard problems from KK, but this is a whole new one for me. Is there an issue with Lollipop not being able to read files that are written through recovery/TWRP? Any help would be greatly appreciated.
Click to expand...
Click to collapse
husky69 said:
I'm still looking forward to automating my backups and syncing them to my server, but I had a similar problem on my OnePlus One today - the TWRP folder was marked as being a zero byte FILE instead of being a folder. Using Solid Explorer for file management on my devices, and the OPO is running a Lollipop ROM as well. Never saw this on KK ROM or on my Samsung Tablet (KK as well)
So - I'd say it's a good observation that this is likely to be ROM related, not device.
BTW: Would you mind telling me how you automated nandroid and syncing?
Click to expand...
Click to collapse
FAQ
Google Play Edition 5.0.1
SdCard
Q.)
The sdcard not being visible via PC is annoying.
Is there any fix for this yet?
A.)
Yes, here is a work-around
Install Terminal Emulator then type:
Code:
su
restorecon -FR /data/media/0
and sdfix in the play store should do it

husky69 said:
I'm still looking forward to automating my backups and syncing them to my server, but I had a similar problem on my OnePlus One today - the TWRP folder was marked as being a zero byte FILE instead of being a folder. Using Solid Explorer for file management on my devices, and the OPO is running a Lollipop ROM as well. Never saw this on KK ROM or on my Samsung Tablet (KK as well)
So - I'd say it's a good observation that this is likely to be ROM related, not device.
BTW: Would you mind telling me how you automated nandroid and syncing?
Click to expand...
Click to collapse
The issue definitely seems to be related to Lollipop. I didn't have the problem running KK, either. From all the research I've done it seems to be related to Lollipop looking for the sdcard in data/media/0 while KK and TWRP point to storage/emulated/0. The terminal command restorecon -FR /data/media/0 fixed it for me.
As for the automated Nandroid and sync, I use a combination of Tasker, OpenRecoveryScript, and FolderSync on the Android side and a few .bat scripts on the server side.
Tasker deletes the previous backup, copies the OpenRecoveryScript to the proper folder, sets a variable to show backup has started, then reboots into recovery where TWRP then performs the Nandroid and reboots. On reboot Tasker checks that the Nandroid folder exists, triggers a notification saying same, then triggers FolderSync to sync to my server. I only keep one backup on my phone and 2 on my server. I set Foldersync to sync deletions which deletes the previous backup on my server, but I also have my server set to copy the Nandroid to a separate directory, so I always have 2 backups if necessary. I use a script on my server that checks for the newest Nandroid, then copies it to separate directory before deleting the oldest one. When I wake up in the morning I can see Tasker notification that Nandroid file exists and FolderSync notification of successful sync. I also have Tasker set to trigger a notification if Nandroid fails, and Foldersync will also notify if an error occurred during sync. I use a Tasker profile to trigger all of this at 3am but I also have a shortcut that allows me to perform it manually whenever I want, with 1 click.
Note that this method requires the paid version of FolderSync for Tasker integration and is a little involved, but I've tried other methods (Onandroid, etc...), and this one is the most reliable. I know I can count on Tasker and TWRP to do their jobs, no third party necessary. The only redundancy variable I haven't taken into consideration is if the Nandroid backup is corrupt, but TWRP seems pretty reliable in that dept and that hasn't happened yet...
If you're interested, I'll send you the corresponding Tasker profiles and tasks.

lords8n said:
If you're interested, I'll send you the corresponding Tasker profiles and tasks.
Click to expand...
Click to collapse
I am interested

husky69 said:
I am interested
Click to expand...
Click to collapse
Sorry for the delay, been busy with holiday stuff. Here are the Tasker/Nandroid files. Extract the .prf files to /Tasker/profiles and the .tsk files to /Tasker/tasks, then import each into Tasker. You will need to edit (in Tasker) Nandroid_Backup.tsk.xml to reflect your TWRP Nandroid backup folder, and openrecoveryscript (in txt editor) to add/remove backup options if necessary.