Hi all.
This is the second time (in a row) that TWRP produces a corrupted backup which really sucks because this is the second time I lose my phone's data over corrupted backups.
This started happening ever since I moved to TWRP 3.1.1-0 (I'm pretty sure of it).
Why is this happening? Is this a TWRP 3.1.1-0 bug? Is there a solve? And also, what's the newest TWRP version that does have working backups?
Thanks in advance
Check Dev forum for unofficial thread.
Related
Hello,
I have a Galaxy s4 i9505 jfltexx. I'm under CWM recovery but I'd rather prefer to have PhilZ Recovery.
I saw that jflexx versions have been stopped and that they recommended to use jflte version... for this OK. But are there some versions that I musn't flash ? Or do I need the last version available ?
Thanks for your help
TWRP is the recommended recovery for us, once you get used to it, it is actually better...
Philz is based on cwm. Since cwm hasn't been updated for a while, neither has Philz.
I also recommend TWRP as many ROMs recommend TWRP.
Ok except that I had a problem with CWM this morning : the Nandroid backups doesn't save the "preload". It was impossible for me to restore it (bootloop). As I understood recently, only PhilZ Recovery has an option to include the preload in the Nandroid backup.
Last but not least, where can I get TWRP on its last version for my phone ? Can you send me a link ?
Here.
TWRP also has a preload backup option if I remember correctly.
Why would you backup preload? As far as I know the partition is empty, for me at least.
Here is a TWRP recovery from autor's website for GT-I9505 (JFLTEXX): https://dl.twrp.me/jfltexx/
GDReaper said:
Here.
TWRP also has a preload backup option if I remember correctly.
Why would you backup preload? As far as I know the partition is empty, for me at least.
Click to expand...
Click to collapse
Because, even if it's not a galaxy S2, I had exactly this problem yesterday with my Nandroid backup : http://forum.xda-developers.com/galaxy-s2/help/bootloop-nandroid-restore-t2337856
Thanks KonowaL !
oldbear3 said:
Because, even if it's not a galaxy S2, I had exactly this problem yesterday with my Nandroid backup : http://forum.xda-developers.com/galaxy-s2/help/bootloop-nandroid-restore-t2337856
Thanks KonowaL !
Click to expand...
Click to collapse
Well, maybe it's a CWM problem.
I never backed up the preload partition, yet I have successfully restored my nandroid backups in the past.
GDReaper said:
Well, maybe it's a CWM problem.
I never backed up the preload partition, yet I have successfully restored my nandroid backups in the past.
Click to expand...
Click to collapse
I just flashed TWRP as you advised. It seems really great (not as the old version I tested by the past)... but there is no preload partition backup option. Or I don't see it. Where do you see it ?
I flashed the 3.0.0 version.
oldbear3 said:
I just flashed TWRP as you advised. It seems really great (not as the old version I tested by the past)... but there is no preload partition backup option. Or I don't see it. Where do you see it ?
I flashed the 3.0.0 version.
Click to expand...
Click to collapse
Hmm..
I think only JDCTeam's TWRP has that option. I know their 2.8.7.2 TWRP had several backup options, including efs and others.
Also note that TWRP backups don't work with CWM backups, so you will have to redo them.
Also, as I mentioned earlier, I never backed up preload (unless TWRP does that on its own) and restored those backups successfully, and without bootlooping.
You might wanna try it yourself in order to believe it.
OK thanks a lot for your help
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
Hi all,
I have TWRP and lollipop and Nethunter 3 installed, as this was my first trip into Nethunter I though it would be wise to backup my base install incase anything goes wrong. Something went wrong and I came to restore from my backup, the restore completes successfully but it seems Nethunter is has not been restored and just the base lollipop ROM is there.
I have previously restored from TWRP Backups for nethunter and they have been fine, it is almost as if the backup process has skipped a large portion of the partition.
I have checked around TWRP and cant see any obvious option I should have checked, also a google search hasnt proved fruitful.
Has anyone else seen this kind of behavior and if so is there a resolution?
Thanks
I experrience a very weird issue. Restoring a nandroid backup with TWRP is working without any errors. But the phone then goes into bootloop. I have only one backup which still result in a properly boot.
I think it has something to do withe the boot.img.
I'm on oreo 8.1. First I thought the culprit was magsik 20.4. So I flashed an oreo 8.1 image and restarted into TWRP as soon I saw the start of the installation wizzard. I made a backup and restored the backup. Again, bootloop.
Some ideas what is the problem?
Hi everyone,
I've been using the official LineageOS 17.1 (SM-G903F) and when I try to backup and restore a ROM from TWRP LineageOS just gets stuck in the load screen (or in some cases the Galaxy S5 Neo Boot Screen loops)
I've so far tried TWRP Versions:
3.5.0_9-0
3.4.0-0
2.8.7.0 (can not create backup)
LastStandingDroid's Unofficial Experimental TWRP (2.8.7.0)
Any ideas on what the problem could be? Are you guys able to recover TWRP backups?
I've also tried not using GApps.
Thanks for any help,
Aventurer
I guess /system cannot be restored. /data and /boot seem to restore fine, but I need to flash the LineageOS .zip along with it.
Any ideas on why? Is it a TWRP problem? I'm not using read-only mode in TWRP and I get no errors, it just bootloops.
I'd like to know the answer to this as well.
I'm experiencing the same issue with LOS 17.1/twrp 3.4