I keep several Nanroid backups on my SD card. All, of course, are dated, but sometimes the date doesn't tell you what you need to know. I tried renaming one but then the (checksum?) didn't match per the file name and the restore was aborted. Is there any way to indicate what a backup file is? Something like "Liberated ROM 004 with Touchdown installed"
Thanks.
I use rom manager to name my backups
HTC Aria,cm6 6.0.2.1,dumfuq's oc kernel 768
delutedsoul23 said:
I use rom manager to name my backups
HTC Aria,cm6 6.0.2.1,dumfuq's oc kernel 768
Click to expand...
Click to collapse
Ditto on this, search rom manager in market and install. Under backup and restore there is an option that says "manage and restore backups" select the back up and then select rename.
Make sure not to put spaces or weird characters in the name (not sure if this matters for ROM Manager, I think it would though). That's what gives you the checksum error. Capital letters might give you this too. I usually just add something to the end of the date, and seperate it by periods, such as .libr004.touchdown.
BTW, has anyone noticed that the date nandroid assigns is off by a few hours? Not a big deal, just curious to see if this is just me.
ls377 said:
Make sure not to put spaces or weird characters in the name (not sure if this matters for ROM Manager, I think it would though). That's what gives you the checksum error. Capital letters might give you this too. I usually just add something to the end of the date, and seperate it by periods, such as .libr004.touchdown.
BTW, has anyone noticed that the date nandroid assigns is off by a few hours? Not a big deal, just curious to see if this is just me.
Click to expand...
Click to collapse
The date/time are GMT, not local time.
bkmo said:
The date/time are GMT, not local time.
Click to expand...
Click to collapse
Didn't even think about that, thanks!
Related
Sorry if this is the wrong section to post this, but i just had about 3hrs of "Did i really Jack this Up"... Not sure if this will go for everybody but its what i found out, a "Tip" i would call it.
If you have used the Nandroid backup (for safety) of cuz your like me and hate redownloading everything and customizing your home screens again, and you've ran into this error when trying to "Restore" from Recovery.
"Error: run 'nandroid-mobile.sh restore' via adb"
I did this and followed some steps online to do so, and then the boot screen would just keep reloading and never get thru...
Foundout, after you save your rom, and connect via usb to pc, and go into your "nandroid" folder, then choose the HT***** folder it will have your Back up, minez started with B******, i changed that name (i.e. manup - Eclair 2.1) so that i can easily choose which rom i wanted to run. well if there is any spaces in the "Name" of your Back-Up, you will get the "Error" listed above, i renamed the folder from; manup - Eclair 2.1 to manup-Eclair2.1 and then booted into recovery via device, and the Nandroid Restore worked perfectly fine, i tested this theory with two other roms i had in my nandroid back up and my theory was correct... so all in all, if you change the folder that has your "Back'd UP" info in it, dont put spaces in the new folder name.
my bad if i confused anyone it's lat. lol
Well, I guess I'll add on to this for fun! If you have low batteries, it'll say the same thing!
good to know, more info given the better
KAwAtA said:
Well, I guess I'll add on to this for fun! If you have low batteries, it'll say the same thing!
Click to expand...
Click to collapse
sanman1185 said:
good to know, more info given the better
Click to expand...
Click to collapse
Or if your sdcard is corrupted.
Okay so this tip comes from personal experience,k before I figured out how to fic the problem that this one created for me.
So, I did a backup before I flashed a mod someone did earlier. Well, the mod did nto work, and it broke some stuff on the phone, so I wanted to do a restore. That was an absolute no-go. I got this error message:
(image link)
So, I got a little worried that I had lots bigger problems. Long story short, I was missing the md5 file that nand creates when it makes a backup.
TIP: When doing a NANDROID backup, verify it's completeness by pressing your "back" key on your phone once the backup is complete. Scroll to USB-MS and select it. This *should* make a box pop up on your computer, meaning that you have access to your SD contents now.
In the SD card, navigate to nandroid/(Hero Serial Number)/XXX-XXXXXXXX-XXXX/ and make sure there is a nandroid.md5 file in there, as well as 3 other files, boot, data, and system.
If any of these are missing, press "Back" hard key to close USB-MS, and do another backup. Delete the current one if you do not have enough room.
The xxx-xxxxxxxx-xxxx above will be a folder, mine's named: BDS-20100523-0334, which is BDS-(year)(mo)(day)-(time). year 4 digits, month 2, day 2, and time 4 digits. If you have multiple ones, choose the most recent one, which would be the nandroid you just made.
Nice tip thanks, I do have a question though.
I thought the whole point of having a recovery in the Hero was to flash roms regardless of what breaks, even nandroid? I mean if your nandroid breaks you can just go into recovery enable usb drive and copy another rom over?
Yeah you should be able to flash any Rom regardless of whether you made a backup or not. I am just saying, its a helpful top to make sure your backup completed properly in case you ever want to go back to your old Rom, in your case, or if you're flashing an update that says will work with any Rom, or your just testing the update, and that update breaks. Same goes with current Rom modifications that you may want to try out.
Long story short, if you know you night need to nandroid backup or want to restore if you're just testing something, be sure to follow the tip above. One more step to save you problems.
-------------------------------------
Sent from your mom!
I would like to know if it's possible to make a Nand Backup via recovery screeen and then recover it in another Tatto, so I can export the ROM, with apps and settings to a friend's tattoo
If not, is there any other way?
Thanks in advance
Zriel said:
I would like to know if it's possible to make a Nand Backup via recovery screeen and then recover it in another Tatto, so I can export the ROM, with apps and settings to a friend's tattoo
If not, is there any other way?
Thanks in advance
Click to expand...
Click to collapse
i did that...it should work...for me all right
Sure it's possible! Since you have identical HW he will get an exact copy of your device (don't know if cache partition is cloned though, could be necessary when using custom ROM using cache as dalvik cache...)...
samsung
Do you think samsung is better ???
they may answer but some thing like "we know it is a problem, but we are working on it, and can not help you now..."
john
Well, I have to say that it hasn't been any success, so it seems not possible. Maybe there's something I gave made wrong, but it says that Nand backup is not possible.
Zriel said:
Well, I have to say that it hasn't been any success, so it seems not possible. Maybe there's something I gave made wrong, but it says that Nand backup is not possible.
Click to expand...
Click to collapse
you have to copy the content of HT99****** into your device's HT99°°°°°°°°
don't copy the HT99****** folder because that is the code of the phone backupped...it is compared with the device to restore and they doesn't match ...
so copy the subfolder of the desired backup to your /HT99°°°°°°°
try this
There are so many TUTs out there explaining how to install a ROM with CWM, and even though this is easy and works well, the actual benefit of using CWM is backing up and restoring a ROM with all personal apps/settings/tweaks.
I had a perfectly set up m-deejay Revolution 2.3 installed with CWM. Then I wanted to try something else and said "sure, why not. I can just make a backup of this and later restore it..."
...well, I guess not.
When I boot into CWM, select the restoring option, and choose the backup file that actually is shown to be on my SD it starts the process just to tell me after a few seconds that some MD5 checksum is wrong. That's it. Nothing else happens or can be done.
It would be extremely important if someone could help me restore this rom. (In it I managed to get cisco openvpn working, which I am not able to repeat in a new and clean rom. I would love to take a look at the setup!)
Here's what I use:
- Radio 2.15.50
- 2.08 HSPL
- MAGLDR 1.12
- CWM 1.2
- a folder "clockwordmod" with the backup inside (I guess/hope)
Help me and I will still be telling my grandchildren about your heroic deed!
Thanks to everyone taking their time to think about it in advance!
-cartonneexpress
Did you re-name the folder where the update is located?
If yes, then undo the change and try again.........make an other backup to check the format.
In my case it is "year" "month" "date" "time"
for instance: 2011-04-27.11.15.........i'm not sure how accurate the time needs to be, but try as close as you can, it worked for me
EDIT
...............ups, didn't check the date before posting......but still, should worke for others......
I made a mistake and formatted the hard drive of my old computer and sold it, without backing up my keystore for my app published in the Android Market.
My attempted solution:
Take the version from the market signed with the original key (key A), sign it again with my new key (key B) and upload it to the market. Then I will be able to upload another version signed only with key B.
I successfully signed the application with both keys, the problem is that I can't upload the same application again because the version code is still 10, I need to change it to 11. I've opened the AndroidManifest.xml and found that I can change the irrelevant versionName, but can't find the versionCode in there.
Anyone have any ideas? I would really prefer not to unpublish the application because I rely on the income I make from advertisements in it and I don't want to compromise my downloads/rating/position in the market.
Thanks in advanced to all who provide constructive feedback.
Nexeo said:
Take the version from the market signed with the original key (key A), sign it again with my new key (key B) and upload it to the market. Then I will be able to upload another version signed only with key B.
Click to expand...
Click to collapse
I think Market will require signing by key A in every new version of an app. Otherwise signing would make no sense, because anyone could hack it using above technique.
Second, even if you modify AndroidManifest.xml, then signature for key A will be invalid.
If you have lost your key then you're screwed. I don't think you can do anything, but release new versions of your app as new app - with different package name. Even Google can't help you.
I could try to modify version number in your AndroidManifest.xml file if you really want, but I don't see any sense in this.
Brut.all said:
I could try to modify version number in your AndroidManifest.xml file if you really want, but I don't see any sense in this.
Click to expand...
Click to collapse
The sense/hope was that I could take version 1.9 (currently in the market signed with the now lost key) and sign it again with the new key, then upload it with both signatures as version 1.9.1 so therefore I could upload version 2.0 signed only with the new key. If I had both keys this would be a successful way of switching between keys, but because I do not have both I was hoping to modify the compiled/signed app to change the versionCode (not versionName) from 10 to 11 (so the android market would accept it as a new version) and then sign it with the new key, and somehow make it so the signature with the old key was still valid.
The more I work on this and try the more I realize it's probably not possible. I've tried inserting new MD2 hashes for everything that has changed after I've tried modifying files and such but I always get that the application failed to install on my device...
Nexeo said:
The sense/hope was that I could take version 1.9 (currently in the market signed with the now lost key) and sign it again with the new key, then upload it with both signatures as version 1.9.1 so therefore I could upload version 2.0 signed only with the new key. If I had both keys this would be a successful way of switching between keys, but because I do not have both I was hoping to modify the compiled/signed app to change the versionCode (not versionName) from 10 to 11 (so the android market would accept it as a new version) and then sign it with the new key, and somehow make it so the signature with the old key was still valid.
The more I work on this and try the more I realize it's probably not possible. I've tried inserting new MD2 hashes for everything that has changed after I've tried modifying files and such but I always get that the application failed to install on my device...
Click to expand...
Click to collapse
I was just in a similar situation and emailed Google directly. Surprisingly, I received a personally written response. So I can tell you with 100% confidence that you are out of luck: to update a published application you HAVE to use the same digital signature as the original. Otherwise, you'll have to publish the update under a new package name. There is absolutely nothing Google can do. Of course, if you were Angry Birds I'm sure they'd make an exception, but small timers like us are out of luck.
Nexeo said:
The sense/hope was that I could take version 1.9 (...)
Click to expand...
Click to collapse
Yeah, you said that already and I gave you two reasons, why you can't do that:
invalid signatures for key A
requirement for key A in all future versions of your app
Chalup said:
Of course, if you were Angry Birds I'm sure they'd make an exception, but small timers like us are out of luck.
Click to expand...
Click to collapse
Google can't do anything even if they want - it's technically impossible. They could replace your app with new one with different package name, then copy all ratings, comments, etc. from old one, but they simply can't change key for existent package name.
Been there, done that...lost keystores of 3 published apps. Wrote Google too...no joy.
You are puckered As am I because I can not post an update to my apps without a new package name. Which of course, leaves all current users unable to get the update without repurchasing.
I wish there was a better way.... we all lose files from time to time. Why not make part of the publish process an upload of your keystore to the Google servers? Seems like a solution to me
In the meantime, I now have at least 5 copies of my keystores saved on various medium: e-mails to myself, file server, CD etc. Just have to deal with it I guess
Sending the hard drive off to a data recovery company who seems to be pretty confident. Hopefully they can find .keystore files.
I GOT MY KEYSTORE BACK!!!
I used the best f-ing software in the universe to restore the file (it truly is amazing): http://www.ntfs.com/boot-disk.htm
Nexeo said:
I GOT MY KEYSTORE BACK!!!
I used the best f-ing software in the universe to restore the file (it truly is amazing): http://www.ntfs.com/boot-disk.htm
Click to expand...
Click to collapse
Sweet find, I have all my stuff backed up on an IronKey flash drive. But it's a lot more than just my Keystores, it's also all of my work files and such. If you have some extra money I would recommend one. The only bad thing is the highest model's capacity is 32GB.
Rootstonian said:
Why not make part of the publish process an upload of your keystore to the Google servers? Seems like a solution to me
Click to expand...
Click to collapse
I think you don't understand what is this signing for. Its purpose is to make sure you're installing application from original author, not some hacked or infected version. And you want to open some backdoor for installing an application created by different author (no keys = different author). Your "solution" would make signing totally useless.
Chalup said:
Of course, if you were Angry Birds I'm sure they'd make an exception, but small timers like us are out of luck.
Click to expand...
Click to collapse
I don't think that's true. Recently, the wildly popular app "Vignette" suffered from pretty much the same issue and had to republish.