Making a backup in TWRP - 8.9" Kindle Fire HD Q&A, Help & Troubleshooting

How long should it take to make a backup of the tock Kindle ROM? I havebeen stuck on a line that says "Breaking backup file into multiple archives..." for several minutes. Probably 10 or more minutes. Should it be breaking the backup into multiple archives?

mikebuck69 said:
How long should it take to make a backup of the tock Kindle ROM? I havebeen stuck on a line that says "Breaking backup file into multiple archives..." for several minutes. Probably 10 or more minutes. Should it be breaking the backup into multiple archives?
Click to expand...
Click to collapse
well, the answer is 2396 seconds, or about 40 minutes :laugh:

Related

nandroid Restore +++Hours+++

Can someone please tell me how long a nandroid restore can take as a maximum?
I am running a nandroid restore as I type.
From CM6 RC1 with snap kernel
To Nandroid back up of Fresh 3.1.0.1.
It's been going for 2+ hours, the dots are still progressing but this seems like its taking longer than it should.
Question: Is this amount of time a sign that something is severely wrong?
How can I correct the issue? What will a battery pull do to my device?
Update: Battery pull did the job and my phone isn't bricked.
Shouldn't take that long.. I've done dozens of restores and most it took was 10 minutes or so.
Pull the battery and try again.. might be a r/w issue with the card.. You should still be able to get to recovery.
did you do the backup with clockwork, and trying to restore with RA, or the other way around? I heard that can cause issues.
yep, 10 minutes is the longest I've ever had one go. Also, fwiw, it always seems to finish somewhere around the fifth line of dots..
fachadick said:
did you do the backup with clockwork, and trying to restore with RA, or the other way around? I heard that can cause issues.
Click to expand...
Click to collapse
Nope, all done with Amon. Still not sure what the issue was. Resolved, I just flashed the rom again instead.

Can't NAND Restore

I NAND backed up my fresh Rom so I could get the PRI 1.40 update, and after the update I tried to restore back and when I click on my restore file I get the error something like " run nandroid-mobile.sh restore via adb"
I've backed up and restore plenty of roms, but for some reason this is the first error like this I've gotten.
I've been using and currently am using Amon RA 1.7 recovery.
I wiped/factory reset twice, data twice, and dalvic twice. Tried several times and even tried retoring another ROM from a few days ago and getting the same error.
I tried the command in adb, but that just doesn't seem right, I don't get a list of all my backup points, it just says "using a G1 keyboard, enter a directory name or substring and then <cr> to find matches or to accept defaults."
any help would be appreciated. Thanks!
first thing i would do is try a different recovery, RA 1.8 or clockwork. also, make sure that the md5 isnt corrupted. otherwise i would have no idea, i probably would just titanium my apps back and manually reset all my settings.
davebu said:
first thing i would do is try a different recovery, RA 1.8 or clockwork. also, make sure that the md5 isnt corrupted. otherwise i would have no idea, i probably would just titanium my apps back and manually reset all my settings.
Click to expand...
Click to collapse
I could do that, and I would, but I'd like to figure out the root cause of the problem so as not to have to do it in the future. I'd like to know I can Nand backup and Nand restore if and when I need to.
If I flash RA 1.8, i assume all my restore points show up the same?
Thanks
I've run into that problem for two different reason:
1. First, I had renamed my NAND backup files. I think if you place decimals within the file name (I.e "8.31.2010") it will give you that error
2. If you do not have a sufficient battery level it will not allow you to do a restore
astro004 said:
I've run into that problem for two different reason:
1. First, I had renamed my NAND backup files. I think if you place decimals within the file name (I.e "8.31.2010") it will give you that error
2. If you do not have a sufficient battery level it will not allow you to do a restore
Click to expand...
Click to collapse
I didn't rename the files, so that can't be it, but I just barely thought of the battery thing about 2 minutes ago. I actually got this error a couple days ago at night and gave up trying, the next morning (after charging the phone all night) I tried again, and it worked right off the bat.
I never thought it was because of the battery, but I do recall reading to make sure you have plenty battery left when flashing roms. I never knew that it was because it wouldn't physically let you flash. I thought it was more so your phone doesn't run out of juice while flashing.
I guess I'll try in the morning with a full battery and post back. I think I'm currently at 20% or so.
Thanks for the feedback.

