Develop Bugs

Factory Reset after Restore with TWRP

Hello,
I was flashing the latest version of AOKP using TWRP, and the update failed. I verified the MD5 hash before attempting the flash, but figured I'd the file had gotten corrupt somehow. So I went to reboot my phone, and it hung on the boot loader screen. I Pulled the battery and tired again, but same result. So I booted back into TWRP, restored from the backup I took just prior to attempting the flash, and upon booting my phone went directly to the Setup Wizard. I rebooted, tried the restore again, but same result. I went through the wizard, and confirmed my phone had factory reset (Note, I didn't manually wipe anything).
Does anyone know what might cause this, and if I have any way to restore the backup I have? I was going from AOKP JB Builld 3 to 4, so I didn't take a Titanium Backup first. I've been using CWM since I got my GNex in January and have never had an issue (I've switched ROMs several times, and done many backup.restores with CWM. So i'd like to think I know what I'm doing ). This is the first time I've tried out TWRP, and everything seemed to go smoothly (Except for the failed flash).
Any help would be greatly appreciated. I've been searching around and haven't found anyone else reporting this.

Not sure why it factory reset but if you still have cwm back ups flash cwm and restore one of those. Factory reset isn't a bad thing though staying fresh is the best way to start a new ROM. I don't recommend restoring anything.
Sent from my Galaxy Nexus using xda premium

I took a TWRP nandroid, now android loads then reboots itself

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.

[Q] "gapps stopped" loop after CWM restore

Hi,
I was frustrated with the delay in T-Mobile's release of KitKat for the GSIII, so I decided to root my phone last night in order to try flashing CM11 on it. Rooted my phone with Towelroot, installed ROM Manager and CWM, and created backups on Kies and through CWM. Then I proceeded to do data wipe/factory reset, cache wipe, and /system format. Tried to flash CM11, but got a status 7 error.
I freaked out, so I decided to restore everything from the backup I'd created. Restoration seemed like a success, but now I get the error "Unfortunately, the process com.google.process.gapps has stopped" in an endless loop, and it prevents me and any apps from doing anything. I tried clearing dalvik cache in recovery, but the problem still persists. Read on a few threads that I should flash to stock firmware via Odin, but I'm currently on a macbook, so I can't install it.
tl;dr - Prepped to flash CM11, reached status 7 error, got freaked out, and did restore via CWM, only to get infinite loop of gapp crashes. No access to Odin or PC. Not hard bricked or soft bricked, but essentially useless phone. Help? );

if you can still get to recovery, download latest gapps and flash that

Did you factory reset before or after you restored your back up?

Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:

Try to factory reset again

vvnn said:
Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:
Click to expand...
Click to collapse
If I'm not mistaken, there is some device ID that will change each time you flash a new rom. It may be something to do with this ID not matching the one in the restored data. Purely a guess but seems logical to me.
Anyway, factory resetting will most likely solve this for you, but I wanted to add that except in certain circumstances, you shouldn't ever manually format /system. (and one format on any partition is sufficient. There shouldn't be any need to format multiple times). If you format /system, you are wiping the O/S off of your device. Then what happens if you have problems flashing a rom, or firmware? I've seen it happen many times and I often end up spending a couple of days working with them just to get the thing to boot up again!
When you flash a rom, the first thing it does is format /system. So there is just no need to do this manually. At least if the rom fails to flash (such as failing the assert checks), youll still have something to boot into. Hope this helps in the future!

I have had the exact same issue. I have a Samsung note 2 N7105. I rooted made a backup in CWM and flashed ditto n3/s5 rom made another backup in CWM. No issues. Got a bit cocky seen as it was my first time doing anything like that. My next adventure was to try a custom kernel (agni). This didn't go so well, so I tried to do a restorw to my working backup of ditto n3/s5 rom through CMW. restore went smoothly and the phone booted. once I opened the lock screen I got the gapps error as described. I had to do a factory reset to get the phone working and then re-flashed ditto n3/s3. I've since flashed other roms and when ever I try to do a restore, I get the issue described. Note I am using the latest CWM. I putting off flashing and trying any other ROMs because of this issue. I do love dn3/s5 but id love to try others. Anyone can help it would be appreciate.

Reboot after booting to recovery

