Restoring from SafeStrap Backup - ANSWERED - Verizon Galaxy S 5 Q&A, Help & Troubleshooting

I just rooted my S5 to PB1 (have '11 eMMC so no MM) per another thread in this forum and had set everything up, then decided to make a full backup with SafeStrap. I loaded Safestrap-G900V-4.04_LL_MM, installed it, went to recovery and then made a full backup to the SDCard.
After completing the backup, I ended up in a SS loop and somehow back to a completely reset phone (however still rooted). I am looking for how to reinstall the backup correctly.
I plan to load all the necessary apps to once again get SS installed and to recovery. Is there anything special to do once I RESTORE my backup? Do I need to also install LL_KERNEL_SS-FF_Flashable.zip again after the RESTORE?
EDIT: THE ABOVE IS WHAT NEEDS TO BE DONE. INSTALLED SUPERUSER.APP, THEN BUSYBOX, THEN SAFESTRAP FROM THE PACKAGE USED TO ROOT. ONCE IN SS INSTALLED MY BACKUP, THEN INSTALLED THE LL_KERNEL_SS-FF_Flashable.zip WITHOUT WIPING ANYTHING. GOT IT TO BOOT, STILL ROOTED, ALL FILES BACK...
Thanks
Frank

Related

[Q] Questions re Red Amazon screen that hangs on boot

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

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

[HELP] Screwd up nandroid

Hello guys!
I was updating from 4.4.4 to lollypop via OTA, then I realized that even if I run the stock ROM, I am still unlocked + root, meaning that the OTA won't run.
I did a complete nandroid backup via Wugs Nexus Toolkit, including data.
Then I wiped and flashed the new 5.0 via Nexus Toolkit, but when I tried to restore only the data it didn't work.
I decided to go back to 4.4.4. and do things properly, but now I'm not able to restore anything.
I am not bothered with the apps and stuff, but I had plenty of pictures which I forgot to backup, and I want to restore them. I even tried to access the nandroid backup files, but no success!
I was accustomed with the old CMW, where you had the .img files, but I got no clue on what to do here!
I add the picture of the nandroid backup folder on my PC ( I think the data files are splitted, but I cannot open them in any case, not even with 7zip).
The nandroid was executed via Nexus Toolkit, but I guess it has been done through TRWP.
Long story short:
1) how can I access the pictures inside the nandroid backup?
2) how can I restore a nandroid backup that keeps failing?
theraizen said:
1) how can I access the pictures inside the nandroid backup?
Click to expand...
Click to collapse
Maybe CWM does things differently, I don't know, but with TWRP, a Nandoid backup doesn't back up your SD card partition, so if you wiped everything, all your pics are gone. Sorry.
Yeah, I guess so.. Managed to recover something with DISK DIGGER (its an app, free on the store). Just wanted to write it here, so if anyone has the same issue can recover this way!

need texts from twrp backup.

rooted and rommed a friend's note 3 to jasmine, and before we did it we upgraded titanium backup to the pro edition via marketplace, without realizing that it had deleted all three backups that were all in separate locations, one in the default location, one on the SD card and one in the phone's internal storage.
before I did anything to the phone rom wise I made a nandroid backup via twrp and I cannot boot it into an emulator successfully AND get the texts from it through installing titanium backup, creating a backup and copying it off, didn't work out.
so now what I need is a way to load up a nandroid backup without corrupting the backup. every time I try to restore the backup into the phone it bootloops, only thing I can think of that would interfere with it is the kernals, NC2/4. jasmine is currently running on NC2 and the stock firmware with the texts on it uses NC4, when I tried reflashing NC4 to the device after reintalling the backup it bootlooped, and vice versa with NC2.
thoughts/suggestions? sol on the texts?
thanks.
Never tried this but worth a shot. https://play.google.com/store/apps/details?id=com.h3r3t1c.bkrestore
Sent from my SM-N900V using Tapatalk
I'll give it a go.
followed the steps found at: http://forum.xda-developers.com/nexus-s/general/extract-restore-sms-mms-contacts-call-t1370349
and had no success, doing the same via root explorer and nandroid manager to get the original files from the backup, nothing was restored.
I'm assuming that they're just gone after that?
rom manager text restore found nothing, quite a few were backed up though so who knows. not a good thing to lose them all.

