I'm hoping someone here can answer this easily and maybe provide a quick, easy fix.
When I do a nandroid backup from either cwm or twrp it saves the backup folder as the date (this is standard) but on this S3 its time stamp is always either 1970 Jan 1 or 1979 Dec 31. Why would this be? My date and time is fine after boot up and on all past phones my backups always had the proper current time within my recovery.
Where does the phone/recovery get this info? Ie, like some sort of bios clock of a pc.
Anyone know why this is happening and how I can fix, if at all?
Thanks
Sent from my SGH-I747M using xda premium
There is no fix as of yet but you can rename them to the proper date if you like. Only use - and . when renaming. No spaces or other characters. eg: [email protected]#$, etc.
Renaming on the latest cwm 6+ will result in falling to pass the md5 check and won't let you flash it.
Sent from my SGH-I747M using xda premium
equlizer said:
There is no fix as of yet but you can rename them to the proper date if you like. Only use - and . when renaming. No spaces or other characters. eg: [email protected]#$, etc.
Click to expand...
Click to collapse
Yeah.I've been renaming for a while now but was still curious why this was happening and if there was a fix.
I'm using TWRP now so no issues with renaming and reflashing backups.
Is this a known issue with just the S3?
Sent from my SGH-I747M using xda premium
equlizer said:
There is no fix as of yet but you can rename them to the proper date if you like. Only use - and . when renaming. No spaces or other characters. eg: [email protected]#$, etc.
Click to expand...
Click to collapse
0u7br3ak said:
Renaming on the latest cwm 6+ will result in falling to pass the md5 check and won't let you flash it.
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
So which one is correct, can it be renamed or not? Because I renamed mine already. Will I never be able to flash them? Or should I just make sure there are no spaces? I've plenty of nandroids in the past that wouldn't flash, so this may by why. But I may have renamed them with spaces in the title.
equlizer said:
There is no fix as of yet but you can rename them to the proper date if you like. Only use - and . when renaming. No spaces or other characters. eg: [email protected]#$, etc.
Click to expand...
Click to collapse
Since the 2.3.0 update TWRP now supports spaces in file names.
Related
I was just wondering if it was possible to rename the backups in root explorer without messing up the md5 sum? I did it a while ago with no issues, but recently did it again, and had md5 mismatch errors. Not sure if it was the rename, or something else? I would like to get some order to my backups, so I know what it's what. Thanks for any info.
Sent from my ADR6300
countryfolk07 said:
I was just wondering if it was possible to rename the backups in root explorer without messing up the md5 sum? I did it a while ago with no issues, but recently did it again, and had md5 mismatch errors. Not sure if it was the rename, or something else? I would like to get some order to my backups, so I know what it's what. Thanks for any info.
Sent from my ADR6300
Click to expand...
Click to collapse
I always rename all my backup with no issue. I use the date and what Rom it is to name them. I've done this with a few diff CWM versions and have never had an issue restoring them.
I just use rom manager to rename, never tried through a file program
Inc
Thanks guys! Not sure what happened last time.
Sent from my ADR6300
Yep you can rename with a file manager, just make sure there are no spaces in the name of your backup.
countryfolk07 said:
Thanks guys! Not sure what happened last time.
Sent from my ADR6300
Click to expand...
Click to collapse
Check for inadvertant spaces in the new name. That WILL cause an issue. Look after any punctuation you might have used.
Sent from my ADR6300 using xda premium
trickster2369 said:
Check for inadvertant spaces in the new name. That WILL cause an issue. Look after any punctuation you might have used.
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
I have a feeling that's what I did. Thanks.
Sent from my ADR6300
Why not use Rom Manager, under Manage and Restore Backups?
I have a few Nandroid backups and I was wondering if there was a way to see what ROM it's from without actually restoring from it.
thatlaoboi said:
I have a few Nandroid backups and I was wondering if there was a way to see what ROM it's from without actually restoring from it.
Click to expand...
Click to collapse
Unfortunately there's not that I know of, I always label nandroid as soon as I make them to keep from forgetting. If you do start renaming them, make sure there are no spaces in the name otherwise you will get an md5 mismatch error (assuming you are on cwm, TWRP does not have this problem)
You just have to rename your nandroid backups on your computer. It's in your sd folder when you connect your phone under clockworkmod. I have 3 backups, and I name them after the rom /theme that they are.
Sent from my Galaxy SII T-mobile using xda premium
yoft1 said:
Unfortunately there's not that I know of, I always label nandroid as soon as I make them to keep from forgetting. If you do start renaming them, make sure there are no spaces in the name otherwise you will get an md5 mismatch error (assuming you are on cwm, TWRP does not have this problem)
Click to expand...
Click to collapse
I am starting to do that, but like the ones from when I began flashing (about a month ago) I have like 5 nandroid right now. I think thats a bit excessive considering that I only used AOKP, Jugg and Stock. And thanks for the heads up about the md5 thingy. I don't rename them on my computer, I upload to box.net and add it in the description. That way I can keep my cluttered computer a bit cleaner. And I have 50GB so it doesn't really matter.
Use ROM Manager for backups as it gives you the option of naming the backup before hand. Personally I'm very specific on the names. I include the ROM, date, and other things like any mods or stuff like that
Sent from my SGH-T989 using XDA
Goofy317 said:
Use ROM Manager for backups as it gives you the option of naming the backup before hand. Personally I'm very specific on the names. I include the ROM, date, and other things like any mods or stuff like that
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
I use rom manager also... So it's safe when backing up to add the name of the rom at the end of the date that it automatically designates for us? Thanks
Sent from my SGH-T989 using xda premium
suaverc118 said:
I use rom manager also... So it's safe when backing up to add the name of the rom at the end of the date that it automatically designates for us? Thanks
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Yep. Name it whatever you wish
Sent from my SGH-T989 using XDA
I can't flash nearly half my zips, and after doing some googling I found out that you have to now replace a file within the zip in order to be useable within twrp. Not a big deal.... only I can't save the dang file without appending some sort of file association. txt, zip, img, bin,mp3 etc...... So how do I exactly save this thing so I can overwrite the original?
I normally frown on double posts, but I can't find this information anywhere. Any information on how to replace an update-binary will prevent me from throwing my phone at a wall. I just want to flash my mason kernel
Sent from my PC36100 using xda premium
Naturesretard said:
I normally frown on double posts, but I can't find this information anywhere. Any information on how to replace an update-binary will prevent me from throwing my phone at a wall. I just want to flash my mason kernel
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
If u having problem with ur recovery flashing I wouldn't care replacing binaries why u don't use another recovery ?
What about smelkus. That could be the faster and the better option to solve ur issue.
Sent from my Nexus 7 using Tapatalk 2
Okay what the problem is that with the 2.3x recovery software they use the jellybean update-binary. To fix this you unzip any zip file that works. Copy that binary over the one that wont flash check updater script to make sure you don't have to change any of the script. Then rezip it all back and it will work fine.
I would suggest changing your recovery also. It is quicker than redoing all the zips. If you want to stay with twrp 2.2.2.0 will work with all your zips.
Oh just double read your post. I use es file explorer on my phone to do the zip fix. I am guessing that you are on a Windows machine. I forget about that sometimes. Been running a Linux box for couple years now.
Sent from my PC36100 using xda app-developers app
a lucid explanation here
If you use 7-zip, simply put the file on windows somewhere and drop it into the right directory. Note that update-script changes to updater-script and the parsing is Amend not Edigy anymore so scripts will change.
Hey, guys. I'm looking for some help here. I've been having some trouble with a few recent ROMs. I try to do a full wipe and do a fresh install of the new ROM, but I get an error saying something about being unable to read the lost + found file. I think it was deleted somehow because I can't find it. Does anyone know how to get it back? Can I possibly just reinstall a recovery or something? I don't actually know where the file even comes from to begin with.
Bump. Really needing some help.
Have you tried restoring a nandroid back up?? (If any)
At least you can start your search for a solution with a working phone.
Sent from my Nexus 7 using xda app-developers app
Mojar7070 said:
Have you tried restoring a nandroid back up?? (If any)
At least you can start your search for a solution with a working phone.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I don't have a recent Nandroid backup at the moment. My last one would take me straight from AOSP 4.3.1 all the way back down to TW 4.1.2 and I just don't like that idea. It's caused me complications before.
File explorer?
Rokonacdc said:
I don't have a recent Nandroid backup at the moment. My last one would take me straight from AOSP 4.3.1 all the way back down to TW 4.1.2 and I just don't like that idea. It's caused me complications before.
Click to expand...
Click to collapse
Have you tried using a file explorer and looked to /data and in there do you happen to see a folder named lost+found? Suggest using ES File Explorer to look through the contents of your phone.
UnknownTroll1 said:
Have you tried using a file explorer and looked to /data and in there do you happen to see a folder named lost+found? Suggest using ES File Explorer to look through the contents of your phone.
Click to expand...
Click to collapse
Hmm... Interestingly enough, I have three lost+found's in /data.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Rokonacdc said:
Hmm... Interestingly enough, I have three lost+found's in /data.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Weird.. Are the contents of each of them the same?? If thats the case then it may have occurred when flashing roms and an not fully wiping.
UnknownTroll1 said:
Weird.. Are the contents of each of them the same?? If thats the case then it may have occurred when flashing roms and an not fully wiping.
Click to expand...
Click to collapse
When I use ES, they are all blank and say 0b in properties. It always has every time I've looked at them, though and ice only recently had the problem.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
When creating a recovery on cwm, an I safely name them something other than the date that is given as default?
I ask because the last time I did this, after trying to restore the ROM it came up with an md5 mismatch error and as told the renaming may have causes this?
Sent from my Nexus 7 using xda app-developers app
razormccabe said:
When creating a recovery on cwm, an I safely name them something other than the date that is given as default?
I ask because the last time I did this, after trying to restore the ROM it came up with an md5 mismatch error and as told the renaming may have causes this?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I have successfully renamed recoveries from the default, and it has always worked.
What might have happened is that you renamed the EXTENSION, make sure you don't rename the .md5 at the end of the file.
Lionex1 said:
I have successfully renamed recoveries from the default, and it has always worked.
What might have happened is that you renamed the EXTENSION, make sure you don't rename the .md5 at the end of the file.
Click to expand...
Click to collapse
Maybe, though I don't see how I could have. Well I'll rename them anyway, I can't re,ember the ROMs simply by what date I saved them! Cheers.
razormccabe said:
Maybe, though I don't see how I could have. Well I'll rename them anyway, I can't re,ember the ROMs simply by what date I saved them! Cheers.
Click to expand...
Click to collapse
Don't use any spaces when you rename the folder. Eg. RenameBackup instead of Rename Backup.