Root [Boost Mobile] [Tool][Port]Online Nandroid Backup "Onandroid"

[cartersball]

So this is an offical fix for onandroid? So it does what the copy we had does?

Any chance youll be able to make it work with twrp?

Question here....when you made the backup you tried to install, you were already using TWRP right? I wasn't a back up that was made with CWM?

 

[Tigatron]

Question here....when you made the backup you tried to install, you were already using TWRP right? I wasn't a back up that was made with CWM?

I already had twrp and used onandroid to make a backup. I then moved the backup onandroid made to trwp backup folder and booted to twrp and tried to restore it. It didnt restore anything as onandroid makes the backup in cwm format.

 

[ameer123456789]

So this is an offical fix for onandroid? So it does what the copy we had does?

Any chance youll be able to make it work with twrp?

This is official. It is somewhat similar to what was done in this thread, but more elegantly, which means that it would survive updates to script as well.

 

[ameer123456789]

I already had twrp and used onandroid to make a backup. I then moved the backup onandroid made to trwp backup folder and booted to twrp and tried to restore it. It didnt restore anything as onandroid makes the backup in cwm format.

Can you try this? (Note: This might not work and if it does not, just restore a previous TWRP backup)

Rename files backed-up by Online Nandroid as below:
.android_secure.vfat.tar to and-sec.vfat.win
boot.img to boot.emmc.win
cache.ext4.tar to cache.ext4.win
data.ext4.tar to data.ext4.win
recovery.img to recovery.emmc.win
system.ext4.tar to system.ext4.win

After that, copy the md5sums in nandroid.md5 file to individual respective files as below:

and-sec.vfat.win.md5
boot.emmc.win.md5
cache.ext4.win.md5
data.ext4.win.md5
recovery.emmc.win.md5
system.ext4.win.md5


After all this, move the backup files to TWRP backup folder. (Where is the folder?). Then try to restore.

PS: I would love to add support (or at least a workaround) for TWRP, but no one has helped me in the past. TWRP is not available for my 'poor' device.

 

[drewhill77]

ok...well playing around with the .win files that twrp creates as its backup... renaming boot.emmc.win to boot.img allows kitchen to open it (I don't have any other img un/packers on my pc) also renaming system.ext4.win and data.ext3.win to system.ext4.gz and data.ext3.gz allows 7zip to open each of them respectively...

this has been on my pc only to see if they could be read...i haven't tried using them as backups or vica-versa

 

[ameer123456789]

ok...well playing around with the .win files that twrp creates as its backup... renaming boot.emmc.win to boot.img allows kitchen to open it (I don't have any other img un/packers on my pc) also renaming system.ext4.win and data.ext3.win to system.ext4.gz and data.ext3.gz allows 7zip to open each of them respectively...

this has been on my pc only to see if they could be read...i haven't tried using them as backups or vica-versa

Basically, backups made with TWRP are GNU compressed tar balls (simply called tar.gz or tgz). It's just the filename extension being ".win". CWM (and Online Nandroid) backups are uncompressed tar balls. TWRP should be able to restore uncompressed tar balls as well. It just requires the exact filenames and separate md5 files.

Let me know once you try a restore.