I got the Note 3 the day it released, but doing a nandroid restore caused a bootloop that I never was able to recover from.
Has anyone else had any issues like this at all with nandroid restores/backups?
Anything odd that caused bootloops?
Has anyone successfully done nandroid backups and restores with no issues at all?
I want to get the Note 3 again, but I want to make sure noone else experienced this issue before I get it.
I want to make sure everyone is fully able to do nandroid backups and restores using twrp just fine with this phone?
This broke my last one, but if anyone can vouch for this working I might try it again. Also, does titanium backup restores work now? They didn't when it first came out.
talktojer said:
I want to get the Note 3 again, but I want to make sure noone else experienced this issue before I get it.
I want to make sure everyone is fully able to do nandroid backups and restores using twrp just fine with this phone?
This broke my last one, but if anyone can vouch for this working I might try it again. Also, does titanium backup restores work now? They didn't when it first came out.
Click to expand...
Click to collapse
no I had the same problem had to return it . try odin back to stock tryed reroot tried new rom . just wouldn't pick up recovery just got my new one and stuck again. so trying to flash update to mj4 and still not working
talktojer said:
Has anyone successfully done nandroid backups and restores with no issues at all?
Click to expand...
Click to collapse
Works fine for me; between TWRP 2.6.3.7 and the newest version of Titanium Backup I have no issues restoring backups and/or apps
Sent from my SM-N900P using Tapatalk 2
rpenrod23 said:
Works fine for me; between TWRP 2.6.3.7 and the newest version of Titanium Backup I have no issues restoring backups and/or apps
Sent from my SM-N900P using Tapatalk 2
Click to expand...
Click to collapse
ditto for me....initially it did...but all is well now...
Try this: http://forum.xda-developers.com/showthread.php?t=2514434
Sent from my SM-N900P using Tapatalk
Related
OK, I'm having an odd issue with my phone. After flashing ICZenwich rc1.4 I decided to restore a backup I made of rc1.3. However it won't properly restore... I keep getting this in CWR...
Checking MD5 sums . . .
Erasing boot before restore . . .
Restoring boot image . . .
Restoring system . . .
Restoring data . . .
Can't mount /data!
Click to expand...
Click to collapse
Then the restore process stops. I've tried starting from scratch via Odin and then again attempted to restore. Nothing works. Help would be greatly, greatly, appreciated!
I had this issue several times with previous versions of ICZen...I saw an app in Xda called Nandroid Browser but i never used it...
Sent from my SGH-T959 using XDA
Thanks for the suggestion, but that didn't really solve the issue. Luckily I frequently backup with Titanium Backup so I was able to upgrade to rc1.4 and restore. Everything seems to be working. Maybe later I'll try what dougfresh suggested and try flashing the Glitch B6 kernel and try to see if the restore works. However at the current I think I'll hold off on any nandroid backups for a while .
i tried also to restore the nandroid after flashing another kernel and still had the same issue...maybe the problem is not with the restore but the backup with the previous versions of MP kernels...
Got an idea Noob. Try to do an advanced restore and restore everything one by one except the boot.img. if it is a kernel issue then this might be a way to bypass it for now until MP or Br1ck'd gets a look at it.
Hey noob, do you remember what kernel you were on when you made the nandroid backup? I think mikka is on the right track, probably an issue with the backup itself rather than the restore operation.
Sent from my ICS'd Vibrant, melting all over XDA Premium
Br1cK'd said:
Hey noob, do you remember what kernel you were on when you made the nandroid backup? I think mikka is on the right track, probably an issue with the backup itself rather than the restore operation.
Sent from my ICS'd Vibrant, melting all over XDA Premium
Click to expand...
Click to collapse
The kernel that was backed up was MP's "cwm-subZero-Vibrant-1.0.1VC_build26-BFS_BLN" kernel. However it wouldn't restore even when attempting to restore after flashing the build 26 kernel. It was a very odd issue, during which I couldn't even mount nor unmount /data in CWR. However it apparently works now. Perhaps I'll start testing backups again at a later date, I've already got everything setup again anyhow. I'm again settled down with your amazing work!
PS- Working on a "Royale with Cheese" boot animation. May take some time, but it's in the works
I got the same Can't mount /data! error when trying to restore a backup after trying a build of CM10.
I just did a wipe data/factory reset, then the restore worked.
I tried JB's KitKatKiller v4 and decided to go back to my previous version of NABD. I did the TWRP Recovery and attempted to restore back to NABD. It is stuck on Restoring Modem. I am not sure if I should power cycle the phone or wait. It has been on the modem portion for probably 10 minutes.
Did you ever get around this? I am having the same issue
Hmm, my phone is in this situation now. Trying to go from CM11 back to stock when I made the backup.
Never used a backup before so hoping it works, but it is just sitting at Restoring Modem for a while now..
Not sure if it restart and try again or wait.. but for how long.
EDIT: Restarted and tried again and it went through the restoring modem bit like instantly.
I had nothing but issues trying to restore with TWRP, I only use Philz now. I wonder if it's also that KitKat Killer is a NC5 ROM not NABD, that could be messing up the restore
12gage said:
I had nothing but issues trying to restore with TWRP, I only use Philz now. I wonder if it's also that KitKat Killer is a NC5 ROM not NABD, that could be messing up the restore
Click to expand...
Click to collapse
+1 I had nothing but issues trying to restore with TWRP, I only use Philz .
TWRP looks nice but performs terrible
Same thing. I had nothing but trouble with TWRP. My advice: don't rely on TWRP backups!!!
metooo said:
Same thing. I had nothing but trouble with TWRP. My advice: don't rely on TWRP backups!!!
Click to expand...
Click to collapse
That's not fair to say. I've had Philz fail more then T.W.R.P. But I'm not going to say at use them. Every1s phone is different..
I've done something that I haven't been able to remedy yet and it had made it so no matter what touchwiz ROM I use the phone app won't even open and getting a call reboots or locks up the phone. I have successfully installed AICP and all is working. Any ideas what I've done? Boot loader is mdk.
Sent from my jflte using Tapatalk
I'm just guessing here but did you anything that would've touched your efs folder? If you've made an efs backup (or a full backup, they usually include efs by default) I would suggest restoring it
Sent from my SCH-I545 using Tapatalk
joshm.1219 said:
I'm just guessing here but did you anything that would've touched your efs folder? If you've made an efs backup (or a full backup, they usually include efs by default) I would suggest restoring it
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
When this first happened I restored a backup I had from Hyperdrive Rls 15 (tw rom) and everything was there however the phone didn't work. I just ran through a tutorial of backing up and restoring my efs folder using terminal emulator and the results i got were the same on the video so I believe that to be in order.
I did flash one file which could possibly have caused this but if so I'm not sure how to reverse it. It was an NC2 WIFI fix after trying to install gdux v2.0
dogg94 said:
When this first happened I restored a backup I had from Hyperdrive Rls 15 (tw rom) and everything was there however the phone didn't work. I just ran through a tutorial of backing up and restoring my efs folder using terminal emulator and the results i got were the same on the video so I believe that to be in order.
I did flash one file which could possibly have caused this but if so I'm not sure how to reverse it. It was an NC2 WIFI fix after trying to install gdux v2.0
Click to expand...
Click to collapse
So personally when there's a problem I can't fix, I use odin to start my phone over. If I were you I would flash the full wipe tar that matches my boot loader. It's up to you though. That's a totally fresh stock start so you have redo root and everything.
I would also suggest PMing surge1223 and jkruse if you really can't lose the data on your phone and don't wanna go through Odin. Keep in mind they're both very busy.
Sent from my SCH-I545 using Tapatalk
Thank you for the advice I will probably end up using Odin as this seems to be a unique situation
Sent from my jflte using Tapatalk
Not sure what went wrong, but I've just had to use flashtool. I decided to flash one of the stock roms available. I don't feel any of what resulted was fault of the Rom so I won't specify. I made another backup of my tweaked Rom, and wiped as instructed and installed. Everything flashed ok but the Rom was a little buggy so I decided to restore my tweaked backup. Rebooted to reovery, wiped then selected which backup to restore. In short, the backup was showing no partitions available to restore and wouldn't work. So, I chose my original backup of stock and that showed everything so I restored. From there, the backup said complete so I rebooted. I ended up with the flashing red and blue led and could only boot to twrp. I tried to reflash the Rom zip but it failed to open. So here I am after using flashtool, which was an adventure as well. I'm curious if anyone else at all has had a similar experience? Is it possible my twrp was corrupt in some way?
Sent from my LGLS990 using Tapatalk
Had you ever tried to restore you backups prior? Just to make sure you had a good backup.
Did you use compression in TWRP? It's been an issue in the past. At least with the OG it was.
I have no other ideas. Sorry you had to go through that. But at least you got it fixed.
I hadn't restored prior to this, no. I think I did use compression on the second backup. Good point. One good thing, I don't have the ugly yellow spark boot ani any more. [emoji6]
Sent from my LGLS990 using Tapatalk
Evolution_Freak said:
I hadn't restored prior to this, no. I think I did use compression on the second backup. Good point. One good thing, I don't have the ugly yellow spark boot ani any more. [emoji6]
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
Is this after Flashtool? The only way I know of to get it back is ##RTN#. And you'll need your MSL.
You shouldn't have Wi-Fi calling either then. That's the clincher.
Be safe and backup your EFS first though.
Evolution_Freak said:
I hadn't restored prior to this, no. I think I did use compression on the second backup. Good point. One good thing, I don't have the ugly yellow spark boot ani any more. [emoji6]
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
i also used compression for my backup did you figure out if that was what caused the problem?
kMogs17 said:
i also used compression for my backup did you figure out if that was what caused the problem?
Click to expand...
Click to collapse
To be safe, boot into recovery and try to restore your backup. If you don't see the partitions listed, then it's probably compression.
Edit:
Don't wipe anything though!
Sent from my LGLS990 using Tapatalk
Evolution_Freak said:
To be safe, boot into recovery and try to restore your backup. If you don't see the partitions listed, then it's probably compression.
Edit:
Don't wipe anything though!
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
Yep yep - Im glad this is my second LG, I never use compression thanks to all I've learned from the lgog. That sucks though dude, but lesson learned.
For the record, I've flashed several things and restored several backups already(I have two, odexed stock and deodexed stock) without any issues.
Evolution_Freak said:
Not sure what went wrong, but I've just had to use flashtool. I decided to flash one of the stock roms available. I don't feel any of what resulted was fault of the Rom so I won't specify. I made another backup of my tweaked Rom, and wiped as instructed and installed. Everything flashed ok but the Rom was a little buggy so I decided to restore my tweaked backup. Rebooted to reovery, wiped then selected which backup to restore. In short, the backup was showing no partitions available to restore and wouldn't work. So, I chose my original backup of stock and that showed everything so I restored. From there, the backup said complete so I rebooted. I ended up with the flashing red and blue led and could only boot to twrp. I tried to reflash the Rom zip but it failed to open. So here I am after using flashtool, which was an adventure as well. I'm curious if anyone else at all has had a similar experience? Is it possible my twrp was corrupt in some way?
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
Noticed that you said you wiped before restore. I did that once on my G2 and ended up having to use flashtool.
leroybrute said:
Noticed that you said you wiped before restore. I did that once on my G2 and ended up having to use flashtool.
Click to expand...
Click to collapse
You should always wipe first IMO. There's always ghosts in the machine. It's just an added measure to give you a clean restore/flash. Most people that have issues with roms don't wipe, and dirty flash/restore.
I've never had an issue wiping all 4. And compression just seems to never work right. At least with all the G series.
engine95 said:
You should always wipe first IMO. There's always ghosts in the machine. It's just an added measure to give you a clean restore/flash. Most people that have issues with roms don't wipe, and dirty flash/restore.
I've never had an issue wiping all 4. And compression just seems to never work right. At least with all the G series.
Click to expand...
Click to collapse
If you wipe all four and your twrp isn't on your external SD card you're screwed if you want to restore.
I always wipe when installing roms, just not restoring. Habit from using phones without ext.
I also thought I saw a wipe script built into the restore option.
I called Sprint today to get my MSL. I needed to use the ##RTN# code to get the WiFi calling app and the other stuff back after flashtool. They had me do a factory reset first to see if that would do it but then gave me my MSL without question.
Thanks again for all the info learned in this thread. I finally got around to re-rooting and re-bumping and all were smooth and easy.
Sent from my Stump'd & Bump'd Sprint LG G3
engine95 said:
You should always wipe first IMO. There's always ghosts in the machine. It's just an added measure to give you a clean restore/flash. Most people that have issues with roms don't wipe, and dirty flash/restore.
I've never had an issue wiping all 4. And compression just seems to never work right. At least with all the G series.
Click to expand...
Click to collapse
I only had a problem with compression once on my OG for the rest of the time it worked fine and was a necessity because it had no external storage but anyway i just checked the compressed backup i made and the partitions show up under restore, but i havent tried it yet because i have no reason to. maybe when aosp comes out
Does twrp-2.8.6.1-hltespr-4.4.img.tar or philz_touch_6.25.0-hlte.tar.md5 work without any problems restoring a 5.0 backup?
Maybe OC5 should be called obsessive compulsive 5.
I've been using TWRP 2.8.6.1 without any problems and yes I am on OC5.
So you did make a oc5 backup, then restore it, just to make sure it works? I'm kinda afraid to at the moment. Maybe I'll try later. I first started on twrp, then went to philz.
oscarthegrouch said:
So you did make a oc5 backup, then restore it, just to make sure it works? I'm kinda afraid to at the moment. Maybe I'll try later. I first started on twrp, then went to philz.
Click to expand...
Click to collapse
Im using cwm 6.0.4.7 and everything works just fine
No issues here using TWRP 2.8.0.0 to restore a backup.