Im curious as to which recovery is working the best with the Galaxy Note 10.1. Im not asking which is the best, but I see darkman has come out with a touch version of cwm and I have the latest TWRP...Only issue i have is that it doesnt see my cwm backups....I havent had any issues with it yet though...Im just curious thats all
I always preferred cwm.. it is more stable.. use to love with twrp when I had asus tf101 but sometimes I couldnt see my internal sd card and sometimes I couldnt mount system.. but just use what works for you..
Sent from my GT-N8013 using XDA Premium HD app
txtmikhail said:
I always preferred cwm.. it is more stable.. use to love with twrp when I had asus tf101 but sometimes I couldnt see my internal sd card and sometimes I couldnt mount system.. but just use what works for you..
Sent from my GT-N8013 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for the input.... I do have to constantly tap the external sd option because it takes me back to the main screen. Im assuming its a sensitivity issue
txtmikhail said:
I always preferred cwm.. it is more stable.. use to love with twrp when I had asus tf101 but sometimes I couldnt see my internal sd card and sometimes I couldnt mount system.. but just use what works for you..
Sent from my GT-N8013 using XDA Premium HD app
Click to expand...
Click to collapse
Agreed. I've found CWM to be very stable. I loved to move to the touch version, though you have to be careful sometimes about accidentally touching an unwanted option. But since a confirmation menu comes up for each option that makes changes, you can easily correct it.
I have used CWM on all my devices and have worked without an itch so prefer CWM
Tried install TWRP on my device once it refused to install contacted the developers did not get the response so ditched it.
Twerp don't seem to get on with note .
But i would say their is very little difference between using TWRP or CWM for most users .
I use TWRP on SGS3 and CWM on Note .
jje
I moved to TWRP awhile ago for my phones and currently use it on my Note. As far as stability goes CWM is much more stable, though I have it tried the touch version(thinking of checking it out though.) TWRP is a little wonky sometimes,but I think that's a sensitivity issue.
As another poster already said, there's no real big difference between the two and they both get the job done.
My big problem with CWM is the backups. Maybe I didn't spend enough time with it or missed an option somewhere. But since they moved to the BLOB model for backups I found it impossible to delete an old backup. I like to do backups often, but I usually only want to keep 2 iterations due to the space they take up. With TWRP it's easy, each backup has it's own folder. Want to delete one, just delete the whole folder.
If someone can tell me how to manage backups properly in CWM I'd be glad to switch back.
midas69 said:
My big problem with CWM is the backups. Maybe I didn't spend enough time with it or missed an option somewhere. But since they moved to the BLOB model for backups I found it impossible to delete an old backup. I like to do backups often, but I usually only want to keep 2 iterations due to the space they take up. With TWRP it's easy, each backup has it's own folder. Want to delete one, just delete the whole folder.
If someone can tell me how to manage backups properly in CWM I'd be glad to switch back.
Click to expand...
Click to collapse
That's one of the reasons I stay with TWRP on my Note despite the super sensitive touch. In all it's wonkiness I've just become more of a fan due to the ease of the touch UI and the ability to just delete the backup folder.
insanecrane said:
That's one of the reasons I stay with TWRP on my Note despite the super sensitive touch. In all it's wonkiness I've just become more of a fan due to the ease of the touch UI and the ability to just delete the backup folder.
Click to expand...
Click to collapse
same thinking for me too..
midas69 said:
My big problem with CWM is the backups. Maybe I didn't spend enough time with it or missed an option somewhere. But since they moved to the BLOB model for backups I found it impossible to delete an old backup. I like to do backups often, but I usually only want to keep 2 iterations due to the space they take up. With TWRP it's easy, each backup has it's own folder. Want to delete one, just delete the whole folder.
If someone can tell me how to manage backups properly in CWM I'd be glad to switch back.
Click to expand...
Click to collapse
Easiest way I've found to manage backups with CWM is to use ROM Manager. It's integrated with CWM such that in the app you ask it to do a backup, you name the backup anything you want, then it automatically reboots into recovery and does it. ROM Manager also allows you to download your backups to you computer via WiFi, and has an easy option to delete backups. Further, CWM has the option to restore data only from a backup for easily getting settings back when doing a ROM upgrade. Geez I'm more sold on CWM than I thought. I almost sound likes a salesperson haha.
glopact said:
Geez I'm more sold on CWM than I thought. I almost sound likes a salesperson haha.
Click to expand...
Click to collapse
Don't apologize, you provided good information. On my HP Touchpad I used TWRP exclusively because it integrated with Goo Manager. But I really don't plan to use anything other than Mobile Odin to flash anything so not much reason to keep it. I may switch back to CWM and try the ROM Manager interface for the backups.
EDIT:
Well that didn't work well at all. Installed and tried to do a backup. Told me (obviously) that I needed CWM installed. Said there wasn't an official version for it so it then asked me if I already had one installed. I answered yes. It then asked if I had version 2 or version 3. But what I have installed has a version number of 6 something. Oh well, back to TWRP I guess.
I thought we could manager the CWM backup from a file manager I have been doing that on my optimus 2x never did it on note though
samir_a said:
I thought we could manager the CWM backup from a file manager I have been doing that on my optimus 2x never did it on note though
Click to expand...
Click to collapse
With older versions I was able to do that. But this newer version I have installed doesn't really work that way. It creates 2 folders for a backup. One has the backup name with just a small file inside. The other folder is called BLOBS. In that fold are multiple other folders that are alphabetical, I assume by file name. The problem is, when you create a 2nd backup, it used the same BLOBS folder. So there is no way to just delete one folder to delete a complete backup.
yes I remember that when I was trying to delete CWM backup files and did not find them. Thanks for the update
---------- Post added at 09:00 PM ---------- Previous post was at 08:59 PM ----------
A noob method try to sort by date/time should tell you which files were updated during your last backup and will give you an idea how the update works. Let me do some R&D on it
I just don't want to have to manually delete files from 20+ directories when, with TWRP, I can just delete one folder.
samir_a said:
I thought we could manage the CWM backup from a file manager ...?
Click to expand...
Click to collapse
midas69 said:
With older versions I was able to do that. But this newer version I have installed doesn't really work that way. It creates 2 folders for a backup. One has the backup name with just a small file inside. The other folder is called BLOBS ...
Click to expand...
Click to collapse
Change the backup format to "tar" and you'll get the old directory structure back.
Related
I put the latest touch recovery from clockworkmod into a flashable zip.
It works with ICS. It is the same recovery as the one you would have to pay for to install with ROM manager.
TO INSTALL CWM TOUCH RECOVERY........
Flash this in recovery as you would any ROM or mod.
Here is the link:
http://db.tt/Ud9qVq7V
I found the recovery http://www.clockworkmod.com/rommanager
**** This is different than sk8tr's version btw. His has a custom ui and this is CWM official. ****
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
If anyone is wondering this doesn't look like its a disaster just as 5.8.4.3 was. I flashed miui and it booted up fine but if anyone has any issues please share.
Sent from my SGH-I727 using xda premium
Working good on my Hercules just flashed aokp jb and aint need any superwipe scripts either
thank you, works great!
Updated op to avoid confusion.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Thanks for the info!
sent from a device using an app
Okay, so I ran a backup and restore test on cm9 and cm10. I thought it was sk8t's version causing me problems restoring backups but the issue is similar on this build.
The backup file that gets created doesn't contain all the data for a full restore -- much of it gets stored in the "blobs" folder in cwm (someone more knowledgeable than me can probably explain better). Also, it takes a REALLY long time to create a backup.
Using the standard restore doesn't work on (on this or on sk8t's version). I keep getting "error restoring system" message and it won't restore. I tried to do an advanced restore doing each part individually but that didn't work either.
Restoring an old rom from before they changed the backup method works fine though. I haven't tried restoring using ROM Manager yet but I may try that next--I'm thinking that's what the new system is designed for...
EDIT: Rom manager fails too. Same error restoring system message.
Please post here if you can successfuly backup and restore cm9 or cm10 (or any other roms) so we can figure out if its just me
skrambled said:
Okay, so I ran a backup and restore test on cm9 and cm10. I thought it was sk8t's version causing me problems restoring backups but the issue is similar on this build.
The backup file that gets created doesn't contain all the data for a full restore -- much of it gets stored in the "blobs" folder in cwm (someone more knowledgeable than me can probably explain better). Also, it takes a REALLY long time to create a backup.
Using the standard restore doesn't work on (on this or on sk8t's version). I keep getting "error restoring system" message and it won't restore. I tried to do an advanced restore doing each part individually but that didn't work either.
Restoring an old rom from before they changed the backup method works fine though. I haven't tried restoring using ROM Manager yet but I may try that next--I'm thinking that's what the new system is designed for...
EDIT: Rom manager fails too. Same error restoring system message.
Please post here if you can successfuly backup and restore cm9 or cm10 (or any other roms) so we can figure out if its just me
Click to expand...
Click to collapse
Did a backup on CM10 Alpha 1. It took awhile but didn't seem to take any longer than a CM 5.x backup. Modified a few things, updated a couple apps, and then did another backup - went a bit quicker. Doing a restore now but it's past the restoring system portion so I'm assuming it'll all be good. I'll edit this if it craps out at some point.
As for the blobs, this is new to CM6.x and from what I understand is supposed to make backups a little quicker and use less space as it will only backup what's been changed since a previous backup instead of the entire thing like CM5.x. Not sure at all on all the technical details but I'd suspect the blobs contain what's been changed at the point of backup and each backup "container" file indicate which blobs to restore...
EDIT: Restore completed just fine.
so you're saying that if I have a backup stored and create a new back up it only backs up the changes since the last one? If so, that sucks. I always like to keep a solid backup and then after numerous changes back up again and delete the old one. Looks like it's back to old faithful 5.8.1.3 for me.
(UPDATE) confirmed. My new backup was 20MB.
Honestly i prefer twrp recovery.. just wanted to provide this for those that needed it.
But, since TWRP does an UNCOMPRESSED backup i can have a nandroid backup done in a little over 2 minutes. Same for restore.. very fast.
TWRP can be set to compress the backup.. but i prefer speed over less space.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
copene said:
so you're saying that if I have a backup stored and create a new back up it only backs up the changes since the last one? If so, that sucks. I always like to keep a solid backup and then after numerous changes back up again and delete the old one. Looks like it's back to old faithful 5.8.1.3 for me.
(UPDATE) confirmed. My new backup was 20MB.
Click to expand...
Click to collapse
Here's the explanation of how it works:
https://plus.google.com/u/0/103583939320326217147/posts/L5aVZe7C9vg
pixelens said:
Here's the explanation of how it works:
https://plus.google.com/u/0/103583939320326217147/posts/L5aVZe7C9vg
Click to expand...
Click to collapse
Thanks. There should be a "FULL backup" and "BLOB backup" option. I'm rolling with 5.8.1.3 cause it's never fu**ed me over (yet).
copene said:
Thanks. There should be a "FULL backup" and "BLOB backup" option. I'm rolling with 5.8.1.3 cause it's never fu**ed me over (yet).
Click to expand...
Click to collapse
I'm not sure if I follow what the point would be? I thought the same, but after reading that and doing a few tests, I'm confident this will do just as well - if not better.
Might be worth mentioning/requesting from Koushik Dutta depending on your reasoning or need.
I think I figured out what the problem was for me in not getting backups to restore (but someone please post if you disagree). I was getting an "Error while restoring /system!" message every time.
Every time I make a backup I go into Root Explorer and change the backup name so that I know which rom it is. Today I did a backup and didn't change the backup name and I was able to restore it successfully.
Changing the name of yesterday's backup to it's original name, however, did not fix the problem. Those backups still won't restore.
skrambled said:
I think I figured out what the problem was for me in not getting backups to restore (but someone please post if you disagree). I was getting an "Error while restoring /system!" message every time.
Every time I make a backup I go into Root Explorer and change the backup name so that I know which rom it is. Today I did a backup and didn't change the backup name and I was able to restore it successfully.
Changing the name of yesterday's backup to it's original name, however, did not fix the problem. Those backups still won't restore.
Click to expand...
Click to collapse
I've always changed the name of my backup folder to make it more descriptive. One thing I read along time ago was that it only works if you don't include any spaces in the changed folder name. And I've never had any problems with restoring any of them. However, if you indeed did not include any spaces, then maybe it's been changed in CWM 6.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
plwalsh88 said:
I've always changed the name of my backup folder to make it more descriptive. One thing I read along time ago was that it only works if you don't include any spaces in the changed folder name. And I've never had any problems with restoring any of them. However, if you indeed did not include any spaces, then maybe it's been changed in CWM 6.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Didn't add any spaces. I only added cm9 or cm10 to the end of the file name (that's how I know I changed it back to the original names when I tried to restore yesterday's backups).
skrambled said:
Didn't add any spaces. I only added cm9 or cm10 to the end of the file name (that's how I know I changed it back to the original names when I tried to restore yesterday's backups).
Click to expand...
Click to collapse
Gotcha. That's interesting then; don't know what it could be.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Hey majic I got a suggestion to cut down on confusion. Put official in the title. At first I thought sk8 had to threads. I thank you kind sir for zipping and uploading this official version. You da man....
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
skrambled said:
Didn't add any spaces. I only added cm9 or cm10 to the end of the file name (that's how I know I changed it back to the original names when I tried to restore yesterday's backups).
Click to expand...
Click to collapse
never had issues changing names of back up folders, what did you use to change the folder name , you could have a space at the end of the file name and dont even know it, use backspace to delete it, if u know dos try its naming conventions
sorry but how is this recovery different from sk8's recovery? That one's also CWM Touch 6.0.1.0 and also flashable zip ... ?
Thanks!
I got a replacement GS3 from Verizon because my current one had a charge port issue. I rooted and am using CWM 6.0.2.3 and get "error while restoring /system" when I try tp restore the nandroid of my old phone to the new one. How do I fix this?
Did you change the name of the nandroid at all? It's also possible that the backup you made contained individual phone information specific to your old phone...I seem to remember a thread before that mentioned it wasn't a good idea to move a nandroid to a new Samsung phone.
Edit: I found the thread shortly after hitting submit - http://forum.xda-developers.com/showthread.php?t=1795031
laurasaurisrex said:
Did you change the name of the nandroid at all? It's also possible that the backup you made contained individual phone information specific to your old phone...I seem to remember a thread before that mentioned it wasn't a good idea to move a nandroid to a new Samsung phone.
Click to expand...
Click to collapse
No I didnt't change anything. Anyway I can fix this?
laurasaurisrex said:
Did you change the name of the nandroid at all? It's also possible that the backup you made contained individual phone information specific to your old phone...I seem to remember a thread before that mentioned it wasn't a good idea to move a nandroid to a new Samsung phone.
Edit: I found the thread shortly after hitting submit - http://forum.xda-developers.com/showthread.php?t=1795031
Click to expand...
Click to collapse
If anyone has a way I can workaround that, please help! I don't want to setup my phone all over again!
droxide said:
If anyone has a way I can workaround that, please help! I don't want to setup my phone all over again!
Click to expand...
Click to collapse
there are a couple of apps where you can just extract the nandroid apps on the play store, but if you want the full restore, the file is probably corrupted.
dragon1357 said:
there are a couple of apps where you can just extract the nandroid apps on the play store, but if you want the full restore, the file is probably corrupted.
Click to expand...
Click to collapse
Yeah I used to use titanium backup but my phone is very customized, CM10, diff kernel, and a very highly customized home screen so I'd rather restore the nandroid if there is some kind of workaround. I also want all my data, texts, etc. without using titanium backup. When I used ti backup in the past, I had a bunch of different issues restoring apps and data, force closes, etc.
http://forum.xda-developers.com/showthread.php?t=1949020
I followed the directions in the last post of that thread.. I made a backup of the new phone, moved the old nandroid from old phone to the twrp back up folder in my new phone. I copied the new backup name and deleted the new backup. i pasted the name into the old back up, I tried to restore and i get an error "no partitions selected for restore. Is it because Im using twrp and I made the old backup with CWM?
Someone help!
droxide said:
http://forum.xda-developers.com/showthread.php?t=1949020
I followed the directions in the last post of that thread.. I made a backup of the new phone, moved the old nandroid from old phone to the twrp back up folder in my new phone. I copied the new backup name and deleted the new backup. i pasted the name into the old back up, I tried to restore and i get an error "no partitions selected for restore. Is it because Im using twrp and I made the old backup with CWM?
Someone help!
Click to expand...
Click to collapse
That could be it. They back up with different formats. Cwm uses the blob folder twrp does not.
Sent from my SCH-I605 (AKA NOTE 2)
kintwofan said:
That could be it. They back up with different formats. Cwm uses the blob folder twrp does not.
Sent from my SCH-I605 (AKA NOTE 2)
Click to expand...
Click to collapse
Ok so how can I switch from TWRP to CWM without resetting everything?
droxide said:
Ok so how can I switch from TWRP to CWM without resetting everything?
Click to expand...
Click to collapse
Ya, you should be able to flash it through odin no problem
Sent from my SCH-I535
droxide said:
Ok so how can I switch from TWRP to CWM without resetting everything?
Click to expand...
Click to collapse
You can just use ez recovery from the play store
Sent from my SCH-I605 (AKA NOTE 2)
I don't know if it has to do with having installed a newer version of ClockworkMod Recovery (6.0.3.1), but when I go to restore a previous backup, I get "md5 mismatch!" and no recovery is done.
Things that my non-developer brain can think of that might be relevant:
I may have changed the name of the folder for the recovery (I didn't think this mattered)
I am trying to go from CyanogenMod M5 to a recovery of an M2 (don't think this should matter).
The recovery was made using a previous version of ClockworkMod Recovery (an earlier, but 2013, version)
The recovery folder was stored on my computer and I put it on my phone using USB on-the-go (I have tried this twice to make sure one wasn't corrupted or whatever).
Thanks for any pointers. Do have have to install an older version of ClockworkMod Recovery or is there something simpler I could do? Thanks! :good:
LudicrousPeed said:
I don't know if it has to do with having installed a newer version of ClockworkMod Recovery (6.0.3.1), but when I go to restore a previous backup, I get "md5 mismatch!" and no recovery is done.
Things that my non-developer brain can think of that might be relevant:
I may have changed the name of the folder for the recovery (I didn't think this mattered)
I am trying to go from CyanogenMod M5 to a recovery of an M2 (don't think this should matter).
The recovery was made using a previous version of ClockworkMod Recovery (an earlier, but 2013, version)
The recovery folder was stored on my computer and I put it on my phone using USB on-the-go (I have tried this twice to make sure one wasn't corrupted or whatever).
Thanks for any pointers. Do have have to install an older version of ClockworkMod Recovery or is there something simpler I could do? Thanks! :good:
Click to expand...
Click to collapse
Changing the name for CWM backups will cause md5 mismatches. If you did this, you should switch and use TWRP which allows native nandroid renaming. Delete your CWM backups and stick to TWRP. It could also be an issue between CWM backups over different CWM versions however if you renamed your backups and each of those renamed backups failed except the ones you left alone then you found your issue.
SlimSnoopOS said:
Changing the name for CWM backups will cause md5 mismatches. If you did this, you should switch and use TWRP which allows native nandroid renaming. Delete your CWM backups and stick to TWRP. It could also be an issue between CWM backups over different CWM versions however if you renamed your backups and each of those renamed backups failed except the ones you left alone then you found your issue.
Click to expand...
Click to collapse
Thanks for the insight. Seems like I should just be able to change the folder name back to what it was named by default, if I can make sure it is correct. Do you think that's worth trying or is it deeper than that? I'll use TWRP from now on since it seems to be more robust (CWM was just the recommended recovery from Cyanogenmod)
LudicrousPeed said:
Thanks for the insight. Seems like I should just be able to change the folder name back to what it was named by default, if I can make sure it is correct. Do you think that's worth trying or is it deeper than that? I'll use TWRP from now on since it seems to be more robust (CWM was just the recommended recovery from Cyanogenmod)
Click to expand...
Click to collapse
Depends on how much you value those nandroids. I only keep two on my phone so it's no thing for me to delete my backups entirely. You can rename them to their original names and your issue should go away.
Sent from my SCH-I535 using Tapatalk 4 Beta
Make sure the name of the backup folder doesn't have any spaces. When I renamed backups and had a space in the name I would get that same "md5 mismatch!" error.
Thanks! So renaming the backup to what it was originally allowed the backup to attempt to restore, but data could not be restored. Attempting to boot it resulted in nor getting past the boot animation. I wonder if it was because I didn't have enough space left on my phone or of it had to so with the newer firmware I installed. Or something else.
Slightly of topic at this point but not really. Any ideas why data could not be restored?
Sent from my SCH-I535 using Tapatalk 2
LudicrousPeed said:
Thanks! So renaming the backup to what it was originally allowed the backup to attempt to restore, but data could not be restored. Attempting to boot it resulted in nor getting past the boot animation. I wonder if it was because I didn't have enough space left on my phone or of it had to so with the newer firmware I installed. Or something else.
Slightly of topic at this point but not really. Any ideas why data could not be restored?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I had a similar issue about a year ago. I resolved it by generating a new md5, but I don't recall what method I used. Do a search for that.
My phones memory is almost full and i would like to delete everything from the virtual sd. But as far as i saw there are some strange files like "ADebugPath" or "Recovery-Tools", so i am a bit afraid of deleting everything.
I have s-off and rooted the phone because i wanted to flash cm11. So by deleting all the files from virtual sd i am afraid of deleting files that might affect adb or s-off. Is it going to be helpfull to send a print-screen of my files?
An other thought is that usually this type of files shouldn't be visible on sd but only on the root of the phone but i want to be 100% sure before doing anything.
Thanks a lot.
Nothing on the SD affects s-off, and pretty sure the same goes with adb. I don't know what that file is "ADebugPath", but I don't believe I have it and adb works fine.
In fact, there are folks on here that regularly format their SD (for instance, when they flash new ROMs) which if of course not mandatory, but just to "clean up shop".
The only things I would suggest you should keep on the SD are Titanium Backup files, and a known good nandroid. And possibly files for any apps (such as games). Other than that, everything can pretty much go.
You can always copy files to your computer before deleting them from the SD, in case you think you might want them later.
Shouldn't he mount via recovery and format? I was told that's the best way to format these integrated SD cards.
Sent from my HTC One X using Tapatalk
chrisb906 said:
Shouldn't he mount via recovery and format? I was told that's the best way to format these integrated SD cards.
Click to expand...
Click to collapse
You mean format using a computer, versus wipe in TWRP? I don't know if it would make much difference.
Or do you mean format, versus manually deleting selected files? I would guess from a technical standpoint a format is going to be better, to reduce fragments, etc. But the data is not written and read from the SD all that often (its not like its the OS memory), so in real world terms, I don't think it would make much difference.
I mean "mount USB storage" via recovery right click on it on PC and chose format
Sent from my HTC One X using Tapatalk
redpoint73 said:
Nothing on the SD affects s-off, and pretty sure the same goes with adb. I don't know what that file is "ADebugPath", but I don't believe I have it and adb works fine.
In fact, there are folks on here that regularly format their SD (for instance, when they flash new ROMs) which if of course not mandatory, but just to "clean up shop".
The only things I would suggest you should keep on the SD are Titanium Backup files, and a known good nandroid. And possibly files for any apps (such as games). Other than that, everything can pretty much go.
You can always copy files to your computer before deleting them from the SD, in case you think you might want them later.
Click to expand...
Click to collapse
I have already done a backup and copy everything to my pc (just in case) so i will format the sd card and after that i will put back for sure the backup and the titanium backup file. Thanks for you help i will let you know when i do the "cleaning" on my phone.
One more thing i changed the battery to a new one (of htc one x+) so do you know any programme that can test the mah just to check it is correctly recognized?
I wouldn't reinstall apps using TB. But that's your choice. I've run into nothing but probs using TB,but that could be just me
Sent from my HTC One X using Tapatalk
It's just you. Thousands of people, including me, have been using Titanium to backup and restore apps for years, that's why it's the single most popular and most used backup app for Android. If you're having problems with it, you're doing something wrong.
Sent from my Evita
Maybe my reasonings are cuz of all the system apps I restored.
Sent from my HTC One X using Tapatalk
Bad flashing has nothing to do with not being able to use Titanium.
Sent from my Evita
chrisb906 said:
I wouldn't reinstall apps using TB. But that's your choice. I've run into nothing but probs using TB,but that could be just me
Click to expand...
Click to collapse
I've restored apps and app data with Titanium countless times (every time I flash a ROM) on this device with no issue. Its migrating system data with Titanium that usually causes problems.
That is what I did. But I learned not to anymore. But I still don't use TB.
Sent from my HTC One X using Tapatalk
chrisb906 said:
Maybe my reasonings are cuz of all the bad flashing
Click to expand...
Click to collapse
Unless you have a definitive reason to blame Titanium, don't blame Titanium.
---------- Post added at 07:58 AM ---------- Previous post was at 07:54 AM ----------
chrisb906 said:
That is what I did. But I learned not to anymore. But I still don't use TB.
Click to expand...
Click to collapse
Its a well known issue that using Titanium to migrate system data does not work well. This is no surprise. You are trying to migrate OS specific data between different OS's, so obviously its not going to go well.
Titanium works perfectly to migrate apps and app data. If you want to make you life harder for no good reason, feel free. But others are going to be fine using the app properly.
Yea. Thanks. This was when I first started flashing Roms and modifying my device. But I learned
Sent from my HTC One X using Tapatalk
I did the format at the sd card throught the computer and i tried to flash the newest version of cm11 but i got an error.
So the format was ok and i deleted a lot of files without a problem. Does anyone know why i get this error. I had it one more before. After that i haven't manage to update the nightly! I tried to google it and i saw something strange like you have to go for an older version of your recovery!
So i decide to go for the PhilZ Touch as far i have read it is the best for cm11. But i still have the some error:
"E:Error executing updater binary in zip '/sdcard/cmupdater/cm-11-20140507-NIGHTLY-evita.zip'
Error flashing zip '/sdcard/cmupdater/cm-11-20140507-NIGHTLY-evita.zip'"
Any ideas why i get this error??
Thanks a lot.
If you read in the CM thread it says you need the latest TWRP recovery to flash the latest nightly.
Sent from my Evita
timmaaa said:
If you read in the CM thread it says you need the latest TWRP recovery to flash the latest nightly.
Sent from my Evita
Click to expand...
Click to collapse
As far as I read cm11 does not need any special recovery:
"Installation Instructions (These are all required)
S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
Update to 3.18 RUU or later.
Flash a custom recovery (TWRP/CWM with SELinux capabilities).
Download latest nightly from http://download.cyanogenmod.org/?device=evita.
Locate 4.4 Gapps via a quick Google search.
Wipe factory/data reset in recovery before installing CM11.0 (unless you are already on a CM11.0 build).
Reboot into recovery and install nightly and gapps.
can not flash if you have an old recovery but i saw that."
Ok but through reading, old version of CWM is fine. As far i have seen PhilZ Touch is the best CWM, most advanced and best choice for recovery (for cm11). That is what i use now....
Furthermore, before that i was using the unofficial recovery twrp-2.6.3.0 4.4. The latest one (until yesterday).
Can you please tell me where exactly did you see the thing about latest recovery??
So, i have to go for the "TWRP 2.7.0.8 Unofficial"????
Because to be honest i thought it is something else.... :/
What do you mean you thought it is something else? You need TWRP 2.7.0.8 to flash the latest nightly, that was reported pretty clearly.
Sent from my Evita
Had to replace my M8 and was hoping I could just nandroid from a prior backup on the previous (identical).
I created the folder structure, and TWRP will run the restore process, but it fails at system each time.
Any suggestions? Looks like I can restore data fine. Using CleanROM.
Thanks!
[Update] Flashing CleanROM over seems to retain most apps/settings as long as I don't wipe first (assume this is the same as wiping/flashing CleanROM then restoring data only).
Malaclypse5 said:
Had to replace my M8 and was hoping I could just nandroid from a prior backup on the previous (identical).
I created the folder structure, and TWRP will run the restore process, but it fails at system each time.
Any suggestions? Looks like I can restore data fine. Using CleanROM.
Thanks!
Click to expand...
Click to collapse
I did it but it was a while ago. I'm pretty sure you need to be on the same version of TWRP that you created the Nandroid with.
Duckman_UF said:
I did it but it was a while ago. I'm pretty sure you need to be on the same version of TWRP that you created the Nandroid with.
Click to expand...
Click to collapse
Thanks, good to know it's possible. I'm pretty sure I'm on the same version (when I installed recovery this time I just fastbooted the same image from the same adb directories I had setup last time).
Malaclypse5 said:
Thanks, good to know it's possible. I'm pretty sure I'm on the same version (when I installed recovery this time I just fastbooted the same image from the same adb directories I had setup last time).
Click to expand...
Click to collapse
That will work!
Duckman_UF said:
That will work!
Click to expand...
Click to collapse
I still fail at restoring system, but restoring data got me most of the way there (hopefully its stable! seems just fine so far).
Any suggestions I'd love to hear em (always thought this should be seamless but first time trying) and thanks for your feedback!
Malaclypse5 said:
I still fail at restoring system, but restoring data got me most of the way there (hopefully its stable! seems just fine so far).
Any suggestions I'd love to hear em (always thought this should be seamless but first time trying) and thanks for your feedback!
Click to expand...
Click to collapse
I don't quite understand why you would want to restore system. Flashing the rom is just as easy and much cleaner. There may be a problem with device ID from the old phone - really have no idea.
But going from one device to another I would flash the rom, restore data - done. You should have an identical phone.
berndblb said:
I don't quite understand why you would want to restore system. Flashing the rom is just as easy and much cleaner. There may be a problem with device ID from the old phone - really have no idea.
But going from one device to another I would flash the rom, restore data - done. You should have an identical phone.
Click to expand...
Click to collapse
Thanks! The only thing I lost by not restoring system are zip's/mods I flashed in twrp seperately, also Xposed framework settings (some didn't carry over). Thanks for the support!
OP, do you have Titanium Backup? It can extract from a Nandroid. Menu>Extract from Nandroid Backup. It takes a while, even if your backup isn't compressed, but it works just fine.
If you DON'T have Titanium, skip Google Play and just Google it. Buy it from his website. Costs you less, developer makes more money (Google doesn't get a cut) and you get a text file for a license. This is much easier than dealing with the license app. Just download the latest version whenever there's an update and stick it on your SD card/internal, and install it upon flashing a new ROM. Text license goes in the root of either. App will pick it up on first run. Real easy. And it can do a ton of other things, too.
I'm done it twice now on two separate Verizon refurbs to find the M8. It has always worked wonderfully for me. Saves a lot of time in setting back up. You do have to create a new TWRP folder though by doing in a quick backup on the new phone, the moving the backup into the new TWRP folder otherwise it won't see it. TWRP will create a new folder with a different set of numbers In your original TWRP folder. You just move it to that. I did it successfully with Viper one Rom twice now.