I see that both the TWRP and CWM page both say experimental but then it says they need people to test for backup and restore. Does that mean i can use it just for flashing (sound mod) without trouble?
mottyengel said:
I see that both the TWRP and CWM page both say experimental but then it says they need people to test for backup and restore. Does that mean i can use it just for flashing (sound mod) without trouble?
Click to expand...
Click to collapse
It seems a few people have issues restoring nandroid backups. It's probably related the the selinux stuff. Just flashing mods seems to work fine. It wouldn't hurt to use that little script posted for Titanium Backup restores to fix up those selinux permissions after flashing though.
TWRP - backed up and restored just fine
Related
First I'm wondering why with almost half the files i want to flash with twrp make it crash and reboot? Using the latest version. Flashed it from zip. I'm stumped. I end up flashing cwm to flash what i want then flash back to twrp. I would just use cwm because I'm more familiar with it but its not making my backups right for some reason.
Also was wondering being that alot of the apps I have uninstalled on tb are for my stock ROM which I have a backup of, can I delete them from my tb? So i don't have what feels like a thousand apps scroll to get what I want? Or will that mess something up? Most i will never use but i don't want to ruin my backup
Thanx
zombielion said:
First I'm wondering why with almost half the files i want to flash with twrp make it crash and reboot? Using the latest version. Flashed it from zip. I'm stumped. I end up flashing cwm to flash what i want then flash back to twrp. I would just use cwm because I'm more familiar with it but its not making my backups right for some reason.
Also was wondering being that alot of the apps I have uninstalled on tb are for my stock ROM which I have a backup of, can I delete them from my tb? So i don't have what feels like a thousand apps scroll to get what I want? Or will that mess something up? Most i will never use but i don't want to ruin my backup
Thanx
Click to expand...
Click to collapse
What version of TWRP are you using?
Also, I don't see any problem in deleting old stock backups from TB, as long as you have a nandroid backup of your stock ROM. Even if you do delete something, and don't have a nandroid, you can always flash back to stock.
Alternatively, you can use the search function in TB to avoid having to scroll through the really long list.
MeetMyBackhand said:
What version of TWRP are you using?
Also, I don't see any problem in deleting old stock backups from TB, as long as you have a nandroid backup of your stock ROM. Even if you do delete something, and don't have a nandroid, you can always flash back to stock.
Alternatively, you can use the search function in TB to avoid having to scroll through the really long list.
Click to expand...
Click to collapse
I'm on twrp 2.3.3.0 but i was having the problem on 2.2.2.0 the zips seem fine they flash in cwm it just makes it a hassle to go through all that trouble.
zombielion said:
I'm on twrp 2.3.3.0 but i was having the problem on 2.2.2.0 the zips seem fine they flash in cwm it just makes it a hassle to go through all that trouble.
Click to expand...
Click to collapse
I have both cwm and twrp in flashable zips could i be not flashing it right or something. I do it the way i do everything else and never have problems? I'm getting used to twrp and the backups work for me where cwm doesn't since first backup just the reboot is such a pain. Should i go to stock and start all over could it be I've messed singing up alone the way? I can't find a postof anyone having the same problem
Seeing as everyone ignores my question in threads such as cm10 and rooting, I thought I'd make a seperate thread.
So my question is if it is proven that a CWM backup and restore works fully without any problems. If I create a backup now, flash a custom rom, then go back to CWM and choose restore, will it restore my backup without any problems and error messages that can lead to a bricked phone?
No one's replied probably because no one (who frequents these forums) have tried it yet!
I just tried it with success.
I did a CWM backup installed stock FW, installed CM10.1 again and did a restore.
everything is back as before.
Mitko said:
Seeing as everyone ignores my question in threads such as cm10 and rooting, I thought I'd make a seperate thread.
So my question is if it is proven that a CWM backup and restore works fully without any problems. If I create a backup now, flash a custom rom, then go back to CWM and choose restore, will it restore my backup without any problems and error messages that can lead to a bricked phone?
Click to expand...
Click to collapse
ratelutz said:
I just tried it with success.
I did a CWM backup installed stock FW, installed CM10.1 again and did a restore.
everything is back as before.
Click to expand...
Click to collapse
Awesome, great to hear. Thanks for testing and reporting. :victory:
Hello there,
I have just bought a Samsung Galaxy Tab S 10.5 LTE T805 and I am going to root it using the method described in
the thread below
[ROOT]Official CF-Auto-Root By Chainfire. [T-700][T-705][T-800][T805]
But I don't know which one is better for my tablet Helium or TWRP? And where can i find a tutorial on how to install either of them? If there is not a tutorial available, could you please guide me through the whole proccess?
I have read on another thread that I could use an app, by the name Flashify currently available on Play store, but i don't know how to use it and if it is safe to use it with the CF-Auto-Root method mentioned above?
(Lots of people that used this app were pretty happy after using it and without problems too, but i want your experience on the matter)
To tell you the truth :angel: I am a huge fan of TWRP and I would have been very glad if I could use it again on my new tablet also.
(I had it installed on my previous tablet an Asus Transformer Pad and it worked flawlessly).
So to sum it up
Could you please tell me what to do and how to do it in order to backup my tablet before i Root it?
Which one Helium or TWRP is safer to use?
Thank you all in advance for your time,
Heluim is to backup your apps/data. Twrp can make an image of your whole os and data so you can restore from bootloops. Installing twrp via flashify is safe with cfautoroot as cfautoroot just flashes root and reverts back to your old recovery. Just download flashify, pick install recovery, then hit twrp and pick twrp 2.8.1.0 and hit yup. Then reboot and youll have twrp. You must cfautoroot first to use flashify.
Dont use twrp 2.8.3.0 as it doesnt work.
I would perfer twrp over heluim becuase its a custom recovery. Not a fan of helium as I use titianuim backup.
I would use TWRP. Basically, root first, then install TWRP via Flashify. Version 2.8.4.0, the latest, works fine. I have used it to both back up and restore and there are no problems. It does have a tendency to enable MTP when you first run it which will throw an error when you do a backup (the error is meaningless and doesn't actually do any harm, but the red type will cause panic, so the first time you go into TWRP hit the mount button and make sure MTP is disabled).
I also use Titanium Backup for backing up and restoring apps and recommend it highly. Between TWRP and TB, I can wipe, install a ROM and restore all my apps in about an hour and the TWRP Nandroid backups mean I can always easily recover if something isn't quite right.:good:
Thank you!!! Thank you both so much, for the much needed advice, much obliged!!! :good:
I will do as you advised me and thank God you clarified everything about the differences between Helium vs. TWRP :good:
Hookmt said:
I would use TWRP. Basically, root first, then install TWRP via Flashify. Version 2.8.4.0, the latest, works fine. I have used it to both back up and restore and there are no problems. It does have a tendency to enable MTP when you first run it which will throw an error when you do a backup (the error is meaningless and doesn't actually do any harm, but the red type will cause panic, so the first time you go into TWRP hit the mount button and make sure MTP is disabled).
I also use Titanium Backup for backing up and restoring apps and recommend it highly. Between TWRP and TB, I can wipe, install a ROM and restore all my apps in about an hour and the TWRP Nandroid backups mean I can always easily recover if something isn't quite right.:good:
Click to expand...
Click to collapse
I usually just restore the data partition after installing a new rom instead of using TB then just wipe caches. . I only use TB for backing up and restoring certain apps or data. Doesnt take me anywhere near an hour, using either method.
ashyx said:
I usually just restore the data partition after installing a new rom instead of using TB then just wipe caches. . I only use TB for backing up and restoring certain apps or data. Doesnt take me anywhere near an hour, using either method.
Click to expand...
Click to collapse
Nice idea, thanks. In the case of a clean flash, however, which is the only time I'm using TB to restore, I often want to restore only some apps and use things for a while and not everything I was experimenting with before.
Samsung apparently does not allow you to boot into the bootloader on their phones. I am trying to return to a different kernel I was using previously, which was contained in a nandroid backup. However, to my understanding, restoring a nandroid backup does not restore the kernel, and you have to extract the boot.img and flash that by itself.
What is the best way to go about doing this without fastboot?
Also, I don't suppose "restore boot" in nandroid advanced restore does this now, does it? Can't find anything on it online.
From what I recall, restoring the nandroid backup would restore the kernel. What recovery was used to create the nandroid?
audit13 said:
From what I recall, restoring the nandroid backup would restore the kernel. What recovery was used to create the nandroid?
Click to expand...
Click to collapse
I used CWM. I read in several places (forums) that it didn't....Hm. I mean I have the boot.img from the backup, so I have the kernel right there. I suppose I could find some way to make it into a flashable zip, but I was just wanting to see if anyone knew a way around that.
But if you are confident that the backup would restore the kernel, do you know if I could restore just the kernel from advanced restore? It'd be fab if I could keep /data the same, but not a must I suppose.
I use TWRP on an HTC and just restored a nandroid backup. After restoring the backup, the previous kernel was restored too.
I don't have any devices at the moment that use CWM.
Not sure about just restoring the kernel. Any particular reason you just want to restore the kernel?
audit13 said:
I use TWRP on an HTC and just restored a nandroid backup. After restoring the backup, the previous kernel was restored too.
I don't have any devices at the moment that use CWM.
Not sure about just restoring the kernel. Any particular reason you just want to restore the kernel?
Click to expand...
Click to collapse
I started getting some problems after flashing a custom kernel and I want to revert to the previous one, the default CM one, to test if my problems are related to that kernel or not. I suppose I'll look into making the .img a flashable zip then, unless anyone else knows of a better way. I'm not familiar enough with Odin to know if you can flash a .img in it.
There's that "restore boot" option in the advanced restore menu on CWM. Do you have any idea what that restores? I want to naturally say that it probably restores the boot.img, but I have searched and searched and just cannot find anything online about what that actually restores.
Nandroid backups created with CWM need to be restored using CWM.
Sorry, not sure what the advanced options will do but you could try different ones.
Restoring boot in advanced nandroid restore restores the zimage and initrd.gz. The kernel. Thus, I suppose a full restore will restore the kernel. Perhaps there are exceptions for certain devices. Restoring boot got me where I needed.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
[Q] Why is "fix permissions" missing from CWM? ... I can't do anything on my phone
I "broke" my phone using PhilZ CWM Touch, I don't know how?
I did a full CWM backup of my ROM / apps etc to my SDCard, it grabs /data/ /system/ all kinds of stuff into a 4gb ZIP or whatever.
I've done this many times before!
All of this so I could do some quick CM12 testing for a snapchat bug.
Then I restored the CWM backup image from my SD Card
Now, I can't save screenshots or write ANY data to the /sdcard/
"Couldn't capture screenshot: couldn't save. Storage may be in use"
Tried wiping Dalvik cache, no fix.
What do I do here? I'm baffled? ?I thought restoring a CWM backup would recover everything.
This PhilZ touch thing is missing "fix permissions" ?
wizzbang3 said:
I "broke" my phone using PhilZ CWM Touch, I don't know how?
I did a full CWM backup of my ROM / apps etc to my SDCard, it grabs /data/ /system/ all kinds of stuff into a 4gb ZIP or whatever.
I've done this many times before!
All of this so I could do some quick CM12 testing for a snapchat bug.
Then I restored the CWM backup image from my SD Card
Now, I can't save screenshots or write ANY data to the /sdcard/
"Couldn't capture screenshot: couldn't save. Storage may be in use"
Tried wiping Dalvik cache, no fix.
What do I do here? I'm baffled? ?I thought restoring a CWM backup would recover everything.
This PhilZ touch thing is missing "fix permissions" ?
Click to expand...
Click to collapse
Philz recovery is one of the best recovery ever been. Unfortunately developer abandoned
This is the message from developer
Project Status:*No Longer Updated
As I mentioned before, I have a lot of new important projects in my real life. I am very happy to abandon this project for real life alternatives.
CWM is a dead project for now, until some dev resurrects it. I was about to do, until these new projects came.
Current version will probably work a while for many devices. Some devices with new ROM installers could have issues. Just use TWRP or the CM Simple Recovery
If the current version works for you, there is no reason you don't use it though. No need to ***** in all threads because it doesn't work for you. Just move on to other alternatives
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=39433458
Latest update for n7100 was at middle of 2014 if I remember well. Probably u used an outdated recovery. I am using the version 6.48.4 at cm12.1 with no problem at all but I never made with this a nandroid backup.
Sent from my GT-N7100
If you check PHilZ FTP / Mega Upload mirror, he's clearly still updating it? ?.... I dunno
Regardless, I did some reading and the impression I get is version 6.3.xx of CWM removed the "FIX PERMISSIONS" code / option (why the @$#%^ it did this, I do not know)
Ultimately I think that's the issue with my phone, right?
wizzbang3 said:
If you check PHilZ FTP / Mega Upload mirror, he's clearly still updating it? ?.... I dunno
Regardless, I did some reading and the impression I get is version 6.3.xx of CWM removed the "FIX PERMISSIONS" code / option (why the @$#%^ it did this, I do not know)
Ultimately I think that's the issue with my phone, right?
Click to expand...
Click to collapse
I don't know about other phones but for n7100 sure abandoned.
About the issue now yes looks like permission problem, maybe you try to fix permissions with some other recovery or if you have some apps installed and for this you want to restore your backup, you can restore your nandroid backup after wipe system, cache, dalvik and install the same rom, gapps you had made backup. The installation of the rom at the end of install normally will fix permissions. Also you can try to clean install your old rom, gapps, reboot check if everything is OK and after from recovery again make selective nandroid restore the data only.
Sent from my GT-N7100