This is the first release of TiB that has not been able to locate my TitaniumBackup_license.txt file. I am using a Nexus 6 on MRA58K (M) with SuperSU 2.52 and TiB 7.2.4. Stock with the exception of a modified stock kernel. (http://forum.xda-developers.com/nexus-6/development/kernel-stock-kernel-root-color-control-t3218958)
Here is what I did to get it working:
If you have a proper key file named "TitaniumBackup_license.txt" try this:
1. Copy TitaniumBackup_license.txt to root of your device (/) using ES File Explorer with root permissions enabled.
2. After you copy the file to the root of your phone (NOT SDCARD root!), from the root directory of your phone, hit home button while in ES File Explorer. This basically leaves ES File Explorer running and in the proper place for this trick to work.
3. Go to Chrome browser and download any random image, use save! Long press an image and do save image. Hit home button.
4. Go to notification shade and open the now downloaded image with ES File Explorer ONCE (do not set as default). This step assumes you do NOT have a default image viewer. If you DO have a default image viewer it needs to be ES File Explorer OR nothing. Ex. If Google Photos opens, then you need to clear defaults for Google Photos.
5. Once image is loaded in ES File Explorer, hit back button and it should put you at root of ES File Explorer. This is the exact same place you left ES File Explorer in step 2.
6. Navigate to /storage/emulated/legacy this directory should be strangely empty. It will not be your typical SDCARD contents. You might only see titanium backup folder that is empty or some other random folder. THIS odd empty directory is where TB looks for the key file!
7. Navigate back to / and copy TitaniumBackup_license.txt to /storage/emulated/legacy
8. Restart Titanium and it should be good to go for registered key!
9. DELETE the TitaniumBackup_license.txt file from / as it or any other random file should NOT be here in your system ROM.
As a senior member, you should know your way around the site.
XDA Assist is here to help navigate the site, not for questions or information. Please post this in an appropriate area. Assist is not that. :good:
Thread closed.
Related
I am updating to Thiaiz rom, and he told me to change permission on the init.d file. but ising the root explorer I cant seem to change it, because it is a read only file. can anyone help me on this issue please..
-Navigate with a file explorer to /system/etc/init.d and change permission on both scripts to "777" it means mark the 9 permission options.
-Install Script manager from market.
-Open script manager, navigate till system/etc/init.d and run the 2 scripts at boot.
thats the instruction, but i cant seem to follow it.
stunny said:
I am updating to Thiaiz rom, and he told me to change permission on the init.d file. but ising the root explorer I cant seem to change it, because it is a read only file. can anyone help me on this issue please..
-Navigate with a file explorer to /system/etc/init.d and change permission on both scripts to "777" it means mark the 9 permission options.
-Install Script manager from market.
-Open script manager, navigate till system/etc/init.d and run the 2 scripts at boot.
thats the instruction, but i cant seem to follow it.
Click to expand...
Click to collapse
There's ES File Explorer installed. Update to latest version in market if needed.
Open up app
Press Settings
Scroll down to root settings...
Check Root Explorer and Mount File System. If you fail to check Root Explorer, update to latest version of ES File Explorer in market.
Now that you got root explorer mode...
Press back till you go back to the file explorer.
Press the Sdcard looking icon on the row of icons. Its the leftmost icon in that row of 6 icons.
After you've pressed it, click into system folder
Next, click into etc folder
Next, click into init.d folder
You will see two files in there.
Hold down on the file (whichever first doesn't matter), then press properties.
Click Change in the permissions section, and then check everything.
Press Okay and repeat for the 2nd file.
After you are done, restart the phone.
After phone is restarted, go check to see if the permissions are changed.
thank you very much for the detailed instruction. i love this forum i tried em and it works
Very frustrating problem. My G2X has been set up exactly the way I like it. I've been using ES File Explorer for network access and it has worked flawlessly.
However, a few days ago there was a new update for ES File Explorer and since that update, file management has been weird.
1. First, using File Manager (built into CM7), when I browse to a directory images, videos, and other files are associated with ES Zip Manager (which I do not have installed). I can change the file association, but the icon for the files stay with ES Zip Manager.
2. Browsing a directory of images with File Explorer or Gallery (built into CM7) will sometimes insert an image from different directory.
3. Using Gallery, as I browse files sometimes an image will duplicate.
I have been forced to uninstall ES File Explorer, but problems #2 and #3 still exist.
I've gone into Development Tools > media Scanner, but no joy.
This is very very frustrating. I now have my media messed up and no way to access files on my network.
HELP!
Hi guys, I'm trying to follow the guides to prevent my wallpaper from changing that need to navigate to /data/data/com.android.settings/files by ES File Explorer or Root Explorer.
However, I couldn't find anything from /data/
Mine is 6.2.1, Burritos rooted.
Please help, thanks
(repeat of posted reply to same question in the How to Apply Wallpaper thead)
I use ES File Explorer 1.6.1.0 from the Market (not Amazon because last I checked they were a version or two behind)
Then go into settings a scroll to bottom and select ROOT EXPLORER and when asked I think I selected the CM option (and for good measure select MOUNT FILE SYSTEM, although I don't think that is required unless you are working in the /system/ folder).
Now you should see the contents of the /data/ folder...
Hope this helps.
hdmunger said:
(repeat of posted reply to same question in the How to Apply Wallpaper thead)
I use ES File Explorer 1.6.1.0 from the Market (not Amazon because last I checked they were a version or two behind)
Then go into settings a scroll to bottom and select ROOT EXPLORER and when asked I think I selected the CM option (and for good measure select MOUNT FILE SYSTEM, although I don't think that is required unless you are working in the /system/ folder).
Now you should see the contents of the /data/ folder...
Hope this helps.
Click to expand...
Click to collapse
I can't select ROOT Explorer with ES File Explorer
Hmmmm........got nothin'....
Are you sure you are looking in /data and not /sdcard/data?
What are you using Root Explorer or ES File Explorer?
If you're not fully rooted, even if you temp root with burrito root and set system to r/w, /data will show as empty unless your file explorer had been granted su permissions (which you'll need full root and super user app for). Found that out the hard way today myself.
Damn you Swype!
I had the same problem when I rooted the first time. I was following SuperOneClick instructions until I read it wasn't working with the latest stock update. Mid-root process, I switched to Burrito Root and completed the process. When I went to make mods in /data/data/... and saw nothing, I did a complete system restore and re-rooted with Burrito Root from the beginning. Everything's been fine since, including /data/data/.
After reading the post above, I guess my issue was either a botched root or something awry with my su install.
The easiest way, at least for me, to get an app into /system/app is to use Root Explorer to copy the apk into /system/app.
To do this:
In Root Explorer, copy the apk file you want to put in /system/app
Navigate to the /system/app directory
Tap the Mount R/W button on the top right
Tap Paste
Scroll down to the pasted apk, long press on it and select Permissions (you'll see 9 check boxes when you do this)
Check the Read and Write buttons for User, and only the Read boxes next to Group and Others, then tap OK (once you're done, the read/write permissions under the app name should be the same as all the other apps listed (rw-r--r--))
Reboot.
If anybody want any system app,i have backup of all the stock rom apps...let me know if somebody want...
I recently Wiped my Phone completely and decided to Re-Flash Viper 1.2.1.
I noticed a problem prior to re-installing but thought nothing of if since it wasn't crucial at the time.
In Root explorer, I am able to delete [i normally delete boot animations] system files but not add where I need to add. Example, I wanted to add a ringtone to my system/media/ringtones folder. I normally [for the last six years] could just copy and paste such files using a root file manager.
However, when I any these files to for example /system/customize/resource/ it doesnt add it. BUT IT DOES rename the file and save it under a dif folder.
Example. Tried copying-copy to-moving to "androidtwirp.mp3" from sdcard to /system/media/notifications and a message pops up saying"notificationsandroidtwirp.mp3 successfully copied-moved to" and it saves notificationsandroidtwirp.mp3 to /system/media/ and it stays there. retrying from that location only results in "notificationsnotificationsandroidtwirp.mp3".
So not only does it rename the file but it saves it in the wrong location. I am at a loss for word. I tried the basics to tryand fix this but i cant seem to hit it on the head.
Thanks!
Edit: Not updating Super SU app, file explorer seems to have worked. Will attempt to duplicate problem to see what actually caused.it.
FOUND IT!
Updating my ES File explorer broke my system writing ability. DO NOT UPDATE is because when you do...
Any file you move, copy/paste to the system will not work properly.
This first happened when I tried to copy and paste a boot animation after I updated ES root explorer. It would rename whatever file i was trying to paste/move/copy over and save it under a sub folder.
example.
copying a ringtone [i.e. androidtwirp.mp3] from SDCard to System folder, the path is /system/media/audio/ringtones/ and it would rename it "ringtonesandroidtwirp.mp3" and save it under /system/media/audio/.
So basically not only was it renamed [which i didnt want it to be] but it would save it to the folder before the actual folder i needed it to be in, plus it would corrupt the file deeming it useless.
moving "ringtonesandroidtwirp.mp3" into the correct folder would only result in "ringtonesringtonesandroidtwirp.mp3"
this happened across the board with all files being moved around
The ES File Explorer version 1.2.1 comes with works flawlessly so don't update it.
I uninstalled ES [also any folders in SDcard related to it] and downloaded JRummy's root explorer and everything is back to normal except i have to reboot the phone to see files [like ringtones and notifications] that i added to the system.
I think it has something to do with our devices having an unlocked bootloaader, but still S-ON. There's S-OFF in the Dev section now if you really need to write to the system folder a lot.
I came from the Vibrant so I know what you're going through
Yeah, im on a low hboot so s-off might not be in my plans since I can practically flash what I want but it was ES file explorer, when I updated the apk the root permissions broke when writting to the system. I emailed the dev and they said they'd have it fixed on the next update.
echo en Android