Related
if I get a new phone hardware and I do a nandroid restore using clockwork mod from my old phone I shouldn't lose rsa keys because clockwork doesn't touch these, correct?
I dont think it does but you can check your nandroid file for a wimax.img
You should not restore a Nandroid between phones for a number of reasons, including the fact that some software's license binds it to a phone's serial number.
Just use Titanium Backup to restore apps and their data, and manually restore settings. Don't Nandroid between phones.
Would you trust an image of one windows system restored on another system - image of a dell on a hp? If the chipset is similar, it may work, but you will likely run into weird issues. Same thing here.
Set up from scratch is best. Backup along the way so you have some thing to fall back on when your tweaking fails. TB is very useful in this case.
If you do restore a backup from your old device, let us know how well your 4g works..
Don't listen to these people. I've done it and it works fine. Just make sure you remove the wimax.img before. And you'll have to change the htc folder inside of the nandroid to match the new phones serial.
I made the mistake of not removing the wimax.img. am now stuck using a friends
freeza, until they're comfortable with the technology, they really shouldn't nandroid between phones.
creyc, there's a lot of reasons you shouldn't flash nandroids between phones and until you understand and feel comfortable with what freeza said, just don't do it. If you lose those rsa keys you won't get them back. I highly suggest backing them up before you make an attempt at flashing nandroids between phones. There's guides posted that'll help you do that.
If it were me, I would backup the wimax partition from the new phone. I would search how to do that, and then doit.
That would allow a complete nandroid restore including wimax from the old phone-to the new, then a simple #flash wimax /sdcard/newsavedwimax (on the new phone)
Just saying..
freeza said:
Don't listen to these people. I've done it and it works fine. Just make sure you remove the wimax.img before. And you'll have to change the htc folder inside of the nandroid to match the new phones serial.
I made the mistake of not removing the wimax.img. am now stuck using a friends
Click to expand...
Click to collapse
I don't agree with this. There's other settings besides those in wimax.img that may cause conflicts. The kernel is part of the backup too, and depending on the level of tweaking, your new device may not support the settings that worked fine in the old phone. Finally, can you say with utmost certainty there no account related parameters (meid, etc) are stored in the backup?
gpz1100 said:
I don't agree with this. There's other settings besides those in wimax.img that may cause conflicts. The kernel is part of the backup too, and depending on the level of tweaking, your new device may not support the settings that worked fine in the old phone. Finally, can you say with utmost certainty there no account related parameters (meid, etc) are stored in the backup?
Click to expand...
Click to collapse
If you are overclocking, you may want to remove SetCPU before the backup or even after through ADB, other than that, it is completely safe. I've been running on a nandroid from a previous backup since September, with updates to the software obviously, but essentially the same. I didn't feel like starting over, and I had over 200 apps that I would have had to redownload. Not to mention all the settings, tweaks, etc. I gave it a try and it worked out just fine.
I think the only thing besides the wimax partition you have to worry about, is the PRL/profile update. It will no longer work, because those contain the previous MEID/ESN in /data/data/ in a text file. A simple edit would fix it though, or even removing that text file will cause Android to create a new one upon reboot. Other than that, everything works fine. ESN/MEID information are contained somewhere in the radio and is completely different from any of the partitions that nandroid backs up/restores.
Good to know. I'll keep that in mind if I ever have the phone swapped. I may have 10-20 apps on here at best, so setting up from scratch isn't that big of a deal. Still a pain none the less.
Coming from a windows platform, at the end of the day, it's usually better to start over from scratch than to migrate an existing installation onto a new system... From what you describe, that isn't entirely applicable here though.
gpz1100 said:
Good to know. I'll keep that in mind if I ever have the phone swapped. I may have 10-20 apps on here at best, so setting up from scratch isn't that big of a deal. Still a pain none the less.
Coming from a windows platform, at the end of the day, it's usually better to start over from scratch than to migrate an existing installation onto a new system... From what you describe, that isn't entirely applicable here though.
Click to expand...
Click to collapse
Yeah, for the most part I agree. But since Android phones are so simple in comparison to Windows and its registry, I figured "Why not?"
For the most part all you're doing is copying what's in /data to make your phone the way it was before anyway.
Since most, if not all of /system remains unchanged by phone specifics, you could really extract your system.img, make a "ROM" out of it, and have everything you had before, minus settings/etc.
/data is where things get interesting and is comparable to the Windows Registry. However, /data is so small in comparison, that most of the time, it's not a big deal to poke around in there.
Swype FC ring any bells? Why? Since the 3.70 adds Swype and its LIB into /system/lib instead of /data/data/, you get two instances of Swype's LIB, assuming you're installing the beta alongside your already included Swype. This leads to FC. All one would have to do is remove the lib in /system/lib, possibly Swype in /system/app to get their beta Swype working again.
Anyway, if anything were to not function correctly from restoring a nandroid from a different phone, all it would take is a look in /data/data, find the troublesome program, poke around in its folder, possibly clear its cache/cache folder, and maybe edit a text file inside of /data/data and you'd be fine.
Never restore from an old phone two a new phone you may brick it
Sent from my PC36100 using XDA App
So, say hypothetically...one didn't read this thread before he nandroid restored to his replacement EVO today. Well, at first it failed to restore the boot so he went in and individually restored each option besides boot and including wimax. He had no 3G before but 4G would wokr. Now he has no 3G/4G after going through and individually restoring each option, just 1X. He checked his RSA keys using WiMAX RSA Key Checker and the RSA key is present.
Is there still anything he could do to get back his 3G/4G if this hypothetical situation were to be true? RUU work maybe?
So, say hypothetically...one didn't read this thread before he nandroid restored to his replacement EVO today. Well, at first it failed to restore the boot so he went in and individually restored each option besides boot and including wimax. He had no 3G before but 4G would wokr. Now he has no 3G/4G after going through and individually restoring each option, just 1X. He checked his RSA keys using WiMAX RSA Key Checker and the RSA key is present.
Is there still anything he could do to get back his 3G/4G if this hypothetical situation were to be true? RUU work maybe?
UPDATE: I used unrevoked's S-On tool and then did the most current RUU. I then updated PRI/Profile and then made a nandroid since 3G/4G was working. I then flashed CM7nightly23 and now I don't have 3G again. 4G is working and 1X when i cut it off? Any insight on this problem? Thanks
He checked his RSA keys using WiMAX RSA Key Checker and the RSA key is present.
Click to expand...
Click to collapse
Its present, but its the wrong key.
Is there still anything he could do to get back his 3G/4G if this hypothetical situation were to be true? RUU work maybe?
Click to expand...
Click to collapse
You're pretty much out of luck. Call Asurion and pony up the 100 bucks to get a replacement. Lesson learned.
The Wimax keys are you unique to each phone, and can't be recovered or "given" a new one. He'll have to claim it via insurance, pay the deductible, or live without 4G.
Well I thought I updated the post before y'all commented, but I did use unrevoked S-On and then did the latest RUU and booted up and everything was working. I then used unrevoked and I nanroid backup the stock ROM rooted. I wiped/data/cache and flashed CM7 nightly 23 and only have 4G and 1X now?
Under wifi connections, or mobile data is on?
teh roxxorz said:
Under wifi connections, or mobile data is on?
Click to expand...
Click to collapse
Yes, and i have toggled it a few times to check. I have also toggled data sync and stuff like that as well.
Welcome,
I've compiled ClockWorkMod 3.0.1.4 and I made some changes to it, copying BlaY0's work for the HTC Legend.
Changes:
Removed menu entries for updating via /sdcard/update.zip
[*]Stripped some "No" line entries from confirmation menus (only 1 left)
[*]Removed some insane size values from partitioning list
[*]Recovery is closed using pkill instead of ps and grep
Installation
Code:
Copy the desired update.zip to your sdcard and apply it from ClockWorkMod
Extras:
Install noconfirm to remove the "no" lines. Works on all clockworkmod-based recoveries.
Thanks to BlaY0, Cyanogen and Koush
Thanks. Thanks a ton! You actually addressed what annoyed me most with this recovery. I have to admit, I do miss RA on the Vision...
But no complaining here, thanks for your work!
Edit: Ugh, I don't get it with the .no_confirm file. Put it where...?
Going to try this, sounds good =))
Sent from my HTC Vision using Tapatalk
Aha i just moved this in clockwork recoveries files then i just renamed the rec.img with the recovery of the g2 then flash it...
Sent from my HTC Vision using Tapatalk
So this still has the fix for power off while charging? And just the menu for sdcard update has been removed that can be noticed other than that, the other two updates to it is file size or so??
Sent from my HTC Vision using Tapatalk
noodles2224 said:
So this still has the fix for power off while charging? And just the menu for sdcard update has been removed that can be noticed other than that, the other two updates to it is file size or so??
Sent from my HTC Vision using Tapatalk
Click to expand...
Click to collapse
It still powers on when charging
And he did remove the other "NO" from the list, so now it's a lot easier
Hey hey! I like what you've done with the source file. I was using your recovery while in the process of making a backup and thought it was pretty neat because I couldn't for the life of me figure out where and what to edit in source since nothing is commented out by anyone. I can read the code but have a difficult time tracing it through. I'm still newbie with the C++
But anyways, while backing up, I was reminded of how annoying it is to backup the system, data, cache, sd-ext, boot, and etc folders into img files for every backup of CM7 when the only thing that really needs to be backed up is the data folder to data.img which contains all the userdata, settings and applications downloaded from the market. The only exception would be if I had changed keymap files, changed stuff inside /system/app/ folder, or any other folder/files other than data since the previous backup of the same rom.
So, if I was to make ONE backup of CM7 Tuesday morning, and wanted to make a backup of the very same rom later on in the day (containing more recent apps, emails, settings, etc. ) I would have to delete the old backup already saved and start the backup process over again from the beginning, or I would have to keep making duplicates of the same backup that differs only by the data.img file, wasting precious space on a baby **** sized microsd. IMO it completely ruins the purpose of the automatic backup feature of Rom Manager since I have to remind myself to delete the previous backup everyday. However, I do think it'll be useful if clockworkmod can be modified.
SO, I was wondering, where should I be looking in the source to add an option such as "backup data only",
that when selected,
1.) Looks for an extra line in the md5sum file for every folder in /sdcard/clockworkmod/backup/ that specifies the android version (cm7, cm6, date, w/e)
2.) Compares extra line with what it's about to back up (via contents of /system/build.prop ) and
3.) if they match up
calls only the function that backs up the data folder excluding calls for the backup of system, cache, boot, etc.
Sorry, if its confusing how I've explained it. Its quite late here in soFla, and I didn't get no sleep 8(
But I'm sure you get what I mean considering that you know some code. That's a very rough pseudo-code I guess.
Another method that probably is a lot easier, if possible, would be to figure out what command/message Rom-Manager leaves behind for clockworkmod before rebooting to clockworkmod. If it is a small script like I hope it is, backing up only data.img would be a heck of a lot easier since I'm pretty sure the source has an individual definition call for backup for each partition.
so how do i fix this powering on issue.. its starting to piss me off -.- lol,. least how to fix it on stock recovery.
CaliBoyPhillip said:
so how do i fix this powering on issue.. its starting to piss me off -.- lol,. least how to fix it on stock recovery.
Click to expand...
Click to collapse
I think this issue is caused by the hardware on the desire z and thus is unfixable. If you press power off from the menu will it just power on again? Because then the entry should be renamed to reboot recovery.
thrice43 said:
Hey hey! I like what you've done with the source file. I was using your recovery while in the process of making a backup and thought it was pretty neat because I couldn't for the life of me figure out where and what to edit in source since nothing is commented out by anyone. I can read the code but have a difficult time tracing it through. I'm still newbie with the C++
But anyways, while backing up, I was reminded of how annoying it is to backup the system, data, cache, sd-ext, boot, and etc folders into img files for every backup of CM7 when the only thing that really needs to be backed up is the data folder to data.img which contains all the userdata, settings and applications downloaded from the market. The only exception would be if I had changed keymap files, changed stuff inside /system/app/ folder, or any other folder/files other than data since the previous backup of the same rom.
So, if I was to make ONE backup of CM7 Tuesday morning, and wanted to make a backup of the very same rom later on in the day (containing more recent apps, emails, settings, etc. ) I would have to delete the old backup already saved and start the backup process over again from the beginning, or I would have to keep making duplicates of the same backup that differs only by the data.img file, wasting precious space on a baby **** sized microsd. IMO it completely ruins the purpose of the automatic backup feature of Rom Manager since I have to remind myself to delete the previous backup everyday. However, I do think it'll be useful if clockworkmod can be modified.
SO, I was wondering, where should I be looking in the source to add an option such as "backup data only",
that when selected,
1.) Looks for an extra line in the md5sum file for every folder in /sdcard/clockworkmod/backup/ that specifies the android version (cm7, cm6, date, w/e)
2.) Compares extra line with what it's about to back up (via contents of /system/build.prop ) and
3.) if they match up
calls only the function that backs up the data folder excluding calls for the backup of system, cache, boot, etc.
Sorry, if its confusing how I've explained it. Its quite late here in soFla, and I didn't get no sleep 8(
But I'm sure you get what I mean considering that you know some code. That's a very rough pseudo-code I guess.
Another method that probably is a lot easier, if possible, would be to figure out what command/message Rom-Manager leaves behind for clockworkmod before rebooting to clockworkmod. If it is a small script like I hope it is, backing up only data.img would be a heck of a lot easier since I'm pretty sure the source has an individual definition call for backup for each partition.
Click to expand...
Click to collapse
I understand the issue. I do have an idea for you which I will work on later today. It's an update.zip with a script in it which will yaffs up the data partition and put the data.img into /sdcard/clockworkmod/backup/*foldername*/
Next is should take the md5sum and write it to md5sums.txt
Like this you can restore your backup. I can cook you a custom recovery which has added update from /sdcard/update.zip baked in, but changed to /sdcard/clockworkmod/backupdata.zip
I know this isn't the easiest way to do it, but it is the easiest to code for me, so I'll use it untill I expand my knowledge
schaggo said:
Thanks. Thanks a ton! You actually addressed what annoyed me most with this recovery. I have to admit, I do miss RA on the Vision...
But no complaining here, thanks for your work!
Edit: Ugh, I don't get it with the .no_confirm file. Put it where...?
Click to expand...
Click to collapse
Ah how stupid of me, it should go in sdcard/clockworkmod/
I'll confirm and update the first post, thanks for pointing it out
Mikevhl said:
I think this issue is caused by the hardware on the desire z and thus is unfixable. If you press power off from the menu will it just power on again? Because then the entry should be renamed to reboot recovery.
Click to expand...
Click to collapse
Yeah, it happens regardless If i plug in my charge and pull of battery and back in or pull out battery and put back in and plug charger haha... same with power menu ugh... =( I'm on a T-Mobile USA G2 if that helps but its pretty much a DZ
CaliBoyPhillip said:
Yeah, it happens regardless If i plug in my charge and pull of battery and back in or pull out battery and put back in and plug charger haha... same with power menu ugh... =( I'm on a T-Mobile USA G2 if that helps but its pretty much a DZ
Click to expand...
Click to collapse
Nah I'm on a Desire Z so it's the same. Since this does not happen on other devices, the problem isn't caused by clockworkmod. The bootloader is just coded to boot into recovery when AC plugs in. I don't know if this happen the stock recovery as well. It could be caused by gfree, but also it could just be that the stock recovery forces the system to be shut down. Whatever it is, we won't be able to fix it..
Mikevhl said:
I understand the issue. I do have an idea for you which I will work on later today. It's an update.zip with a script in it which will yaffs up the data partition and put the data.img into /sdcard/clockworkmod/backup/*foldername*/
Next is should take the md5sum and write it to md5sums.txt
Like this you can restore your backup. I can cook you a custom recovery which has added update from /sdcard/update.zip baked in, but changed to /sdcard/clockworkmod/backupdata.zip
I know this isn't the easiest way to do it, but it is the easiest to code for me, so I'll use it untill I expand my knowledge
Click to expand...
Click to collapse
Damn... Why are you so OG? I would appreciate that so much. How many source files were actually modified from the original clockworkmod source? If its not many, would you mind commenting out some important bits of code so I can pick up from somewhere when looking through the code and have a better understanding of the basic/general algorithm used by the original dev? Its cool if you don't though lol. I still appreciate what you've already put together.
thrice43 said:
Damn... Why are you so OG? I would appreciate that so much. How many source files were actually modified from the original clockworkmod source? If its not many, would you mind commenting out some important bits of code so I can pick up from somewhere when looking through the code and have a better understanding of the basic/general algorithm used by the original dev? Its cool if you don't though lol. I still appreciate what you've already put together.
Click to expand...
Click to collapse
Do you mean the things that I've removed and added? If you take a look at the sources you will aee that there is a line on which the modification takes place, next a + or - which indicates if the line was added or removed. Is that what you mean?
Mikevhl said:
Do you mean the things that I've removed and added? If you take a look at the sources you will aee that there is a line on which the modification takes place, next a + or - which indicates if the line was added or removed. Is that what you mean?
Click to expand...
Click to collapse
Whoops yes I understand the layout now. sorry. I was curious as to where, and which file to begin looking to unstand customizing cwm
Mikevhl said:
Nah I'm on a Desire Z so it's the same. Since this does not happen on other devices, the problem isn't caused by clockworkmod. The bootloader is just coded to boot into recovery when AC plugs in. I don't know if this happen the stock recovery as well. It could be caused by gfree, but also it could just be that the stock recovery forces the system to be shut down. Whatever it is, we won't be able to fix it..
Click to expand...
Click to collapse
actually, it DOES happen on other devices, and it IS a clockwork issue that, to my knowledge, Koush is aware of and is looking to fix. Before I came to the g2, I had a red mytouch 4g which, when rooted and CWM was installed, would boot into recovery from a powered down state when it connected to the charger. The explanation I heard back then was that the stock recovery for the phone would boot up upon connecting to a charger while off, but that it would somehow keep the screen off. however, when the recovery is replaced with CWM, it still exhibits this behavior, but it does not keep the screen off.
Just an fyi, though, in the mexDroid forum OP, there is a modded version of CWM which, when installed, will keep the phone off while charging. I have personally verified that it works (now if only someone would find a way to have android start up and shut down at preset times, like to have an alarm go off.. that would be awesome).
Would it be safe to assume that this'll also work on my galaxy tab?
Sent from my GT-P1000 using XDA Premium App
JasonTCelum said:
Would it be safe to assume that this'll also work on my galaxy tab?
Sent from my GT-P1000 using XDA Premium App
Click to expand...
Click to collapse
no, that's a bit of a stretch, as each recovery is made for the device that uses it, not device-agnostic. However, if you would like to try it out and dont mind taking the risk, you never know, you could get lucky.
mt4g?
Currently loving this on my G2 is there any chance of it becoming compatible for the mytouch 4G?
Ill be the Guinea!
Hello all
I find myself posting here because I don't have the required 10 posts to pose my question elsewhere.
I recently switched from Clockwork to AmonRA recovery. My second backup was of my stock SenseROM. My first backup was of CM 7.0.2.1, which could not be restored. My flash to CM 7.0.3.1 was successful, so I wasn't concerned.
Now, I cannot restore the stock SenseROM. I have transferred the recovery log to the SD card, but do not know how to decipher it.
I did change the name of the folder in /sdcard/nandroid, but not the names of the folders inside that folder.
Basically I'm not sure the proper way to rename a RA backup, and if there is any way to fix/repair the stock SenseROM that I cannot restore.
Thanks for your patience and help.
Skid
Skid71 said:
Hello all
I find myself posting here because I don't have the required 10 posts to pose my question elsewhere.
I recently switched from Clockwork to AmonRA recovery. My second backup was of my stock SenseROM. My first backup was of CM 7.0.2.1, which could not be restored. My flash to CM 7.0.3.1 was successful, so I wasn't concerned.
Now, I cannot restore the stock SenseROM. I have transferred the recovery log to the SD card, but do not know how to decipher it.
I did change the name of the folder in /sdcard/nandroid, but not the names of the folders inside that folder.
Basically I'm not sure the proper way to rename a RA backup, and if there is any way to fix/repair the stock SenseROM that I cannot restore.
Thanks for your patience and help.
Skid
Click to expand...
Click to collapse
I don't know the name it needs to be. But if you need stock rom Ruu sense to unroot I have links to the latest Ruu you would need in my guide.
Skid71 said:
Hello all
I find myself posting here because I don't have the required 10 posts to pose my question elsewhere.
I recently switched from Clockwork to AmonRA recovery. My second backup was of my stock SenseROM. My first backup was of CM 7.0.2.1, which could not be restored. My flash to CM 7.0.3.1 was successful, so I wasn't concerned.
Now, I cannot restore the stock SenseROM. I have transferred the recovery log to the SD card, but do not know how to decipher it.
I did change the name of the folder in /sdcard/nandroid, but not the names of the folders inside that folder.
Basically I'm not sure the proper way to rename a RA backup, and if there is any way to fix/repair the stock SenseROM that I cannot restore.
Thanks for your patience and help.
Skid
Click to expand...
Click to collapse
I was actually at a restaurant eating dinner when I was initially replying to your post and then all of a sudden, my phone rebooted and kept bootlooping so I had to rewipe and restore a nandroid backup while driving home...Sorry. Anyway, you cannot rename the folder which the nandroid backups are kept in, but you can rename the backups themselves as long as you don't use special characters. If you did change the name of the folder that the nandroids are in, you will not be able to restore. If you remember the name of the folder, change the name back to what it was. If you're familiar with ADB, connect your device to your computer, start the Terminal app (I use a MacBook) and then type, "adb connect". It *should* display the name of your device which is the same name as the folder that the nandroids are kept in.
Skid71 said:
Hello all
I find myself posting here because I don't have the required 10 posts to pose my question elsewhere.
I recently switched from Clockwork to AmonRA recovery. My second backup was of my stock SenseROM. My first backup was of CM 7.0.2.1, which could not be restored. My flash to CM 7.0.3.1 was successful, so I wasn't concerned.
Now, I cannot restore the stock SenseROM. I have transferred the recovery log to the SD card, but do not know how to decipher it.
I did change the name of the folder in /sdcard/nandroid, but not the names of the folders inside that folder.
Basically I'm not sure the proper way to rename a RA backup, and if there is any way to fix/repair the stock SenseROM that I cannot restore.
Thanks for your patience and help.
Skid
Click to expand...
Click to collapse
Just to be sure, the backup you're trying to restore is one that was created with Amon Ra, right? You can't restore a backup that was made with Clockwork. So, as long as the backup you're restoring was made by Amon Ra, it should restore.
You said you renamed the file right? Which folder exactly did you rename? If you renamed the nandroid backup itself, it cannot have any spaces in the name, or any odd characters. Keep the name simple, with no spaces. If that's what you renamed, try renaming it to something short and simple, then try restoring again.
If you renamed a different folder (the folder that the nandroid backups are actually in), I don't think you can do that at all. mine is like this : /nandroid/HT066HL***/(nandroid backups). If you renamed the one that is bolded, I'm almost positive that will bork things. You can only rename the backups themselves, and as I said, you can't use spaces. Double check your stuff, and see if it sounds like any of that might be your problem. Good luck.
EDIT: Dang Doug! Your post wasn't there when I started typing! I got distracted on a phone call during my reply, and delayed it way too long. Didn't mean to step on your toes man. At least our advice is the same! BTW, which rom bootlooped ya? I had that happen on decks 1.2m today.
k2buckley said:
Just to be sure, the backup you're trying to restore is one that was created with Amon Ra, right? You can't restore a backup that was made with Clockwork. So, as long as the backup you're restoring was made by Amon Ra, it should restore.
You said you renamed the file right? Which folder exactly did you rename? If you renamed the nandroid backup itself, it cannot have any spaces in the name, or any odd characters. Keep the name simple, with no spaces. If that's what you renamed, try renaming it to something short and simple, then try restoring again.
If you renamed a different folder (the folder that the nandroid backups are actually in), I don't think you can do that at all. mine is like this : /nandroid/HT066HL***/(nandroid backups). If you renamed the one that is bolded, I'm almost positive that will bork things. You can only rename the backups themselves, and as I said, you can't use spaces. Double check your stuff, and see if it sounds like any of that might be your problem. Good luck.
EDIT: Dang Doug! Your post wasn't there when I started typing! I got distracted on a phone call during my reply, and delayed it way too long. Didn't mean to step on your toes man. At least our advice is the same! BTW, which rom bootlooped ya? I had that happen on decks 1.2m today.
Click to expand...
Click to collapse
I'm thinking I borked myself then
I'll try to describe this...
nandroid/AmonRASenseROM/BDS-20110525-****
I should not have changed the bolded part, but instead, change the "BDS-20110525****" part?
I think I can change the name of that folder, or better yet, just move the "BDS..." folder to the folder that is named HT0CFH***** which contains my current CM 7.0.3.1 backup. I DID NOT change that folder name.
My gosh, did that make any sense?
And yes, that Sense ROM was backed up with AmonRA.
Really appreciate the help!
Skid71 said:
I'm thinking I borked myself then
I'll try to describe this...
nandroid/AmonRASenseROM/BDS-20110525-****
I should not have changed the bolded part, but instead, change the "BDS-20110525****" part?
I think I can change the name of that folder, or better yet, just move the "BDS..." folder to the folder that is named HT0CFH***** which contains my current CM 7.0.3.1 backup. I DID NOT change that folder name.
My gosh, did that make any sense?
And yes, that Sense ROM was backed up with AmonRA.
Really appreciate the help!
Click to expand...
Click to collapse
That is correct. You should not have changed the bolded part. You wanted to leave that what it originally was (I think it may be the phone's serial number, but not sure). The BDS-20110525 is the actual backup that you created. It is coded by the date you created the backup. So it looks like you created that one on the 25th (or 24th, often times the recovery will stamp my nandroid backup time as the next day for some reason. I'll make one on the 19th, but will have the date code of the 20th in there). So, as far as fixing the issue goes....I'm not positive how to get that folder named back to what it originally was..as I'm not sure what the exact name would have been. Hopefully someone else will chime in on it, and confirm what the name of that folder should be. I'll check in a second and see if that number is indeed my serial number. If it is, you should be able to rename it to that, and try it out.
Yes, I confirmed that the name of that folder should indeed be the serial number of your phone, in all capital letters. To get your serial number, you can either use adb, by typing 'adb devices', and the number it gives back to you will be your serial. If not, shut your phone down and pull your battery. Your serial number is back there. If you rename that folder with your serial number, you should be good to go (hopefully). Give it a shot.
Edit: And just to clarify, the one you CAN rename, is the BDS-20110525 one. Just be sure to not have any spaces in the name, or odd characters, as has already been noted. You should be on the right track after that.
k2buckley said:
That is correct. You should not have changed the bolded part. You wanted to leave that what it originally was (I think it may be the phone's serial number, but not sure). The BDS-20110525 is the actual backup that you created. It is coded by the date you created the backup. So it looks like you created that one on the 25th (or 24th, often times the recovery will stamp my nandroid backup time as the next day for some reason. I'll make one on the 19th, but will have the date code of the 20th in there). So, as far as fixing the issue goes....I'm not positive how to get that folder named back to what it originally was..as I'm not sure what the exact name would have been. Hopefully someone else will chime in on it, and confirm what the name of that folder should be. I'll check in a second and see if that number is indeed my serial number. If it is, you should be able to rename it to that, and try it out.
Click to expand...
Click to collapse
In trying to decipher the recovery log, I noticed that the other folder created in /nandroid was also the number of the phone (not sure if it's the serial). When I first made the Sense ROM backup, I changed the name of that folder (instead of the folder contained inside), then made a backup of the CM ROM. I noticed that it created another folder within /nandroid that was identical to the folder it created when I made the Sense backup. I hope I'm not confusing you as much as myself.
Anyway, what I did was rename the correct Sense ROM folder, then moved it to the "HT0CFHL****" folder. I hope that does the trick.
**Edit** I did use a - when renaming the Sense ROM. No spaces. That sound alright?
______________________________________________________________
Hope you don't mind another question while I'm here.
When performing a backup, should I just do a backup of the items that AmonRA recovery already has chosen, or should I do the Wimax, sd-ext, etc?
Would just like to make sure I'm doing this right.
Wish I would have started out with AmonRA instead of Clockwork (no offense meant)
Thanks again
Skid
Skid71 said:
In trying to decipher the recovery log, I noticed that the other folder created in /nandroid was also the number of the phone (not sure if it's the serial). When I first made the Sense ROM backup, I changed the name of that folder (instead of the folder contained inside), then made a backup of the CM ROM. I noticed that it created another folder within /nandroid that was identical to the folder it created when I made the Sense backup. I hope I'm not confusing you as much as myself.
Anyway, what I did was rename the correct Sense ROM folder, then moved it to the "HT0CFHL****" folder. I hope that does the trick.
______________________________________________________________
Hope you don't mind another question while I'm here.
When performing a backup, should I just do a backup of the items that AmonRA recovery already has chosen, or should I do the Wimax, sd-ext, etc?
Would just like to make sure I'm doing this right.
Wish I would have started out with AmonRA instead of Clockwork (no offense meant)
Thanks again
Skid
Click to expand...
Click to collapse
Okay, I am slightly confused, but not too confused, haha. So when you created the CM backup, and you say that you were left with a duplicate folder, which folder do you mean? That's all I'm confused about. Do you mean the one containing your serial number, that you renamed (the one that starts with H), or do you mean the BDS-2011...one? If you mean the BDS-2011 one, then that is normal. Every backup you create is automatically named BDS-20110524 (or whatever the date/time is). If you look closer, the time should be different. Anyways, if that is not what you're referring to, then it may have regenerated the folder which contains your backups (because it has to be named as your serial number, so since you changed the name of the first one, it may have regenerated a new one. In which case, if you moved your first backup to that new folder, it SHOULD work. (i think that's what you said you were doing..). If that worked, just delete the folder that you renamed, and leave the new one. You should then be good to go.
I hope I understood you right. If I did, it sounds like you should be set.
EDIT: forgot to answer your second question:
To be honest, I don't use Amon Ra 2.3. I have always stayed with the earlier version of 1.8.0, as it has NEVER faild me, so I saw no reason to change it. It is slightly different than the version you're on, as there are no backup options. It just automatically backs up what it needs to. With your version you do have the option to select what you backup. I for sure would make a couple backups that include your wimax.img. That is important to have, for if you ever lose your RSA keys, that backup of the wimax.img is how you would recover them. You would only need to include sd-ext if your sd card is partitioned, and you're using DT a2sd. If you are, then including the sd-ext is a must. If you don't have your card partitioned, or don't know what DT a2sd is, then you don't need to worry about backing up your sd-ext. I honestly don't recall what the other options are, and hopefully someone else who actively uses that recovery will help ya with that. I believe I remember there being an android_secure, recovery, or something like that. Sorry. Just definitely include the wimax.img. I believe that my friend Dougjamal posted something in the General section about the recommended way to backup using Amon Ra. Search that out, and you may find the answers. Good luck
Here's how I rename my nandroids and it works.
\nandroid\HT121HL07014\BDEARS-20110318-0300-koni_III
Anything else i Ever tried = fail
k2buckley said:
Okay, I am slightly confused, but not too confused, haha. So when you created the CM backup, and you say that you were left with a duplicate folder, which folder do you mean? That's all I'm confused about. Do you mean the one containing your serial number, that you renamed (the one that starts with H), or do you mean the BDS-2011...one? If you mean the BDS-2011 one, then that is normal. Every backup you create is automatically named BDS-20110524 (or whatever the date/time is). If you look closer, the time should be different. Anyways, if that is not what you're referring to, then it may have regenerated the folder which contains your backups (because it has to be named as your serial number, so since you changed the name of the first one, it may have regenerated a new one. In which case, if you moved your first backup to that new folder, it SHOULD work. (i think that's what you said you were doing..). If that worked, just delete the folder that you renamed, and leave the new one. You should then be good to go.
I hope I understood you right. If I did, it sounds like you should be set.
Click to expand...
Click to collapse
Yeah, confusing. But yes, you are correct sir. I'm itching to try flashing to it, but I'm a bit hesitant since the only current ROM backup I have is one with the pre-selected (in AmonRA) choices.
I'm not communicating very effectively tonight.
I appreciate the help.
Skid71 said:
Yeah, confusing. But yes, you are correct sir. I'm itching to try flashing to it, but I'm a bit hesitant since the only current ROM backup I have is one with the pre-selected (in AmonRA) choices.
I'm not communicating very effectively tonight.
I appreciate the help.
Click to expand...
Click to collapse
Well, I think you should be all set. If not, this is what I would do. Take both of your nandroid backups (the folder labeled BDS-2011....) and copy them to a different folder.
Then be sure you have a directory on your sd card named: nandroid/(your serial number). Then place both of your nandroid backups in that folder. (the one with your serial number). Then boot to recovery, and select backup/restore. Then select 'restore backup'. You should then see the folder named as your serial number. Select it. You should then see your backups. Select the one you want to restore, and try to do it. It should work.
k2buckley said:
EDIT: Dang Doug! Your post wasn't there when I started typing! I got distracted on a phone call during my reply, and delayed it way too long. Didn't mean to step on your toes man. At least our advice is the same! BTW, which rom bootlooped ya? I had that happen on decks 1.2m today.
Click to expand...
Click to collapse
(laughing)....You know it's not a big deal with me. As much as we post in these forums, it's a surety that we will post similar replies around the same time. As for the rom, it was SalvageMod. It hadn't happen prior to today and it haven't happened since. I was eating and replying from inside a Cracker Barrel restaurant when it occurred....lol
posting & replying via the XDA Premium app.
Just wanted to say thanks again to you both. I sincerely appreciate the time and help. Coming from WinMo 6.5, this is my first android device. It becomes quite the little hobby.
I hope to soak in knowledge like a sponge then pass it on.
XDA is a great community.
Thanks again
Skid
Skid71 said:
Just wanted to say thanks again to you both. I sincerely appreciate the time and help. Coming from WinMo 6.5, this is my first android device. It becomes quite the little hobby.
I hope to soak in knowledge like a sponge then pass it on.
XDA is a great community.
Thanks again
Skid
Click to expand...
Click to collapse
You're very welcome, my friend. Before purchasing my Droid Incredible last year, I was a die-hard Blackberry user. (First Blackberry was the 7290 and the last one was the original Bold 9000 with several other models in between). After I rooted the D-Inc, I realized that the capabilities with Android devices were vast. I then wanted a larger screen and was torn between the Droid X and the EVO. Being that I was already familiar with HTC Sense, I chose the EVO and without doubt, I made the right choice. This device is amazing and through trial and error and from being helped by the good people who frequent these forums, I've learned a great deal and am still learning. I love this community and I try to help others and often as I can. The success rate is less than 100% but the effort is more than that....lol. Anyway, take care and enjoy your day...
posting & replying via the XDA Premium app.
Exact same thing happened to me. I kept reading posts saying to get amon recovery. So I did. But when I went to try and restore it wouldn't let me choose a clockwork restore. I just used Rom manager and re flashed clockwork. Then went and did a restore. I like clockwork so I will keep it. Don't know what makes amon so special. Seems like the same options.
Sent from my PC36100 using XDA App
sand1303 said:
Exact same thing happened to me. I kept reading posts saying to get amon recovery. So I did. But when I went to try and restore it wouldn't let me choose a clockwork restore. I just used Rom manager and re flashed clockwork. Then went and did a restore. I like clockwork so I will keep it. Don't know what makes amon so special. Seems like the same options.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Amon Ra is known to be more reliable. It wipes better, and flashes more reliably. Clockwork works flawlessly for some, but not for all. Amon Ra seems to be nearly flawless for all who use it. Also, if you continue using clockwork, you will surely run into some zips that you cannot flash, such as anything that is scripted with edify. Clockwork only supports amend scripting, and there are still PLENTY of zips out there that are edify only. In that case, clockwork will tell you that it can't flash it, and you need to change the scripting to amend. Amon flashes both amend and edify. Also, the newest clockwork doesn't flash radios for some reason, the flash will just not take.
So yea, clockwork works perfectly, and everyone else who suggests amon ra is wrong.
k2buckley said:
So yea, clockwork works perfectly, and everyone else who suggests amon ra is wrong.
Click to expand...
Click to collapse
Wow, I never said it was perfect or anyone was wrong. I simply never ran into problems with clockwork and had a problem with amon. So I didn't know why people would use it.
I greatly appreciate you informing me. I guess if I ever have a problem with clockwork and decide to use amon I will do a backup first thing so restore will be usable.
I also saw on Rom manager that certain things wouldn't work without clockwork. And Rom manager seems to make flashing easier.
Sent from my PC36100 using XDA App
sand1303 said:
Wow, I never said it was perfect or anyone was wrong. I simply never ran into problems with clockwork and had a problem with amon. So I didn't know why people would use it.
I greatly appreciate you informing me. I guess if I ever have a problem with clockwork and decide to use amon I will do a backup first thing so restore will be usable.
I also saw on Rom manager that certain things wouldn't work without clockwork. And Rom manager seems to make flashing easier.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yea, sorry didn't mean to come off harsh. Sorry about that. And yes, Amon Ra doesn't work with rom manager. I won't get started on my opinions on ROM manager, lol
Clockwork jacked up my phone before and left a bad taste in my mouth!
It's all good!
Sent from my PC36100 using XDA App
Hi,
I'm just wondering if it's possible to manually disable bootanimation on start to decrease boot time. I know there's no option in CyanogenMod settings, but if I delete the bootanimation file, will that work or will it just mess stuff up? Also where is it located?
I'm using the stable release of CyanogenMod 7.1.0
Its already merged in source but there's no nightly for it
Sent from my HTC Pyramid using Tapatalk
I see, thanks for the reply. But do you know if removing the file completely will mess the device up? And where the location of said file is?
File is in /system/media/bootanimation.zip but there are other considerations I'm not sure may cause problems. There's a file I think in /system/lib labeled bootanimation, recommend nandroid backup and then(easiest if you have root explorer) browsing the root files, namely /system directories and delete anything referencing /bootanimation or /bootanimation.zip unless you update to latest nightly where its an option, unless its just integrated to the ILWT I'm running
olegnoleg said:
File is in /system/media/bootanimation.zip but there are other considerations I'm not sure may cause problems. There's a file I think in /system/lib labeled bootanimation, recommend nandroid backup and then(easiest if you have root explorer) browsing the root files, namely /system directories and delete anything referencing /bootanimation or /bootanimation.zip unless you update to latest nightly where its an option, unless its just integrated to the ILWT I'm running
Click to expand...
Click to collapse
It's absolutely fine to remove it. Your bootup will be black but don't worry.
"You know, a long time ago being crazy meant something. Nowadays everybody's crazy."
If you still need help and my last post isn't as helpful to you as you need, pm me or email [email protected]; if you're having issues I can try this method myself(as I do have root explorer) and see if I can make it work, though my phones fairly stable atm and id rather not unless you need the help. Always glad to help somebody else trying to learn as I am.
NUNsLAUGHTER92 said:
It's absolutely fine to remove it. Your bootup will be black but don't worry.
"You know, a long time ago being crazy meant something. Nowadays everybody's crazy."
Click to expand...
Click to collapse
Yeah, my old phone had a nightly that had an option to remove the bootanimation, which is why I asked in the first place
Anyway thanks for all the replies. I deleted the /system/media/bootanimation.zip file and also /system/bin/bootanimation file (took backups of course ) and glad to say to say it worked! Booting into homescreen in.. 5-10 seconds
Worked for me too!! thanx!! now boot very fast!!
Just wondering if you guys enable compression to save space when making nandroids on twrp. I have never done it and want to try but wanted to see how many people do it.
Thanks
stu5797 said:
Just wondering if you guys enable compression to save space when making nandroids on twrp. I have never done it and want to try but wanted to see how many people do it.
Thanks
Click to expand...
Click to collapse
I do it every time. Why wouldn't you want your backups compressed? It lowers their size so you save some room on internal or external
Sent fromPH-L710 using xda app-developers app
evo4gnoob said:
I do it every time. Why wouldn't you want your backups compressed? It lowers their size so you save some room on internal or external
Sent fromPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Is there any downside to this? Have you successfully restored a backup after compressing it in this fashion?
hayzooos said:
Is there any downside to this? Have you successfully restored a backup after compressing it in this fashion?
Click to expand...
Click to collapse
nope none that i see and yes i have restored the compressed backups before. Only problem is after you restore a compressed backup it gets uncompressed and goes back to the size it would be if you didnt compress it. But all you would have to do is delete it that backup and make a new compressed backup
well sure. it takes longer on both ends (compression and decompression) but its seriously minor. I always used it and restoring has never proven a problem yet.
Good deal, thanks for the feedback. I'm backing up right now and chose to compress it. I'll be interested to see how big it is compared to an older backup and how much space it actually saves.
I compress mine, longest its taken so far was 420seconds to do the whole setup with about 300apps installed. A basic backup of a rom takes me 190seconds. One thing I haven't noticed is my backups themself being decompressed after restore, but I don't pay much attention cuz I usually delete and make a fresh one just so its more current.
Sent from my SPH-L710
Any reason why this is not the default?
stu5797 said:
Any reason why this is not the default?
Click to expand...
Click to collapse
Mine is enabled by default always has been on every device I've ever used twrp on
Sent from my SPH-L710
I use twrp on my gs3 and my note2. Neither have compressed as a default setting
Its enabled on my et4g, gs3, kindle fire and og evo4g I've never had to enable it, however the gs3 already had twrp on it so my dad may have enabled it on it and being as its always default on the others I didn't pay much attention. Twrp on the gs3 is a different build than my other devices they are all on twrp2.x and the gs3 is twrp3.1.0 so they may have disabled it by default on the newer builds
Sent from my SPH-L710
What do you have checked when backing up?
Hi..
Nice info..
What information do you have have Xd out when doing the nand?
I have Boot, Data, Modem, EFS, System .. What else should we have checked?
I use TWRP 2.3.3.2. on the Note 2 running CleanROM 4.0.5 and Jedi XP9
navyvet420 said:
Hi..
Nice info..
What information do you have have Xd out when doing the nand?
I have Boot, Data, Modem, EFS, System .. What else should we have checked?
I use TWRP 2.3.3.2. on the Note 2 running CleanROM 4.0.5 and Jedi XP9
Click to expand...
Click to collapse
http://teamw.in/whattobackup
I would certainly not zip a nandroid backup (at least not the one you carry on your device in case of need). Besides taking more time and work for the process, there are two major drawbacks. Imagine the necessary storage space to be not sufficient for the decompression, you would have first to estimate the needed space to free, then search and decide which files to get rid of, while counting the sum it frees and then perform the unzip. Now the worst and most probable situation.. If you need a restore it's likely that you get a system failure. So what if wou're not able to decompress first?
Aerocap said:
I would certainly not zip a nandroid backup (at least not the one you carry on your device in case of need). Besides taking more time and work for the process, there are two major drawbacks. Imagine the necessary storage space to be not sufficient for the decompression, you would have first to estimate the needed space to free, then search and decide which files to get rid of, while counting the sum it frees and then perform the unzip. Now the worst and most probable situation.. If you need a restore it's likely that you get a system failure. So what if wou're not able to decompress first?
Click to expand...
Click to collapse
Seriously dude? I think this topic has been asked answered and solved 4 to 5 years ago. So why bump a thread that has been dead for nearly half a decade?
madbat99 said:
Seriously dude? I think this topic has been asked answered and solved 4 to 5 years ago. So why bump a thread that has been dead for nearly half a decade?
Click to expand...
Click to collapse
Oh my, your post makes me feel rather ashamed, sorry to have annoyed you
Since I didn't see it anywhere and you're nice to join on a dead thread please can you lead me where this have been "solved"?
Thanks much
Aerocap said:
Oh my, your post makes me feel rather ashamed, sorry to have annoyed you
Since I didn't see it anywhere and you're nice to join on a dead thread please can you lead me where this have been "solved"?
Thanks much
Click to expand...
Click to collapse
Twrp has the option built in to enable compression. You don't zip it yourself. The answer is, it's simply a preference. It's also advised to save twrp backups off device, in external sd or flash drive, even on a PC. Device storage never enters the equation. You can restore backups directly from said storage devices.
So again, simply a preference. You didn't "annoy me. That's a fairly arrogant assumption. I just thought it odd to attempt to answer a question that no one has queried in years.
@madbat99 Of course there is also to save a backup somewhere else, I mentionned especially the one we carry for emergency after reading a previous post
Notorious said:
Only problem is after you restore a compressed backup it gets uncompressed and goes back to the size it would be if you didnt compress it.
Click to expand...
Click to collapse
Aerocap said:
@madbat99 Of course there is also to save a backup somewhere else, I mentionned especially the one we carry for emergency after reading a previous post
Click to expand...
Click to collapse
Emergency backups should be on external sd. What if /data is corrupted? Backup is lost. Who would ever run device storage so close to full that a decompressed backup wouldn't fit, if it fit while compressed? Your device would run horribly.
So many issues would be solved if people would just maintain healthy device habits. Don't run right at storage limits, keep backups on external sd.
I never compress my backups by the way. No need. But it's not because I don't have room for it to decompress. It's just an extra step that I have no use for.