Android App Review: Google Inbox to Improve Your Life – XDA TV

Recently, Google+ exploded with the announcement of Google Inbox, as … more

Damp the LG G3 Thermal Throttling

As our mobile devices grow thinner and more powerfulwith each passing generation, it’s inevitable … more

Google Play Developer Distribution Agreement Due Tomorrow

Every once in a while, Google updates theGoogle PlayDeveloper Distribution … more

LG to Release Octa-Core “Nuclun” SoC in the LG G3 Screen

LG is set to follow the likes of Samsung and other manufacture its own … more
Post Reply

[Q] TWRP Backup Failing

OP runner1717

14th April 2014, 09:30 AM   |  #1  
OP Member
Thanks Meter: 15
 
50 posts
Join Date:Joined: Sep 2010
Hi all,

I have a Droid MAXX with 4.22 (jellybean) installed, unlocked bootloader, rooted, with TWRP 2.6.3.1 installed.

I use Android File Verifier to verify backup and keep getting Java read errors on the backups. If I open the backups in Titanium Backup, several files are missing, so the backup if definitely bad. I've made several backups, all with the same error. I backed everything up on my Internal SD and used TWRP to wipe the internal SD, thinking the partition was corrupt. No difference.

I installed TWRP 2.7 thinking that might help. The files seem to verify through a little further but then fail with the same message. I've attached a screen shot of the error message.

Any thoughts? I'm freaking out not having a good backup and I'm scared that maybe the internal SD in bad? I hope not, I like my unlocked MAXX! Is there a way to format or sector check the internal SD? I don't think the wipe in TWRP actually does a format, just an erase.

Anyone else having similar problems? Things to check?

Thanks!

Mike
Attached Thumbnails
Click image for larger version

Name:	Screenshot_2014-04-14-01-37-15.png
Views:	694
Size:	96.3 KB
ID:	2685303  
Last edited by runner1717; 14th April 2014 at 09:33 AM.
14th April 2014, 12:08 PM   |  #2  
Senior Member
Thanks Meter: 42
 
145 posts
Join Date:Joined: Jun 2012
More
Have a look at and/or post your log from twrp. You can find this under advanced options then copy log or use the command adb pull /tmp/recovery.log.

Also, I know in the past titanium backup hasn't been great at extracting nandroids. Try https://play.google.com/store/apps/d...3t1c.bkrestore and see if it makes a difference.
Last edited by hawkswind1; 14th April 2014 at 12:11 PM.
14th April 2014, 02:53 PM   |  #3  
Senior Member
Iowa
Thanks Meter: 1,834
 
2,774 posts
Join Date:Joined: Jan 2011
More
Quote:
Originally Posted by runner1717

Hi all,

I have a Droid MAXX with 4.22 (jellybean) installed, unlocked bootloader, rooted, with TWRP 2.6.3.1 installed.

I use Android File Verifier to verify backup and keep getting Java read errors on the backups. If I open the backups in Titanium Backup, several files are missing, so the backup if definitely bad. I've made several backups, all with the same error. I backed everything up on my Internal SD and used TWRP to wipe the internal SD, thinking the partition was corrupt. No difference.

I installed TWRP 2.7 thinking that might help. The files seem to verify through a little further but then fail with the same message. I've attached a screen shot of the error message.

Any thoughts? I'm freaking out not having a good backup and I'm scared that maybe the internal SD in bad? I hope not, I like my unlocked MAXX! Is there a way to format or sector check the internal SD? I don't think the wipe in TWRP actually does a format, just an erase.

Anyone else having similar problems? Things to check?

Thanks!

Mike

Have you actually tried using the backup to restore? You sure the app you are using to check isn't the issue?
15th April 2014, 12:05 AM   |  #4  
Senior Member
Thanks Meter: 520
 
2,553 posts
Join Date:Joined: Sep 2012
Quote:
Originally Posted by runner1717

Hi all,

I have a Droid MAXX with 4.22 (jellybean) installed, unlocked bootloader, rooted, with TWRP 2.6.3.1 installed.

I use Android File Verifier to verify backup and keep getting Java read errors on the backups. If I open the backups in Titanium Backup, several files are missing, so the backup if definitely bad. I've made several backups, all with the same error. I backed everything up on my Internal SD and used TWRP to wipe the internal SD, thinking the partition was corrupt. No difference.

I installed TWRP 2.7 thinking that might help. The files seem to verify through a little further but then fail with the same message. I've attached a screen shot of the error message.

Any thoughts? I'm freaking out not having a good backup and I'm scared that maybe the internal SD in bad? I hope not, I like my unlocked MAXX! Is there a way to format or sector check the internal SD? I don't think the wipe in TWRP actually does a format, just an erase.

Anyone else having similar problems? Things to check?

Thanks!

Mike

Switch to Philz it will handle twrp bu's too. You can watch the md5 check going on before you command the restore to take place. At least on 624.
The Following User Says Thank You to aviwdoowks For This Useful Post: [ View ]
16th April 2014, 06:39 AM   |  #5  
OP Member
Thanks Meter: 15
 
50 posts
Join Date:Joined: Sep 2010
Thanks for the help and suggestions. Here's what I found:

Tried TWRP 2.6.3.1, 2.6.3.0 and 2.7, all with the same result. Corrupt files. I verified this using Android File Verifier (great utility, used for years). When running Calc MD5 checksums on the individual backup files, some would verify and others would not.

Running multiple backups with each version resulted in failed backups. On a weird note, I could not remove the TWRP directory using either Root Explorer or ES file explorer. Both would cause the phone to reboot. The only way I could remove the directory was using file manager in TWRP.

Switched to Philz recovery and ALL backups verified just fine! Although it doesn't have the fancy interface or some of the features of TWRP, it gets the job done!

My conclusion is that there's some sort of issue with TWRP writing to the internal SD as proven with the incomplete backups and the directory problem it caused on the SD. I would recommend others use the Android File Verifier to make sure they are getting complete backups!

Mike
The Following 3 Users Say Thank You to runner1717 For This Useful Post: [ View ]
22nd September 2014, 04:06 AM   |  #6  
Member
Thanks Meter: 5
 
55 posts
Join Date:Joined: Jan 2012
I just installed twrp and completed my first nand, the adv program said everything was fine. So I should be safe finally
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes