Every time I take a nandroid backup in TWRP and boot the phone up, I seem to get boot loops.
Yesterday
------------------
I was running HTC's factory 4.4.2 firmware that came with my phone when I bought it. It was rooted and I was using XPosed. I wanted to upgrade to 4.4.3 via OTA, but I wanted a roll-back method. So I took a nandroid, all is well.
I flash stock recovery and take the OTA. All is well. I re-root, install xposed, tinker with some modules and then the phone reboots itself.
I did the upgrade from 4.4.2 to 4.4.3 again after restoring my nandroid backup. All is well. I decide not to tamper with root stuff, but the su binary has been flashed. I restored a majority of my apps and app data by using titanium backup to load application data from my TWRP backup. Everything is STILL fine.
Today
------------------
My TWRP backup of 4.4.2 was at work so I had to wait until I got back to move the backup back onto my phone. So here I am. I decide to do the following:
1. I shut my perfectly working 4.4.3 ROM down so I can take a nandroid before I load the 4.4.2 nandroid and try another fresh update
2. I make the nandroid backup and boot the OS back up so I can copy the TWRP folder over to my computer
3. Phone boot loops again.
What is causing this? I've tried a bunch of things like fixing permissions from TWRP, clearing the dalvik and cache. I tried sending "adb logcat" to a file on my computer to examine the output but nothing sticks out before it reboots.
Only fix I know is to factory reset and start the long process all over again.
M8_UL
HBOOT-3.18.0.0000
RADIO-1.19.21331147A1.09G
Carrier: Wind Mobile (Canada)
Have you tried fastboot erase cache, and flash TWRP again?
No I have not. Once I try that, what point will I be at? Will I be able to boot into my OS or will I need to restore my backup again?
What does fastboot erase cache do? Is it the same cache I can clear from TWRP?
One thing I just remembered... I'm using TWRP 2.7.1.0, where prior to upgrading I was using TWRP 2.7.0.2 from Hasoon2000's toolkit. Not sure if this matters or not yet.
ninjai117 said:
No I have not. Once I try that, what point will I be at? Will I be able to boot into my OS or will I need to restore my backup again?
Click to expand...
Click to collapse
The point is to re-install TWRP. As I don't have issues with the phone rebooting after doing a nandroid, I'm just guessing that maybe its just a bad TWRP install.
For that matter, try to download the TWRP file again, to make sure the file isn't corrupt.
You won't be able to boot into the OS just from what I suggested, you will still need to restore the nandroid.
erase cache is suggested as sometimes folks have trouble re-installing TWRP, and erase cache will often solve this. I always install TWRP by fastboot, so fastboot erase cache just takes 2 more seconds, which is time well spent to reduce headaches.
redpoint73 said:
The point is to re-install TWRP. As I don't have issues with the phone rebooting after doing a nandroid, I'm just guessing that maybe its just a bad TWRP install.
For that matter, try to download the TWRP file again, to make sure the file isn't corrupt.
You won't be able to boot into the OS just from what I suggested, you will still need to restore the nandroid.
erase cache is suggested as sometimes folks have trouble re-installing TWRP, and erase cache will often solve this. I always install TWRP by fastboot, so fastboot erase cache just takes 2 more seconds, which is time well spent to reduce headaches.
Click to expand...
Click to collapse
OK well I reverted back to my nandroid I created with my previous version of TWRP, and did the OTA again. Have not bothered to root or create further nandroids. So far everything is great. Just wish I could create a nandroid without the thing going crazy on me.
ninjai117 said:
Just wish I could create a nandroid without the thing going crazy on me.
Click to expand...
Click to collapse
I haven't had this happen to me. Only issue with TWRP for me so far on this device, is a backup failed to restore on an earlier TWRP version (so I had to flash a ROM and setup again) and I haven't had this issue on more recent TWRP versions.
Again, I'd suggest downloading TWRP again, and doing a fresh install of it and see if the problem persists. Or try CWM.
redpoint73 said:
The point is to re-install TWRP. As I don't have issues with the phone rebooting after doing a nandroid, I'm just guessing that maybe its just a bad TWRP install.
For that matter, try to download the TWRP file again, to make sure the file isn't corrupt.
You won't be able to boot into the OS just from what I suggested, you will still need to restore the nandroid.
erase cache is suggested as sometimes folks have trouble re-installing TWRP, and erase cache will often solve this. I always install TWRP by fastboot, so fastboot erase cache just takes 2 more seconds, which is time well spent to reduce headaches.
Click to expand...
Click to collapse
redpoint73 said:
I haven't had this happen to me. Only issue with TWRP for me so far on this device, is a backup failed to restore on an earlier TWRP version (so I had to flash a ROM and setup again) and I haven't had this issue on more recent TWRP versions.
Again, I'd suggest downloading TWRP again, and doing a fresh install of it and see if the problem persists. Or try CWM.
Click to expand...
Click to collapse
I instead flashed TWRP from Hasoon2000's HTC M8 All In One Kit, which is what I previously had and created my 4.4.2 nandroid with. Every time after that I was using the latest version from TWRP's website. I suspect that is the culprit, but I have no evidence yet as I have not created a nandroid again. I'm currently on 4.4.3 with SuperSU.zip flashed. No problems yet.
ninjai117 said:
Every time after that I was using the latest version from TWRP's website. I suspect that is the culprit, but I have no evidence yet as I have not created a nandroid again.
Click to expand...
Click to collapse
I always get TWRP from their website.
I'm running stock android (6.0.1), encrypted (without a pin), with root, TWRP 3.0.2-0 and Xposed. I recently did a Nandroid backup (Boot/System/Data/EFS) successfully. Until I tried to restore the the Nandroid Backup. After I successfully restored the Backup the phone rebooted and started. But is started like a Factory Image. It was a fresh install. All my apps and settings where gone. What is the problem here?
I made a backup of my 5x when it was running rooted/xposed 6.0.1 but then decided to update to 7.1.1 to try out the new features. But now I really miss a lot of xposed modules so I decided that I want to restore my 6.0.1 backup that I made a couple of weeks ago. So I flashed the 6.0.1 factory image from Google's developer website and was able to successfully boot into Marshmallow again. However after installing TWRP I tried restoring the backup (through USB OTG) after wiping system and cache and a doing factory reset but it pauses on "restoring system image" for a brief moment then proceeds to reboot by itself despite that it's only 27% complete. The reboot however does not go to completion and so the phone is stuck in a bootloop. I'm really not sure where the problem is here. Is it TWRP? Or the backup file? What can I do?
Which version of TWRP have you used? By any chance the backup also contained EFS?
marioemp2k7 said:
Which version of TWRP have you used? By any chance the backup also contained EFS?
Click to expand...
Click to collapse
I used version 3.0.2-2.
And isn't EFS supposed to be backed up anyway? I just checked the backup folder and it contains 4 files that begin with "efs". Should I delete those and try again?
Format everything from TWRP except internal storage. Restore your backup without EFS. Next time you want to come back to another version just be sure that you also backup the vendor or you flash the vendor corresponding to the version you're restoring beforehand.
marioemp2k7 said:
Format everything from TWRP except internal storage. Restore your backup without EFS. Next time you want to come back to another version just be sure that you also backup the vendor or you flash the vendor corresponding to the version you're restoring beforehand.
Click to expand...
Click to collapse
I made the backup while I was running 6.0.1 and I flashed the 6.0.1 factory image so they both should have the same vendor image.
I also tried wiping everything except for internal storage and I unchecked "EFS" when restoring the backup but the same problem still persists, the phone automatically reboots itself before the restoring is complete and gets stuck in a bootloop. I'm not sure where the problem is at this point. I guess I'll just have to start from scratch again
I am getting an error saying Unsuccessful Encryption after restoring from a Nandroid Backup of Stock OOS 4.7.6. I was on Omnirom 8.1.
Is there any way to get past this?
Install first Stock OOS 4.7.6 and boot it, and after try to restore Nandroid Backup. Not Format Data after boot 4.7.6 stock
Thanks, Although I have updated to the latest version and copied the backup I had on my PC. I wonder why this happened since the Nandroid backups make an image of the whole partition.
using twrp to make a nandroid backup?
just backup and restore as normal or.
do i wipe yes option before i flash a twrp recovery image?
and just flash as normal.
how to create and flash nandroid recovery on g6-play rooted a8 Oreo without breaking encryption or messing up magisk first time using magisk and disabler
been out of the mobile device game forever