[Q] Any idea what just happened? (bricked for a few minutes?)

This evening I was playing around with my Evo and got thinking, "I really like how everything is running right now! I've been running SteelH I.2 ROM stable for a few weeks, launcherpro, all my homescreens setup... perfect! I should take a backup."
I reboot into recovery, take a nandroid backup, then go to reboot the phone. Backup completed without any errors, but the phone would not restart. It sat at the white HTC and would not budge. I removed the battery several times and rebooted, but nothing. I could still get into recovery, so I wiped data, cache, dalvik and attempted to reboot. Again, nothing... just sat at the HTC screen. At this point I was thinking, "great... gonna have a long night ahead of me troubleshooting this one." I restored the backup I had just taken about 30 minutes earlier, but wasn't very confident that it would help at all... reboot, and after a few seconds, my boot screen starts loading!
So, here is what I am wondering.... I had not done any "hacking" since the last reboot... just installed/uninstalled a few apps from the market. What could have caused my phone to react like this? Also, if it wouldn't reboot in the first place, why did restoring the backup work? I had just taken the backup a few minutes earlier....
thanks!
Well, that certainly is unique. I've had problems doing nandroid back-ups (recovering from and creating them) before but it always booted just fine no matter what happened. Maybe there was a small software error that was fixed when you recovered.
Either way, I wouldn't worry about it. Recovering a nandroid back-up = problem got deleted.
That's why I tell everyone to nandroid before doing anything

[Q] why nandroid backup/restore is so slow?

