TWRP stuck at 101% while doing a nandroid backup. - Galaxy Note 3 Q&A, Help & Troubleshooting

As the title states when I perform a nandroid backup with TWRP 3.0.2-1 it gets stuck at 101% and I have to hard reset the phone.
I'm running ressurection with android 6.0.1

Have you tried using older version of TWRP?

audit13 said:
Have you tried using older version of TWRP?
Click to expand...
Click to collapse
I used TWRP manager and it worked, it took about an hour but it worked.
I wasn't working from within the recovery for some reason.

Related

My phone won't boot after installing a ROM

I was having issues with my phone not getting a GPS fix. So, I figured I'd try a few different ROMs. I was on this rom, http://forum.xda-developers.com/showthread.php?t=2771110, and everything worked great except the GPS. I then did a TWRP backup and installed Cyanogen 11. It booted fine into it, but I still couldn't get a GPS lock. So, I thought, maybe it's a kitkat issue with my phone. So, I tried installing this rom, http://forum.xda-developers.com/showthread.php?t=2595586, after doing a full wipe except for internal storage. It sat at "formatting", as the OP says it may, but it finally finished. Then, it wouldn't boot. It just sat at the LG logo screen. I went back into TWRP and tried a few wipes (cache, dalvik, and data), but it still wouldn't boot. So, I decided to restore my TWRP backup of Lam Hoang 7.1, and now it is still stuck at the LG logo, and won't boot.
Any help would be appreciated!
Try a different recovery. I'd start with Philz recovery. After flashing Philz recovery I'd reflash the most recent ROM listed in your second link. In my experience twrp has given me quite the trouble. Good luck.
Sent from my SAMSUNG-SGH-I317.
CharliexCharger said:
Try a different recovery. I'd start with Philz recovery. After flashing Philz recovery I'd reflash the most recent ROM listed in your second link. In my experience twrp has given me quite the trouble. Good luck.
Sent from my SAMSUNG-SGH-I317.
Click to expand...
Click to collapse
Can I restore a TWRP backup with Philz recovery?
ledvedder said:
Can I restore a TWRP backup with Philz recovery?
Click to expand...
Click to collapse
Not that I've ever been made aware of.
Sent from my SAMSUNG-SGH-I317.
ledvedder said:
Can I restore a TWRP backup with Philz recovery?
Click to expand...
Click to collapse
Yes you can but you cannot restore a philz backup with twrp
Sent from my Potato powered G2 D800
How? When I go into restore backup in Philz and select my backup, it just shows me a bunch of files (some with a .md5 extension).
I got it back up. Flashed Philz and installed a rom. Then, I restored one of my backups, and it booted fine.
ledvedder said:
I got it back up. Flashed Philz and installed a rom. Then, I restored one of my backups, and it booted fine.
Click to expand...
Click to collapse
Awesome. Twrp just seems buggy from time to time.
Sent from my SAMSUNG-SGH-I317.
Still have no GPS though. I wish I knew why, because it used to work fine.

[Q] TWRP with Lollipop

Hi All,
Wondering if anyone is having this issue.
Flashed Lollipop with NRT on Nexus 4.
When using ROM Manager, trying to backup current ROM.
Boots to TWRP, but it cannot find the 'sd-ext' partition.
Proceeds to do a backup but the file is corrupt.
Also tried to backup right from TWRP, same issue.
Using latest version of TWRP.
I also reset to factory and cleared cache .... same issue.
Thanks,
Malcolm
Hmmmm, I'd reflash TWRP and stop using Rom manager.
Nicknoxx said:
Hmmmm, I'd reflash TWRP and stop using Rom manager.
Click to expand...
Click to collapse
Using TWRP Manager, I installed 2.8.2.0.
Same problem even if I boot into TWRP and try to do backup from there.
Any other app to replace ROM Manager suggestions?

Can't boot into recovery

