Hey,
I've had this problem for ages now, and always gave up on my data, but now I really want to fix this for good.
Yesterday I was ready to update my CM12 nightly to the lastest version (didn't see it was actually CM13), and did a backup in cwm before the update. The backup succeeded, but it gave the message that .android_secure couldn't be found and it didn't back that up. It always gives me this message after a backup and after google searching, it seems to me that it doesn't matter.
After installing the update, I noticed it was CM13, and my gapps wasn't updated to the marshmellow stock, as expected, so errors occured all the time.
I didn't want to upgrade to CM13 just yet, so I decided to restore my backup.
As always, the restore process goes without errors, but upon reboot I'm stuck at the CM logo. I can wait untill the battery is dead or ignites from the heat, but nothing happens. This has also happened to me every time I make a backup. I've watched about every video on youtube on how to do a proper backup and how to restore one, so I'm confident that I did it right.
For some reason, any backup I make, no matter what android version (didn't work with stock kitkat, either, before I switched to CM12) it never works and I'm forced to do a clean install and start over again.
I've tried to do partial restores from the backup file, and if I only restore the data partition (and wipe dalvik) It does boot, but gives me non stop errors that apps are crashing.
I've tried to do a dirty flash to no avail, always endless error messages.
When I do a clean install and check the MK5 of the backup with nandroid manager it gives no errors.
Is there anything wrong with my phone or something? I'm not making backups to be unable to restore them.
Can anyone help me out with this?
(I have a i9505)
Try a different recovery. CWM is outdated. TWRP is nice. Worked for ne every time. There are TWRP flashable zips so you won't have to mess around with Odin.
GDReaper said:
Try a different recovery. CWM is outdated. TWRP is nice. Worked for ne every time. There are TWRP flashable zips so you won't have to mess around with Odin.
Click to expand...
Click to collapse
Won't changing recovery make my old backups useless? I'm all for changing to TWRP, but first I'd love to restore my CWM backup...
Yes it will. Unfortunately I don't know what to suggest. Haven't used CWM since I switched to the S4.
[unnecessary background information] A while back I decided to encrypt my OnePlus 2 - mostly to compare its performance with my Nexus 6P, which is also (obviously) encrypted. Today I decided I was tired of Oxygen OS and wanted to install CM13 since Grarak had gotten the fingerprint scanner working properly. I went ahead and unlocked the bootloader, installed TWRP 3.0.0.2, and excitedly flashed the shiny new OS (without making a backup, like an idiot)[/]
After booting up into CM13 the system asks me for my encryption key (sure, whatever) and then I get this big screen that says "Decryption Unsuccessful....The password that you entered is correct but unfortunately your data is corrupt" and goes on to say that a factory reset will fix the problem and any lost data can be re-downloaded from the cloud. I said "great!" and hit the "reboot now" button that reboots back into TWRP, runs a short script, and sends me back to where I started (presumably not on purpose).
Now, I tried doing a full wipe of the entire device via TWRP, which sent me into a new panic mode when I couldn't manage to get any files to transfer over when I tried to send them over MTP - I finally went about using the ADB Sideload feature in TWRP to once again install the same (and a different) ROM all of which garnered the same result.
Finally, the point of the story: Is there a way for me to fully remove encryption from the system from within TWRP? If not, am I totally hosed or does someone have another idea? Frankly, I'd be happy to just have a booting phone at this point.
Thanks in advance!!
So following up on my own thread, I found the setting in TWRP that specifically allows you to erase the data partition (something that I thought I had done when I did a standard wipe and/or when I did the advanced wipe and specifically told it to wipe everything) and rebooted and it finally booted happily into Android. I'm not sure if this is a bug in TWRP or a bug in CM's script that is causing issues but something isn't quite right.
I'm having issues with restoring the factory image of stock Android 6.0.1, I'm using
@Heisenberg guide to create the fresh back up image on TWRP-3.0.2-0. Once I create
the back up, I boot into the OS and perform a factory reset, when i do that the phone resets
into TWRP, and performs the wipe to the device, when i go to do the restore, it freezes
at about 39%, and reboots fully trying to enter the OS, but its corrupt due to TWRP restarting
in the middle of the recovery.
I did at one point upgrade to Android N, but reverted back to android 6.0.1 if that makes a difference.
TL;DR - Created a fresh factory image of 6.0.1 using TWRP, cannot recover with it, TWRP freezes at 39% every time.
What options are you selecting to backup/restore?
Heisenberg said:
What options are you selecting to backup/restore?
Click to expand...
Click to collapse
I'm doing a back up selecting the system/data/boot/vendor boxes, leaving everything else unchecked, and a second back up with only the EFS,
When i go to restore, I'm just using the first back up, leaving the EFS alone unless ever needed, and am selecting the system/data/boot/vendor boxes
DeathSentinels said:
I'm doing a back up selecting the system/data/boot/vendor boxes, leaving everything else unchecked, and a second back up with only the EFS,
When i go to restore, I'm just using the first back up, leaving the EFS alone unless ever needed, and am selecting the system/data/boot/vendor boxes
Click to expand...
Click to collapse
I can only think that your backup is corrupt. Also, instead of booting into Android and performing a factory reset that way, just go into the advanced wipe section of TWRP and wipe only data. Maybe you'll just need to flash the factory images to get the phone booting up fresh again.
That's where it gets interesting, I've flashed the factory 6.0.1 image, then flashed twrp, created the back up again, did the advanced wipe as you said, did the restore again, and same result, at around 39% of the recovery the phone reboots and the back up gets corrupt. My main goal is to make sure this back up absolutely works before I root and start playing around with flashing xposed modules, but I'm unable to do a successful restore for the life of me.
DeathSentinels said:
That's where it gets interesting, I've flashed the factory 6.0.1 image, then flashed twrp, created the back up again, did the advanced wipe as you said, did the restore again, and same result, at around 39% of the recovery the phone reboots and the back up gets corrupt. My main goal is to make sure this back up absolutely works before I root and start playing around with flashing xposed modules, but I'm unable to do a successful restore for the life of me.
Click to expand...
Click to collapse
I'm stumped, I really don't know why it wouldn't be working if you're performing the backup the way you say you are. Sorry I can't be more helpful. If it's any consolation, a backup probably isn't strictly necessary because you can always get back to stock by flashing the factory images.
Heisenberg said:
I'm stumped, I really don't know why it wouldn't be working if you're performing the backup the way you say you are. Sorry I can't be more helpful. If it's any consolation, a backup probably isn't strictly necessary because you can always get back to stock by flashing the factory images.
Click to expand...
Click to collapse
I'm stumped too, I've been able to do this effortlessly in the past with this phone, my Nexus 9 and m8 GPE, it wasn't until I upgraded to N and reverted back to 6.0.1 this started to happen. I've even gone as far as trying different versions of twrp, but have had the same result.
I'm just worried in a worst case scenario I'm away from a comp, something crashes and I can't do a restore via twrp, I could be SOL until I get to a comp with adb.
i had a similiar problem , but when i got into the stock image , i went into settings and did a factory reset from there , no worries your BL stays unlocked , once thats done get whatever apps you want back , disable fingerprint /security junk , then boot into bl just like the guide says , youll be able to fastboot install recovery , (boot back into bl, then scroll to recovery and start a gain) then make your backups yor OG & EFS , then reboot , get su reboot into recovery install and yould be be fine , i think you can also try fastboot format userdata , as well
DeathSentinels said:
I'm stumped too, I've been able to do this effortlessly in the past with this phone, my Nexus 9 and m8 GPE, it wasn't until I upgraded to N and reverted back to 6.0.1 this started to happen. I've even gone as far as trying different versions of twrp, but have had the same result.
I'm just worried in a worst case scenario I'm away from a comp, something crashes and I can't do a restore via twrp, I could be SOL until I get to a comp with adb.
Click to expand...
Click to collapse
Just keep a ROM zip + gapps on your phone at all times, if you run into trouble you can flash that.
That definitely makes sense , i always dk that
Sent from my Nexus 6P using XDA-Developers mobile app
I bought a new XT1575 a couple of weeks ago. Once I'd read enough to have confidence I followed the instructions to extract that long number to paste into the form on the Motorola web site and ask them to send me a code. They did, I input the code, I got a notice that my bootloader was unlocked. Once that was done I installed TWRP via ABD (I think, whatever the directions said). TWRP worked, I wiped the stock OS, flashed a custom ROM (Lineage 14) and everything worked perfectly.
Today I wanted to backup my existing ROM, wipe the device and install a different custom ROM. I booted into TWRP and I think it completed the backup. When I went to wipe though, it would crash partway through and boot back to the bootloader unlocked screen. If I tried to simply overwrite the existing ROM with the new ROM that would crash and boot to the bootloader unlocked screen too. Now I can't complete a backup either.
As I'm writing this I'm wondering if the micro USB card could be at fault, since that's where I want to back up to and that's where the new ROM is. However, if it was a corrupted card wouldn't the wipe function still work?
Any idea if reflashing TWRP would solve my problem? Any better solutions?
As the title says, TWRP is unable to decrypt data. It doesn't even ask me for my passcode anymore.
This started yesterday after I flashed a ROM and it bootlooped, and I ended up having to format my entire data partition including internal storage because I couldn't get it to boot etc, and I to fastboot flash all the stock images.
Anyway, I was wondering if anyone else has had the same problem, or if anyone might know a potential fix. I can still adb sideload zips, but I have no access to my internal storage whatsoever, so I can't even make Nandroid backups.
Regards
What version of twrp are u using or did u use cause I have twrp on my 6T and I had none of those issues and ijusdidit a few days ago..there's a fajita-3.2.3-28 what I used..you'll have to use the msm download tool to get back to stock..just do a search for it..it's popular..anyways I had previously put mine in abootloop about month ago and I used that tool and it erased everything and put me back to 9.0.11 I believe..
smiles19 said:
What version of twrp are u using or did u use cause I have twrp on my 6T and I had none of those issues and ijusdidit a few days ago..there's a fajita-3.2.3-28 what I used..you'll have to use the msm download tool to get back to stock..just do a search for it..it's popular..anyways I had previously put mine in abootloop about month ago and I used that tool and it erased everything and put me back to 9.0.11 I believe..
Click to expand...
Click to collapse
I actually got it fixed. I tried flashing the unofficial fajita-3.2.3-28 and was able to decrypt my data partition (after I had already formatted it, much to my dismay) but then it forced me into a bootloop for some odd reason. In the end, I just installed the latest official build of TWRP and it can both decrypt data and doesn't bootloop me. So yay.
Nice