Database Users

[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.

[Q] Restoring from backup

Hello,
I'm running TWRP v2.8.4.0 on a G900T. Before testing out my first custom rom after rooting the device I made a full backup through TWRP. I was having some difficulties with the ROM I chose and decided to restore my backup so I could use my phone still while figuring things out. Unfortunately, after restoring the backup file through TWRP and rebooting I am receiving crash report after crash report of a long list of apps.
I tried searching the forums but no such luck with the wording that I've used for a fix.
I've tried disabling MTP and Fixing Permissions (without the "SELinux contexts" option) after doing another factory reset (Wiping Data, Cache, and Dalvik.
If there is anything else that I could try or read up on that would be great. Thank you!
**Update**
The only thing I can think of is something to do with downgrading from Lollipop 5.0 to Stock 4.4.2. I'll update this thread if I end up getting something to work.
I ended up flashing the Alliance Rom to get it back to something very close to stock. Still interested in possible solutions to restoring that original backup though as if I need to send it in for maintenance that's the one that I'll need to use.

Stuck at boot screen after restoring ány Nandroid backup.

Hey,
I've had this problem for ages now, and always gave up on my data, but now I really want to fix this for good.
Yesterday I was ready to update my CM12 nightly to the lastest version (didn't see it was actually CM13), and did a backup in cwm before the update. The backup succeeded, but it gave the message that .android_secure couldn't be found and it didn't back that up. It always gives me this message after a backup and after google searching, it seems to me that it doesn't matter.
After installing the update, I noticed it was CM13, and my gapps wasn't updated to the marshmellow stock, as expected, so errors occured all the time.
I didn't want to upgrade to CM13 just yet, so I decided to restore my backup.
As always, the restore process goes without errors, but upon reboot I'm stuck at the CM logo. I can wait untill the battery is dead or ignites from the heat, but nothing happens. This has also happened to me every time I make a backup. I've watched about every video on youtube on how to do a proper backup and how to restore one, so I'm confident that I did it right.
For some reason, any backup I make, no matter what android version (didn't work with stock kitkat, either, before I switched to CM12) it never works and I'm forced to do a clean install and start over again.
I've tried to do partial restores from the backup file, and if I only restore the data partition (and wipe dalvik) It does boot, but gives me non stop errors that apps are crashing.
I've tried to do a dirty flash to no avail, always endless error messages.
When I do a clean install and check the MK5 of the backup with nandroid manager it gives no errors.
Is there anything wrong with my phone or something? I'm not making backups to be unable to restore them.
Can anyone help me out with this?
(I have a i9505)

Try a different recovery. CWM is outdated. TWRP is nice. Worked for ne every time. There are TWRP flashable zips so you won't have to mess around with Odin.

GDReaper said:
Try a different recovery. CWM is outdated. TWRP is nice. Worked for ne every time. There are TWRP flashable zips so you won't have to mess around with Odin.
Click to expand...
Click to collapse
Won't changing recovery make my old backups useless? I'm all for changing to TWRP, but first I'd love to restore my CWM backup...

Yes it will. Unfortunately I don't know what to suggest. Haven't used CWM since I switched to the S4.

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?

Issues with restoring recovery using TWRP-3.0.2-0

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