I'm using an AT&T M8, BL unclocked through HTCdev, Sunshine S-OFF, SuperCID.
Yesterday, I flashed PA. Today, I decided to restore my nandroid for Viper.
I rebooted to recovery (TWRP), wiped my data, and then told it to restore my backup of Viper. Almost immediately after doing so, my phone rebooted without completing the restore. I tried then rebooting to recovery, and wiping /system before doing the restore, in the belief that it was a Sense/AOSP conflict. However, TWRP decided to reboot before I could even start the restore.
Now, I don't have an OS to boot to, and TWRP continually reboots 10-15 seconds after it boots.
I've tried updating my recovery, which was successful, but this did not seem to have an effect.
I've also tried clearing cache with fastboot, and while this was also successful, it also has not had an effect.
Has anyone seen this happen before?
Edit:
I've installed PhilZ recovery, and it no longer reboots immediately after booting to recovery. However, each time it starts, it gives a series of "E: Can't Mount /cache/recovery"...etc.
When I try to wipe data in PhilZ, it reboots again. I've tried reflashing PA, but it gave me a "E: failed to set up expected mounts for install; aborting".

OMGMatrix said:
I'm using an AT&T M8, BL unclocked through HTCdev, Sunshine S-OFF, SuperCID.
Yesterday, I flashed PA. Today, I decided to restore my nandroid for Viper.
I rebooted to recovery (TWRP), wiped my data, and then told it to restore my backup of Viper. Almost immediately after doing so, my phone rebooted without completing the restore. I tried then rebooting to recovery, and wiping /system before doing the restore, in the belief that it was a Sense/AOSP conflict. However, TWRP decided to reboot before I could even start the restore.
Now, I don't have an OS to boot to, and TWRP continually reboots 10-15 seconds after it boots.
I've tried updating my recovery, which was successful, but this did not seem to have an effect.
I've also tried clearing cache with fastboot, and while this was also successful, it also has not had an effect.
Has anyone seen this happen before?
Edit:
I've installed PhilZ recovery, and it no longer reboots immediately after booting to recovery. However, each time it starts, it gives a series of "E: Can't Mount /cache/recovery"...etc.
When I try to wipe data in PhilZ, it reboots again.
Click to expand...
Click to collapse
I don't think the recovery was "restored" / flashed to the boot partition but maybe try just in case. Flash the boot.img for Viper ROM and see if it stops the bootloop. After that you can make a clean wipe and install the ROM again, not restore but INSTALL. You surely have the ROM's .zip still?
Reason I suggested boot.img: i cannot get anything to restore with the h3g__001 backups keep getting recovery.emmc.win' is larger than target device '/dev/block/mmcblk0p42 error
mmcblk0p42 is the boot partition, so I don't know why TWRP tried to restore/flash a recovery to boot partition. He solved it by manually flashing boot.img after renaming.
if anyone gets this error heres how i solved it.change the boot.emmc.win to boot.img and it let me restore
Just a suggestion...

So this has been thoroughly confusing.
It seems that I had to clear the cache several times in PhilZ in order to resolve the first error. I tried to flash the original rom zip for Viper, but it still failed even though the "E: can't mount" messages weren't showing any more. However, I was able to re-flash the rom zip for PA, and upon booting, I found that Many of my apps were still there dispite the fact that they should have not been.
I then was able to reboot to recovery and flash the zip for Viper.
No clue what happened, but at least if anyone else has this problem, they'll be able to see how I fixed it

OMGMatrix said:
So this has been thoroughly confusing.
It seems that I had to clear the cache several times in PhilZ in order to resolve the first error. I tried to flash the original rom zip for Viper, but it still failed even though the "E: can't mount" messages weren't showing any more. However, I was able to re-flash the rom zip for PA, and upon booting, I found that Many of my apps were still there dispite the fact that they should have not been.
I then was able to reboot to recovery and flash the zip for Viper.
No clue what happened, but at least if anyone else has this problem, they'll be able to see how I fixed it
Click to expand...
Click to collapse
The apps will be there if you restored without making changes to the data partition which contains the your userdata. I've converted and changed over from International to Developer edition quite a few times now and not once in all those times did I lose my data, I just never restored the data partition.
Not sure if you have to actively choose whether to flash over data or not, I'm not that big into custom ROMs, only tried Viper ROM and even then I kept my original data.

