So I've tried with a few different roms including the official 8.1 oreo, lineage OS 15 and 16 and a few other custom pie/oreo roms. Installed everything normal, latest TWRP version tried both full disk encryption and FBE based TWRP's and roms and although the backup and restore process doesnt show any error upon reboot it either goes directly to TWRP or shows the boot image of the restored rom for a few seconds then shuts down and boots up to TWRP again. Any ideas on whats wrong? Factory resetting at this point doesn't help it work.
Would appriciate any insight on this, I've tried so many roms now with f2fs as well as fde file systems, both encrypted and unencrypted and none of the nandroid backups I make using the latest TWRP or TWRP-FBE depending have worked at all. I am able to make the backup and restore it, no errors but it will never boot up, always either boot loop or stuck on Google logo screen.
Now I just can't seem to find what I'm doing wrong with this phone, I've formatted and reinstalled a bunch of times with latest Magisk root, last two roms I tried with android 9 was RR 7.2 and AICP weeklies, and before that the stock 8.1 from google none of which could be restored from nandroid backup. On my other phones I have TWRP backup/restore function working no problem, so I know how to use the UI with sucess.
Anyone come across anything for this maybe?
Related
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.
Ok, so I have NEVER been able to successfully restore from a backup made using TWRP when the backup was of a Cyanogen based ROM.
I've tried selecting every box/option for the backup thus creating a big arse file and even those don't successfully install during a restore attempt.
The only backup I have the will successfully install is the one I made immediately after installing TWRP of the stock rom.
When I attempt to restore my CM13 rom it usually gets to around 10 to 14 percent complete and then suddenly just reboots and seems to be stuck on the boot loading image forever until my patience runs out and I flash back to stock.
Any ideas guys? I would LOVE to be able to restore one of my CM13 backups.
I'm on Nexus 6p using newest TWRP and had backed up a couple CM13 nightlies.
Currently running CM13 snapshot.
theinvid said:
Ok, so I have NEVER been able to successfully restore from a backup made using TWRP when the backup was of a Cyanogen based ROM.
I've tried selecting every box/option for the backup thus creating a big arse file and even those don't successfully install during a restore attempt.
The only backup I have the will successfully install is the one I made immediately after installing TWRP of the stock rom.
When I attempt to restore my CM13 rom it usually gets to around 10 to 14 percent complete and then suddenly just reboots and seems to be stuck on the boot loading image forever until my patience runs out and I flash back to stock.
Any ideas guys? I would LOVE to be able to restore one of my CM13 backups.
I'm on Nexus 6p using newest TWRP and had backed up a couple CM13 nightlies.
Currently running CM13 snapshot.
Click to expand...
Click to collapse
Have you read my guide?
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
You definitely shouldn't be selecting all options in the backup menu. You only need to select system, data, boot, and vendor. And obviously only restore those.
Heisenberg said:
Have you read my guide?
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
You definitely shouldn't be selecting all options in the backup menu. You only need to select system, data, boot, and vendor. And obviously only restore those.
Click to expand...
Click to collapse
Thanks for the information. Ok I made a backup of only the 4 things listed...before I made the backup I made sure that I had NO security of any kind.
This time the backup got to 100% and then asked me to reboot the system. I was excited...thinking this had actually worked this time...only to find that it stays stuck io the GOOGLE plash screen...it never makes it to the boot animation.
The original stock backup still works...and in looking at that backup it only had 3 things backed up (no vendor).
Suggestions???
At this point a backup has failed once again and I'll have to spend hours getting it back the way I had it.
theinvid said:
Thanks for the information. Ok I made a backup of only the 4 things listed...before I made the backup I made sure that I had NO security of any kind.
This time the backup got to 100% and then asked me to reboot the system. I was excited...thinking this had actually worked this time...only to find that it stays stuck io the GOOGLE plash screen...it never makes it to the boot animation.
The original stock backup still works...and in looking at that backup it only had 3 things backed up (no vendor).
Suggestions???
At this point a backup has failed once again and I'll have to spend hours getting it back the way I had it.
Click to expand...
Click to collapse
You could try restoring the backup without the vendor, but then you'll need to flash the appropriate vendor image to suit the ROM that you're restoring.
tried
Heisenberg said:
You could try restoring the backup without the vendor, but then you'll need to flash the appropriate vendor image to suit the ROM that you're restoring.
Click to expand...
Click to collapse
tried that. it also failed.
Now things seem to be worse. I restore the original stock backup and then from there begin the process again of installing Cyanogenmod 13...only no matter what I do to install it...it gets stuck on the Google unlock screen.
I've tried.
Factory Reset - Install Just CM13 snapshot = fail
Factory Reset - Install CM13 snapshot and Gapps = fail
Factory Reset - Install CM13 snapshot and Gapps and Xposed and Vendor file fix thingy = Fail
a few other combinations all failing the same way.
A phone is worthless to me if I can't run CM13 I "NEED" to customize!!
Please help.
theinvid said:
tried that. it also failed.
Now things seem to be worse. I restore the original stock backup and then from there begin the process again of installing Cyanogenmod 13...only no matter what I do to install it...it gets stuck on the Google unlock screen.
I've tried.
Factory Reset - Install Just CM13 snapshot = fail
Factory Reset - Install CM13 snapshot and Gapps = fail
Factory Reset - Install CM13 snapshot and Gapps and Xposed and Vendor file fix thingy = Fail
a few other combinations all failing the same way.
A phone is worthless to me if I can't run CM13 I "NEED" to customize!!
Please help.
Click to expand...
Click to collapse
Are you flashing the appropriate vendor image for the ROM after you've flashed the ROM? When you say factory reset are you just choosing the factory reset option in TWRP? If so, you should instead go into the advanced wipe section and wipe system, data, cache, and dalvik cache. CM isn't the only ROM out there with customisation, there are other ROMs that have the same or more level of customisation available.
theinvid said:
tried that. it also failed.
Now things seem to be worse. I restore the original stock backup and then from there begin the process again of installing Cyanogenmod 13...only no matter what I do to install it...it gets stuck on the Google unlock screen.
I've tried.
Factory Reset - Install Just CM13 snapshot = fail
Factory Reset - Install CM13 snapshot and Gapps = fail
Factory Reset - Install CM13 snapshot and Gapps and Xposed and Vendor file fix thingy = Fail
a few other combinations all failing the same way.
A phone is worthless to me if I can't run CM13 I "NEED" to customize!!
Please help.
Click to expand...
Click to collapse
also simply tried a Factory Reset followed by reboot and that failed in the same way.
currently it would seem that Screw'd ROM is successfully installing. hmm
what's up with my CM13??
I hope I like this ROM
theinvid said:
currently it would seem that Screw'd ROM is successfully installing. hmm
what's up with my CM13??
I hope I like this ROM
Click to expand...
Click to collapse
I really don't know, there's no reason it shouldn't install. You must be missing something, or perhaps the zip is corrupt, did you check the MD5?
I had AOSPEX room on my sm-g530w 8.1 Oreo with restored efs, modem and firmware from stock backup, but after not enjoying the experience I tried to switch to Resurrection Remix 7.1.2 nougat, also with restored efs, firmware and modem.
On the first boot I realized it was a boot loop as it kept on vibrating after certain intervals of time. I decided to switch back to stock rom and restore a backup I made, but it kept giving me error 255. I gave up and reflashed AOSPEX room without restoring efs and other partitions. None of the reboot options worked as no matter where I wanted to boot (power off, download mode), it brought me back to twrp. I then tried to force reboot my device and at a first glance it seems to work. Should I restore the partitions again, and how screwed is my device?
Hi. I am currently running the latest lineage is. I recently tried the aosp pie build and also the unofficial lineage 16. I ran into some trouble restoring my phone back to lineage when I was done trying out pie. My twrp backups are not restoring for some reason. I am on the latest version of twrp. I also encrypted my data partion so now I have to put my password on before I boot into recovery and before my phone boots up. I also had a hard time getting it to read my sim card after I installed lineage fresh.
So first thing does anyone have any idea why my backups are not restoring or how to fix the issue?
And the second thing is i want to get rid of the encryption. So how do I do that. Do I wipe all my partions and then push fresh copies of lineage and gapps to my phone from my PC?
mojorisin7178 said:
Hi. I am currently running the latest lineage is. I recently tried the aosp pie build and also the unofficial lineage 16. I ran into some trouble restoring my phone back to lineage when I was done trying out pie. My twrp backups are not restoring for some reason. I am on the latest version of twrp. I also encrypted my data partion so now I have to put my password on before I boot into recovery and before my phone boots up. I also had a hard time getting it to read my sim card after I installed lineage fresh.
So first thing does anyone have any idea why my backups are not restoring or how to fix the issue?
And the second thing is i want to get rid of the encryption. So how do I do that. Do I wipe all my partions and then push fresh copies of lineage and gapps to my phone from my PC?
Click to expand...
Click to collapse
The errors you get when trying to restore your TWRP backups would help a lot with answering why they fail
Your right I should know better. I didn't write them down. It's been a while for me. Anyway I got my phone working really good now. I have to make a backup of my current system. After I do that I will try to restore the old one and see if it gives me the error msg and post it. If not then next time I run into a problem I will make sure I pay attention to the details so I can give a s much info as possible.
So... I installed LOS & it all went fine, but when I restored my MIUI backup with TWRP, the phone is stuck on the very first boot screen (on which it says Redmi by Xiaomi) & won't move any further. I've wiped the system, data & boot partitions yet no luck. What could be wrong? I want to go back to MIUI to backup my apps
it happened to me too.
when i done updating my device to newer nightly update, i got stuck on twrp decrypt data password. trying to restore back to miui, but then getting stuck on the very first boot screen.
i got no luck when trying several times restoring twrp recovery and miui, so i stay in LOS with no other options.
if someone could help please show me the guide.
thanks