My N10 with stock 5.1 previously had root with TWRP 2.8.6, but for some reason it recently lost root. In addition, it seems that TWRP has been corrupted because whenever I try to boot into recovery I get a dead bootloader with a red exclamation mart. After I flashed the most recent version of TWRP 3.0.0-1 using "fastboot flash recovery twrp-3.0.0-1-manta.img" (bootloader still unlocked), I still get a dead bootloader when booting into recovery.
Then I flashed back to TWRP 2.8.6, but the problem remains!
How to fix the problem? Thanks!
I hope you can go to bootloader mode... Revert to stock by flashing the factory images and then start over again
nitin.chobhe said:
I hope you can go to bootloader mode... Revert to stock by flashing the factory images and then start over again
Click to expand...
Click to collapse
Thanks!
Just flashed an even older version (2.8.5) of TWRP, and now suddenly it can boot into recovery without any problem. I have also gained root now after flashing SuperSU.
I was planning to flash the most recent version of TWRP (3.0.0-1), and then try out CM13, but for some reason my N10 with stock 5.1 does not like those newer versions of TWRP. Do you know why?
mj56gt said:
Thanks!
Just flashed an even older version (2.8.5) of TWRP, and now suddenly it can boot into recovery without any problem. I have also gained root now after flashing SuperSU.
I was planning to flash the most recent version of TWRP (3.0.0-1), and then try out CM13, but for some reason my N10 with stock 5.1 does not like those newer versions of TWRP. Do you know why?
Click to expand...
Click to collapse
No, I do not konw that. Are you flashing correct version of TWRP made for manta?
nitin.chobhe said:
No, I do not konw that. Are you flashing correct version of TWRP made for manta?
Click to expand...
Click to collapse
I downloaded all the three versions (2.8.5, 2.8.6, and 3.0.0-1) of TWRP I've flashed so far from here:
https://dl.twrp.me/manta/
This is weird. Is it because I didn't have root during the time I flashed 2.8.6 or 3.0.0-1? I thought that flashing TWRP would not require root.
Can I flash CM13 with TWRP 2.8.5? I'll definitely make a Nandroid backup before proceeding.
mj56gt said:
I downloaded all the three versions (2.8.5, 2.8.6, and 3.0.0-1) of TWRP I've flashed so far from here:
https://dl.twrp.me/manta/
This is weird. Is it because I didn't have root during the time I flashed 2.8.6 or 3.0.0-1? I thought that flashing TWRP would not require root.
Can I flash CM13 with TWRP 2.8.5? I'll definitely make a Nandroid backup before proceeding.
Click to expand...
Click to collapse
With nandroid, you are good to go.
Should be possible :fingers-crossed:
nitin.chobhe said:
With nandroid, you are good to go.
Should be possible :fingers-crossed:
Click to expand...
Click to collapse
I did factory reset in TWRP 3.0.0-1 and then flashed CM 13.0-20160309 on my N10 with the dynamic Gapps. Now I get this error Unfortunately Google Play Services Has Stopped. Is it because the default factory reset is not good enough or something else? If it needs a full wipe, what exactly should I wipe, system and data? And after a full wipe, do I need to reflash CM13 or just Gapps?
Thanks!
mj56gt said:
I did factory reset in TWRP 3.0.0-1 and then flashed CM 13.0-20160309 on my N10 with the dynamic Gapps. Now I get this error Unfortunately Google Play Services Has Stopped. Is it because the default factory reset is not good enough or something else? If it needs a full wipe, what exactly should I wipe, system and data? And after a full wipe, do I need to reflash CM13 or just Gapps?
Thanks!
Click to expand...
Click to collapse
Problem solved: Just flashed the pico Gapps, and now everything works fine. For some reason the dynamic Gapps didn't work for me.
mj56gt said:
Problem solved: Just flashed the pico Gapps, and now everything works fine. For some reason the dynamic Gapps didn't work for me.
Click to expand...
Click to collapse
May be there isn't enough space to flash them.
Happy that is working now
Sent from my Nexus 4 using XDA Free mobile app

Phone won't boot after flashing the SuperSU - SOLVED

Hi!
EDIT: Never mind, problem solved. Sorry.
I have finally decided to root my G900F (6.0.1). I flashed TWRP through Odin without problems, booted to TWRP to make it permanent, booted normally to check that all is well. After that I made a full backup in TWRP and flashed the BETA-SuperSU-v2.49.zip. After that, my phone no longer boots (hangs on the Galaxy S5 screen with a blue indicator LED).
I can still boot to TWRP.
How can I fix my phone? Please help. What did I do wrong?
I did try wiping the cache partition but nothing else.
Hopefully the solution does not require a full wipe.
EDIT: I see what I did wrong. I have accidentally flashed an old SuperSU.
Can I use a backup I made with a TWRP?
EDIT2: Luckily the restore did work! Will try to flash a more recent SuperSU.
flash it again but with latest version of supersu. It will work
Spawnknight said:
flash it again but with latest version of supersu. It will work
Click to expand...
Click to collapse
Yup, it did work beautifully. Lucky for me that I remembered to make a backup before rooting.

Cannot boot into recovery

Been using NRT and since restoring I cannot reboot into recovery.
I flashed TWRP 3.2.1 supposedly but anyone I try now I'm getting the dead Android icon
Any ideas? Trying to flash latest TWRP to try out NZh54D ROM
lilk1d777 said:
Been using NRT and since restoring I cannot reboot into recovery.
I flashed TWRP 3.2.1 supposedly but anyone I try now I'm getting the dead Android icon
Any ideas? Trying to flash latest TWRP to try out NZh54D ROM
Click to expand...
Click to collapse
NM i wasnt rooted it appears. After rooting w/ NRT. I've got things working again.

Categories

Resources