SM-G900F with TWRP 2.7.1.0 - Nandroid restore resulting in all apps force stopping

Hi experts,
I would very much appreciate some help regarding the following:
I have a Samsung Galaxy S5 SM-G900F with factory installed stock rom G900FXXU1BPA2 (Android 5.0). I used the SkipSoft Unified Android Toolkit 1.4.5 to root the phone and install TWRP recovery (2.7.1.0-klte as recommended by Unified Android Toolkit). I made a first Nandroid Backup and was able to successfully restore this backup (I restored boot, system and data to verify that Nandroid restore works). I then used Titanium Backup to restore my apps from another phone, and all was well.
A week or so later I wanted to modify something I wasn't sure I wanted to keep (using apktool). I therefore made a second Nandroid backup and then proceeded to make modifications to the phone. After I saw the result, I didn't like it, and therefore restored the second Nandroid backup. After rebooting, the phone gave a flurry of forced stops ("Unfortunately XXX has stopped"). It is not a bootloop but I can't do anything meaningful with the phone other than restart it.
To try and resolve this, I used TWRP to wipe cache and dalvik cache and rebooted. The phone went through the lengthy "Android is upgrading" process but the result was the same: all my apps force stop.
I then decided to try and restore the original first Nandroid backup (which I had been able to restore successfully earlier), and this resulted in the same issue. Since I have several backups of this first backup I was able to verify that the files were good. Also did MD5 checksum verification in TWRP and it all checked out.
Using Odin, I was able to restore a stock ROM from SamMobile (G900FXXU1BOL1_G900FOJK1BOL1_ILO) and after restart, the phone works as usual, but of course all my apps and data were gone.
I was then able to use TWRP to restore only boot and system from the second backup, so I would be back on the exact same ROM that my phone came with, and this worked just fine; the phone started as if factory restored.
I then used TWRP to restore only data, and this resulted again in the same problem: all apps force close. Note that this is a restore of data only to the same phone running the exact same ROM that the Nandroid backup was made on, and it still did not work.
I have been thinking about this issue and searching through the various forums but I did not find anyone having this same exact issue. Here are some questions I came up with:
1. Is TWRP 2.7.1.0 completely compatible with this phone and with Android 5.0? Would it help if I installed a newer version of TWRP? Would I be able to restore Nandroid backups made with TWRP 2.7.1.0 with TWRP 3.X?
2. Assuming my second Nandroid backup is not corrupt, is there a better (less intrusive) restore I can do of the apps? Can Titanium Backup read TWRP 2.7.1.0 backups and restore them, including SMS?
3. What could be the reason for TWRP 2.7.1.0 restore not to be working properly? I did activate the fingerprint reader after the first Nandroid Backup, but if that is the issue I would have expected that first backup (in which fingerprints were not yet enabled) to restore properly and it doesn't.
Would appreciate any help!
Thanks,
AH
That version of TWRP is pretty old, possible it doesn't fully support 5.0
Grab 3.0.0.0 from here (newer versions are not fully bug free yet)
https://dl.twrp.me/klte/
Flash .tar version with ODIN 3.10.7
TiBu can read Nandroid backups and restore apps yes
Not sure about SMS
The method you used to root and flash TWRP is not a usual method used here, most of us use ODIN to flash TWRP and then flash SuperSU from recovery
or use CF Auto Root to root, and then flash TWRP with ODIN
I'd flash stock again, factory reset, and then flash TWRP and SuperSU, then try restoring your apps with TiBu
*Detection* said:
That version of TWRP is pretty old, possible it doesn't fully support 5.0
Grab 3.0.0.0 from here (newer versions are not fully bug free yet)
dl.twrp.me/klte
Flash .tar version with ODIN 3.10.7
Click to expand...
Click to collapse
Thanks *Detection*! I installed TWRP 3.0.0.0 as per your instructions and restored just data. Same result as before.
Then I used TWRP 3.0.0.0 to restore the entire backup including system, boot, recovery, and data. Same result (of course I lost TWRP 3.0.0.0 and was back on TWRP 2.7.1.0).
This exercise was useful for one reason: I now know that TWRP 3.0.0.0 is able to read Nandroid backups from TWRP 2.7.1.0.
This is quite crazy but I seem to be unable to restore a full Nandroid backup and get a working system.
Am going to try Titanium Backup.
Thanks again!
AH

Categories

Resources