Related
So last night I received the official OTA update on my phone. I'm not really ready for it (mainly because Lockpicker doesn't work on 2.2 yet).
Anyway, I digress. Anyone know the physical location of the update.zip file is downloaded to? The one on the root of my sd card is way too small to be the right one. I've searched through the directories with Astro File Manager and came up empty. It's on there though. I just can't seem to find it.
I just want to move the file for future use. The dialog box to update is already getting on my nerves and the day just started.
On a side note, is it safe to assume my update will fail with any changes I have made to the system folders? I haven't done a lot but I know I have done a few things. I may end up just going the RUU route when I'm ready. I think I've just renamed some bogus apps (City ID, etc.), updated the kernel to allow wireless tethering, installed boot animations with sound, and updated the splash screen after enabling S-OFF. I'm going to try and restore as much as I can to stock up ultimately will probably forgotten something I did. The boot animations and splash screen are probably not part of the update checksum, right?
I believe it's in /cache. I'm not 100% sure though, never actually had to check, just what i've heard. Try using root explorer and checking.
tcberg2010 said:
I believe it's in /cache. I'm not 100% sure though, never actually had to check, just what i've heard. Try using root explorer and checking.
Click to expand...
Click to collapse
Is Root Explorer really better than ASTRO File Manager? Would it allow me to access this directory? ASTRO File Manager didn't see anything due to rights probably. Root Explorer nice but I'm not sure if it's worth the cash. Worth it?
I was able to pull the via adb by mounting the system.
Thanks for the help. The location was dead on.
Any ideas of what files I can delete other than the .zip file? I deleted the zip file but still am getting the update dialog.
Out of curiosity, does anyone know that update.zip can be used on any Incredible, or is there some sort of authentication process?
Any Droid Incredible that is at the proper level can use the update. Same as getting it Over The Air.
Does anyone know what files I should delete in the /cache folder to get rid of whatever files the OTA pushed? It tried to update but failed and am trying to get rid of all traces of it.
Thanks.
8e5ad8d6ea2d.OTA_IncredibleC_Verizon_WWE_3.21.605.1_1.22.605.2_release_sign.zip
What folder is that in?
zmanzbo said:
What folder is that in?
Click to expand...
Click to collapse
It's in /cache, as stated in Post #2 of this thread. You can access it with Root Explorer, which is cool, or via adb in shell by mounting the system folder.
So I feel like a noob, but here goes. Going into restore from recovery shows to backups I created. I can not find these folders from any explorer. I've checked all /clockworkmod/backup folders under /storage/ and they are all empty. I also tried searching for boot.img and gave up after a few mins, I also searched various responses on the net.. So where else could the backup folders be, i'm running a 4.2.1 rom.
Thanks
voidstab said:
So I feel like a noob, but here goes. Going into restore from recovery shows to backups I created. I can not find these folders from any explorer. I've checked all /clockworkmod/backup folders under /storage/ and they are all empty. I also tried searching for boot.img and gave up after a few mins, I also searched various responses on the net.. So where else could the backup folders be, i'm running a 4.2.1 rom.
Thanks
Click to expand...
Click to collapse
Should be under Storage/SDcard0
BWolf56 said:
Should be under Storage/SDcard0
Click to expand...
Click to collapse
I'm using v6.0.2.3 could it be a version issue and the backups are not actually created...
Recovery still shows two folders and shows the location as /sdcard/clockworkmod/backup/ and ES file explorer shows that folder as empty.
So I don't think it is working. I let a search from root finish for 1970-03-02.03.38.38 which is showing in recovery and it found nothing. I'm curious why recovery is showing these folders, does it keep a list of backups in a file somewhere.
Figured it out. Right in ROM manager it states, In Android 4.2 backups are placed in secure directory, inaccessible to other apps.
So anyways..
*edit*
If anybody else happens across this, if you enable root explorer the secure folder where the backups are can be accessed.
In my defense I didn't have rom manager installed...
voidstab said:
Figured it out. Right in ROM manager it states, In Android 4.2 backups are placed in secure directory, inaccessible to other apps.
So anyways..
*edit*
If anybody else happens across this, if you enable root explorer the secure folder where the backups are can be accessed.
In my defense I didn't have rom manager installed...
Click to expand...
Click to collapse
Sorry, I took for granted that you knew more about root explorer, my bad.
As for ROM Manager, please unistall it. It will only cause problems.
use "ES Filexplorer" and enable hidden files in the settings menu. Then go to the root folder in ES and look for a folder called mnt and you will find it in there
I know its an old thread but took me a while to figure out.
muks11 said:
use "ES Filexplorer" and enable hidden files in the settings menu. Then go to the root folder in ES and look for a folder called mnt and you will find it in there
I know its an old thread but took me a while to figure out.
Click to expand...
Click to collapse
I wanted to delete the folder from root browser, apparently it deleted, but the folder remained there. So what I did is quite simply, open up a terminal, su, then rm -fr /mnt/whereclockworkfolderis, and that's it.
You can find here:
\storage\emulates\clockworkmod\backup
voidstab said:
I'm using v6.0.2.3 could it be a version issue and the backups are not actually created...
Recovery still shows two folders and shows the location as /sdcard/clockworkmod/backup/ and ES file explorer shows that folder as empty.
Click to expand...
Click to collapse
Doing a search w/ Root Explorer I finally found it here on my Galaxy Nexus on VZW (toro) running CM 10.1:
/mnt/shell/emulated/clockworkmod/backup
Plesk8 said:
Doing a search w/ Root Explorer I finally found it here on my Galaxy Nexus on VZW (toro) running CM 10.1:
/mnt/shell/emulated/clockworkmod/backup
Click to expand...
Click to collapse
Yes. With ES Explorer and turning on "Root Explorer" in the Tools menu in Settings, I was able to see /mnt/shell/emulated/clockworkmod/backup/<mybackup>
I just backed up my AT&T Galaxy Note 2 running CM 10.1.3 Android 4.2.2 and was unable to find it until I saw this thread.
Thanks,
Dennis
dperique said:
Yes. With ES Explorer and turning on "Root Explorer" in the Tools menu in Settings, I was able to see /mnt/shell/emulated/clockworkmod/backup/<mybackup>
I just backed up my AT&T Galaxy Note 2 running CM 10.1.3 Android 4.2.2 and was unable to find it until I saw this thread.
Thanks,
Dennis
Click to expand...
Click to collapse
mee to!
how to put back the backup to phone?
someone knows how to put this backup back to the phone? because it is not a .zip
it is like:
aaaa.tar.a
bbbb.zip
cccc.log
dddd.md5
eeee.img
so when I whant to put it back with clockworkmood - wich file should I select and it will knows to reupload ALL?
thx,
Laurentiu
thx
Plesk8 said:
Doing a search w/ Root Explorer I finally found it here on my Galaxy Nexus on VZW (toro) running CM 10.1:
/mnt/shell/emulated/clockworkmod/backup
Click to expand...
Click to collapse
thank you very much, i find i want.:good:
Date of file creation?
voidstab said:
So I don't think it is working. I let a search from root finish for 1970-03-02.03.38.38 which is showing in recovery and it found nothing. I'm curious why recovery is showing these folders, does it keep a list of backups in a file somewhere.
Click to expand...
Click to collapse
Now this one just makes me wonder. I was cleaning out some files and of course I ran across this one. I have, actually two backup files. Im deleting the older, however I noticed something odd and pulled up properties of the file. I have no idea as to why it says the file was created in 1969 or as it says 1970 in the file. Is this some possible issue?
Casper Young said:
I have no idea as to why it says the file was created in 1969 or as it says 1970 in the file. Is this some possible issue?
Click to expand...
Click to collapse
No. When you reset a phone, it doesn't have the correct time. it's like replacing the battery of your bed alarm clock. So when you create a file, it will use this date.
Unrational!
nehc_rm said:
No. When you reset a phone, it doesn't have the correct time. it's like replacing the battery of your bed alarm clock. So when you create a file, it will use this date.
Click to expand...
Click to collapse
Well that's even more odd. You think that if it didn't know the correct time or date, it would probably reset to 2000. But 1969, 1970? Weren't PCs way back then, so where's this very odd number coming from? A Grand-Father Clock? There was a period that many PCs weren't ready for when the time came. The turn of the century, when 1999 went to 2000, it was a numerical difficulty with Computers. Kind of makes what you are saying difficult to believe shall I say. It's a really odd number to reset to.
Casper Young said:
Well that's even more odd. You think that if it didn't know the correct time or date, it would probably reset to 2000. But 1969, 1970? Weren't PCs way back then, so where's this very odd number coming from? A Grand-Father Clock?
Click to expand...
Click to collapse
Early computers were made after the WWII, mostly used by government. It's not an random date/time. Every computer use unix time https://en.wikipedia.org/wiki/Unix_time
U.S.S.N. Pegasus RCVN
Capitans log, Stardate 72221.6. We was flying in the sector containing the XDA Neutral zone when suddenly killer confectionaries were all about. Abandon Shi.... Ker-Peeewf! Q? Where did you come from?
Is there anyway I can enable full write privileges on my external SD Card without rooting my M8?
I am currently running stock software to see how I get on with it, and so far this is the only thing that is stopping me moving to non-rooted full time?
Are there any workarounds that I don't know about?
Cheers
Stewart
Nope. No dice without root.
berndblb said:
Nope. No dice without root.
Click to expand...
Click to collapse
Ah well, such is life, Im sure I will get used to it!
Use the HTC File Manager that comes with the new 2.22 update. Read/Write access was the first thing I checked, and it works flawlessly; you can use it to cut/paste/delete what you please.
I also checked if ES File manager can do these operations as well after the update, but it seems unaffected.
So, happy deleting/moving files and folders with HTC File Manager...
Cheers
shirreer said:
Use the HTC File Manager that comes with the new 2.22 update. Read/Write access was the first thing I checked, and it works flawlessly; you can use it to cut/paste/delete what you please.
I also checked if ES File manager can do these operations as well after the update, but it seems unaffected.
So, happy deleting/moving files and folders with HTC File Manager...
Cheers
Click to expand...
Click to collapse
I haven't got the update yet, but I look forward to getting it so I can use this functionality!!
Cheers
Stewart
shirreer said:
Use the HTC File Manager that comes with the new 2.22 update. Read/Write access was the first thing I checked, and it works flawlessly; you can use it to cut/paste/delete what you please.
I also checked if ES File manager can do these operations as well after the update, but it seems unaffected.
So, happy deleting/moving files and folders with HTC File Manager...
Cheers
Click to expand...
Click to collapse
The stock file manager is a system app, so it has permissions to read/write anywhere.
ES File Explorer found a way around the new permissions by hijacking the media server process. That is clearly circumventing what Google intended and I don't expect them to allow it for long...
It's hardest for the 3rd party file explorers. They are mostly useless with this new change until Google allows the user to decide which apps get permission for what. As it should be....
How do you enable full write to SD card on rooted T-mobile One M8?
My T705 is running very nicely on KK and I'm not really too bothered about updating it to Lollipop. So is there a way to get rid of the Update icon in the notification bar?
Thanks
If you are rooted you should not get the notification.
There is a guide but it is for the S3 phone, it might give you a guide.
http://forum.xda-developers.com/showthread.php?t=1856632
John.
I think that means you've already downloaded the update. From memory you should have a folder named FOTA on your internal storage. Delete that to get rid of the notification.
However it would be better to actually move it to your external sd card for future use.
Also I'm sure you can disable automatic updates in settings.
The only FOTA files I could find were these, please see image attached.
schrodinger56 said:
The only FOTA files I could find were these, please see image attached.
Click to expand...
Click to collapse
Should be a normal folder. If it's not there then you probably don't have the update downloaded yet.
ashyx said:
Should be a normal folder. If it's not there then you probably don't have the update downloaded yet.
Click to expand...
Click to collapse
According to the screens (see images) the update has been downloaded.
It could be in the root of your internal storage. You may need a file manager such as es explorer that can show root folders.
ashyx said:
It could be in the root of your internal storage. You may need a file manager such as es explorer that can show root folders.
Click to expand...
Click to collapse
I've tried a couple of file manager apps but all I can find called FOTA is what's shown above.
No they are just apps.
It must be there somewhere. It is most certainly on your internal storage.
It may not necessarily be in a folder called fota. That is coming from memory. Ota's are usually zips, but could be named anthing.
It'll just be one large file somewhere.
ashyx said:
No they are just apps.
It must be there somewhere. It is most certainly on your internal storage.
It may not necessarily be in a folder called fota. That is coming from memory. Ota's are usually zips, but could be named anything.
It'll just be one large file somewhere.
Click to expand...
Click to collapse
If it's there, which it is, it's keeping itself very well hidden. The various Root File Explorers I've used just cannot find it!!
Looks like I'll just have to put up with it.
Can an file manger with a large file finder not find it for you, if the file is 800mb+ it should show up.
Try File Manager HD
John.
Tinderbox (UK) said:
Can an file manger with a large file finder not find it for you, if the file is 800mb+ it should show up.
Try File Manager HD
John.
Click to expand...
Click to collapse
Tried that app i.e. File Manager HD but still no luck. I've tried searching by size, name etc but nothing shows up.
Have you looked in Android/data? Both internal and ex sdcard.
I eventually found it, don't ask how!! I moved it to the ext SD card and now the notification has gone. Ironically it wouldn't have installed anyway because my T705 is rooted and OTAs don't install on a rooted device.
Thanks to all.
schrodinger56 said:
I eventually found it, don't ask how!! I moved it to the ext SD card and now the notification has gone. Ironically it wouldn't have installed anyway because my T705 is rooted and OTAs don't install on a rooted device.
Thanks to all.
Click to expand...
Click to collapse
Where was it and what's it called?
ashyx said:
Where was it and what's it called?
Click to expand...
Click to collapse
I think it was just luck that I came across it. It was in a Folder called Data in another folder called FOTA. I moved it to my external SD card where it now resides.
And the name of the file?
It was called update.zip
I just flashed developer preview 4 and rooted but I cannot get the build.prop edited. I've tried multiple apps but always says error saving. Had anyone gotten the build.prop edited?
lawtalking said:
I just flashed developer preview 4 and rooted but I cannot get the build.prop edited. I've tried multiple apps but always says error saving. Had anyone gotten the build.prop edited?
Click to expand...
Click to collapse
I have successfully edited the build prop by using root explorer. Make sure you are rooted and allow super su to use root explorer.
You will will need to hold down on build.prop to highlight it, then go to menu and select, open in text editor.
lucky_strike33 said:
I have successfully edited the build prop by using root explorer. Make sure you are rooted and allow super su to use root explorer.
You will will need to hold down on build.prop to highlight it, then go to menu and select, open in text editor.
Click to expand...
Click to collapse
I am rooted and I did give permission to root explorer. I am able to mount the other files and folders as read write but it will not let me Mount the system as read write. I've tried multiple apps it all says error saving.
lawtalking said:
I am rooted and I did give permission to root explorer. I am able to mount the other files and folders as read write but it will not let me Mount the system as read write. I've tried multiple apps it all says error saving.
Click to expand...
Click to collapse
What file explorer are you using. Fx works fine.
toknitup420 said:
What file explorer are you using. Fx works fine.
Click to expand...
Click to collapse
I've tried multiple. Its not the file explorer. I've tried re flashing the factory image but still will not let me edit any system folders or files. I think that maybe it is systemless root. Not sure how I got systemless root or if it is possible to get regular root. Is there a setting is Supersu?
lawtalking said:
I've tried multiple. Its not the file explorer. I've tried re flashing the factory image but still will not let me edit any system folders or files. I think that maybe it is systemless root. Not sure how I got systemless root or if it is possible to get regular root. Is there a setting is Supersu?
Click to expand...
Click to collapse
You may have a SUPER.img - i just learned about this myself - its a combined image containing /system - /vendor & /Product - it looks like it is similar to Systemless root or system as root... idk they are weird but i do think its possible to modify build.rpop, but it may require a PC.... Im looking for a way to edit build.prop myself and learning all this now.