I was attempting to change my Galaxy Nexus from Cyanogenmod 10.2.1 to cm 11 (current stable release). So, I did the following:
Created a Nandroid backup, saved it to my laptop, and deleted it from my phone as after creating the backup I had almost no free space. Before deleting it, I did test it and confirm that it worked.
Downloaded the CM ROM and gapps from the CM website
Verified their hashes.
Copied them to /sdcard. I didn't think to verify their hashes again. This may well have been a mistake.
Used TWRP v2.6.3.0 to wipe the phone and attempt to install CM. A message appears: "Failed." Here's a sample output (note that the output falls off the right-hand edge of the screen and there seems to be no way to scroll it to make it readable):
Code:
Updating partition details...
Installing '/sdcard/cm-11-20150626-SNAPSHOT-XNG3
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard
Updating partition details...
At this point, the phone won't boot. It goes directly to recovery.
To recover, I thought I'd just copy over my Nandroid backup. But, I can't use adb in recovery. I tried to use fastboot to flash my nandroid backup, but the format seems to be different, and I wound up with a phone that, when attempting normal boot, gets stuck on the Google logo until I remove the battery. I do have access to recovery still.
How can I get something bootable on my phone? I just want to restore my Nandroid backup. (And maybe see if I can figure out why CM-11 didn't work.) I can't find any way to copy arbitrary files to my phone.
Solved
This guide enabled me to resolve my issue. The steps I took:
Downloaded the latest stock ROM for my phone
used fastboot to flash it following the instructions on the linked post (which involved unzipping things and whatnot)
Booted into the new system and restored /sdcard from backup
Copied the latest Nandroid backup to /sdcard
Restored the Nandroid backup
Tried to install CM 11 again (this time without deleting the backup from my phone). It failed, so I restored again and am giving up for now.
Related
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error while restoring /system!
I did nothing but boot into recovery and this is all that happens when trying to recover my cwm backups. The version of CWM should not have changed and I've flashed these files before. I accidentally started another backup and shut the phone off while it was plugged in through usb (debugging might have been enabled but I don't use adb commands or have a shell).
I can restore my rom but I want to restore my backup.
How can I know the version of the backups and see if they are different from the cwm recovery version? Also in the past I have flashed and backup through rom manager, but would my rom manager boot into cwm recovery load a different cwm recovery (it shouldn't)?
I also tried this...reload the rom but restore each partition except for system, but it fails on data too then.
At a loss here. I love my backup. I was just a system camera apk away from perfection
Please help
Solution: 5 hours of playing around and the solution is that you need to make sure the cwm version is always the same...through rom manager.
When I try to update all that happens in the output window is:
Updating partition details...
Running boot script...
Finished running boot script...
Simulating actions...
After about 15 seconds it comes back with "Successful"
I updated it to the most current TWRP 2.6.3.0 and still have the same issue.
Also, whenever I try to give the backup a name, no matter what I give it it says "A backup with that name already exist!"
The backup folder is empty.
You may want to try an older version of TWRP. You can find them HERE. You may also want to check out THIS thread.
i followed a guide from techbeasts.com
using ODIN to push "CF-Auto-Root-konawifi-konawifixx-gtn5110"
then with ODIN i pushed "RECOVERY_GT-N5110-CivZ_rev1.1-PhilZ_5-ODIN.tar"
then i downloaded a rom and through the CWM recovery i chose "clean for new rom" or something along those lines
trying to install several different roms keeps giving me a "status 7". i tried multiple recovery versions of CWM, and 1 TWRP.
now the backup i MOVED to an external SD wont flash back, it gives me a md5 mismatch error.
please help!!!
right before i get the "status 7" error it says:
set_metadata_recursive: some changes failed
i was able to get my old back up to work when i went to restore.
THIS IS WHY ITS IMPORTANT TO BACK UP YOUR RESTORE FILE TO AN *EXTERNAL SD CARD*
i broke in to the back up file and cleaned out the "nandroid.md5" with a text editor, tried the restore and it worked!
Hey,
I wanted to create an nandroid backup in TWRP and got error 255 in the process.
I got the log of the failed update:
cloud.directupload.net/dfZq
So i searched for a solution, and the internet said that i should remove the file wich causes backup to fail. The logs said it was '/system/app/AndroidPay'
This is a file, not a folder.
So i removed the file, keeping an backup of it, booted into TWRP and the backup still failed.
To my surprise the boot into OxygenOS fails now. It shows the Oneplus Powerd by Android logo, turns black and reboots into twrp. Recovery and Bootloader seems to work fine.
So I connected my device with my computer and tried to get the file back to '/system/app' using adb.
I tried 'adb push AndroidPay /system/app' and it seems to be transferred succesfully, however the boot into oxygenOS is still not working.
I think it can be fixed by formatting the device and flash OxygenOS new to it, but I really don't wanna do that.
General Information:
Oneplus 3
OxygenOS 3.3.4
Rooted
Xposed Installed
No custom kernal
TWRP 3.0.2-0
File wich may be broken: cloud.directupload.net/dfZs
Is there an easyer way than resetting my whole phone to get it to work ?
I'm sorry for language mistakes or maybe leaving relevant information.
Thank you for help
I've had same problem today, my solution is restore "System" part (only system) from old backup, it saved my data and OP3 works fine after that
Wipe system, then flash OOS and it should work fine. If it doesn't Im afraid you need to do a full clean install since it isn't system related then.
Hi everyone !
I wanted to install the new MIUI 9 rom (9.5.8.0 OCAMIFA) through the recovery, but couldn't find any file in the TWRP recovery. I had an error when mounting the data partition.
I saw the solution was to reformat the data partition, so I wiped and reformated the partition. After that, I coudn't flash the 9.5.8.0 rom. I had an arror telling me that my device was not compatible. Actually the updater script within the ROM zip file looks for a variable called product and it must be set to 'sagit', the name of the MI6. But on mine it is not set, I don't know why. So I modified the updater script and succeded in flashing the ROM, but the phone got stuck at startup, with the Mi logo.
I saw that to get rid of that I had to flash the rom through fastboot. So I downloaded the Mi flash tool and the fastboot version of a rom (9.5.6.0). Once again, I had to modify the bat scripts, since they were looking for this 'product' variable that is not set on my phone. The flash started well but eventually after 30 seconds I had an error (write error) whatever the bat file I used.
But I didn't give up. I still had an old TWRP backup on my hard drive. So I rebooted in recovery mode, and transfered the backup files. But during the transfer, it stops copying ; the progress bar get stuck. I tried to copy file by file, but only the small files are copied. The big ones never make it to the end.
I think I'm cursed. Now I don't know what to do. I think I've tried almost anything I could.
Does anyone have an idea ?
i've also got bootloop after updating from 9.2.2.0 to 9.5.8.0 through TWRP, now i'm hopeless and also looking for help. i've wiped cache,dalvik,and data (exclude internal storage) even i've flashed dm-verity.zip to avoid bootloop after flashing the rom
jeanvalery said:
Hi everyone !
I wanted to install the new MIUI 9 rom (9.5.8.0 OCAMIFA) through the recovery, but couldn't find any file in the TWRP recovery. I had an error when mounting the data partition.
I saw the solution was to reformat the data partition, so I wiped and reformated the partition. After that, I coudn't flash the 9.5.8.0 rom. I had an arror telling me that my device was not compatible. Actually the updater script within the ROM zip file looks for a variable called product and it must be set to 'sagit', the name of the MI6. But on mine it is not set, I don't know why. So I modified the updater script and succeded in flashing the ROM, but the phone got stuck at startup, with the Mi logo.
I saw that to get rid of that I had to flash the rom through fastboot. So I downloaded the Mi flash tool and the fastboot version of a rom (9.5.6.0). Once again, I had to modify the bat scripts, since they were looking for this 'product' variable that is not set on my phone. The flash started well but eventually after 30 seconds I had an error (write error) whatever the bat file I used.
But I didn't give up. I still had an old TWRP backup on my hard drive. So I rebooted in recovery mode, and transfered the backup files. But during the transfer, it stops copying ; the progress bar get stuck. I tried to copy file by file, but only the small files are copied. The big ones never make it to the end.
I think I'm cursed. Now I don't know what to do. I think I've tried almost anything I could.
Does anyone have an idea ?
Click to expand...
Click to collapse
Try to transfer your backup file with adb push maybe, and see if that manages to copy your file over (You need to have adb installed on your computer of course)
I dont have my Xiaomi Mi 6 rooted, so I can't test it on my Mi 6, but I tested this on my rooted Z3 Compact, and it seems to work great there
Reboot into recovery launch a command prompt on your computer and type:
adb devices to see if you can see your device
if that works you can try to adb push to transfer your TWRP-backup
like this:
adb push /home/zteam/adb-backup/backup.zip /