I moved from SGS2 (having befor many android phone for more than 4 years now).
And what's amaze me is how long it takes to make nandroid backup/restore in comparisson to SGS2
Is it the hardware or CWM version for GN is slower?
I am with recovery-clockwork-touch-5.8.0.2-maguro.
You cannot rush perfection.
Sent from my Galaxy Nexus
pesho00 said:
I moved from SGS2 (having befor many android phone for more than 4 years now).
And what's amaze me is how long it takes to make nandroid backup/restore in comparisson to SGS2
Is it the hardware or CWM version for GN is slower?
I am with recovery-clockwork-touch-5.8.0.2-maguro.
Click to expand...
Click to collapse
ICS is a much larger OS...
adrynalyne said:
ICS is a much larger OS...
Click to expand...
Click to collapse
Really?
I have Nandroids from SGS2 and they are in average 830-840 MB, ICS 4.0.3 nandroid of GN is in average 970 MB (first nandroid was in fact 470 MB, than 670 MB and just now 970 MB), or in other words SGS2 ones are 14% smaller but it takes like 2x faster to be backed up?
pesho00 said:
I moved from SGS2 (having befor many android phone for more than 4 years now).
And what's amaze me is how long it takes to make nandroid backup/restore in comparisson to SGS2
Is it the hardware or CWM version for GN is slower?
I am with recovery-clockwork-touch-5.8.0.2-maguro.
Click to expand...
Click to collapse
You can speed things up in the backup process by putting a file named ".hideandroidprogress" in the Clockworkmod folder on your sdcard. It will prevent CWMR from displaying the little progress meter during a backup.
Good luck
To get the "hideandroidinprocess". There are two ways, terminal and rom manager. Rom manager might be the easier way. Install it if you don't already have it installed. Menu, settings, check mark the backup and restore. Delete rom manager after done if you want, setting will remain.
Geezer Squid said:
You can speed things up in the backup process by putting a file named ".hideandroidprogress" in the Clockworkmod folder on your sdcard. It will prevent CWMR from displaying the little progress meter during a backup.
Good luck
Click to expand...
Click to collapse
Das not work for me it steal shows a progres and time is the same Near 11 minutes!!!!
But i have done some research - Backup files grow constantly - mainly data.ext4.tar - i have done some analisys and it happen that cache and dalvik cache are groing dramaticaly ~300 MB. I wiped cahce in CWM and Dalvik but it took same time to finish backup???
It's always good to keep a nandroid of your setup. Mine has never taken 11 min. to make a backup. Probably always less than 5. Make sure you have the latest version of CWM installed. If you change Roms often and that is why you are making backups, may I suggest the app Boot Manager. It allows you to install several Roms and a simple reboot and you will be in a different ROM once you get them installed. This eliminates having to make a nandroid for all the different Roms you like and want to update. I'm not going to go into a bunch of detail on the app, but if you want to learn more here's the Market link: http://tinyw.in/upSZ
There is also a free version which will allow you to install 1 other Rom. You should try the free version and if you think it is something you would use, you could buy the full version. Take a look on the Market description and you will find the user manual to help you get more info on the app and on how to use it. They even have a video posted now to show more about it. The devs are very responsive and will help via email if you email them for help. They always reply to me within a couple hours of contacting them and usually within the hour. I am in no way affiliated with the app. I just love it and it is the best purchase I have ever made on the Market for sure!
Waw! I have installed ROM Manager and set Quick Backup option (Thank You for sugestion!!!) Now Nandroid takes 4:15 Minutes - Tremendouse improvment!!!
How come showing progres can slow the whole proces 2.5 times???
Geezer Squid said:
You can speed things up in the backup process by putting a file named ".hideandroidprogress" in the Clockworkmod folder on your sdcard. It will prevent CWMR from displaying the little progress meter during a backup.
Good luck
Click to expand...
Click to collapse
It sholud be .hidenandroidprogress instead of .hideandroidprogress
pesho00 said:
Waw! I have installed ROM Manager and set Quick Backup option (Thank You for sugestion!!!) Now Nandroid takes 4:15 Minutes - Tremendouse improvment!!!
How come showing progres can slow the whole proces 2.5 times???
Click to expand...
Click to collapse
Good to know about this setting. I will try after my back up is complete. I'm about 60% complete and about an hour into the backup. The only thing I can think of as to why it is taking so long to backup is because of all my music (not sure why it backs that up when it is already on device).
I'm going to try this trick too. I have the Verizon Galaxy S3 and my nandroids take an hour and a half. On my DInc, they only took around 10 minutes. It's really annoying having to wait and hour and a half for a nandroid. That, and it eats ~40% of my battery doing it. Hopefully this little file helps it out. <fingers crossed>
Well, with adding the file to hide the progress bar, my Android took about 25 minutes last night. So it did speed up considerably, which I like, but it still takes longer than they used to. I'm definately content with that though. Thanks for the tip.
What file system r u usen.. I noticed with my samsung intercept usen anything other then rfs made nandroid backups real slow..
Sent from my Galaxy Nexus using Tapatalk 2
The microSD card is formatted as FAT32, and I have no clue what the internal storage is.

TWRP backup hung at 75%

I'm trying to do a TWRP backup of my GPE M8, but it's stuck at 75% for the last 40 minutes with no sign of progress. The striped progress bar is still moving, but the progress indicator has not budged. How do I get out of backup mode, or does it really take an hour to do a backup?
I believe it has a zip-up function, if you unselect that option the backup won't be zipped and should be ready in minutes.
Correct me if i am wrong.....
Mr Hofs said:
I believe it has a zip-up function, if you unselect that option the backup won't be zipped and should be ready in minutes.
Correct me if i am wrong.....
Click to expand...
Click to collapse
Ya thanks I had selected the compression option. I was able to use the HTC AIO toolkit to reboot the phone, unselected compress, and backup was done in a couple of minutes. Thanks!
yngdiego said:
I'm trying to do a TWRP backup of my GPE M8, but it's stuck at 75% for the last 40 minutes with no sign of progress. The striped progress bar is still moving, but the progress indicator has not budged. How do I get out of backup mode, or does it really take an hour to do a backup?
Click to expand...
Click to collapse
had that installed nandroid all worked fine https://play.google.com/store/apps/details?id=com.h3r3t1c.onnandbup&hl=en_GB

Categories

Resources