OMGMatrix said:
I'm using an AT&T M8, BL unclocked through HTCdev, Sunshine S-OFF, SuperCID.
Yesterday, I flashed PA. Today, I decided to restore my nandroid for Viper.
I rebooted to recovery (TWRP), wiped my data, and then told it to restore my backup of Viper. Almost immediately after doing so, my phone rebooted without completing the restore. I tried then rebooting to recovery, and wiping /system before doing the restore, in the belief that it was a Sense/AOSP conflict. However, TWRP decided to reboot before I could even start the restore.
Now, I don't have an OS to boot to, and TWRP continually reboots 10-15 seconds after it boots.
I've tried updating my recovery, which was successful, but this did not seem to have an effect.
I've also tried clearing cache with fastboot, and while this was also successful, it also has not had an effect.
Has anyone seen this happen before?
Edit:
I've installed PhilZ recovery, and it no longer reboots immediately after booting to recovery. However, each time it starts, it gives a series of "E: Can't Mount /cache/recovery"...etc.
When I try to wipe data in PhilZ, it reboots again. I've tried reflashing PA, but it gave me a "E: failed to set up expected mounts for install; aborting".
Click to expand...
Click to collapse
Had that exact same issue as you. What version of twrp were you running when the issue started? Also, did you make any firmware upgrades or downgrades recently?
I ended up just running an RUU and starting over. I was able to adb pull all my files from internal sd card before i ran it.

mattprice86 said:
Had that exact same issue as you. What version of twrp were you running when the issue started? Also, did you make any firmware upgrades or downgrades recently?
Click to expand...
Click to collapse
I was using a version of TWRP that had been bundled with a previous version of Viper that was supposed to have been newer, but was actually 2.7.0.1. I updated to the newest (2.8.0.3) from the TWRP site through fastboot, but that didn't change anything. I had somewhat recently updated to the 3.xxx.xxx.7 firmware, but had flashed other roms since that without issue.
BerndM14 said:
The apps will be there if you restored without making changes to the data partition which contains the your userdata. I've converted and changed over from International to Developer edition quite a few times now and not once in all those times did I lose my data, I just never restored the data partition.
Click to expand...
Click to collapse
I did a factory reset (cache, Dalvik, data) before attempting the nandroid restore.
It looks like TWRP failed to actually do the reset in the first place, which caused it to get hung up thinking that the storage was actually being used.

OMGMatrix said:
I did a factory reset (cache, Dalvik, data) before attempting the nandroid restore.
It looks like TWRP failed to actually do the reset in the first place, which caused it to get hung up thinking that the storage was actually being used.
Click to expand...
Click to collapse
Doesn't matter mate, if you restore the data partition the backup that you made of data gets restored, period. It'll be another issue worth interest if you deselected "data" while doing the restore. As you clearly stated yourself, you did a factory reset(wipe all) BEFORE you did the nandroid restore(In which case you might have restored "Data" as well), in that case the factory reset doesn't matter at all. If you did it after you restored then, again, it's something different.

BerndM14 said:
Doesn't matter mate, if you restore the data partition the backup that you made of data gets restored, period. It'll be another issue worth interest if you deselected "data" while doing the restore. As you clearly stated yourself, you did a factory reset(wipe all) BEFORE you did the nandroid restore(In which case you might have restored "Data" as well), in that case the factory reset doesn't matter at all. If you did it after you restored then, again, it's something different.
Click to expand...
Click to collapse
I don't think you understand.
The restore never happened. It rebooted before anything happened when I told it to restore. Nothing got restored.

Strange boot problem

Dear All,
I have a strange problem.
I was with open beta 8, unlocked bootloader with twrp 3.0.2-28.
By distraction, I accepted the update proposed by OTA (even if I known that it is impossible to update via ota, in my conditions). So it just restarted to twrp.
So I downloaded the full ROM, i pushed it through adb to the op3, and I flashed the full ROM. I got no error after flashing.
BUT, the big problem is that the phone just restart to TWRP. It neither try to boot the system. Every time i restert, It goes to TWRP.
I already tried to wipe again dalvik, cache, data and system, then flash rom again, But it just go to TWRP.
What happened? What can I do? I tried everything :crying:

The big worst coincidence is that I deleted from the PC the TWRP backup, while I usually keep at least 1-2 of them...... and I have never needed in the past. OMG
It's look a joke.
EDIT: I found an OLD backup in my old hardisk. It was of the stock oxygen. So, I restored everything, because I couldn't solve the problem.
I changed to f2fs and i flashed the new open beta 9.
Everything is ok.