So I'm trying to figure out why I can't perform a backup in SafeStrap. When I try to perform a backup I end up getting createTarFork() returned ERROR=255 and I haven't been able to find out anything about why it's returning that. Here's the snippet of the log where it all goes wrong:
==> tar_append_tree(0x421b18c0, "/data/system/netstats", "/system/netstats")
E:Error appending '/data/system' to tar archive '/sdcard-ext/TWRP/BACKUPS/0000000000000000/rom-slot1-2013-11-10--20-36-24 cm_maserati-userdebug 4.2.2 JDQ3//data.ext3.win'
I:createTarFork() process ended with ERROR=255
Any help would be appreciated as I'd like to resize that rom slot and upgrade to the CM 10.2 M1 build.
Related
For those of you using Safestrap and want to restore your "preinstall" back to stock but don't have a backup to restore from:
Download the below file and unzip it under your "safestrap/backup" directory on the SD card.
Inside Safestrap you can do an "Advanced Restore" and select "System" and then choose this backup.
Download: http://www.mediafire.com/?3zfz332vefe84j3
MD5SUM: 1e13bd36d5f04b7d0f03e11fa28e36d8
So flashing this would return your device to stock out of box condition or is this just for your "safe" system in safestrap?
debating whether to try your ICS rom but wanting to be sure I can get back to factory conditions if I absolutely must, just moved from hd2 running android so bootloader stuff is different.
Whenever I try restoring this backup it always comes up saying md5 mismatch... not sure what to do in that case.
Sent from my DROID4 using XDA
Coriolis3ffect said:
Whenever I try restoring this backup it always comes up saying md5 mismatch... not sure what to do in that case.
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
Try deleting the file, clearing your browser cache, and then redownloading.
Sent from my DROID4 using XDA
Didn't work, so I'm just going to stick with the stock rom in safe mode and leave it at that
nm wrong thread
is it me or does this back up only contain 3 files, one of them being Let's Golf game? i opened the backup file in WinRar and that's all I see.
The original link is dead, and I need this now to install the ICS update. Anyone got it handy? Otherwise I'm going to have to see if I can pull it out of the full rom image.
[edit] never mind, got it from the full rom image.
highlandsun said:
The original link is dead, and I need this now to install the ICS update. Anyone got it handy? Otherwise I'm going to have to see if I can pull it out of the full rom image.
[edit] never mind, got it from the full rom image.
Click to expand...
Click to collapse
I have the full rom Image but how do I get it back?
Assume that is what i need to do.
I have an error:
qe 1/1
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Deleting Facebook cache folder...
Verifying Current System...
assert failed: apply_patch_check("/preinstall/Knowyourdevice/Motorola_XT894_Batterysave.3gp", "71ce34b3b53ae3a2d9bbfb9ce3ba4452d73ea98", "4e7e24a6817763a5539e569c9d7e15c6e430a27b")
E:Error in /cache/Blur_version.6.13.219.XT894.Verizon.en.US.zip
(status 7)
Installation Aborted
From the full ROM zip file, extract "preinstall.img" and copy it to the phone. I would use adb push to do it.
Code:
adb push preinstall.img /sdcard-ext/
adb shell
su
umount /preinstall
dd if=/sdcard-ext/preinstall.img of=/dev/block/preinstall bs=1024k
mount -t ext3 /dev/block/preinstall /preinstall
Then copy the ICS update files back to /cache and go to Settings / About Phone / System Updates again. It will check for the update, try to download it again, and then see that it's already downloaded. Then you can install it.
By the way, if there's anything on your /preinstall partition that you wanted to save, you must back it up before doing any of this.
So after some messing around today with one of the cm12 builds, everytime I try to do anything in twrp I get the error "E: Unable to stat ' /data/power_supply_logger/power_supply_info.bin' " and i have no idea how to solve it. The only effect it seems to have is it makes restoring and backing up data fail at the last second (although as far as I can tell all of the data makes it). The error is always right after "updating partition details". I've tried reflashing 2 or three different versions of twrp (2.7.1.1, 2.6.3.1, and 2.8.1) as well as restoring stock vzw firmware through rsd lite as well as the gpe rom to no avail. Any help would be greatly appreciated.
Also, when flashing cm12, i get "mount: failed to mount /dev/block/platform/msm_sdcc. 1/by-name/userdata at /data: Device or resource busy"
StATicxTW0T said:
So after some messing around today with one of the cm12 builds, everytime I try to do anything in twrp I get the error "E: Unable to stat ' /data/power_supply_logger/power_supply_info.bin' " and i have no idea how to solve it. The only effect it seems to have is it makes restoring and backing up data fail at the last second (although as far as I can tell all of the data makes it). The error is always right after "updating partition details". I've tried reflashing 2 or three different versions of twrp (2.7.1.1, 2.6.3.1, and 2.8.1) as well as restoring stock vzw firmware through rsd lite as well as the gpe rom to no avail. Any help would be greatly appreciated.
Also, when flashing cm12, i get "mount: failed to mount /dev/block/platform/msm_sdcc. 1/by-name/userdata at /data: Device or resource busy"
Click to expand...
Click to collapse
I have the same problem with my moto g falcon XT1032.
Wen I try to flash CM 12 he gives the same error.
BinBug said:
I have the same problem with my moto g falcon XT1032.
Wen I try to flash CM 12 he gives the same error.
Click to expand...
Click to collapse
The first error or the second? I've narrowed the first down to a missing file in my data folder. Unfortunately rsd'ing doesn't help. If anyone'd be willing to upload it for me that'd be awesome. It's the bin file in /data/power_supply_logger/
The first error or the second error
StATicxTW0T said:
The first error or the second? I've narrowed the first down to a missing file in my data folder. Unfortunately rsd'ing doesn't help. If anyone'd be willing to upload it for me that'd be awesome. It's the bin file in /data/power_supply_logger/
Click to expand...
Click to collapse
Wen I try to flash te ROM he give me this:
Code:
Installing 'data/media/0/sideload.zip" ...
Checking for MD5 file ...
Skipping MD3 check : no MD5 file found
mont: failed to mount /dev/block/platform.msm_sdcc.1/by-name/userdata at /data: devices or resource busy
unmount of /data failed (-1): Devices or resource busy
E: Error Exexuting updater binary in zip ' /data/media/0/sideload.zip"
You say that i most change the bin file in /data/power_supply_logger/, but how?
link to rom that i use : CM12 for flacon
BinBug said:
Wen I try to flash te ROM he give me this:
Code:
Installing 'data/media/0/sideload.zip" ...
Checking for MD5 file ...
Skipping MD3 check : no MD5 file found
mont: failed to mount /dev/block/platform.msm_sdcc.1/by-name/userdata at /data: devices or resource busy
unmount of /data failed (-1): Devices or resource busy
E: Error Exexuting updater binary in zip ' /data/media/0/sideload.zip"
You say that i most change the bin file in /data/power_supply_logger/, but how?
link to rom that i use : CM12 for flacon
Click to expand...
Click to collapse
That error is caused by the version of TWRP you are using. Something about different versions and different updater scripts. Some have had sucess with 2.8.1, some with 2.6.3.1 and some with 2.7.1.1. You will need to try all three until you find the one that works for you. Do not touch the power supply file, that's whats causing my first error. Somehow it got deleted, and restoring to complete stock does not replace it, thats why i need someone to upload theirs.
In case you have "error 7" or "error 6" while installing ROM , to save you trouble let me just point you to the right direction. I found out that a core problem is in differently set partitions between different ROMs and in that case not even editing the "update script" and deleting "assert" lines will be of no help. So, after hours of trial and error I stumbled upon the solution suggested by our fellow members an all credits go to them.
Read This:
http://forum.xda-developers.com/showpost.php?p=57424509&postcount=1403
Than Go To
http://forum.xda-developers.com/xperia-sp/development/flashtool-flashing-stock-roms-pc-t2825808
Once I followed these instructions and flash stock ROM via recovery I was able to flash custom ROM later.
TL;DR: Tried updating OS using flashable zip thru TWRP, didn't work so used fastboot method, got it working on stock but can't restore nandroid backup (not even /data partition), have app data that I need, what can I do?
Background
I picked up the Nexus 6 not too long ago and I soon decided to unlock the bootloader, install a custom recovery, and root it. Thanks to the info here on XDA, that was painless. A few weeks ago, I got a notification for an OTA update. Having read that OTA updates no longer work for modified /system partitions, I knew that I wouldn't be able to update it.
I ignored the update for a while until I finally decided to look into how I could make the update yesterday. I really didn't want to deal with setting up the device the way I like it again so I was hoping to find a method that didn't nuke the /data or /data/media partitions. I found what looked to be the easiest method which entailed flashing a zip from TWRP.
What I Did
I ran a nandroid backup before doing anything and naively figured that would be enough. Afterwards, I wiped the system and caches for what I thought would be "good measure", flashed the zip, and was surprised to see that TWRP was reporting no OS was installed. I was under the impression that the system partition was going to be overwritten.
To make it short, I tried restoring from the nandroid backup but it would fail at the system part with TWRP reporting something along the lines of 'Cannot restore System -- mounted read only'. I hopped on fastboot, flashed the images provided by Google, and was back on stock. I tried restoring the backup once again but to no avail. I even tried restoring just the data partition but that didn't go well either.
Much Regret Section
Now, I know I should have backed up the apps separately with something like Titanium Backup but I had a lapse in judgement and assumed I could just revert back if anything went wrong. Unfortunately, I have applications with data that I can't easily get back. I tried using Nandroid Manager to restore applications from the backup but, as with past experience with the app, not all data is recovered.
Is there anything that I could try to either revert back to that backup or at least get the applications in data back the way they were prior to updating?
Wow, I feel like a doofus. After quite some digging on Google and XDA, I found the remedial solution to my problem in this post. For simplicity's sake, here's a quote:
Nevermind, I finally figured it out. In TWRP under MOUNT you have to uncheck "make system partition read only". Now my restore is working.
Click to expand...
Click to collapse
If that isn't clear enough, he's referring to the first page/menu of TWRP which has the 'Mount' button that leads you to a page with a checkbox at the bottom that is ticked and makes the system partition read only.
EDIT: As it turns out, this was only my first problem. After trying to restore the backup, I receive the same error message that I got when I attempted to only recover /data. I get the following error: 'extractTarFork() process ended with ERROR: 255'. From what I gathered online, it looks like some file may have been modified? The only thing that I did to the backup was move it from the phone over to my computer before flashing the image. Other than that, Nandroid Manager I believe decompressed it. However, now I'm stumped and I'm not sure how to proceed here.
EDIT 2: This was likely due to Nandroid Manager decompressing the backup. Luckily, I still had the uncompressed copy on my computer. I restored the backup but the phone would get stuck loading. I tried flashing the older images that I had before updating and then restoring the backup but that didn't make a difference. Finally, I gave up and salvaged what I could from the backup using Titanium Backup.
I have an H811 with an unlocked boot loader and rooted with BETA-SuperSU-v2.67-20160121175247.zip. I do not have TWRP installed, but instead opt for fastboot boot trwp-xxx.img when I want to make a nandroid backup. I did not install TWRP specifically so I could use the OTAs when they come in from Tmo. The other day, one came in but the install fails. This is the error message. I'm not sure why GoogleTTS.odex and Hangouts.odex are missing.. I may have froze them in Titanium Backup or accidentally removed them during a bloat cleansing., but it doesn't seem to be barfing on those two Google packages.. just the boot partition. Why?
I've not installed any mod kernels. Only thing I can think of is the unlocked bootloader. I have a stock nandroid that I can restore to the phone, and then possibly apply the patch, but if this is due to the unlocked bootloader that won't matter.
Second question: I have a saved copy of the update.zip from Tmo. I've read that trying to install this from TWRP is a bad idea. Is there another way to kick off the install instead of waiting for the download from Tmo again every night?
Thanks
HTML:
Verifying current system...
failed to stat "system/app/GoogleTTS/oat/arm/GoogleTTS.odex": No such file or directory
failed to stat "system/app/Hangouts/oat/arm64/Hangouts.odex": No such file or directory
contents of partition "/dev/block/bootdevice/by-name/boot" didn't match EMMC:/dev/block/bootdevice/by-name/boot:28227584:bba9b35edd32cf7e117d238d9220ebfedb0b8155:28207104:f3a1ce0f44594bc48e57a0402d2044508ba3d391
file "EMMC:/dev/block/bootdevice/by-name/boot:28227584:bba9b35edd32cf7e117d238d9220ebfedb0b8155:28207104:f3a1ce0f44594bc48e57a0402d2044508ba3d391" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: "EMMC:/dev/block/bootdevice/by-name/boot:28227584:bba9b35edd32cf7e117d238d9220ebfedb0b8155:28207104:f3a1ce0f44594bc48e57a0402d2044508ba3d391" has unexpected contents.
"EMMC:/dev/block/bootdevice/by-name/boot:28227584:bba9b35edd32cf7e117d238d9220ebfedb0b8155:28207104:f3a1ce0f44594bc48e57a0402d2044508ba3d391" has unexpected contents.
E:Error in /cache/update.zip
(Status 7)
[LGE][Recovery] Installation aborted. no valid image in CACHE.
I:Saving locale "en_US"
I:timed out waiting for key input; rebooting.
I:Saving locale "en_US"
[email protected]:/cache/recovery #
Nevermind. After some more searching, this is a really common problem with rooting and OTA. Sorry for the static. I'm new to all this.