Issues with restoring recovery using TWRP-3.0.2-0 - Nexus 6P Q&A, Help & Troubleshooting

I'm having issues with restoring the factory image of stock Android 6.0.1, I'm using
 @Heisenberg guide to create the fresh back up image on TWRP-3.0.2-0. Once I create
the back up, I boot into the OS and perform a factory reset, when i do that the phone resets
into TWRP, and performs the wipe to the device, when i go to do the restore, it freezes
at about 39%, and reboots fully trying to enter the OS, but its corrupt due to TWRP restarting
in the middle of the recovery.
I did at one point upgrade to Android N, but reverted back to android 6.0.1 if that makes a difference.
TL;DR - Created a fresh factory image of 6.0.1 using TWRP, cannot recover with it, TWRP freezes at 39% every time.

What options are you selecting to backup/restore?

Heisenberg said:
What options are you selecting to backup/restore?
Click to expand...
Click to collapse
I'm doing a back up selecting the system/data/boot/vendor boxes, leaving everything else unchecked, and a second back up with only the EFS,
When i go to restore, I'm just using the first back up, leaving the EFS alone unless ever needed, and am selecting the system/data/boot/vendor boxes

DeathSentinels said:
I'm doing a back up selecting the system/data/boot/vendor boxes, leaving everything else unchecked, and a second back up with only the EFS,
When i go to restore, I'm just using the first back up, leaving the EFS alone unless ever needed, and am selecting the system/data/boot/vendor boxes
Click to expand...
Click to collapse
I can only think that your backup is corrupt. Also, instead of booting into Android and performing a factory reset that way, just go into the advanced wipe section of TWRP and wipe only data. Maybe you'll just need to flash the factory images to get the phone booting up fresh again.

That's where it gets interesting, I've flashed the factory 6.0.1 image, then flashed twrp, created the back up again, did the advanced wipe as you said, did the restore again, and same result, at around 39% of the recovery the phone reboots and the back up gets corrupt. My main goal is to make sure this back up absolutely works before I root and start playing around with flashing xposed modules, but I'm unable to do a successful restore for the life of me.

DeathSentinels said:
That's where it gets interesting, I've flashed the factory 6.0.1 image, then flashed twrp, created the back up again, did the advanced wipe as you said, did the restore again, and same result, at around 39% of the recovery the phone reboots and the back up gets corrupt. My main goal is to make sure this back up absolutely works before I root and start playing around with flashing xposed modules, but I'm unable to do a successful restore for the life of me.
Click to expand...
Click to collapse
I'm stumped, I really don't know why it wouldn't be working if you're performing the backup the way you say you are. Sorry I can't be more helpful. If it's any consolation, a backup probably isn't strictly necessary because you can always get back to stock by flashing the factory images.

Heisenberg said:
I'm stumped, I really don't know why it wouldn't be working if you're performing the backup the way you say you are. Sorry I can't be more helpful. If it's any consolation, a backup probably isn't strictly necessary because you can always get back to stock by flashing the factory images.
Click to expand...
Click to collapse
I'm stumped too, I've been able to do this effortlessly in the past with this phone, my Nexus 9 and m8 GPE, it wasn't until I upgraded to N and reverted back to 6.0.1 this started to happen. I've even gone as far as trying different versions of twrp, but have had the same result.
I'm just worried in a worst case scenario I'm away from a comp, something crashes and I can't do a restore via twrp, I could be SOL until I get to a comp with adb.

i had a similiar problem , but when i got into the stock image , i went into settings and did a factory reset from there , no worries your BL stays unlocked , once thats done get whatever apps you want back , disable fingerprint /security junk , then boot into bl just like the guide says , youll be able to fastboot install recovery , (boot back into bl, then scroll to recovery and start a gain) then make your backups yor OG & EFS , then reboot , get su reboot into recovery install and yould be be fine , i think you can also try fastboot format userdata , as well

DeathSentinels said:
I'm stumped too, I've been able to do this effortlessly in the past with this phone, my Nexus 9 and m8 GPE, it wasn't until I upgraded to N and reverted back to 6.0.1 this started to happen. I've even gone as far as trying different versions of twrp, but have had the same result.
I'm just worried in a worst case scenario I'm away from a comp, something crashes and I can't do a restore via twrp, I could be SOL until I get to a comp with adb.
Click to expand...
Click to collapse
Just keep a ROM zip + gapps on your phone at all times, if you run into trouble you can flash that.

