I have 2 backups that I have tried to restore while using twrp 3.0. No h seem like they restore but when the phone gets to the screen where it would eventually say Android after the animation never goes away and the phone doesn't boot all the way up. Has anyone else had this problem or know a solution. When I did my back ups I backed up everything available including vendor and vendor.img. I just continue to get a bootloop and phone doesn't boot. Thank u to anyone who may help
This happened to me as well even before trwp 3.0. It worked for me once I restored only boot, system, and data.
janedoesmith said:
This happened to me as well even before trwp 3.0. It worked for me once I restored only boot, system, and data.
Click to expand...
Click to collapse
Thanks. I think I tried this how you've said but I'll try again later as I need to make sure my phone is working for now.
Since day 1 I've always backed up boot, system and data. Not sure why anyone would ever back up anything else. Takes up too much space and is unnecessary. I've never had one issue. On all past devices (all Nexus) I've always backed up boot, data and system. New twrp is great! Now we can flash vendor images!! ?
Sent from my Nexus 6P using Tapatalk
Related
Okay, I'm about to SBF my phone, which is a major PITA. So I thought I should caution other members. I was on the Rooted/DeOdex'd Gingerbread release with the ALPHA1 theme and wanted to try out RubixBlurryBread. Rubix install went fine, and booted no problem. It didn't seem like an improvement over the original leak, and actually ran slower on my phone. I thought "No biggie, I made a backup before flashing Rubix"...... wrong. I restored my backup and everything went as it always does with a backup, until the bootup. It's a backup, a 1-to-1 match of how my phone was just 30 minutes earlier, this can't be happening, but I'm stuck in a boot loop. So, even though I hate the idea, I formatted the Data and Cache. Still boot looping. Grrr... Did factory reset from standard recovery, no help. Wiped Data/Cache and reinstalled the original DeOdex'd zip from TBH.. nothing is working, everything results in a boot loop.
Anyone have any insight on this? I really don't want to have to set everything up again. I'm going to SBF, but not going to set everything up again, until I know for sure that my backup is useless, for whatever reason.
raziel36 said:
Okay, I'm about to SBF my phone, which is a major PITA. So I thought I should caution other members. I was on the Rooted/DeOdex'd Gingerbread release with the ALPHA1 theme and wanted to try out RubixBlurryBread. Rubix install went fine, and booted no problem. It didn't seem like an improvement over the original leak, and actually ran slower on my phone. I thought "No biggie, I made a backup before flashing Rubix"...... wrong. I restored my backup and everything went as it always does with a backup, until the bootup. It's a backup, a 1-to-1 match of how my phone was just 30 minutes earlier, this can't be happening, but I'm stuck in a boot loop. So, even though I hate the idea, I formatted the Data and Cache. Still boot looping. Grrr... Did factory reset from standard recovery, no help. Wiped Data/Cache and reinstalled the original DeOdex'd zip from TBH.. nothing is working, everything results in a boot loop.
Anyone have any insight on this? I really don't want to have to set everything up again. I'm going to SBF, but not going to set everything up again, until I know for sure that my backup is useless, for whatever reason.
Click to expand...
Click to collapse
just SBF, reroot, and reflash the GB leak
boot into the GB leaked than boot into recovery again
than advance restore data only
if this doesnt work than your back to square 1 with your data
raziel36 said:
Okay, I'm about to SBF my phone, which is a major PITA. So I thought I should caution other members. I was on the Rooted/DeOdex'd Gingerbread release with the ALPHA1 theme and wanted to try out RubixBlurryBread. Rubix install went fine, and booted no problem. It didn't seem like an improvement over the original leak, and actually ran slower on my phone. I thought "No biggie, I made a backup before flashing Rubix"...... wrong. I restored my backup and everything went as it always does with a backup, until the bootup. It's a backup, a 1-to-1 match of how my phone was just 30 minutes earlier, this can't be happening, but I'm stuck in a boot loop. So, even though I hate the idea, I formatted the Data and Cache. Still boot looping. Grrr... Did factory reset from standard recovery, no help. Wiped Data/Cache and reinstalled the original DeOdex'd zip from TBH.. nothing is working, everything results in a boot loop.
Anyone have any insight on this? I really don't want to have to set everything up again. I'm going to SBF, but not going to set everything up again, until I know for sure that my backup is useless, for whatever reason.
Click to expand...
Click to collapse
You have to install the rooted version first then install the deodexed zip because I believe the deodexed zip only changes some system files, I did the same thing by mistake. So unfortunately you will have to SBF but when you get back up and running just remember to flash the root only zip first then boot into recovery and you can then flash the deodexed zip, hope this helps
luigi90210 said:
just SBF, reroot, and reflash the GB leak
boot into the GB leaked than boot into recovery again
than advance restore data only
if this doesnt work than your back to square 1 with your data
Click to expand...
Click to collapse
This is what I did last night, just before going to sleep. Thankfully, it worked, so only thing I had to really do was re-apply the theme and 180 LCD Density. Cool that we had the same idea but I'm still concerned about the backup not working, because I definitely don't want to make a habit of SBF'ing any time I don't like a new ROM, though I'm probably going to wait for LibertyGB before I flash another, and I'm fairly certain I will like that one
Thanks for taking the time to read and comment, really appreciate it.
I tried to go back to my stock bg backup also. It went ok and started up but I got force close on all my blur apps. I couldn't get the fc's to stop so I also had to sbf and reload everything.
TWRP 2.5.0.0 reboots my device while performing a restore. It usually happens during the DATA phase. I've tried two different restores and the same thing happens. Thanks
If you need more detail, i'll do my best to provide.
sorryihaveaids said:
TWRP 2.5.0.0 reboots my device while performing a restore. It usually happens during the DATA phase. I've tried two different restores and the same thing happens. Thanks
If you need more detail, i'll do my best to provide.
Click to expand...
Click to collapse
I've actually been getting random freezes and reboots in TWRP myself, in the last 2 weeks or so, since I've gone flash-crazy. Have you been flashing a lot?
dibblebill said:
I've actually been getting random freezes and reboots in TWRP myself, in the last 2 weeks or so, since I've gone flash-crazy. Have you been flashing a lot?
Click to expand...
Click to collapse
I wouldn't say flash-crazy, but i've tried two different roms in the past two days. It's not really freezing either. It will just start to restore, make it half way through, and reboot. My rom will be restored but none of my data.
sorryihaveaids said:
TWRP 2.5.0.0 reboots my device while performing a restore. It usually happens during the DATA phase. I've tried two different restores and the same thing happens. Thanks
If you need more detail, i'll do my best to provide.
Click to expand...
Click to collapse
Yep, seems to be happening a lot. One suggestion was to revert to 2.4 or even 2.3.3.0. I tried that, and thought the problem was solved, but then it happened again, so I figured what the hell, I'll go back to 2.5.
You're right, it always happens during the data restore, but so far the second attempt at restoring always succeeds, so it's more annoying than anything. I can't recall it ever happening on my phone, though, so I wonder if it's a device issue. Also my phone is running JB 4.1.2 and my N10 is on 4.2.2.
Sent from my Nexus 10 using Tapatalk HD
Ive noticed this problem as well. Hopefully it will be fixed in later releases.
brGabriel said:
Ive noticed this problem as well. Hopefully it will be fixed in later releases.
Click to expand...
Click to collapse
So yesterday I went to flash a new ROM and TWRP froze immediately after doing a Factory Reset Wipe. Nexus kept bootlooping and then getting stuck on the TEAMWIN screen. Was able to get into the bootloader and flash the stock image and unroot through the Nexus Toolkit. I lost all my data though. So my question is, if you can get to bootloader mode and the toolkit recognizes it in bootloader mode, can you recover data without having to do what I did and wipe the device? For future reference sake. God I need to get better about backing up my data on my PC.
Anyone found the solution to this? I am not able to restore my data ( During the resotre in TWRP it goes blackscreen and then just reboots. I've triel like 10 times already..
ky3bmu4 said:
Anyone found the solution to this? I am not able to restore my data ( During the resotre in TWRP it goes blackscreen and then just reboots. I've triel like 10 times already..
Click to expand...
Click to collapse
I had the same issue. Its most likely a corrupt backup and can't be solved. But if you've successfully restored that backup before try reflashing the recovery. Just a tip that somebody else gave me. Use philz cwm touch recovery. It has no issues and more reliable then other recoveries.
Sent from my Nexus 10 using xda app-developers app
abdel12345 said:
I had the same issue. Its most likely a corrupt backup and can't be solved. But if you've successfully restored that backup before try reflashing the recovery. Just a tip that somebody else gave me. Use philz cwm touch recovery. It has no issues and more reliable then other recoveries.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Yes, i'm thinking the same. Maybe it also because the backup was huge (maybe like 4 gb).
But I am not really sure if it is corrupted because the system restores fine and data do not, but it fails in different places, i.e. it may reboot in 30 seconds and may reboot in 2 minutes...
So I just tried to flash the newest PA build, and now my phone won't boot...suggestions?
shredder47 said:
So I just tried to flash the newest PA build, and now my phone won't boot...suggestions?
Click to expand...
Click to collapse
are you coming from another rom, did you wipe data? redownload and try again? reflash your previous rom? restore a nandroid backup?
simms22 said:
are you coming from another rom, did you wipe data? redownload and try again? reflash your previous rom? restore a nandroid backup?
Click to expand...
Click to collapse
I wiped data, and I don't have a previous ROM or nandroid to go back to, because I (stupidly) wiped EVERYTHING last night, and I've been working on fixing it since then .... I'm currently booted to recovery though, and I may just push a new ROM to it and try again
says my SD card is read only? trying to remount it as rw
I ended up having to reflash all the stock images...
could be worse.
keep a copy of your latest running rom/kernel/gapps in your storage, for just in case. thats my normal procedure, if you dont want to keep a nandroid backup in your storage, because of its size. but a nandroid backup would be ideal
Having the same issue. Tried installing new Carbon nightly (with factory reset) and didn't boot past Google logo. After that I restored my nandroid, which lasted for about a day or two. Today I started getting force closes and phone won't boot. Now I'm backing up everything (ADB rules ) and will try stock image.
Dont feel bad. When twrp updated I didn't notice wipe internal as I usually wipe all but USB in bottom but it was too late. I had swiped my finger and lost everything. Worse? My computer crashed. So RMA backordered so I bought new s2 for backup. I have to fix before sending back. But its not broken. All asurion does is push files and make sure it boots. They wipe everything. So I did most of the job for them lol. I feel stupid as I've never had a problem in four years. Bam I got too far comfy and forgot the twrp updated and had no idea what was added. I will just find a computer and fix or they will get a wiped device with twrp lol not that I think they will do anything as I've heard far worse but I did it so I'll pay if they mention.
Sent from my Nexus 4 using xda premium
Mostly just out of curiosity I flashed a new ROM this weekend. I decided I like pure nexus better so I flashed my backup from twrp but wound up in bootloop. Even though I've never had issues restoring ROMs with MANY other devices, I still followed the directions for backing it up very carefully. I also did a full wipe before trying to restore it. In fact after the 3rd attempt I accidentally wiped internal storage. So that wasn't the issue.
Only thing I can figure is I was using elemental kernel when I made the backup so maybe that was the problem? I don't see why it would matter (or how that would work--removing the kernel, make backup, flash kernel again...) but I'm really stumped on how I went wrong.
KLit75 said:
Mostly just out of curiosity I flashed a new ROM this weekend. I decided I like pure nexus better so I flashed my backup from twrp but wound up in bootloop. Even though I've never had issues restoring ROMs with MANY other devices, I still followed the directions for backing it up very carefully. I also did a full wipe before trying to restore it. In fact after the 3rd attempt I accidentally wiped internal storage. So that wasn't the issue.
Only thing I can figure is I was using elemental kernel when I made the backup so maybe that was the problem? I don't see why it would matter (or how that would work--removing the kernel, make backup, flash kernel again...) but I'm really stumped on how I went wrong.
Click to expand...
Click to collapse
What partitions did you backup/restore?
Heisenberg said:
What partitions did you backup/restore?
Click to expand...
Click to collapse
Well Ive got the right guy to talk to Pretty sure it was what you suggested (system/data/boot/vendor boxes)
But I don't recall if I checked everyone to restore. However, I did store the backup on my computer. Even though I've since got everything back I can try again to restore it. But can you just confirm which I should check when I restore it?
I'll be certain to pay closer attention next time. Its just that this is one thing I had never struggled with. Thanks
KLit75 said:
Well Ive got the right guy to talk to Pretty sure it was what you suggested (system/data/boot/vendor boxes)
But I don't recall if I checked everyone to restore. However, I did store the backup on my computer. Even though I've since got everything back I can try again to restore it. But can you just confirm which I should check when I restore it?
I'll be certain to pay closer attention next time. Its just that this is one thing I had never struggled with. Thanks
Click to expand...
Click to collapse
I recommend restoring system, data, boot, and vendor. Just make sure you're not restoring system image or vendor image.
Heisenberg said:
I recommend restoring system, data, boot, and vendor. Just make sure you're not restoring system image or vendor image.
Click to expand...
Click to collapse
So simple. Thanks a lot!
KLit75 said:
So simple. Thanks a lot!
Click to expand...
Click to collapse
Let me know if you get it booting.
Heisenberg said:
Let me know if you get it booting.
Click to expand...
Click to collapse
Well yes. Thanks again. However, I've got something funky going on. Pin pointing is hard but yea the backup restored. Then I tweaked elemental kernel (nothing crazy, used stable profiles) maybe it was that and an xposed mod (thinking ifont because its one I only just started using lt recently). Anyway when I rebooted to install drivers for viper I got stuck in bootloop. This time I couldn't restore my backup. So I factory reset and reflashed pure nexus. Due to the time I couldn't try and restore the backup again but will try tonight. If I wasn't so hasty I could've deleted the modules list in twrp then maybe booted up but I'm not 100% it has anything to do with xposed. One other factor, it was using dark stock theme.
EVERYTHING I mentioned I've done/run on this ROM without issues but there's a combination of things that's causing the bootloop I think.
Hi guys, little issue here with nandroid backups. I've been using the 6p since it's release and have tried about 5 different Roms. I like switching between them monthly or weekly, but every time I attempt a nandroid restore, I get a boot loop. Every time. I'm using twrp recovery, and when I go into backup, I just leave the default ones chosen, but I've even tried choosing all of them. The boot loop goes on for over 10 minutes before I power it down. I've tried wiping the phone, minus storage, I've tried restoring without wiping and both fail.
Can anyone here tell me what I might be doing wrong? I've looked around for guides but they all seem to work without issue for everyone.
Edit: maybe if someone can write me a simple guide on how to do a nandroid or link me to one in case I missed a step, although it seems pretty straight forward, I'd appreciate it
Robertdudeman said:
Hi guys, little issue here with nandroid backups. I've been using the 6p since it's release and have tried about 5 different Roms. I like switching between them monthly or weekly, but every time I attempt a nandroid restore, I get a boot loop. Every time. I'm using twrp recovery, and when I go into backup, I just leave the default ones chosen, but I've even tried choosing all of them. The boot loop goes on for over 10 minutes before I power it down. I've tried wiping the phone, minus storage, I've tried restoring without wiping and both fail.
Can anyone here tell me what I might be doing wrong? I've looked around for guides but they all seem to work without issue for everyone.
Edit: maybe if someone can write me a simple guide on how to do a nandroid or link me to one in case I missed a step, although it seems pretty straight forward, I'd appreciate it
Click to expand...
Click to collapse
All you need for a backup is system, data, and boot if that's what you're doing it might be you need to flash the vendor
I'm having this issue as well. Maybe we can work together to narrow it down. This happens every time and the only reason can currently think of is that I may need to remove the fingerprint and pin security before the backup. My question to you is, have you tried disabling lockscreen security before backing up?
Robertdudeman said:
Hi guys, little issue here with nandroid backups. I've been using the 6p since it's release and have tried about 5 different Roms. I like switching between them monthly or weekly, but every time I attempt a nandroid restore, I get a boot loop. Every time. I'm using twrp recovery, and when I go into backup, I just leave the default ones chosen, but I've even tried choosing all of them. The boot loop goes on for over 10 minutes before I power it down. I've tried wiping the phone, minus storage, I've tried restoring without wiping and both fail.
Can anyone here tell me what I might be doing wrong? I've looked around for guides but they all seem to work without issue for everyone.
Edit: maybe if someone can write me a simple guide on how to do a nandroid or link me to one in case I missed a step, although it seems pretty straight forward, I'd appreciate it
Click to expand...
Click to collapse
stryver said:
I'm having this issue as well. Maybe we can work together to narrow it down. This happens every time and the only reason can currently think of is that I may need to remove the fingerprint and pin security before the backup. My question to you is, have you tried disabling lockscreen security before backing up?
Click to expand...
Click to collapse
You're most likely selecting the wrong options when creating the backup. There's a section dedicated to nandroid backups in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
This helped a lot, thank you.