First off sorry if this is answered in another post, lease kindly direct me to the post if it is =)
I just tried to install a second ROM from ROM Manager. I was running DCU and created a back-up in ClockworkMod before I started then installed the new Fresh ROM successfully. When I tried to go back to my first ROM via the restore point I set up it gets stuck in a boot loop. The 2nd restore point from the Fresh ROM loads up just fine.
Is there anyway to fix the older restore point and get back to DCU or should I just wipe everything and reinstall DCU...
Thanks in advanced!
do a data wipe, clear cache and dalvick
Then restore your backup. Clockwork does not seem to like certain roms.
Bielinsk said:
do a data wipe, clear cache and dalvick
Then restore your backup. Clockwork does not seem to like certain roms.
Click to expand...
Click to collapse
thanks, i was able to wipe everything from the original android recovery mode and upload an old nandroid back up but from Clockwork it didnt seem to clear the dalvik cache, when i clicked clear it just went back to the last menu it never said anything in the log and when i loaded up the Clockwork backup it still didnt work :/
Ah well, it was only a matter of time. I was rooted with Reflash 3, loving it, and then I got too comfortable... I tired to add the Incredible Revolution mod, and "POOF" an endless cycle of rebooting over and over again. I guess I need to go to Verizon today and plead insanity! Unless someone has a last minute idea?
Thanks guys
Restore a nandroid backup. That'll fix it.
either remove the battery and let it sit for a few minutes and then nandroid backup.
if that doesn't work, i'm pretty sure you can factory reset from Recovery and start over
Your phone is not bricked. As mentioned do a nandroid restore or put the rom on your sd card, factory reset/wipe cache/wipe dalvik and flash the rom. You are going to be up and running in no time!
yeah... that aint a brick. i just hope you followed instructions and have a backup waiting to restore through recovery. i always have at least 2 stable rom backups on my sdcard.
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
First time to post here, but have gotten a lot of useful info from you guys. I'm kind of a noob at all this, but here it goes. I've been flashing the CM nightlies and haven't had one issue. I flashed to the new version yesterday, and everything seemed to be going ok. I went it and attempted some kernel tweaks via Pimp my Rom, and things went crazy. I started getting Process.acor. errors, and a multitude of others, then it shut down. I rebooted into recovery and wiped cache, davlik, factory reset, and wiped system..flashed my twrp restore and waited...it restored the system files, but did not restore the data or boot files...I assume that somehow the data partition has been changed to read only...How do i change that back to RW?
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.