That definitely makes sense , i always dk that
Sent from my Nexus 6P using XDA-Developers mobile app

Related

Can't wipe or make any changes. Reverts on reboot!

I cant make any changes to my phone. Every time I reboot it reverts back to the state it was this morning. I'm on CM7.
My phone was crashing today, so I decided to do a wipe, however on reboot everything reverts back to the state it was this morning.
I tried doing a nandroid restore using TWRP. Restore completed successfully, but everything reverts back to today's state on reboot.
I tried wiping everything in TWRP, but on reboot everything is reverted as if i had not done anything
Thinking TWRP was the problem i installed clockworkmod and did multiple wipes, but on reboot everything reverted
I have tried doing a Format system, data, etc and no matter what everything reverts back on reboot
I tried re-installing CM7, but again everything reverts back
I tried installing CM9 and it would not boot at all. I then re-installed CM7 and when i rebooted everything reverted to today's state.
Even if i uninstall an app, remove widgets, or anything, on reboot everything reverts back
When I try to wipe using system settings, I get the following error message "Invalid Path: null"
At this point I'm out of ideas. I want to do a full wipe and do a fresh rom flash. Any thoughts would be appreciated.
One more detail. I set the alarm on the phone for 7:00am last night, however the alarm went off at 6:30am which was the time I set it to the night before. I assume the phone rebooted on its own during the night and set the alarm back to what it was the day before. Thanks in advance if anyone has some insight.
No idea what the hell is going on with the phone.
Full wipe and flash the official factory images onto your phone with fastboot. They are here. https://developers.google.com/android/nexus/images
Guides on how to do it are on these forums....
albundy2010 said:
No idea what the hell is going on with the phone.
Full wipe and flash the official factory images onto your phone with fastboot. They are here. https://developers.google.com/android/nexus/images
Guides on how to do it are on these forums....
Click to expand...
Click to collapse
I didn't try fastboot yet. I'll try that when I get home. Thanks
I just performed a wipe via fastboot and tried installing a rom via fastboot. I got successful messages, but open reboot everything reverted back. At this point I don't know what to do.
Installing a ROM via fastboot? What exactly did you do?
albundy2010 said:
Installing a ROM via fastboot? What exactly did you do?
Click to expand...
Click to collapse
I actually just did the wipe via fast boot then installed the rom via clockwork. I performed the fastboot -w command.
I also just flashed Twrp again. Mounted the SD card, deleted all files on the SD card. SD card showed full capacity. I then unmounted and remounted and all files returned. I dont get any errors in clockwork or twrp yet they are unable to do anything and have it stick.
Within the rom i mounted The SD card and deleted all my files in windows. I took about 15 seconds and everything looked clear. I then unmounted and mounted again and all files appear. Its almost like i don't have write access to the phone, but there are zero error messages during deletes and wipes
Only thing left to try is stock screwing around with a ROM / cmw etc and flash factory images with fastboot.
Sounds like it may not work but try it. Was your device encrypted?
Can try a fastboot OEM lock and unlock and flash back all factory images. If that don't work you're Sol I suppose. Could try odin but if fastboot flash factory images dont work I don't see that working either.
It sounds like the sd card becomes read-only

[Q] Restoring Note 3prior backup causes Red Verizon hang screen

