Hey XDA,
Lately I have been a lurker here eversince the haters on the G2x thread caused me to stop dev'ing. Anyways I have found a fix for the failed updates that a lot of us are getting. Follow the steps below to fix. You need a root file browser'
BEFORE FOLLOWING THESE STEPS
OPEN A ROOT BROWSER AND BROWSE TO /cache/recovery/last_log
This will show why the update failed! Undo whatever changes you made based on the output and you should be Golden
-Thanks to Namidairo and Disconnect from IRC for this tip
Step 0 (Only if you have V6 Script): Launch Script and Unsupercharge
Step 1: Browse to system and open your build prop and if there is a line at the bottom saying something like "#Supercharger Entries" then edit your build.prop and delete it.
Step 2: In system if there is a SU-Backup and another SU file delete it and then open Voodoo Root and Make a protected backup of SU.
Step 3: Browse to data and delete Su-Test
Step 4(Only if you messed with GPS) Make sure to revert GPS to original settings -> etc/gps/gps....xml
Step 5: Launch system settings navigate to apps, find DMClient and clear cache and Data and then in settings goto about and the firmware upgrade and let it download the update again.
Step 6: Once Downloaded apply the update and you will see that the red exclamation wont happen.
Basically if the build.prop file is modified then the update fails the other files mentioned above are just to make sure.
Let me know if you encounter issues. Good Luck
Edit: Once updated you will be greeted with "Please check system date"
Edit 2: New Features
-SystemBar Lock : Under Asus Customized Settings in Settings
-Disconnect Network during sleep under Asus Customized Settings in Settings
-Wifi Direct
-Asus Live WP has sunshine rays that are animated. Night Scene is also animated with glow bugs and transition from Day to Night with Sun Setting.
ASUS MyWater2 changed and modified with more detail and Night-Day Mode
-Searching for more
What your Build.prop should look like
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's not always the build.prop that is at fault.
It was mentioned in irc that /cache/recovery/last_log will tell you what went wrong.
thanks for that I had not seen that in XDA. I did though do the steps above and was able to update after 7 failed update attempts.
I will add your suggestion to the OP if its okay?
Great tip on the log file. The update didn't like that I had renamed some files in system/app to stop them loading.
Added more changes found in the OP
Added Suggestion to check Cache in OP
flak0 said:
thanks for that I had not seen that in XDA. I did though do the steps above and was able to update after 7 failed update attempts.
I will add your suggestion to the OP if its okay?
Click to expand...
Click to collapse
Just add credit to Disconnect from IRC, I'm just remembering that it was mentioned.
Namidairo said:
Just add credit to Disconnect from IRC, I'm just remembering that it was mentioned.
Click to expand...
Click to collapse
Done check OP. Also gave you thanks
I seen this thread and im having simular problems. I am rooted but never unlocked.. I did modify lcd density and corrected it via fixing the build.prop and copying files from adb (i didnt make a backup of build.prop. When i look at mine it has lcd density line at the very bottom and there is a blank line directly above that. Is that the way the build.prop is? I have nothing to refer to. Can someone check this for me. I would really like to install this update Been messing with this thing for last 2 hours!
Seems like alot lotta people are having problems with this update and red failed..
flipper2006 said:
I seen this thread and im having simular problems. I am rooted but never unlocked.. I did modify lcd density and corrected it via fixing the build.prop and copying files from adb (i didnt make a backup of build.prop. When i look at mine it has lcd density line at the very bottom and there is a blank line directly above that. Is that the way the build.prop is? I have nothing to refer to. Can someone check this for me. I would really like to install this update Been messing with this thing for last 2 hours!
Seems like alot lotta people are having problems with this update and red failed..
Click to expand...
Click to collapse
I will post a screenshot in 2 minutes below this post to help you. Actually Ill post it on the OP too
I deleted an APK or two from /system/app and was unable to run the update as a result.
I just manually downloaded and reran the .15 update, then ran the .21 OTA update without any problems
Looking at the log file using test viewer....the log file is empty
Build Prop seems OK.....no extra entries
Step 2 - One SU backup there....but protected....can't delete....if I use Rootkeeper to delete, then it's gone, but I'm still rooted....when I try to unroot, it come back.
Step 3 - No Su-test in Data
Step 4 - Only gps.xml in GPs folder
Step 5 - cleared DM file in "Apps"'
Still can't upgrade.
The only files that are not original are for the AD=HOC fix.....BUT....I can't delete them.....This is the only computer/internet access... that I have...tethered to my TouchPro2.....If I change, then I can't download the update.....Catch 22....will be away from home for about 2 weeks
Solved!! Went to Mickey D's and used their free wifi got 15 downloaded/installed, then, using their wifi updated to 21 using OTA....whewwww.....AD-Hoc still works
flak0 said:
I will post a screenshot in 2 minutes below this post to help you. Actually Ill post it on the OP too
Click to expand...
Click to collapse
thx that will help.. i will try it tommorow when i get back from work. domt think its a good idea to mess with build.prop when sleepy.
robertg9 said:
Tried looking at the log file using test viewer....the log file is empty
Build Prop seems OK.....no extra entries
Step 2 - One SU backup there....but protected....can't delete....if I use Rootkeeper to delete, then it's gone, but I'm still rooted....when I try to unroot, it come back.
Step 3 - No Su-test in Data
Step 4 - Only gps.xml in GPs folder
Step 5 - cleared DM file in "Apps"'
Still can't upgrade.
The only files that are not original are for the AD=HOC fix.....BUT....I can't delete them.....This is the only computer/internet access... that I have...tethered to my TouchPro2.....If I change, then I can't download the update.....Catch 22....will be away from home for about 2 weeks
Click to expand...
Click to collapse
Yes - me too. Tried this, no dice.
what`s the name of the widget that shows cpu usage in status bar in the first post screenshots?
product26 said:
I just manually downloaded and reran the .15 update, then ran the .21 OTA update without any problems
Click to expand...
Click to collapse
Can you remind me how to do this? And what do I lose from my current .19 installation as a result of rerunning it?
Thanks.
180490 said:
what`s the name of the widget that shows cpu usage in status bar in the first post screenshots?
Click to expand...
Click to collapse
yeah, which one is that? haven't seen that one before?
-lukin- said:
Can you remind me how to do this? And what do I lose from my current .19 installation as a result of rerunning it?
Thanks.
Click to expand...
Click to collapse
Not sure what you would lose but here is how you do it manually
go to http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+Prime+TF201&p=20&s=16
Download the .15 update for your sku. It is a zip file, in that zip file is another zip file. Take that 2nd zip file and put it on your micro sd card. remove your sd card and then put it back in and it should detect the update on the sd card.
edit: I too was having issues getting the .21 update(kept failing) and I just flashed .15 manually and just flashed the .21 update and it worked! No laying down droid with red ! mark.
graffixnyc said:
Not sure what you would lose but here is how you do it manually
go to http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+Prime+TF201&p=20&s=16
Download the .15 update for your sku. It is a zip file, in that zip file is another zip file. Take that 2nd zip file and put it on your micro sd card. remove your sd card and then put it back in and it should detect the update on the sd card.
Click to expand...
Click to collapse
One important part after you do this if you have root and want to keep it, you need to either reappy through voodoo root keeper or re root it. I didn't now I'm waiting for a root method.......
Before you apply .21 update
Namidairo said:
It's not always the build.prop that is at fault.
It was mentioned in irc that /cache/recovery/last_log will tell you what went wrong.
Click to expand...
Click to collapse
Thanks for that. I checked the log and saw that system/bin/wpa.supplicant2 was causing the failure. I had replaced that file so that I could get adhoc back. I just restored the original file and the update worked.
IGNORE - MY POST WAS:
stu•pid
[stoo-pid, styoo‐] -er, -est, noun
adjective
1. lacking ordinary quickness and keenness of mind; dull.
2. characterized by or proceeding from mental dullness; foolish; senseless: a stupid question.
3. tediously dull, especially due to lack of meaning or sense; inane; pointless: a stupid party.
4. annoying or irritating; troublesome: Turn off that stupid radio.
5. in a state of stupor; stupefied: stupid from fatigue.
Related
I just changed the mms.apk that came with the rom, to one that i had on another rom(Bulletproof). And it worked like a charm, here is a screen shot of it..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
the link is at the bottom of post
Then just use root explorer mount as rw then make a backup of your mms.apk located in system/app (i would save it to the external sd card) then copy and paste the new mms.apk to system/app and set permissions..
I cant post to the development section yet so if anyone can put a link to this thread in nrg's thread that would be great.....
Awesome, thanks!
Sent from my HTC_Amaze_4G using XDA
Link Fixed
I just changed the attached files link, idont know what i did but it should work now....
P.S. Thanks Glacierguy
Was the timestamp thing happening on every text message, or just some of them? Are you sure this fixes it? (I'm going to install it, but I have kept WiFi calling off for a long time now just because of this...just want to be sure this 100% fixes it before I turn it back on)
MildewMan said:
Was the timestamp thing happening on every text message, or just some of them? Are you sure this fixes it? (I'm going to install it, but I have kept WiFi calling off for a long time now just because of this...just want to be sure this 100% fixes it before I turn it back on)
Click to expand...
Click to collapse
Yes it fixes it, but the only way to know is just try it out for yourself.. just make a backup of your mms.apk before and your good.....
Sent from my HTC_Amaze_4G using Tapatalk
Does this also fix not being able to receive mms pictures?
rbaruch said:
Does this also fix not being able to receive mms pictures?
Click to expand...
Click to collapse
Mms still does not work on WiFi calling, its a T-mobile thing but everthing else does...
Sent from my HTC_Amaze_4G using Tapatalk
Is there any way you could go a little more in depth with the instructions? I'm used to something that is a lot less annoying to work with (I came from a G2) so I'm lost as how to replace the MMS.APK. I can't do anything through the file manager with the one that is there, and it won't let me write to that folder. Help?
Lulzmaster said:
Is there any way you could go a little more in depth with the instructions? I'm used to something that is a lot less annoying to work with (I came from a G2) so I'm lost as how to replace the MMS.APK. I can't do anything through the file manager with the one that is there, and it won't let me write to that folder. Help?
Click to expand...
Click to collapse
I used an app called Root Explorer, it allows you to mount the system as r/o which means read only, and mount r/w which means read write. This allows you to copy, paste, delete to Android system files very easily, but be careful this is where you can really cause a problem if you don't what you are doing.
Sent from my HTC_Amaze_4G using Tapatalk
I have ES File Explorer (what comes with the Rom) and I've been messing around with it. I get the new .apk copied but when I navigate to the system folder it says I don't have permission to do anything, I'm assuming because I haven't mounted the /system folder?
Edit- scratch that, I think I got it working. Won't be able to test to see if it worked but the icon is unthemed... So we shall see.
Also, through the "share" context menu, messaging doesn't pop up anymore, after a restart. Any way to change that?
Lulzmaster said:
I have ES File Explorer (what comes with the Rom) and I've been messing around with it. I get the new .apk copied but when I navigate to the system folder it says I don't have permission to do anything, I'm assuming because I haven't mounted the /system folder?
Edit- scratch that, I think I got it working. Won't be able to test to see if it worked but the icon is unthemed... So we shall see.
Also, through the "share" context menu, messaging doesn't pop up anymore, after a restart. Any way to change that?
Click to expand...
Click to collapse
I'm not sure why the share feature is not working with es file explorer but it works on root explorer, Lulzmaster check you pm box......
Sent from my HTC_Amaze_4G using Tapatalk
elwaxman said:
I just changed the mms.apk that came with the rom, to one that i had on another rom(Bulletproof). And it worked like a charm, here is a screen shot of it..
View attachment 1004265
the link is at the bottom of post
Then just use root explorer mount as rw then make a backup of your mms.apk located in system/app (i would save it to the external sd card) then copy and paste the new mms.apk to system/app and set permissions..
I cant post to the development section yet so if anyone can put a link to this thread in nrg's thread that would be great.....
Click to expand...
Click to collapse
Thanks for the fix man. I used root explorer and text time stamp issue is fixed. thanks a bunch!
elwaxman said:
I just changed the mms.apk that came with the rom, to one that i had on another rom(Bulletproof). And it worked like a charm, here is a screen shot of it..
Then just use root explorer mount as rw then make a backup of your mms.apk located in system/app (i would save it to the external sd card) then copy and paste the new mms.apk to system/app and set permissions..
I cant post to the development section yet so if anyone can put a link to this thread in nrg's thread that would be great.....
Click to expand...
Click to collapse
Okay, I followed these instructions (files copied without any errors). When I click on the new mms.apk, it tries to install it as a system application (I have non-market installations allowed). However, when I click "Install" it does it's little thing and then says "Application not installed". Is there a step missing somewhere? Thanks.
Disregard. I thought I needed to reinstall. I just sent a text and it used the new apk.
Sent from my HTC_Amaze_4G using XDA
ernieg92 said:
Disregard. I thought I needed to reinstall. I just sent a text and it used the new apk.
Sent from my HTC_Amaze_4G using XDA
Click to expand...
Click to collapse
Just make sure you set permissions in root explorer
Sent from my HTC_Amaze_4G using Tapatalk
elwaxman said:
Just make sure you set permissions in root explorer
Click to expand...
Click to collapse
For some reason I didn't need to do that. They were already set at rw-r--r--.
Thanks again.
tried it and my messaging vanished... ended up reinstalling the nrg rom.
I pulled the stock mms.apk from the ICS leak rom. This could be identical to the one in the OP, but may want to try this one if on ICS Energy. Don't forget to fix permissions afterwards.
bangsters said:
tried it and my messaging vanished... ended up reinstalling the nrg rom.
Click to expand...
Click to collapse
The MMS.apk in the op was for NRG's Gb rom sense 3.0, i have been trying to fix the issue with ICS 3.6 rom but the problem i have is that the MMS.apk is odexed so cant seem to get it to stick....
MildewMan said:
I pulled the stock mms.apk from the ICS leak rom. This could be identical to the one in the OP, but may want to try this one if on ICS Energy. Don't forget to fix permissions afterwards.
Click to expand...
Click to collapse
Try pulling the the MMS.odex as well, make a backup of the original mms.apk and mms.odex and push the new ones to system/apps and set permissions, i went back to stock ics for now so i cant test this...
So my friend was playing around with my T-Prime awhile back when he shows me he has entered the incorrect pattern so many times that it will only allow me to sign in with my Google account to regain access to it. Im like okay, no big deal, ill just sign in change the password and no problem.. Well, I have tried that and it will not accept my log in information.. I know the username (email) and password is right. I can log in from my computer just fine and I haven't changed the password for that account since I've had the tablet. I do not know what else to do..? I have tried putting just the first part of my username, tried entering null into the password box. didn't work.. I believe it might have something to do with the wifi not being on, but i cant turn it on because my tablet is locked! Is there anyway i can use ADB or something to turn wifi on or to let me reset the lock screen so i can enter my unlock pattern? I do know what the unlock pattern is. I would really like to not have to factory reset and wipe all the data and loose everything.. Thanks in advance!
You can use adb if you had usb debugging e.nabled and then you can remove some file which keeps the lockscreen info.I can't remember the file name but you can google it.If uou can't find anything the only thing you can do is hard reset.
Sent from my Optimus Me using xda premium
yup
but rember if you try to whipe data/cash in recovery mode u still have to enter your lockscreen password
as mentioned try hardreset via buttons at startup
hope u get done fast =)
nerot said:
You can use adb if you had usb debugging e.nabled and then you can remove some file which keeps the lockscreen info.I can't remember the file name but you can google it.If uou can't find anything the only thing you can do is hard reset.
Click to expand...
Click to collapse
I do have debugging enabled and I'm not really good with ADB, but I have tried accessing the file in: data/data/com.android.providers.settings/databases/settings.db
Now on my OG Droid, when I navigate to this file using Root Explorer, it allows me to open and view the settings.db file with its internal viewer, where I can see an entry called "secure". When you open that, the most notable entry is the one called "lockscreen.lockedoutpermanently" and its value is of course 0 being "false", because this is on my Droid. but its likely the value of 1 means "true", which is what i assume to be the case on my T-Prime. This all seems like a promising lead, meaning, in theory, all I would have to do is be able to get that file from the tablet and change the value to 0.. however, using ADB when I navigate to that folder, I cannot pull the settings.db file because it says permission denied. Any ideas on what might cause that? I might not be using ADB correctly, or its because it's a system file. I found some instructions awhile ago saying you could use ADB and call a program called sqlite3 to edit the file that way and return the value to 0, but when I tried that it could not locate a program called sqlite3.. Also, I have tried hard resetting with volume down and power multiple times.. no luck.. So I'm out of knowledge and ideas..
Ryco26 said:
I do have debugging enabled and I'm not really good with ADB, but I have tried accessing the file in: data/data/com.android.providers.settings/databases/settings.db
Now on my OG Droid, when I navigate to this file using Root Explorer, it allows me to open and view the settings.db file with its internal viewer, where I can see an entry called "secure". When you open that, the most notable entry is the one called "lockscreen.lockedoutpermanently" and its value is of course 0 being "false", because this is on my Droid. but its likely the value of 1 means "true", which is what i assume to be the case on my T-Prime. This all seems like a promising lead, meaning, in theory, all I would have to do is be able to get that file from the tablet and change the value to 0.. however, using ADB when I navigate to that folder, I cannot pull the settings.db file because it says permission denied. Any ideas on what might cause that? I might not be using ADB correctly, or its because it's a system file. I found some instructions awhile ago saying you could use ADB and call a program called sqlite3 to edit the file that way and return the value to 0, but when I tried that it could not locate a program called sqlite3.. Also, I have tried hard resetting with volume down and power multiple times.. no luck.. So I'm out of knowledge and ideas..
Click to expand...
Click to collapse
Hmm try typing
su
*adb pull command*
if it doesn't work download Qt ADB and use that its a windows software.Afte lr you download it get the file and upload it here.I might be able to help you then,edit it reupload it so that you can push it back and see.
Sent from my Optimus Me using xda premium
nerot said:
Hmm try typing
su
*adb pull command*
if it doesn't work download Qt ADB and use that its a windows software.Afte lr you download it get the file and upload it here.I might be able to help you then,edit it reupload it so that you can push it back and see.
Click to expand...
Click to collapse
This is what I have tried doing so far:
using ADB and typing:
adb shell
[email protected]:/ $ su
[email protected]:/ # adb pull data/data/com.android.providers.settings/databases/settings.db C:\Users\Ryan\Desktop
and it returns "error device not found"
I have tried:
adb pull data/data/com.android.providers.settings/databases/settings.db C:\Users\Ryan\Desktop
and it returns "failed to copy 'data/data/com.android.providers.settings/databases/settings.db' to 'C:\Users\Ryan\Desktop/settings.db': Permission denied"
here's what it shows:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If i just try to pull the whole data folder, it returns:
"pull: building file list... 0 files pulled. 0 files skipped."
I dont know whats wrong here.. it does not want me to have access to the data folder in any way I try to pull from there.. maybe I'm missing something.. like I said I'm not very good with ADB.
So then I tried using QtADB like you recommended, which looked really promising! and it does work great for a lot of things. I'm happy to now have it if I need it.. except when I try to use it to navigate into the data folder it shows nothing!
See the screen shots:
and
Any ideas what to do?
Dude. Go on your comp. Go to the play store and look for no luck screen. There's an app that disables your lock screen in instances like this. It tells you to download it to your phone, then to find another app to download. Do that from your comp and you're golden
Sent from my 8-Core LG Galaxy S7
Alphaneus said:
Dude. Go on your comp. Go to the play store and look for no luck screen. There's an app that disables your lock screen in instances like this. It tells you to download it to your phone, then to find another app to download. Do that from your comp and you're golden
Click to expand...
Click to collapse
You do realize I wont be able to set the app up, or even download it to the tablet..? The tablet is locked, I cannot unlock it to set the app up, and the wifi is not on, so no internet connection.
I may be missing something here, but I am honestly open to any ideas.
Ryco26 said:
This is what I have tried doing so far:
using ADB and typing:
adb shell
[email protected]:/ $ su
[email protected]:/ # adb pull data/data/com.android.providers.settings/databases/settings.db C:\Users\Ryan\Desktop
and it returns "error device not found"
I have tried:
adb pull data/data/com.android.providers.settings/databases/settings.db C:\Users\Ryan\Desktop
and it returns "failed to copy 'data/data/com.android.providers.settings/databases/settings.db' to 'C:\Users\Ryan\Desktop/settings.db': Permission denied"
here's what it shows: http://oi47.tinypic.com/mcum8z.jpg
If i just try to pull the whole data folder, it returns:
"pull: building file list... 0 files pulled. 0 files skipped."
I dont know whats wrong here.. it does not want me to have access to the data folder in any way I try to pull from there.. maybe I'm missing something.. like I said I'm not very good with ADB.
So then I tried using QtADB like you recommended, which looked really promising! and it does work great for a lot of things. I'm happy to now have it if I need it.. except when I try to use it to navigate into the data folder it shows nothing!
See the screen shots:
http://oi47.tinypic.com/9sc7c8.jpg
and
http://oi49.tinypic.com/f1hycw.jpg
Any ideas what to do?
Click to expand...
Click to collapse
Hmm there must be some sort of protection.Are you rooted? If not thwn I really don't know what else you could do.The only thing that you can do is go to the place where you bought it and explain the situation and hope they will take it for repair.
Sent from my Optimus Me using xda premium
nerot said:
Hmm there must be some sort of protection.Are you rooted? If not thwn I really don't know what else you could do.The only thing that you can do is go to the place where you bought it and explain the situation and hope they will take it for repair.
Click to expand...
Click to collapse
Yes, I am rooted.. and I did figure out what was wrong! I had to change the permissions of each folder and the settings.db file to allow "other" to read, write and execute.
I used ls -l to see what was there and what permissions they currently had and took note. So here's what I had to do.
> adb shell
$ ls -l
gives you this:
(This is after I had already changed the permissions)
So I then took note of all the permissions of the folders that were in the path of data/data/com.android.providers.settings/databases/settings.db
I then read up on changing permissions and came across this site: http://ss64.com/bash/chmod.html
Very useful.
So I then did:
$ su
# chmod 777 data/
and it worked. I could now see the data/ folder in QtADB
So, finally some progress!
I did the same thing for the remaining folders using chmod and changed whatever the existing permissions were by adding only read, write and execute to the "other" category. This works perfectly on my Droid. and after all that I can use adb and pull the settings.db file right to my desktop or wherever. I then found an SQLite program to open and edit the file on my computer. http://sourceforge.net/projects/sqlitebrowser/
This all works perfectly and now I'm thinking all I have to do is do all of this to my T-Prime, pull the file, edit the database file, push back to device, go back and change permissions back to the way they were, reboot and I'm good to go.
However, I make it into the databases/ folder and discover there are 3 files in there.
1) settings.db
2) settings.db-shm
3) settings.db-wal
There was only one on my droid. And the main database file seems to kind of depend on the others. So I pull it and try to open it with the program I mentioned earlier and it is empty. there is nothing in it to edit. the file size is 39Kb, which is slightly larger than the 34Kb file I pulled from my Droid, yet its empty. I don't know how to edit it at this point. I believe it uses the other 2 files somehow.
I would like someone else, preferably with a Transformer Prime, to try this, pull the file and upload and link it so I can see if it will open for me and contain anything. They don't seem to contain any personal or device specific information in them, just settings. if it's from another Prime and opens for me, what the heck, i'll push it onto mine and give it a shot. All I have now is a $630 paperweight and headache.
You could try using your phone to edit it using an editor from the market, then push the file back to your tab.
I had something like this happen to me once when trying to import contacts to a freshly reset device.
What worked for me was disabling 2 step verification in Gmail.
Theonew said:
You could try using your phone to edit it using an editor from the market, then push the file back to your tab.
Click to expand...
Click to collapse
I thought of that too and I tried doing that. It says: "An error occurred while opening the database. database disk image is malformed: , while compiling: SELECT * FROM sqlite_master WHERE type in('table','view') ORDER BY name"
Whatever that means.. I don't know.
Thanks for the suggestion though.
Try using SQLite Editor from the market.
Theonew said:
Try using SQLite Editor from the market.
Click to expand...
Click to collapse
That is what I'm using in the previous post. I navigate to it through Root Explorer and it opens it with that. it opens all the other ones just fine though..
Ryco26 said:
That is what I'm using in the previous post. I navigate to it through Root Explorer and it opens it with that. it opens all the other ones just fine though..
Click to expand...
Click to collapse
That is weird. I tried it with the one from my tab and it opened it perfectly. Have you tried another editor in that case?
Theonew said:
That is weird. I tried it with the one from my tab and it opened it perfectly. Have you tried another editor in that case?
Click to expand...
Click to collapse
Yeah, I have tried the one on my computer, SQLite Editor, like you had mentioned and another from the market, i forget which one, but all with no luck. It's like because its locked, the file is blank.. but i think it could also be because of the other 2 files. The ones called settings.db-shm and settings.db-wal. What do you think? Do you have a T-Prime?
Ryco26 said:
Yeah, I have tried the one on my computer, SQLite Editor, like you had mentioned and another from the market, i forget which one, but all with no luck. It's like because its locked, the file is blank.. but i think it could also be because of the other 2 files. The ones called settings.db-shm and settings.db-wal. What do you think? Do you have a T-Prime?
Click to expand...
Click to collapse
No, I do not have a Prime (waiting for something else to come along ). You could try pulling all files and placing them in a folder, then using an editor to see if that works.
Theonew said:
No, I do not have a Prime (waiting for something else to come along ). You could try pulling all files and placing them in a folder, then using an editor to see if that works.
Click to expand...
Click to collapse
Oh ha okay. I shoulda waited for the TF700t.. anyway thats what i have done, is pull all files and put them into a folder.. it doesn't seem to make a difference because the -shm and -wal make them unreadable to average editors as database files. I can zip them and link them to you if you think you can figure something out?
Ryco26 said:
Oh ha okay. I shoulda waited for the TF700t.. anyway thats what i have done, is pull all files and put them into a folder.. it doesn't seem to make a difference because the -shm and -wal make them unreadable to average editors as database files. I can zip them and link them to you if you think you can figure something out?
Click to expand...
Click to collapse
Go ahead .
There has been a patched version of the updated Google Wallet released. Links updated. Now the Play Store won't ask you to update Wallet.
This is a link w/the method I used to install the apk (the linked OP method didn't work for me) and the Google Wallet app seems to work fine for me. It is showing me my unused $10, but it is too late in the evening for me to actually go test it. I will do my best to not be lazy tomorrow and find a store that has a NFC payment system.
Tested and it works perfectly.
So you can try the linked OP method, my method, or OMJ's flashable zip.
Region / Device / Root Patched Google Wallet APK (1.1-R67-v5) - Android Software - MoDaCo
apk
Patched apk
Flashable zip by OMJ:
Flashable zip by OMJ. It is the latest version so the Play Store won't ask you to update Wallet.
And here is his post in this thread. Please follow his instructions and hit the thanks and donate button for him. He is doing more actual work than I am. I am merely a broker.
http://forum.xda-developers.com/showpost.php?p=28229671&postcount=189
The install method I used is similar to the linked OP method. First I deleted the apk from system/app and data/app. Then I used Dropbox to get it on my phone from my PC. You can use whatever method you would like. Then I used Root Explorer to move the patched apk to system/app AND data/app. I also renamed the apk to what it was named previously on my phone when I downloaded Google Wallet from the Play Store. Your phone may have a different name as well. I think as long as they are named the same in system/app and data/app you should be fine. That is how I have it. Then don't forget to change permissions once you move it. With Root Explorer you will long press to get the menu and once you select permissions you will check the first two radio buttons on the first row of three. Then uncheck the last two radio buttons on the second row. Then uncheck the last radio button on the last row. Those permissions should match with all the other apps listed. It will look like this: rw-r--r--
Step by step:
- Be rooted
- Uninstall Google Wallet in Play Store OR just delete Google Wallet from data/app
- Delete Google Wallet apk in system/data
- take the patched Google Wallet apk and rename to something closer to what was already listed under system/app that you previously deleted. It isn't terribly important that you rename it exactly.
- move that apk to system/app
- change permissions to read rw-r--r--
- copy that apk and move to data/app
- reboot
Good luck.
Here is a solid step-by-step list from fpineda101:
I had to reboot my phone to get it to work. Here re the steps I took
1. Write down apk name in system/app
2. Delete apk in system/app
3. Mount r/w in system/app using root Explorer
4. Copy apk to system/app and rename it
5. Set permissions. I actually used this which worked for me
x x x
x
x
6. Mount system/app as r/o
7. Delete apk in data/app
8. Copy apk from system/app with rename to data/app
9. Reboot and run the sucka
Don't take the update in Goggle Play. It still doesn't fix Google Wallet for the Evo 4G LTE. BUT if after you did this apk switch you took the update -- don't fret. Because we installed the apk in system/app all you have to do is go back into the Play Store and select uninstall. It will revert back to the version we manually installed.
Thank you guys for hitting the thanks button. And you're welcome. It's cool knowing this is helping and working. I hope I reach 100.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This first screen starts with the W in grey scale and animates to color after your phone has been read by the merchant:
This is the following screen if all is going well. Actually, even if it isn't. I got this screen when the grocery store register said "RFID payment system not setup blah blah."
This isn't intended for those with secure element bricks, right? It's just to activate it?
LiquidSolstice said:
This isn't intended for those with secure element bricks, right? It's just to activate it?
Click to expand...
Click to collapse
I do not believe this will help those with bricked secure elements. If you are in that boat give it a go and see what you can do.
utnick said:
I do not believe this will help those with bricked secure elements. If you are in that boat give it a go and see what you can do.
Click to expand...
Click to collapse
Oh, not at all. I don't have the phone yet. Just attempting to learn as much about it as possible. Random Google Wallet question; if I already have a Visa card connected to my Google Wallet account from a long time ago, would paying for items be as simple as just signing in and using it? In the thread you linked it appears that some cards require certain dependencies to be able to be used for Wallet.
LiquidSolstice said:
Oh, not at all. I don't have the phone yet. Just attempting to learn as much about it as possible. Random Google Wallet question; if I already have a Visa card connected to my Google Wallet account from a long time ago, would paying for items be as simple as just signing in and using it? In the thread you linked it appears that some cards require certain dependencies to be able to be used for Wallet.
Click to expand...
Click to collapse
Forgive me, Liquid, for being brief because I don't want to get off-topic. Your linked Visa I don't think will be usuable. There are a few options and those are the Google pre-paid card. Gift cards. And Citi MasterCard.
utnick said:
Forgive me, Liquid, for being brief because I don't want to get off-topic. Your linked Visa I don't think will be usuable. There are a few options and those are the Google pre-paid card. Gift cards. And Citi MasterCard.
Click to expand...
Click to collapse
Ahhh. I see. My apologies for the OT posts. It might not be as useful as I thought it would be, but I wholeheartedly thank you for making the fix available for us.
LiquidSolstice said:
Ahhh. I see. My apologies for the OT posts. It might not be as useful as I thought it would be, but I wholeheartedly thank you for making the fix available for us.
Click to expand...
Click to collapse
My pleasure. Searched high and low for a solid fix and finally found one in the One X forums from someone across the pond.
utnick said:
This is a link w/the method I used to install the apk (the linked OP method didn't work for me) and the Google Wallet app seems to work fine for me. It is showing me my unused $10, but it is too late in the evening for me to actually go test it. I will do my best to not be lazy tomorrow and find a store that has a NFC payment system.
Anyway, you can try the linked OP method or I would recommend mine.
OP
Region / Device / Root Patched Google Wallet APK (1.1-R67-v5) - Android Software - MoDaCo
apk
ROMraid by MoDaCo
The install method I used is similar to the linked OP method. I used Dropbox to get it on my phone from my PC. You can use whatever method you would like. Then I used Root Explorer to move the patched apk to system/app AND data/app. I also renamed the apk to what it was named previously on my phone when I downloaded Google Wallet from the Play Store. Your phone may have a different name as well. I think as long as they are named the same in system/app and data/app you should be fine. That is how I have it. Then don't forget to change permissions once you move it. With Root Explorer you will long press to get the menu and once you select permissions you will check the first two radio buttons on the first row of three. Then uncheck the last two radio buttons on the second row. Then uncheck the last radio button on the last row. Those permissions should match with all the other apps listed.
Good luck.
Click to expand...
Click to collapse
So permissions should be as follows?
x x
x
x x
Nvm
Permissions per op should be
x x
x
x
That's what all the system apps have
Sent via XDA Premium
fpineda101 said:
So permissions should be as follows?
x x
x
x x
Nvm
Permissions per op should be
x x
x
x
That's what all the system apps have. I will try to make a flashable zip in the morning
Sent via XDA Premium
Click to expand...
Click to collapse
Right on.
And permissions should read rw-r--r--
I had to reboot my phone to get it to work. Here re the steps I took
1. Write down apk name in system/app
2. Delete apk in system/app
3. Mount r/w in system/app using root Explorer
4. Copy apk to system/app and rename it
5. Set permissions. I actually used this which worked for me
x x x
x
x
6. Mount system/app as r/o
7. Delete apk in data/app
8. Copy apk from system/app with rename to data/app
9. Reboot and run the sucka
Thanks op for this find!
Sent via XDA Premium
Sweet. Glad to know it works for real. And thanks for a little reminder. Updated the OP.
Got another confirmation. Works!
Got my $10 pre-paid card ready to test later today.
Simply changing the file extension of the old version (to .bak) worked for me, didn't have to delete fwiw.
are unrooted users still at a disadvantage?
you gotta be rooted to have this work..
but those of us that arent rooted cant do this because it'll brick our nfc if we try to root right now. we still need to wait on an official ota fix?
fpineda101 said:
I had to reboot my phone to get it to work. Here re the steps I took
1. Write down apk name in system/app
2. Delete apk in system/app
3. Mount r/w in system/app using root Explorer
4. Copy apk to system/app and rename it
5. Set permissions. I actually used this which worked for me
x x x
x
x
6. Mount system/app as r/o
7. Delete apk in data/app
8. Copy apk from system/app with rename to data/app
9. Reboot and run the sucka
Thanks op for this find!
Sent via XDA Premium
Click to expand...
Click to collapse
I did it just like you said and it worked...but it then updated itself and wouldn't work. So I uninstalled the update and it works. Thanks to you and the op, it's too late now to go to McDonalds, but I'm going when I wake up.
thank you so much for this, i have been trying other methods for hours now and still couldnt get this to work. i had unrooted and now i re-rooted and was about to give up when i saw this post. thank you again
great find, thanks!
worked like a champ! right after installing, I got a notification of an update for Wallet & it was dated today 7/1...I updated thinking Google finally fixed Wallet for the ELTE, but nope, got unsupported device again. Uninstalled update, back working again. I'll be adding a flashable odex & deodex zips in my thread.
flashable zip
LiquidSolstice said:
This isn't intended for those with secure element bricks, right? It's just to activate it?
Click to expand...
Click to collapse
From the research I've done (see my thread linked in my signature) there is no recovery from a bricked secure element. That and the FAQ I put together (also in my signature) should get you started on what to know about this device
Also, OP is it okay with you if I add a link to this thread to my aforementioned threads?
There is a new update in the play Store dated July 1, do not take the update!
Sent via XDA Premium
TorxT3D said:
are unrooted users still at a disadvantage?
you gotta be rooted to have this work..
but those of us that arent rooted cant do this because it'll brick our nfc if we try to root right now. we still need to wait on an official ota fix?
Click to expand...
Click to collapse
Rooting does not brick the element per se.
The potential bricking of your secure element would only be an issue if you have data in the app and now can't get into the app to clear the data because of the "unsupported" error.
@untick-now that OMJ created zips it may not matter but you don't need to install the app in both /system/app and /data/app.
I looked at OMJ's zip and he has it only going to /system/app and I deleted the one I installed manually in /data/app, rebooted and it still worked.
You may also want to include a note in the OP about not doing any updates. Easy enough to uninstall an update but figured it was worth mentioning.
EDIT: @fpineda- TIE!
I followed the op's instructions & it worked like a charm! My previous balance showed up and I just bought a couple things at Wawa. Thanks!
Sent from my EVO using Xparent ICS Blue Tapatalk 2
Welcome.
For over a month, I look forward to the support, assistance from the manufacturer of the program Titanium Backup (as a licensed user) and until now I did not get any response from them. Therefore, I have a request to the honorable members of this forum, may have solved the problem of conservation of archives in Titanium Backup.
Now, it is the holder of the smartphone HTC One (you know, no SD card slot), and from the beginning there is a problem with the function called "Protected archive".
If you try to select it and other miscellaneous copy is returned in dyku message "Sorry, the operation failed".
HTC is ROOT, S-Off. I use a ROM called "ViperOne v1.1.1," but on other ROMs is the same problem.
Changing the backup directory in the preferences of the Titanium Backup does not work.
I tried the method described here:
http://forum.xda-developers.com/showthread.php?t=2059240
but it also does not give the result and does not change the situation.
Other features TitaniumBackup working properly, except for the protection of files: (((
Does anyone have any ideas, suggestions what to do to be able to protect (selected) copies of the program TitaniumBackupPRO?
I do not have the support to count - they do not write off: (((
greetings
q.
I have the same problem. I wanted to protect a couple old backups for safe keeping. All I get is operation failed. I did it before. But not on my Nexus 10. I will keep searching to see what I come up with. If I find it I will post back here.
Hi,
Same here with my HTC ONE X+ International.
I wrote to TitaniumTrack support here (http://www.titaniumtrack.com/support/product-support.html#usermessagea), you may also do it, this could help.
Concerning me, I went from an HTC DESIRE HD (32GB SDCARD) to an HTC ONE X+ (64GB internal memory).
When I edit my "platform.XML" file, In the "WRITE_EXTERNAL_STORAGE" section, the group definitions line refers to "<group gid="sdcard_rw"/>" instead of "<group gid="media_rw"/>".
I don't know if I should replace the "sdcard" by "media" or if I should add it. If yes, how to add it (syntax. Please write it here, I'll make a copy/paste).
I had to stop backing up my apps for now because of this problem... very annoying.
I may try others solutions, and I'll report them if it help.
tag : titanium backup protection, protéger cette sauvegarde, protect this backup.
Tried this... Didn't work
Tried what was recommended from the link below. Didn't work. Have the same issue with my htc one.
http://androidforums.com/sprint-gal...t-backups-feature-in-titanium-backup-pro.html
The worst thing is that the author/producer of Titanium Backup PRO totally not responsible for any e-mail asking for support.
The problem is from what I can see quite broad, applies to devices without SD card - and this is quite a lot.
We do not honest approach to their customers the application developer.
If someone manages to find a solution - we would ask for a response.
greetings
q
Hi
Did anyone find a solution, or even better an alternative that would make possible the availability to make severals backup of a same app with severals app data ???
Any clone of titanium ?
same problem since upgrading OS to 4.4
Since I upgraded my Note 3 from 4.3 to 4.4, I have not been able to use the "protect this backup" feature. Every time I try I get the error "Sorry, the operation failed". That feature worked fine before I upgraded the OS.
Most of the solutions to this problem seem to relate to the memory not being writable. That doesn't seem to be the case with me though. My backups are stored on my external SD card and I can create new backups just fine. I just can't protect them. And whether the backup was an old one made on 4.3 or a new one made on 4.4, the error message is the same.
I checked the file at /system/etc/permissions/platform.xml as suggested in this thread and elsewhere but the suggested additional group definitions are already there, so I couldn't add any. But again, since I can create new backups I don't think this is the root of the problem anyway.
I have contacted Titanium support and asked for suggestions. I'll report back here if I find a solution. Has anyone else been able to protect backups with TB after upgrading to Kitkat?
you can try with es browser to zip the archive you want to protect than you are good to go and you can also put it on your pc
xfive420 said:
I have contacted Titanium support and asked for suggestions. I'll report back here if I find a solution. Has anyone else been able to protect backups with TB after upgrading to Kitkat?
Click to expand...
Click to collapse
Just an update... Titanium support has been completely unresponsive after two attempts to contact them about this issue. The protect backup feature is still broken and they either don't know about the problem or are choosing to ignore it. Yes, you can manually zip or move backup files to an alternate location to preserve them, but that doesn't fix the feature.
Hi, wondering if anyone may have a suggestion. I'm not getting any action restoring a backed up User Dictionary with TB. It seems to create the backup but not restore it. Tried both data and app+data and reboots but still no action. HTC One rooted ARHD 71.1 (4.4.2)
Sent from my HTC One using XDA Premium 4 mobile app
xfive420 said:
Since I upgraded my Note 3 from 4.3 to 4.4, I have not been able to use the "protect this backup" feature. Every time I try I get the error "Sorry, the operation failed". That feature worked fine before I upgraded the OS.
Most of the solutions to this problem seem to relate to the memory not being writable. That doesn't seem to be the case with me though. My backups are stored on my external SD card and I can create new backups just fine. I just can't protect them. And whether the backup was an old one made on 4.3 or a new one made on 4.4, the error message is the same.
I checked the file at /system/etc/permissions/platform.xml as suggested in this thread and elsewhere but the suggested additional group definitions are already there, so I couldn't add any. But again, since I can create new backups I don't think this is the root of the problem anyway.
I have contacted Titanium support and asked for suggestions. I'll report back here if I find a solution. Has anyone else been able to protect backups with TB after upgrading to Kitkat?
Click to expand...
Click to collapse
Not sure if this will help anyone but it worked for me... I have a Galaxy S4 i9505... backup path was set to storage/extSdCard/ and could not protect backups... out of chance I decided to allow it to detect where any backups may be... well it came up with this funky path... mnt/media_rw/extSdCard... I set it to that and can now protect backups
cdzo72 said:
Not sure if this will help anyone but it worked for me... I have a Galaxy S4 i9505... backup path was set to storage/extSdCard/ and could not protect backups... out of chance I decided to allow it to detect where any backups may be... well it came up with this funky path... mnt/media_rw/extSdCard... I set it to that and can now protect backups
Click to expand...
Click to collapse
Glad you were able to fix the issue on the S4. I was optimistic it would work on my Note 3 but when I click "Detect" it shows me /storage/extSdCard/, I tried to manually browse to /mnt/media_rw/extSdCard but once I descend into the media_rw directory I get the error message "This folder cannot be accessed". I tried selecting /mnt/extSdCard (yet another path to the same place) but protecting backups still fails. So unfortunately the workaround didn't work for me, but hopefully it will fix this issue for someone else. Thanks for the tip.
cdzo72 said:
Not sure if this will help anyone but it worked for me... I have a Galaxy S4 i9505... backup path was set to storage/extSdCard/ and could not protect backups... out of chance I decided to allow it to detect where any backups may be... well it came up with this funky path... mnt/media_rw/extSdCard... I set it to that and can now protect backups
Click to expand...
Click to collapse
Hi there.
@cdzo72, many thanks for tips, I had some hope when reading you, but this was unsuccessful for me and my HTC ONE X+ .
I did try all those paths :
/storage/sdcard0/TitaniumBackup
/storage/emulated/legacy/TitaniumBackup
/mnt/sdcard/TitaniumBackup
/sdcard/TitaniumBackup
/storage/emulated/0/
/mnt/usbdisk/TitaniumBackup
Anyway, thank you so much.
After adding:
Code:
<group gid="media_rw" />
to WRITE_EXTERNAL_STORAGE in /system/etc/permissions/platform.xml I switched backup location in Titanium Backup from /storage/extSdCard/... to /mnt/media_rw/extSdCard/... and I'm able to protect backups now
Galaxy S5 SM-G900F, rooted stock 4.4.2
xfive420 said:
Glad you were able to fix the issue on the S4. I was optimistic it would work on my Note 3 but when I click "Detect" it shows me /storage/extSdCard/, I tried to manually browse to /mnt/media_rw/extSdCard but once I descend into the media_rw directory I get the error message "This folder cannot be accessed". I tried selecting /mnt/extSdCard (yet another path to the same place) but protecting backups still fails. So unfortunately the workaround didn't work for me, but hopefully it will fix this issue for someone else. Thanks for the tip.
Click to expand...
Click to collapse
Try using a file explorer (I prefer solid explorer) to change the permissions on the /mnt/media_rw/ directory. I changed mine to rw for all and then titanium could access the folder and protect backups there.
EDIT: The permissions wouldn't stick so it needed an init.d script.
DarkStarr said:
Try using a file explorer (I prefer solid explorer) to change the permissions on the /mnt/media_rw/ directory. I changed mine to rw for all and then titanium could access the folder and protect backups there.
EDIT: The permissions wouldn't stick so it needed an init.d script.
Click to expand...
Click to collapse
Thanks for the solution! Adding RWX to group permissions did the trick for me, but as you said in your edit the permissions don't stick. After a reboot they are reset and TB can no longer see the backup directory. I suppose an init.d script or maybe a tasker task could address this, but I feel writing a patch for the default folder permissions is more trouble than it's worth just to be able to protect backups again.
After I upgraded to Kitkat, some other apps had issues with writing to the external SD card. It seems they worked around the issue by writing to a specific folder with a name similar to /storage/externalSdCard/Android/data/com...... I tried that solution with TB but still couldn't get the backup protection feature to work.
I hope Titanium fixes or at least addresses this issue. I still have not received a response from their support team, and I'm not holding my breath.
xfive420 said:
Thanks for the solution! Adding RWX to group permissions did the trick for me, but as you said in your edit the permissions don't stick. After a reboot they are reset and TB can no longer see the backup directory. I suppose an init.d script or maybe a tasker task could address this, but I feel writing a patch for the default folder permissions is more trouble than it's worth just to be able to protect backups again.
After I upgraded to Kitkat, some other apps had issues with writing to the external SD card. It seems they worked around the issue by writing to a specific folder with a name similar to /storage/externalSdCard/Android/data/com...... I tried that solution with TB but still couldn't get the backup protection feature to work.
I hope Titanium fixes or at least addresses this issue. I still have not received a response from their support team, and I'm not holding my breath.
Click to expand...
Click to collapse
The easy solution here would be to download ROM Toolbox Lite and go to Scripter then import the script I will attach to this post then tell it to set it on boot. It will take a few seconds after boot to run but it worked fine for me. I had too many ROM issues though so I rolled back to 4.3.
I had to put it in an archive since it has no extension and XDA wouldn't accept it so just extract it and follow the previous instructions.
Your script admittedly allowed to give rights to the directory "/ mnt / media_rw", but despite this still does not solve the problem of copy protections on the device running HTC One ViperOne 6.2.1 (Android 4.4.2, Sense 6.0)
So I set TitaniumBackupPro:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
greetings
q.
qriozum said:
Your script admittedly allowed to give rights to the directory "/ mnt / media_rw", but despite this still does not solve the problem of copy protections on the device running HTC One ViperOne 6.2.1 (Android 4.4.2, Sense 6.0)
So I set TitaniumBackupPro:
[SNIP]
greetings
q.
Click to expand...
Click to collapse
If you look in your image TB is using the wrong directory to reach the backups. It must go through /mnt/media_rw in order to be able to protect backups. Even then another folder may need to be given proper permissions if you are not using an SD card. I haven't tried since I put all my backups on my SD.
In the directory "/MNT/Media_RW" is just one subdirectory called "USB" and it has nothing, is empty.
In the preferences TBP tried to change the directory to copy "/storage/emulated/legacy" and "storage/sdcard0" - but it did not bring any result.
I must mention that the subdirectory "sdcard0" symlinks in storage only and not the physical directory.
In the root directory of the device is a symlink to "sdcard".
But it is known that the symlink is impossible Aug. set of rights and attributes.
---------EDIT:
Curiosity, from the TBP can not create directory "/ mnt" or in "/ mnt / media_rw".
Please look at the screenshots, in theory, rights are granted:
Some users don't always take a look at other threads since we have infinitybillion forums for the HTC ONE... Thought I would share a boot animation I created specifically for our devices. First, a preview:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you like it, click the link to go to the main thread.
http://forum.xda-developers.com/showthread.php?t=2357926
Crackanug said:
Some users don't always take a look at other threads since we have infinitybillion forums for the HTC ONE... Thought I would share a boot animation I created specifically for our devices. First, a preview:
If you like it, click the link to go to the main thread.
http://forum.xda-developers.com/showthread.php?t=2357926
Click to expand...
Click to collapse
Hi, is it possible to make request for qmg file or boot animation.zip to be used in samsung s4 w/o the htc one word and the final screen instead of one change to my name? thank you!!:victory:fingers-crossed:
When I try this, the T-Mobile animation keeps coming back...I have only been successful with a custome kernel, which causes other issues...is there any way to flash this on a rooted stock HTC One? Even if I try to manually install it, it doesn't work.
Thanks,
mm0
muzicman0 said:
When I try this, the T-Mobile animation keeps coming back...I have only been successful with a custome kernel, which causes other issues...is there any way to flash this on a rooted stock HTC One? Even if I try to manually install it, it doesn't work.
Thanks,
mm0
Click to expand...
Click to collapse
My one is pretty much stock as well. I install it manually by copying the files to the correct directories and changing their permissions. After that I edit the ".xml" file and point it to use whatever boot animation I want. All you have to do is make sure the naming is correct during your edit. Save the file and reboot.
If that doesn't help, can you be a little more specific on the steps you took to install it manually?
I obviously missed the xml file that needs edited... where is it located?
muzicman0 said:
I obviously missed the xml file that needs edited... where is it located?
Click to expand...
Click to collapse
The full set of directions are near the end of the first post in the link to the boot animation. It's a little more detailed, but all you need to do is navigate to the directory "/system/customize/CID" and find the appropriate .xml file for your boots. then add the lines or information I have written out in the main thread. Hope that helps. :good:
Crackanug said:
The full set of directions are near the end of the first post in the link to the boot animation. It's a little more detailed, but all you need to do is navigate to the directory "/system/customize/CID" and find the appropriate .xml file for your boots. then add the lines or information I have written out in the main thread. Hope that helps. :good:
Click to expand...
Click to collapse
Even when I edit the xml file, that comes back on boot with the original info. It looks like I will have to use a custom kernel, or something...but the only custom kernel I have found has issues with the touch screen. Oh well. I guess I will wait until T-Mobile releases 4.2, so I can have more options.
muzicman0 said:
Even when I edit the xml file, that comes back on boot with the original info. It looks like I will have to use a custom kernel, or something...but the only custom kernel I have found has issues with the touch screen. Oh well. I guess I will wait until T-Mobile releases 4.2, so I can have more options.
Click to expand...
Click to collapse
Upload a copy of the xml file you have. I'll take a look at it and see if I can get something working for you.
Crackanug said:
Upload a copy of the xml file you have. I'll take a look at it and see if I can get something working for you.
Click to expand...
Click to collapse
It's not a matter of having the XML wrong...I save the changes I make, and even close out, and reload it to verify they are there, but as soon as I reboot the phone, it has reverted back to what it was before I made the change.
muzicman0 said:
It's not a matter of having the XML wrong...I save the changes I make, and even close out, and reload it to verify they are there, but as soon as I reboot the phone, it has reverted back to what it was before I made the change.
Click to expand...
Click to collapse
I understood. I was wanting you to upload two copies of the xml file (one already edited and one stock or like you have now) and I will package it into a flashable zip. That way you can flash it from recovery and it should stick. Plus I will make a stock flashable zip so you can go back to what it was if you want.
Crackanug said:
I understood. I was wanting you to upload two copies of the xml file (one already edited and one stock or like you have now) and I will package it into a flashable zip. That way you can flash it from recovery and it should stick. Plus I will make a stock flashable zip so you can go back to what it was if you want.
Click to expand...
Click to collapse
OK, cool...I will get that ASAP. Thanks.
Here are the files. I appreciate your time! Both the stock, and the edited file are in the .zip file. Thanks.
mm0
muzicman0 said:
Here are the files. I appreciate your time! Both the stock, and the edited file are in the .zip file. Thanks.
mm0
Click to expand...
Click to collapse
Here you go, try flashing the edited zip xml zip file from recovery and see if that works. If it does not, let me know. I included the stock xml zip just in case, but make sure you got some type of backup to fall back on in case something has gotten buggered.
Crackanug said:
Here you go, try flashing the edited zip xml zip file from recovery and see if that works. If it does not, let me know. I included the stock xml zip just in case, but make sure you got some type of backup to fall back on in case something has gotten buggered.
Click to expand...
Click to collapse
that works! Thanks!
I just got this working! Great job!
Sent from my HTC One using xda app-developers app
TheFuzz said:
I just got this working! Great job!
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Glad you like it!
Crackanug said:
Glad you like it!
Click to expand...
Click to collapse
I am on the AT&T version of HTC one. have viperone rom installed and after i flash the .zip it makes my power button stop working. Is there any other way to make it work? Thx in advance
w8 let me try and send you my xml
sorry can't find them on my pc... i can on my phone ES explorer but not on pc
down animation
Crackanug said:
Here you go, try flashing the edited zip xml zip file from recovery and see if that works. If it does not, let me know. I included the stock xml zip just in case, but make sure you got some type of backup to fall back on in case something has gotten buggered.
Click to expand...
Click to collapse
that worked. can you fix the xml file for the down animation to be changed too ?
Thanks nick
Mmm, beatiful, downloading!
Very good! To how to use