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.
Related
Hey guys,
Got a very weird problem here. I have previously flashed a CM10 nightly to my One X (international) and everything has been fine for around 3 weeks. Decided i wanted to try our the ViperX ROM. Previously upon flashing this ROM it just bootlooped but after another try with a slightly different method, i managed to get it to boot and all was merry. After titanium restore i rebooted, and this once again put me into a bootloop. Cannot get the ROM to boot. Why is this!!! Switched back to CM10. :good:
You need to do
fastboot flash boot boot.img
You may have done
fastboot boot boot.img
BenPope said:
You need to do
fastboot flash boot boot.img
You may have done
fastboot boot boot.img
Click to expand...
Click to collapse
Still doesnt boot man, im sure i flashed the boot image properly. This is the rundown of my flash process:
1: install from sd
2: in recovery, factory reset, wipe cache, wipe dalvic cache
3: Boot into fastboot and flash the boot.img
4: Reboot.
So it booted but into viper X, but after restoring with Titanium i was unable to get it to boot again.
I also tried "fastboot erase cache" to no avail
In fastboot type fastboot erase cache
Jamekerr said:
So it booted but into viper X, but after restoring with Titanium i was unable to get it to boot again.
Click to expand...
Click to collapse
Did you restore system apps or data?
Where does it stop booting, what is on the screen?
With tb, make sure you restore user apps only, none of the system apps.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
eyosen said:
With tb, make sure you restore user apps only, none of the system apps.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
Sorry forgot to mention I also used the "fast book erase cache" command.
As for titanium I restored all user apps and data and now that you mention it that could be the problem. I'll have another crack tomorrow and let you know.
Main reason I want to switch is I need much better battery life than CM10 but only temporarily. Can anyone recommend viperx as being a significant improvement?
BenPope said:
Did you restore system apps or data?
Where does it stop booting, what is on the screen?
Click to expand...
Click to collapse
It comes up with "HTC" vibrates then the viper crawls across the screen and it stops at the "htcONE" logo.
Restored apps and app data and guess what. Still doesn't boot. WHY! Going to just try apps, no data at ALL. Will report back.
I dunno why it won't start, double check you have the right boot.img (download it again and flash it again), in recovery erase cache and dalvik cache.
same issue
Hi i am also getting the same problem, i used the viper rom and others but it goes past the HTC logo looks as though it works but the lock ring is froze up and then it reboots itself over and over doing the same thing each time. Ive tried One_X_All-In-One_Kit_v1.2 and the manual CMD fastboot tutorial i dont know what to do to fix this, can anyone help me please?
EDIT* I seem to have it working now (fingers crossed), i used 'Nocturnal_Special_Edition_4.0_Odex' so thx to their good work that i now have a working rom for my phone phew
EDIT 20 MIN LAter* OK looks like i did something i shouldnt, it seemed to work, i made a change in the settings and then it rebooted and continued to reboot over and over so i tried installing a rom again and now it just stays at the htc quietly brilliant screen, what have i done this phone is now not so brilliant as its looking more and more that ive goosed it Any help apreciated.
boot.img
Help please
Hello,
I have 1x (CID 203) unlocked and rooted with cwm recovery. I had Cyanogenmod 10 nighly on it, well in hope of no bugs like in CM10 I flashed this http://forum.xda-developers.com/showthread.php?t=1763240 to it. Well it seemed to work a moment but then the device started rebooting randomly. I couldn't boot to recovery (strange?), the recovery screen flashed less than a second and the phone started to boot normally again. After a few tries (and reflashing recovery) I luckily got into the recovery. Tried to restore a nandroid backup which I made earlier yesterday. CWM said that the restore was successful but the device didnt boot anymore. Only shows htc logo and cyanogenmod loading screen. But nothing happens. Well, then I flashed Android Revolution HD 10.3. (with wiping the system data and so on) but it wont load any longer than the htc one logo screen. Rom installed fine and I flashed the boot.img.
Now I'm able to get into recovery and fastboot and charge my phone but how could I safely and surely return my phone to stock or make the ARHD work without completely bricking it? I'm thinking that relocking my device is not very safe if the RUU fails to install. What do you think? Can the firmware updates cause this problem to happen? Can I flash ARHD 9.7.2 to my device? Too bad I can't ask these questions in the ARHD thread....
In bootloader my phone says
Code:
hboot-0.94.0000
radio 1.1204.104.14
Any advice is highly appreciated, I'm not ready to bury my phone yet
Edit. ARHD 9.7.2 flashed correctly. Any ideas why the ARHD 10.3 keeps bootlooping? Yes, I have flashed the correct boot.imgs.
BenPope said:
I dunno why it won't start, double check you have the right boot.img (download it again and flash it again), in recovery erase cache and dalvik cache.
Click to expand...
Click to collapse
If I restore apps only it does boot however any sort of data and it refuses to. Very annoying as I am not able to retain texts accounts etc. I have a feeling it's because I originally backed up on a jellybean ROM and the data just doesn't want to work on ics
Squbbe said:
Hello,
I have 1x (CID 203) unlocked and rooted with cwm recovery. I had Cyanogenmod 10 nighly on it, well in hope of no bugs like in CM10 I flashed this http://forum.xda-developers.com/showthread.php?t=1763240 to it. Well it seemed to work a moment but then the device started rebooting randomly. I couldn't boot to recovery (strange?), the recovery screen flashed less than a second and the phone started to boot normally again. After a few tries (and reflashing recovery) I luckily got into the recovery. Tried to restore a nandroid backup which I made earlier yesterday. CWM said that the restore was successful but the device didnt boot anymore. Only shows htc logo and cyanogenmod loading screen. But nothing happens. Well, then I flashed Android Revolution HD 10.3. (with wiping the system data and so on) but it wont load any longer than the htc one logo screen. Rom installed fine and I flashed the boot.img.
Now I'm able to get into recovery and fastboot and charge my phone but how could I safely and surely return my phone to stock or make the ARHD work without completely bricking it? I'm thinking that relocking my device is not very safe if the RUU fails to install. What do you think? Can the firmware updates cause this problem to happen? Can I flash ARHD 9.7.2 to my device? Too bad I can't ask these questions in the ARHD thread....
In bootloader my phone says
Code:
hboot-0.94.0000
radio 1.1204.104.14
Any advice is highly appreciated, I'm not ready to bury my phone yet
Edit. ARHD 9.7.2 flashed correctly. Any ideas why the ARHD 10.3 keeps bootlooping? Yes, I have flashed the correct boot.imgs.
Click to expand...
Click to collapse
Try the fast boot erase cache command and see if that solves the boot issue. If not make sure in recovery your have cleared cache partition performed a factory reset and also cleared the dalvik cache. Again if none of these work try re flashing the boot.img or perhaps try another rom that is known to be stable.
Hey guys, this post is not for me but for a friend.
As the title already mentions, he's trying to get to stock
so the step he follows are:
Move boot.img from his stock rom nandroid backup to his fastboot folder
so lets begin
first step-> boot into bootloader
fastboot erase cache
fastboot flash boot boot.img
fastboot erase cache
--> boot into recovery
wipe data/factory reset
wipe cache
wipe delvik cache
-> back up and restore
--> restore
--- nandroid backup gets installed ---
... so far i can't see where he is doing anything wrong
so he proceeds to reboot his phone.. and now i asked him multiple times about the taken procedure and he claims his phone boots normally to the point where the wallpaper shows up and then he talks about the phone falling into a constant bootloop
What went wrong? Why is he experiencing this?
I've taken into consideration that he might be doing something wrong, but then i even wrote the steps above and he says he did it exactly that way.
i'm clueless to say the least and i hope someone here could help me help him
thank you
Try the cache clean up after the nandroid is restored.
Also try to install some other compatible kernel (if it's stock it should be also to find on the forums) after the restore with its modules if the cache clean up doesn't help.
Sent from my HTC One X using Tapatalk 2
Wipe the cache and dalvik cache again.
shadehh said:
Hey guys, this post is not for me but for a friend.
As the title already mentions, he's trying to get to stock
so the step he follows are:
Move boot.img from his stock rom nandroid backup to his fastboot folder
so lets begin
first step-> boot into bootloader
fastboot erase cache
fastboot flash boot boot.img
fastboot erase cache
--> boot into recovery
wipe data/factory reset
wipe cache
wipe delvik cache
-> back up and restore
--> restore
--- nandroid backup gets installed ---
... so far i can't see where he is doing anything wrong
so he proceeds to reboot his phone.. and now i asked him multiple times about the taken procedure and he claims his phone boots normally to the point where the wallpaper shows up and then he talks about the phone falling into a constant bootloop
What went wrong? Why is he experiencing this?
I've taken into consideration that he might be doing something wrong, but then i even wrote the steps above and he says he did it exactly that way.
i'm clueless to say the least and i hope someone here could help me help him
thank you
Click to expand...
Click to collapse
I restored my original 4.0.3 nandroid backup yesterday and got exactly the same problem coming from arhd 9.7.2 4.0.4. I want to get back to stock so I can get JB ota when its available. Mine also loaded the wallpaper and then rebooted. All I did to fix it was copy the boot.img from my nandroid backup and reflash that after I had restored again.
So the way I did it was
Boot into recovery
Full wipe
Restored rom
booted into bootloader
flash boot.img (from original nandroid)
rebooted and worked a treat
Thanks for the help guys. I mentioned all the suggestions on this thread to him and it he was able to get it running
Sent from my HTC One X using xda app-developers app
bradmax57 said:
I restored my original 4.0.3 nandroid backup yesterday and got exactly the same problem coming from arhd 9.7.2 4.0.4. I want to get back to stock so I can get JB ota when its available. Mine also loaded the wallpaper and then rebooted. All I did to fix it was copy the boot.img from my nandroid backup and reflash that after I had restored again.
So the way I did it was
Boot into recovery
Full wipe
Restored rom
booted into bootloader
flash boot.img (from original nandroid)
rebooted and worked a treat
Click to expand...
Click to collapse
OK I had the same issue and followed these steps, however when I try to flash boot.img I get an error in command prompt saying it cannot load boot.img (even though the file is copied to root of the 'sd card')
any idea what I'm doing wrong
squirrelbo1 said:
OK I had the same issue and followed these steps, however when I try to flash boot.img I get an error in command prompt saying it cannot load boot.img (even though the file is copied to root of the 'sd card')
any idea what I'm doing wrong
Click to expand...
Click to collapse
The file shouldn't be on the phone, but on the PC.
Place it in the folder in which you have your fastboot files.
oh of course. I'm being a moron again.
I cant believe I did that. so very very simple. sorry for being a numpty guys. wasn't thinking strait. Done a few custom rom installs but never flashed a backup. Didnt even think. You even have to type the directory into command prompt.sorry guys I can't believe I didn't think that. (was thinking along the lines of installing from zip way)
to be fair the only reason I'm doing all this is because my screen is playing up and I need to return it so getting everything as close to stock as possible so got other things on my mind
everything is working now. Thanks guys. My god stock rom on HTC one x from orange is ugly.
No worries mate. You're not a moron, just a beginner.
TToivanen said:
No worries mate. You're not a moron, just a beginner.
Click to expand...
Click to collapse
thanks heaps for the thread guys, this has been a great help as I'm doing a similar thing and had the same problem.
Hi everyone. Just guy my note tablet. Rooted with towlie.
Build number kot49h.p607tuvuane2
Finding a bit of confusion on which TWRP I should install. I did one with Odin, and it didn't take.
Can someone point me to right file and/or directions if i need to downgrade first?
I want to start playing and customizing, but cannot back up or reflash.
redheadplantguy said:
Hi everyone. Just guy my note tablet. Rooted with towlie.
Build number kot49h.p607tuvuane2
Finding a bit of confusion on which TWRP I should install. I did one with Odin, and it didn't take.
Can someone point me to right file and/or directions if i need to downgrade first?
I want to start playing and customizing, but cannot back up or reflash.
Click to expand...
Click to collapse
most stable version would be 2.6.3.3
buhohitr said:
most stable version would be 2.6.3.3
Click to expand...
Click to collapse
Have heard a few things about needing an Odin firmware downgrade. Is that necessary with my firmware? And should I use Odin, or ADB?
Really appreciate the info. I want to tinker, but without working recovery, I'm a bit Leary.
redheadplantguy said:
Have heard a few things about needing an Odin firmware downgrade. Is that necessary with my firmware? And should I use Odin, or ADB?
Really appreciate the info. I want to tinker, but without working recovery, I'm a bit Leary.
Click to expand...
Click to collapse
the version I stated is most stable, other twrp version may cause cache corruption and other issues.
buhohitr said:
the version I stated is most stable, other twrp version may cause cache corruption and other issues.
Click to expand...
Click to collapse
the closest release i could find was twrp 2331.
i flashed with odin. but when i tried to reboot to recovery, i got a scrambled, pixelated screen which after a few seconds rebooted system.
redheadplantguy said:
the closest release i could find was twrp 2331.
i flashed with odin. but when i tried to reboot to recovery, i got a scrambled, pixelated screen which after a few seconds rebooted system.
Click to expand...
Click to collapse
Get it here http://www.techerrata.com/browse/twrp2/lt03wifiue
You need to wipe cache, davik cache and data, then flash the rom.
buhohitr said:
Get it here http://www.techerrata.com/browse/twrp2/lt03wifiue
You need to wipe cache, davik cache and data, then flash the rom.
Click to expand...
Click to collapse
I found that version on the link, but i thought that was for the Exynos chipset.
I have the Qualcomm LTE version. Will it still work?
redheadplantguy said:
I found that version on the link, but i thought that was for the Exynos chipset.
I have the Qualcomm LTE version. Will it still work?
Click to expand...
Click to collapse
For Qualcomm LTE the version is 2.6.3.1
https://goo.im/devs/OpenRecovery/lt03ltexx/openrecovery-twrp-2.6.3.1-lt03ltexx.zip/
Hi,
This post saved me, I installed TWRP 2.8 and my system froze, I couldn't get past the Samsung 10.1 screen.
But found this post and flashed 2.6.3.3 via Odin and it all went smoothly.
PS Goo.img.com dosen't have the files anymore
buhohitr said:
For Qualcomm LTE the version is 2.6.3.1
https://goo.im/devs/OpenRecovery/lt03ltexx/openrecovery-twrp-2.6.3.1-lt03ltexx.zip/
Click to expand...
Click to collapse
I currently have no recovery. I tried flashing 2.8 originally.
How would i clear cache, data, and all before trying to flash 2631?
redheadplantguy said:
I currently have no recovery. I tried flashing 2.8 originally.
How would i clear cache, data, and all before trying to flash 2631?
Click to expand...
Click to collapse
No, you flash TWRP 2631, then boot into the twrp then select advance then put a check for cache, davik cache and data, then swipe. Once done just flash your rom. I would copy the rom to the download folder on the internal storage (/sdcard/download/) before flash your new twrp.
Is 2.6.3.3 more reliable / stable in terms of making / restoring nandroids? I just got my new Note last week (p607t) and flashed xKat with TWRP at one point, restoring apps from (some with data to avoid re-entering account info or redoing complex settings...) I have had one problem however, when I was almost done restoring, I noticed that I was getting fc's, particularly with games that required an internet connection. I wiped dalvik and cache in TWRP, then hit fix permissions, which I think screwed everything up (maybe due to the bootloader / firmware base mismatch). Anyway, my most recent nandroid was with the fresh xKat install, but fixing permissions caused this weird "hot"-bootloop where it skipped the boot animation but start loading immediately after rebooting, but then freezing before all boot tasks had completed (ex. some optimizations on boot with Android Tuner Pro, FolderMount mounting folders, loading xposed modules...)
Not wanting to re-restore, I first just tried dirty-flashing the ROM again (only wiped dalvik and cache, but did something I hadn't tried before: in the wipe menu I hit "repair partition" for system and data, pre-flash). Luckily it worked and set everything straight... but just want to make sure, 2.6.3.3 is still recommended as the most stable version (in my experience, fixing permissions in recovery can be very hit or miss on any version)?
2 questions before I roll back my recovery, I think these "killer features" (totally serious, #2 has been huge since I got a couple of the newish flash drives with micro usb on one side and regular usb on the other) of TWRP were implemented in 2.6.3.3, but just want to make sure: can you 1) compress nandroids and 2) mount a USB OTG drive and flash from or backup to it? Thanks all, really loving my new Note (massive upgrade from my Note 8!)
buhohitr said:
No, you flash TWRP 2631, then boot into the twrp then select advance then put a check for cache, davik cache and data, then swipe. Once done just flash your rom. I would copy the rom to the download folder on the internal storage (/sdcard/download/) before flash your new twrp.
Click to expand...
Click to collapse
I HAVE flashed 2631 for the qualcomm lte.
I've done or several times since you told me that's the best version.
IT WILL NOT BOOT INTO TWRP. it's a scrambled screen. That's all. No touch options. No check boxes. After a minute, tablet reboots itself. I am on stock firmware still. Rooted.
Maybe I should just try CWM. never had this much problems with twrp on any other device.
redheadplantguy said:
I HAVE flashed 2631 for the qualcomm lte.
I've done or several times since you told me that's the best version.
IT WILL NOT BOOT INTO TWRP. it's a scrambled screen. That's all. No touch options. No check boxes. After a minute, tablet reboots itself. I am on stock firmware still. Rooted.
Maybe I should just try CWM. never had this much problems with twrp on any other device.
Click to expand...
Click to collapse
How about wipe cache/davikcache/data with your stock recovery (just reflash your stock recovery). After that let it boot up, then power down and flash twrp. Once done, don't boot up, boot back to twrp . Let me know how it goes.
Cool. I can try that when I get home. Do you have a link handy for the stock recovery?
redheadplantguy said:
Cool. I can try that when I get home. Do you have a link handy for the stock recovery?
Click to expand...
Click to collapse
Please try this twrp. Many ppl reported it's working for p607t.
http://forum.xda-developers.com/showpost.php?p=53138918&postcount=776
If not working then we will go for stock recovery.
buhohitr said:
Please try this twrp. Many ppl reported it's working for p607t.
http://forum.xda-developers.com/showpost.php?p=53138918&postcount=776
If not working then we will go for stock recovery.
Click to expand...
Click to collapse
THANK YOU SO MUCH! TWRP booted right up, and nandroid in progress. now I'll be able to try some custom ROM's and play in system.
:laugh:
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.
Background:
1. Was on the latest Resurrection Remix. Made a Backup with TWRP.
2. Went back to stock [MTC20F] using this.
3. Updated to 7.0 using this threads 7.0 OTA.
4. Made a Backup in TWRP.
I restored the backup from point 1, but now my phone won't boot anymore.
It shows the boot animation for about 1 second. Goes black and reboots.
I tried restoring to 6.0.1 using the method in point 2 -> same problem.
Tried restoring to 7.0.0 using the same method -> same problem.
After that, I tried restoring from both of my TWRP backups. Neither of them get any further.
So, no matter what I do I cant get past the first second of the boot animation.
I'm out of ideas, any help is greatly appreciated!
TWRP version 3.0.2.1
MiePx3 said:
Background:
1. Was on the latest Resurrection Remix. Made a Backup with TWRP.
2. Went back to stock [MTC20F] using this.
3. Updated to 7.0 using this threads 7.0 OTA.
4. Made a Backup in TWRP.
I restored the backup from point 1, but now my phone won't boot anymore.
It shows the boot animation for about 1 second. Goes black and reboots.
I tried restoring to 6.0.1 using the method in point 2 -> same problem.
Tried restoring to 7.0.0 using the same method -> same problem.
After that, I tried restoring from both of my TWRP backups. Neither of them get any further.
So, no matter what I do I cant get past the first second of the boot animation.
I'm out of ideas, any help is greatly appreciated!
TWRP version 3.0.2.1
Click to expand...
Click to collapse
Did you boot into recovery and do a factory reset in there. Sometimes that works.
jsgraphicart said:
Did you boot into recovery and do a factory reset in there. Sometimes that works.
Click to expand...
Click to collapse
Yep, every time I try to restore something I wipe everything. Also tried to lock and unlock the bootloader. No Luck.
Also tried wipe and erasing every partition possible, flashing an older 6.0.1 build.
Am I SOL? I tried anything google would give me....
Hey, I'm currently in the very same situation. Was on 6.0.1 stock rooted, applied 7.0 OTA using the beta program. Then for various reasons wanted to roll back to where I was with 6.0.1, but now the device just constantly reboots. I have wiped everything I can, tried to flash the factory images multiple times, but nothing seems to do the trick.
same problem here
i was on rooted android n preview 5 with twrp recovery and root, i applied 7.0 ota and then it bricked
now it starts up till bootscreen with the 4 coloured dots it freezes and goes in a bootloop but fastboot and recovery working fine
flashed a factory image wiped everything tried diffrent things restored a twrp backup but nothing
now im going to try to flash 7.0 ota again
Also in the same situation :crying:. Gets to the boot animation for 1 second then freezes and restarts.
Updated to 7.0 and got stuck in a bootloop.
Then tried restoring my TWRP backup to no avail.
Then tried flashing 6.0.1 factory image and still no luck.
Done factory resets, wiped system, data partitions etc, and still same problem.
If anyone has any other ideas that would be greatly appreciated!
this is what i tried so far
-wiped and restored 3 diffrent backups
-full wipe and flashed diffrent roms
-flashed factory image 6.0 and 6.0.1
-flashed 7.0 ota zip in twrp (extracted and flashed system.img and vendor.img )
-flashed factory image and used stock recovery to flash 7.0 ota.zip trough ADB sideload
i think im going to relock the bootloader and just send it back to google for a repair
I'm on the same situation
32 hours after updating to final 7.0 from stock dp5 the device turned off and stuck on boot animation
it seems like google did something wrong...
Looks like some people with the 6P are having the same issue as well. Still no fix either.
http://forum.xda-developers.com/nexus-6p/help/botched-nougat-install-phone-boot-loop-t3445709
I've had the same problem. I was coming from from a Pure Nexus install and thought i'd have a look at 7 so I made a full backup in TWRP then installed the lastest TWRP (twrp-3.0.2-1-bullhead). Then did a full wipe all bar internal storage and flashed radio/bootloader zip and Stock+ rom from the tupac4u thread which worked fine. Upon deciding there were a few dealbreakers for me I decided to go back to PN. So I booted back into TWRP, wiped again and restored the previously made backup. that's when I was getting the boot to 4 dots and reboot bootloop. I tried everything flashing various MM roms, and flashing 7 again, different roms / vendor images / full wipes including int storage, all via TWRP and ADB to no avail.
Though this evening I decided to go to an even earlier version of TWRP (twrp-3.0.0-1-bullhead) and try everything again. I flashed that and tried the repair filesystem on all the partitons I could, one of them gave an error I can't remember what it was. After doing that I did a full wipe and restored my PN backup, everything ticked. I then rebooted with everything crossed and it worked, it booted without any problems! (apart from the fact i'd forgot to remove the pin security before backing up so had to reflash anyway! which also worked). I can't be sure which part of that fixed it but if it helps anyone else that's great!
People with this problem - Does flashing new Factory Image 7.0.0 (NRD90M) fix something?
Just curious.
zeesyl said:
People with this problem - Does flashing new factory image 7.0.0 (NRD90M) fix something?
Just curious.
Click to expand...
Click to collapse
Nope, changed nothing in my case at least. At this point I'm just going to use the warranty card to get out of this mess, as nothing seems to revive the device.
MiePx3 said:
Background:
1. Was on the latest Resurrection Remix. Made a Backup with TWRP.
2. Went back to stock [MTC20F] using this.
3. Updated to 7.0 using this threads 7.0 OTA.
4. Made a Backup in TWRP.
I restored the backup from point 1, but now my phone won't boot anymore.
It shows the boot animation for about 1 second. Goes black and reboots.
I tried restoring to 6.0.1 using the method in point 2 -> same problem.
Tried restoring to 7.0.0 using the same method -> same problem.
After that, I tried restoring from both of my TWRP backups. Neither of them get any further.
So, no matter what I do I cant get past the first second of the boot animation.
I'm out of ideas, any help is greatly appreciated!
TWRP version 3.0.2.1
Click to expand...
Click to collapse
Type fastboot -w flash falsh vendor vendor.img then restore from your twrp backups
neaznc021 said:
OMG I finally got mine to work
I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked
Let me know if it worked for you guys or if you need any more help
Click to expand...
Click to collapse
this worked for me
neree said:
Nope, changed nothing in my case at least. At this point I'm just going to use the warranty card to get out of this mess, as nothing seems to revive the device.
Click to expand...
Click to collapse
Did that yesterday (With my N6P), will see what will come out of it. (Service guys said, that ''Oh, it's nothing serious, tomorrow (today) you will get your phone back (hopefully in working condition)''. I'm not so sure about that
(EDIT: Before I took my phone to warranty service, I flashed latest MM factory image and locked bootloader, maybe it was unnecessary, but I wanted to be sure, that phone looks fresh, maybe it was a big mistake.)
I had the same Bootloop issue, and it's all because of TWRP 3.0.2-1 !!! I have just reverted back to TWRP 3.0.2-0, and my backup restored just fine. There's no point for all that flashing. Just revert the TWRP.
Oh my... Guess what? My backup is corrupted...
Edit: maybe this can help, before bricking with full factory image, I flashed bootloader, radio, boot, vendor, system, Elementalx and supersu, wiped data and booted and work.
But I had problems with suspersu installed as systemless (it didn't work), so I flashed factory image. And bootlooped.
So, I'd say that what's causing issue is userdata, recovery or cache.