Recently installed Hyperdrive Rom on my Verizon Note 3. SM-900V, NC4, running KK 4.4.2 prior to this installation.
Followed instructions re flashing back to NC2, Rom installed, everything is good,
BTW, as a part of the process installed SafeStrap, which provided a nice TWRP related recovery.
Did as suggested, a backup through recovery.
subsequently, made a couple of other changes, making a new backup through recovery each time. At present, there are three recoveries in backup.
Now comes the problem...........Decided to restore a prior backup, as instructed, did the full wipe using SS recovery, selected restore file desired, all went well and rebooted phone, only to have it hang once it reached the Bright Red Verizon screen.
Rebooted to recovery, followed the above procedure two other times on the remaining two backups. Same results.
Have wiped (Factory reset) each time in recovery with no apparent success.
Is this now being caused by the fact that I'm @ NC2, rather than NC4?
Would appreciate any suggestions as how I can get back to being able to restore and use any of the prior backups.
As a temporary measure, I went into recovery and reinstalled the Hyperdrive rom but would like to be able to go back in time if possible, and for no other reason to be able to understand just exactly what is causing this issue. Perhaps others have the same and have resolved in some way. A Google search shows that some are suggesting a return to factory settings, i.e. a full wipe through recovery, however I've done that with no success.
Another question, what happens if I also "wipe" the system files as well as dalvic, cache and data? Have hesitated to do that for fear of the unknown consequences
Bump
Kicking Deuce on the Beast, Note 3
sacgeek said:
Recently installed Hyperdrive Rom on my Verizon Note 3. SM-900V, NC4, running KK 4.4.2 prior to this installation.
Followed instructions re flashing back to NC2, Rom installed, everything is good,
BTW, as a part of the process installed SafeStrap, which provided a nice TWRP related recovery.
Did as suggested, a backup through recovery.
subsequently, made a couple of other changes, making a new backup through recovery each time. At present, there are three recoveries in backup.
Now comes the problem...........Decided to restore a prior backup, as instructed, did the full wipe using SS recovery, selected restore file desired, all went well and rebooted phone, only to have it hang once it reached the Bright Red Verizon screen.
Rebooted to recovery, followed the above procedure two other times on the remaining two backups. Same results.
Have wiped (Factory reset) each time in recovery with no apparent success.
Is this now being caused by the fact that I'm @ NC2, rather than NC4?
Would appreciate any suggestions as how I can get back to being able to restore and use any of the prior backups.
As a temporary measure, I went into recovery and reinstalled the Hyperdrive rom but would like to be able to go back in time if possible, and for no other reason to be able to understand just exactly what is causing this issue. Perhaps others have the same and have resolved in some way. A Google search shows that some are suggesting a return to factory settings, i.e. a full wipe through recovery, however I've done that with no success.
Another question, what happens if I also "wipe" the system files as well as dalvic, cache and data? Have hesitated to do that for fear of the unknown consequences
Click to expand...
Click to collapse
I am essentially having the same problem. I am currently running on Biggins ROM and that had me install a unified verision of the NC2 and NC4 kernels (I came from NC4 prior to flashing). I wanted to go back to stock root and flashed my backup from SS, everything went well so I restarted and just like you the phone just never went passed the Verizon logo screen. So I reinstalled the Biggins ROM and it works fine now but I also want to know what I have to do when I want to install other ROMS or simply go back to stock root.

TWRP sayd system not mounted, then rebooted during restore, phone is softbricked

I was bootloader unlocked, latest TWRP installed, systemless root with SuperSU 2.6, cataclysm rom, ex kernel, layers, xposed. I had made a ton of backups and even kept some of them backed up in another locations. I needed to restore a backup in TWRP. At first it wouldn't let me, kept saying that phone system was mounted as read only.
this is my question #1 - How do you mount system for read in TWRP? I see there's an option called "mount," I go in there, i see settings I can select, but I don't see any option to "execute" or "apply" settings (like TWRP has on other screens - swipe to backup, swipe to restore, etc). There's no "clicke here to mount option." what do you do here?
#2 - it finally mounted rw, i think, but after picking my latest backup, it started and then when it got to 19% it reboot the phone. Phone is softbricked.
#3 - I'm very confused about all the checkboxes to restore, and all the checkboxes to wipe.
What should I be wiping and what should I be restoring? When making backups I checked all the boxes.
I had the galaxy nexus before and I knew that phone and clockworck mod inside out. TWRP is confusing and glitchy to me. I'm stuck and work with a phone without an OS and I'm starting to freak out, and don't have A to C cables with me.
Please explain where I went wrong here and how to do things correctly. I want to understand what I'm doing better, not just follow steps.
When you restored, with all the check boxes did you click "system image" for restore?
You should wipe then restore only system, data, and boot.
dontbeweakvato said:
When you restored, with all the check boxes did you click "system image" for restore?
You should wipe then restore only system, data, and boot.
Click to expand...
Click to collapse
Yes, I selected all the boxes, including system image I believe.
I did a wipe. I selected all the boxes. Went back into TWRP and now all my backups are gone. I said reboot, and TWRP said there's no OS installed. I think I deleted everything. I should not have wiped. I do have a backup saved on a computer, it's a folder with lots of .img files inside. How can I get that onto my phone with only having fastboot and TWRP modes available? I mean how can I place it on the phone in a way that TWRP would recognize it and restore from it.
I ended up just flashing the stock google image and that at least gave me a working phone back.
Yes. You beat me to it, that's what I was going to say. You have to reflash. Just remember for future references you only need to backup boot, system, and data( and efs etc). But Not "system image" that'll Bork your stuff up.
dontbeweakvato said:
Yes. You beat me to it, that's what I was going to say. You have to reflash. Just remember for future references you only need to backup boot, system, and data( and efs etc). But Not "system image" that'll Bork your stuff up.
Click to expand...
Click to collapse
I'd like to really understand this better. Do you know why system image borks the phone? Also, when you say efs etc., do you mean "absolutely everything except system image"? (I actually didn't see EFS listed there)
Well boot system and data. But you also need efs cause thats your imei. So just look around and familiarize with what youve found so far. Right now Im trying to flash 6.0.1 with a systemless root. Its kinda goin ridiculous right now because there aren't any directions or suggestions.
If you get to "no OS installed" restoring system image, then system will get you back
Sent from my Nexus 6P using Tapatalk
zgroten said:
If you get to "no OS installed" restoring system image, then system will get you back
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
After it said no OS installed, I tried to restore system image from my TWRP backup, and the restore failed and the phone reboot itself at 19% restored. I had to ADB flash the factory system image from google. This brings me back to the original question.
Why was the restore in TWRP failing?
Did you mount system in TWRP before attempting to restore?
Sent from my Nexus 6P using Tapatalk
mistermojorizin said:
After it said no OS installed, I tried to restore system image from my TWRP backup, and the restore failed and the phone reboot itself at 19% restored. I had to ADB flash the factory system image from google. This brings me back to the original question.
Why was the restore in TWRP failing?
Click to expand...
Click to collapse
actually in twrp you could of wiped, then restored boot, system , data and it would of restored everything

restore from backup fails

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?

How do you go from a custom rom back to OOS?

Love this phone, but using custom roms have been the most frustrating thing with this device. I like testing out multiple roms because you never know which one you will enjoy until you actually use it. But every time I want to go back to OOS, I find myself having to use the MSM tool and start from scratch.
TWRP Nandroid backups are pretty much useless it seems. There are probably over 20 methods here explaining how to backup and restore (don't restore vendor, don't restore system, etc...). I have tried literally every combination and every time I restore, it never works and just loops back to TWRP and leaves me w/an encrypted device. Bring in the MSM.
Flashing the full stock rom usually results in the same thing or no change at all.
Does anybody have a simple straight to the point method of going back to OOS from custom rom? Much appreciated
msmdownloadtool will 100% wipe the phone (backup!!) And return the phone to 100% stock with OxygenOS and even re-lock the bootloader. That's the fastest and easiest way and I've done it a few times.
Edit : just fully read your post and you're familiar with MSM. Just use Google cloud backup in combination with backing up files and using sms backup and restore... There is no way you can keep your data partition from a custom ROM and have it boot or work right on OOS. Even switching custom ROMs without wiping data can cause massive instability, but at least it has a chance at booting.
How to restore,I have no real clue, but to get back to at least a working version of OOS with your internal storage intact..
After you flash OOS and twrp installer, reboot back to twrp.. it will likely be encrypted.. from there go to the wipe menu, then swipe for factory reset.. wipes data, not internal storage.. then boot into OOS.. at that point you can boot back to twrp and flash magisk or whatever else you need to do.
If that fails, you'll lose all data doing this next step, but it will boot.. use the "format data" option in twrp, type yes, then reboot to system. Then you can set it up, download or transfer whatever you want to flash, then reboot to recover and flash away... All without having to use the msm tool

Categories

Resources