Related
I just did a CWM backup of my awesome ROM before I flasha new one (like I always does) and noticed it backed up awfully fast.
I just flashed the new 6.0.0.5 touch recovery so I booted back into Android before flashing a new ROM and noticed my backup folder in CWM was 20 megs...
Did my ROM really get backed up with data? Is all the info now in the "blobs" folder?
I am honestly tempted to just reflash the older CWM and do a backup just in case.
Is this normal?
Normal.
Backups are handled VERY differently for CWM now.
From what I understand:
Each file is diffed from the backup you're currently making to any old backups.
If the file was modified...a copy is made for your new backup.
If it wasn't...a reference to the file is made so that it doesn't have to copy said file over...it just says: Yes. File exists...it's here.
This cuts down on the a)
TIME. By a lot.
b)
Size...of incremental backups.
Edit:
This is just how my brain is processing the new CWM's features.
I've read nothing that states how it works...all I know is that YES, the above sizes are normal.
I'm generally pretty close in my assumptions...but I'm not a dev. Just...intuitive.
So if I'm wrong ::: Don't shoot me.
Makes sense.
here goes nothing...
Have done some reading a yesterday about this since I wanted to see if this was worthy of leaving my Old Touch Recovery.
It was worthy because the one feature that caught my eye was that it makes files smaller by compressing and preventing duplicated files in a back up.
This is why the back up is smaller(ish) and faster to back up and restore.
--------------------------------------------------
If I have helped you.... hit that sexy thanks button. ^_^
How can we safely delete old backups? I've read up on how it works, but it's still not clear. If I delete my oldest backup, will it render all the new ones useless because they don't have the duplicated files?
Well the ROM I flashed was fubar, couldn't get past the boot-animation, so I had to ADB enter recovery and did a CWM restore on 6.0.0.5 Touch, seems to work fine.
grantith said:
How can we safely delete old backups? I've read up on how it works, but it's still not clear. If I delete my oldest backup, will it render all the new ones useless because they don't have the duplicated files?
Click to expand...
Click to collapse
This is a good question. I'm thinking the same thing. If I have backup #1, #2, and #3 (the newest) where #3 is incremental differences from #1 and #2 will backup #3 be trash if I delete backup #1 and #2??
VTENGR said:
This is a good question. I'm thinking the same thing. If I have backup #1, #2, and #3 (the newest) where #3 is incremental differences from #1 and #2 will backup #3 be trash if I delete backup #1 and #2??
Click to expand...
Click to collapse
You delete the entire CWM folder and do a fresh backup.
Some of you may be thinking "well, how do I delete a backup?".
First, never delete the blobs directory. This would actually delete all your backups by rendering them unusable.
Simply delete the usual backup directory, and the next time you run a backup, all the unused hash files will be automatically delete (a process known as garbage collection). The recovery will show "Freeing space..." while this is happening.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1757146
"Simple delete the usual backup directory." Unfortunately I don't really get what that means. Any ideas?
grantith said:
How can we safely delete old backups? I've read up on how it works, but it's still not clear. If I delete my oldest backup, will it render all the new ones useless because they don't have the duplicated files?
Click to expand...
Click to collapse
Just to add, it looks like the app data and such is stored in the blobs folder, so if you delete an old "backup" from backup folder, but keep the blob folder intact, it will still restore fine.
grantith said:
http://forum.xda-developers.com/showthread.php?t=1757146
"Simple delete the usual backup directory." Unfortunately I don't really get what that means. Any ideas?
Click to expand...
Click to collapse
exactly what I just said above
This jump in recovery version confuses the hell out of me, I honestly don't understand it. I have 9 different rom's backed up on my phone and I want to update them but I've read stories of people having issues restoring old backups. My question is do I need restore to each rom with a version of clockworkmod 5 then flash clockworkmod 6 and back up with clockworkmod 6?
masully84 said:
This jump in recovery version confuses the hell out of me, I honestly don't understand it. I have 9 different rom's backed up on my phone and I want to update them but I've read stories of people having issues restoring old backups. My question is do I need restore to each rom with a version of clockworkmod 5 then flash clockworkmod 6 and back up with clockworkmod 6?
Click to expand...
Click to collapse
That's what I did.
Not sure if you "have to" but I didn't want to chance it.
orangekid said:
That's what I did.
Not sure if you "have to" but I didn't want to chance it.
Click to expand...
Click to collapse
Thanks man, yeah it seems like the safest way to approach it
masully84 said:
Thanks man, yeah it seems like the safest way to approach it
Click to expand...
Click to collapse
And it also sounds like it will conserve a lot of space because it won't double up on app data which matches your other ROMs.
Hello again.
Since I am under 10 posts and not allowed to participate in the relevant thread plus searching didn't yield any results I am posting here.
After one month of using my nexus I want to play with it and try some custom things that all people talk so much about.Fact is I first want to backup current state where everything works fine in case something goes wrong.
I 've already backed up my apps and their data with Titanium Backup.
Now I need current OS state bootloader, etc.Am I right to believe this is the NANDROID backup? Is this the backup that can bring the phone back to its current state?
Second thing is that the Galaxy Nexus Toolkit v7.8.0 I am using recommends backing up the EFS partition.Did some research that revealed this hidden partition is about the IMEI - I can't understand how such a valuable data isn't hardcoded inside the phone.But nevertheless I would like to know where are those backups (NANDROID and ESF partition) stored (already checked backups folder in toolkit).
My phone's current state is: unlocked bootloader, CWM recovery, rooted and on stock 4.1.1.No mods or any other custom file.
Another question regarding the CWM recovery.How is it possible to go back to the stock recovery? By flashing the stock ROM?
Also from GN Toolkit I flashed CWM Touch but after trying an update through CWM ROM Manager I got the manual version (both 6.0.1).Can I reflash the touch version from Toolkit?
Sorry if some of those questions sound silly but I am new in Android and prefer the safe path.
Thank you in advance.
TR-909 said:
Hello again.
Since I am under 10 posts and not allowed to participate in the relevant thread plus searching didn't yield any results I am posting here.
After one month of using my nexus I want to play with it and try some custom things that all people talk so much about.Fact is I first want to backup current state where everything works fine in case something goes wrong.
I 've already backed up my apps and their data with Titanium Backup.
Now I need current OS state bootloader, etc.Am I right to believe this is the NANDROID backup? Is this the backup that can bring the phone back to its current state?
Second thing is that the Galaxy Nexus Toolkit v7.8.0 I am using recommends backing up the EFS partition.Did some research that revealed this hidden partition is about the IMEI - I can't understand how such a valuable data isn't hardcoded inside the phone.But nevertheless I would like to know where are those backups (NANDROID and ESF partition) stored (already checked backups folder in toolkit).
My phone's current state is: unlocked bootloader, CWM recovery, rooted and on stock 4.1.1.No mods or any other custom file.
Another question regarding the CWM recovery.How is it possible to go back to the stock recovery? By flashing the stock ROM?
Also from GN Toolkit I flashed CWM Touch but after trying an update through CWM ROM Manager I got the manual version (both 6.0.1).Can I reflash the touch version from Toolkit?
Sorry if some of those questions sound silly but I am new in Android and prefer the safe path.
Thank you in advance.
Click to expand...
Click to collapse
toolkit is not a safe path for you.
read these:
http://forum.xda-developers.com/showthread.php?t=1812959
http://forum.xda-developers.com/showthread.php?t=1626895
http://forum.xda-developers.com/showthread.php?t=1529058
http://forum.xda-developers.com/showthread.php?t=1420351
learn how to troubleshoot and search, you'll be a whole lot happier. don't use toolkits.
TR-909 said:
Now I need current OS state bootloader, etc.Am I right to believe this is the NANDROID backup? Is this the backup that can bring the phone back to its current state?
Click to expand...
Click to collapse
nandroid doesn't backup the bootloader. if you ever need to go back to a specific bootloader version (which you won't), it is available online.
bk201doesntexist said:
toolkit is not a safe path for you.
read these:
http://forum.xda-developers.com/showthread.php?t=1812959
http://forum.xda-developers.com/showthread.php?t=1626895
http://forum.xda-developers.com/showthread.php?t=1529058
http://forum.xda-developers.com/showthread.php?t=1420351
learn how to troubleshoot and search, you'll be a whole lot happier. don't use toolkits.
nandroid doesn't backup the bootloader. if you ever need to go back to a specific bootloader version (which you won't), it is available online.
Click to expand...
Click to collapse
That's a lot of reading.
Anyway thanks for pointing me to those threads (I don't mind reading hehe) but still I don't understand why toolkit is so bad.In my view the toolkit just automates a set of commands which otherwise I would have to give through a command prompt.Only good thing I can find avoiding a toolkit, is getting a deeper knowledge on the subject but maybe the risks of doing something wrong are increased (say a typo)?
Anyway let me read those and I may be back.
TR-909 said:
That's a lot of reading.
Anyway thanks for pointing me to those threads (I don't mind reading hehe) but still I don't understand why toolkit is so bad.In my view the toolkit just automates a set of commands which otherwise I would have to give through a command prompt.Only good thing I can find avoiding a toolkit, is getting a deeper knowledge on the subject but maybe the risks of doing something wrong are increased (say a typo)?
Anyway let me read those and I may be back.
Click to expand...
Click to collapse
Toolkit is a automated set of other people's command, programme are coded by humans and human errors are bound to happen, not to mention if something went wrong somewhere, you won't know what went wrong. By doing the steps yourself, you will know exactly what went wrong, and it will simplify things should you have to ask questions here, which you most likely don't have to once you know how to use adb and fastboot, trust me.
Typos while doing your commands won't hurt because it simply will fail and not do anything. Immediately you will know you typed something incorrectly and know you have to do it again. With the kit you will not know at which step it failed so figuring out something will become a task. Doing it yourself sounds like it's longer and difficult but once you do it you will see how easy and simple it is plus you will understand what you did and why.
Sent from my Galaxy Nexus
TR-909 said:
[snip]
Now I need current OS state bootloader, etc.Am I right to believe this is the NANDROID backup? Is this the backup that can bring the phone back to its current state?
Click to expand...
Click to collapse
Yes and yes.
TR-909 said:
Second thing is that the Galaxy Nexus Toolkit v7.8.0 I am using recommends backing up the EFS partition.Did some research that revealed this hidden partition is about the IMEI - I can't understand how such a valuable data isn't hardcoded inside the phone.But nevertheless I would like to know where are those backups (NANDROID and ESF partition) stored (already checked backups folder in toolkit).
Click to expand...
Click to collapse
I won't comment on the toolkit, but nandroid backups are stored in /sdcard/clockworkmod/backup/ on your device.
As for the efs partition, you could back it up, but I don't really see what the necessity of it is. That partition is never written to by any ROM (stock or otherwise), so the only way it will get messed up is if you do something to it.
If you want to back it up on your device, just open a terminal window and type:
su
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/efs of=/sdcard/efs.img
That will store it in /sdcard, and then just copy it off your device.
TR-909 said:
Another question regarding the CWM recovery.How is it possible to go back to the stock recovery? By flashing the stock ROM?
Click to expand...
Click to collapse
Just pull the recovery.img file out of the version of the stock factory image that you are currently using, place it in the same directory where you have your fastboot.exe file, reboot your device into fastboot mode and type:
fastboot flash recovery recovery.img
Or, just save it to /sdcard on your device and type the following in a terminal:
su
dd if=/sdcard/recovery.img of=/dev/block/platform/omap/omap_hsmmc.0/by-name/recovery
TR-909 said:
Also from GN Toolkit I flashed CWM Touch but after trying an update through CWM ROM Manager I got the manual version (both 6.0.1).Can I reflash the touch version from Toolkit?
Click to expand...
Click to collapse
Can't help you out with any toolkit, sorry.
Hello efrant.
Seems you are the n00bs hero in here! I was reading your FAQ and threw some basic ADB commands through cmd to see how it feels ,lol.
Well reading made some good, I backed up through CWM but the backup size baffles me - only 21.4MB in total.Is this normal?
Also took a fresh backup with Titanium for all apps and data - this is a lot bigger 728MB in total.Still Storage (in Settings) reports that applications and their data hold 3.54GB.Is there some kind of ultra compression involved?
As for the stock bootloader I found that image (recovery-stock-jro03c-maguro) which I think is for my GN (GSM).I am asking in case something bad happens and go for a warranty claim.In that case I believe I 'll need to flash the stock bootloader, stock ROM and finally lock the bootloader.
As for the EFS partition is it impossible to be harmed? Say File System corruption, sdcard bad blocks, etc?
It's ok.I clearly understand your position on the toolkit and any similar programms out there.It's just they are so "convenient" and "time savers".Still you 're all right that most of the time you do not understand what you are doing when using toolkits.
Thanks to all of you for your great help. :good:
PS - to test my progress I am going to flash stock recovery through flashboot.I just hope I won't mess it up. :fingers-crossed:
To clear a few things:
TR-909 said:
As for the stock bootloader I found that image (recovery-stock-jro03c-maguro) which I think is for my GN (GSM).I am asking in case something bad happens and go for a warranty claim.In that case I believe I 'll need to flash the stock bootloader, stock ROM and finally lock the bootloader.
Click to expand...
Click to collapse
we don't have any custom bootloaders, as of yet.
TR-909 said:
As for the EFS partition is it impossible to be harmed? Say File System corruption, sdcard bad blocks, etc?
Click to expand...
Click to collapse
not impossible, but many many users never had any issues. to be on the safe side, back it up.
TR-909 said:
It's ok.I clearly understand your position on the toolkit and any similar programms out there.It's just they are so "convenient" and "time savers".Still you 're all right that most of the time you do not understand what you are doing when using toolkits.
Thanks to all of you for your great help. :good:
Click to expand...
Click to collapse
glad you understand. just because something is convenient doesn't mean that it's the best for you.
TR-909 said:
PS - to test my progress I am going to flash stock recovery through flashboot.I just hope I won't mess it up. :fingers-crossed:
Click to expand...
Click to collapse
easy. you can't fail with fastboot. like said before, if you type it wrong, it won't go through. :good:
'fastboot flash recovery recovery.img'
done.
Regarding the nandroid, copy off the whole clockworkmod folder.
Will the next nexus have a longer screen?
@bk201doesntexist: yes you 're right I was reffering to the stock recovery image.Thanks for correcting me
@Mach3.2: I 've read just the backup folder is needed (the one with the date and time).
For the sake of learning, I started in ADB then:
adb devices : to check I am online
adb reboot-bootloader: to get into fastboot
fastboot devices: check again status
and then
fastboot recovery recovery-CWM-touch-6.0.1-maguro
blah...
blah...
blah...
Finished and voila CWM touch recovery installed. :victory:
I am going to try with stock recovery but I am trying to find an official source to download it (if any).
EDIT: I see the only way to find the original recovery img is to extract it from the official ROM.So I am downloading from Google a .tgz and will continue from there.
Any comments for my backup sizes?
Now with my backups in hand what is the possible way to verify them? In theory with nandroid (from CWM recovery) and Titanium, I can restore phone in today's state.Right or wrong?
I am thinking of going a bit further flashing the stock ROM again (wiping everything) and then recovering from the backup archives as my next learning exercise.I should obviously backup photos, music, etc but I was wondering if SMS history is taken care by Nandroid or have to use a seperate application.Contacts are in google's server so np on that.
Thanks again.
TR-909 said:
[snip]
Well reading made some good, I backed up through CWM but the backup size baffles me - only 21.4MB in total.Is this normal?
Also took a fresh backup with Titanium for all apps and data - this is a lot bigger 728MB in total.Still Storage (in Settings) reports that applications and their data hold 3.54GB.Is there some kind of ultra compression involved?
Click to expand...
Click to collapse
If you are using the 6-series CWM, it does backups a little differently (incrementally), and stores the backup in two locations in /sdcard/clockworkmod. I personally use 5.5.0.2, which does a full backup and stores it in one location.
TR-909 said:
As for the stock bootloader I found that image (recovery-stock-jro03c-maguro) which I think is for my GN (GSM).I am asking in case something bad happens and go for a warranty claim.In that case I believe I 'll need to flash the stock bootloader, stock ROM and finally lock the bootloader.
Click to expand...
Click to collapse
As was mentioned above, all bootloaders available are stock bootloaders. A list can be found in the bootloader thread (link in my signature).
TR-909 said:
As for the EFS partition is it impossible to be harmed? Say File System corruption, sdcard bad blocks, etc?
Click to expand...
Click to collapse
But if you have bad blocks in the efs partition, you would probably need to get a new device, at which point you have no need for the backup, no? But I guess yes, better safe than sorry.
TR-909 said:
In theory with nandroid (from CWM recovery) and Titanium, I can restore phone in today's state.Right or wrong?
Click to expand...
Click to collapse
With a nandroid alone you can return to today's state.
TR-909 said:
I am thinking of going a bit further flashing the stock ROM again (wiping everything) and then recovering from the backup archives as my next learning exercise.I should obviously backup photos, music, etc but I was wondering if SMS history is taken care by Nandroid or have to use a seperate application.Contacts are in google's server so np on that.
Click to expand...
Click to collapse
Wiping from CWM does not wipe the data you have on /sdcard, so no need to backup photos, music, etc.
SMS will get wiped, but both Titanium and a nandroid will back them up. However, you can use a third-party app (there are many of them) to do it as well, which is simpler actually.
TR-909 said:
@bk201doesntexist: yes you 're right I was reffering to the stock recovery image.Thanks for correcting me
@Mach3.2: I 've read just the backup folder is needed (the one with the date and time).
For the sake of learning, I started in ADB then:
adb devices : to check I am online
adb reboot-bootloader: to get into fastboot
fastboot devices: check again status
and then
fastboot recovery recovery-CWM-touch-6.0.1-maguro
blah...
blah...
blah...
Finished and voila CWM touch recovery installed. :victory:
I am going to try with stock recovery but I am trying to find an official source to download it (if any).
EDIT: I see the only way to find the original recovery img is to extract it from the official ROM.So I am downloading from Google a .tgz and will continue from there.
Any comments for my backup sizes?
Now with my backups in hand what is the possible way to verify them? In theory with nandroid (from CWM recovery) and Titanium, I can restore phone in today's state.Right or wrong?
I am thinking of going a bit further flashing the stock ROM again (wiping everything) and then recovering from the backup archives as my next learning exercise.I should obviously backup photos, music, etc but I was wondering if SMS history is taken care by Nandroid or have to use a seperate application.Contacts are in google's server so np on that.
Thanks again.
Click to expand...
Click to collapse
The backup is just a shell, it's backed up in blobs, so you will need to copy the whole thing off.
You 're both right that in that the CWM recovery "image" is incremental and the base backup is the blops folder - now the total size is 1.75GB which is logical.
@efrant: thanks for clarifying on backup now it all starts making sense.I 've read Titanium Backup can pull individual files (may I call it selective restore) from a Nandroid backup, say a single app and its data.If that is so then the Titanium Backup could be used as a reserve app and that could save me some precious space.
efrant said:
SMS will get wiped, but both Titanium and a nandroid will back them up. However, you can use a third-party app (there are many of them) to do it as well, which is simpler actually.
Click to expand...
Click to collapse
I prefer to use less apps for doing the job so if Nandroid has the data it is fine with me.I hope it isn't that complicated to pull the data out.
@Mach3.2: You were right, my bad.The article I read was about CWM recovery 5.5.0.2 so now I copied the whole thing on PC. :good:
TR-909 said:
[snip]
I prefer to use less apps for doing the job so if Nandroid has the data it is fine with me.I hope it isn't that complicated to pull the data out.
Click to expand...
Click to collapse
The issue is that SMS's are stored as data for a specific system app (I can't remember which one at the moment). If you change ROMs, it is generally not a good idea to restore system apps or system app data via Titanium Backup, as those apps/data could cause some instability. You may get lucky, you may not.
efrant said:
The issue is that SMS's are stored as data for a specific system app (I can't remember which one at the moment). If you change ROMs, it is generally not a good idea to restore system apps or system app data via Titanium Backup, as those apps/data could cause some instability. You may get lucky, you may not.
Click to expand...
Click to collapse
Point taken.:good:
A bit more on the backup subject...
As I can see CWM recovery backups boot image, recovery image and the /system partition.I also saw in one of efrant's posts about different bootloaders but honestly I fail to comprehend the need for flashing a bootloader.
*In your "convert to latest yakju" post you recommend flashing it "5) Optional (NOT optional for n00bs) -- Flash the bootloader: fastboot flash bootloader bootloader-maguro-primela03.img (or whatever the name of the bootloader image that you downloaded)."
** Also the radio partition is a mystery so far.And I 've read a lot of guys talking of better connectivity (be it GSM, 3G, WiFi) through flashing custom (?) radio images.On list to be explored...
The recovery image is pretty straight and the system partition is the one with the OS - now all this can't be 1.7GB unless it backups the userdata partition too.
EDIT: It seems it also backups the data folder (hence the apps) so the size now makes sense.I reverted to 5.5.0.2 because incremental backup is fast and slick but brings two issues: first the "blops structure" gives me problems when I want to transfer those thousands of files via MTP and second it is much more practical when I want to backup completely different "builds" (that is my guess).
Also in between flashing ROMs a standard procedure is recommended about wiping data, clearing dalvik cache, etc
Could you please give me in details the series of tasks needed (or point me to a thread) for properly preparing a custom ROM installation when unlocked and rooted?
About restoration in the "new enviroment" I read this:
"If your bootloader is unlocked: yes, you can root (if you haven't done it already) and use TiB to backup apps + app data. Installing a ROM will not wipe your /sdcard. It's always a good idea to back it up though before a flash. Use TiB to restore apps + appdata to your new ROM. Be careful with system apps and settings, restoring such data can lead to issues."
Am I right in that "illegal" system apps are those painted with red colour in TiB?
Final steps I am going to backup SMS history and find a custom ROM to install.Any ROM recommendations for a "novice user" are welcome...
Off Topic: what would be the adb commands to push/pull folders (or files) from /sdcard to PC (eg. \sdcard\clockworkmod --> C:/Nexus) .Right now I am doing MTP transfers but would prefer the "adb way" if possible.
Thanks a lot for your support and sharing of knowledge!
PS - So much reading!
Wow, that's a lot of questions for one post! I'll try to tackle some of them.
TR-909 said:
As I can see CWM recovery backups boot image, recovery image and the /system partition.I also saw in one of efrant's posts about different bootloaders but honestly I fail to comprehend the need for flashing a bootloader.
*In your "convert to latest yakju" post you recommend flashing it "5) Optional (NOT optional for n00bs) -- Flash the bootloader: fastboot flash bootloader bootloader-maguro-primela03.img (or whatever the name of the bootloader image that you downloaded)."
Click to expand...
Click to collapse
I don't think anyone knows what changes are in each new bootloader revision (given that they are closed source), but some have had issues with running Jelly Bean on bootloaders older than LA03. I guess "newer is better" holds true in this case.
TR-909 said:
** Also the radio partition is a mystery so far.And I 've read a lot of guys talking of better connectivity (be it GSM, 3G, WiFi) through flashing custom (?) radio images.On list to be explored...
Click to expand...
Click to collapse
Again, no one know what changes are made in each radio revision. I personally have not noticed much difference among a lot of the radios, but others have said otherwise. (And no, there are no "custom" radios. All radios are stock -- just from different versions of Android. (A list of radios can be found in the radio link in my signature.)
TR-909 said:
The recovery image is pretty straight and the system partition is the one with the OS - now all this can't be 1.7GB unless it backups the userdata partition too.
EDIT: It seems it also backups the data folder (hence the apps) so the size now makes sense.
Click to expand...
Click to collapse
Yup, it backs up the cache, boot, recovery and system partitions, and everything in /data except /data/media (which is /sdcard).
TR-909 said:
I reverted to 5.5.0.2 because incremental backup is fast and slick but brings two issues: first the "blops structure" gives me problems when I want to transfer those thousands of files via MTP and second it is much more practical when I want to backup completely different "builds" (that is my guess).
Click to expand...
Click to collapse
I also like 5.5.0.2. I found it to be the most compatible, i.e., it has no issues flashing anything (that I have tried anyway), whereas other versions have issues with certain things.
And I personally wouldn't use MTP to transfer files -- it is flaky at best. ADB is much more stable.
TR-909 said:
Also in between flashing ROMs a standard procedure is recommended about wiping data, clearing dalvik cache, etc
Could you please give me in details the series of tasks needed (or point me to a thread) for properly preparing a custom ROM installation when unlocked and rooted?
Click to expand...
Click to collapse
There is not much to do:
1) Download ROM to /sdcard
2) Reboot into recovery
3) Nandroid
4) Wipe /data and /cache
5) Flash ROM
6) Reboot
TR-909 said:
About restoration in the "new enviroment" I read this:
"If your bootloader is unlocked: yes, you can root (if you haven't done it already) and use TiB to backup apps + app data. Installing a ROM will not wipe your /sdcard. It's always a good idea to back it up though before a flash. Use TiB to restore apps + appdata to your new ROM. Be careful with system apps and settings, restoring such data can lead to issues."
Am I right in that "illegal" system apps are those painted with red colour in TiB?
Click to expand...
Click to collapse
I think so. I haven't use TB in a while, so I just checked and it looks like you are correct -- red.
TR-909 said:
Off Topic: what would be the adb commands to push/pull folders (or files) from /sdcard to PC (eg. \sdcard\clockworkmod --> C:/Nexus) .Right now I am doing MTP transfers but would prefer the "adb way" if possible.
Click to expand...
Click to collapse
Have a read of the "basics" link in my signature. ADB is covered there.
Wow that's some great answers and a big motive for me to continue "digging".:good:
I will leave you in peace for the time being as here it's about to dawn.
Big thanks and have a nice day.
PS - To be continued...
There is a article on the main xda site about running a FTP server on your phone, maybe that will transfer the blobs faster than MTP.
Mach3.2 said:
There is a article on the main xda site about running a FTP server on your phone, maybe that will transfer the blobs faster than MTP.
Click to expand...
Click to collapse
Hey mach3.2.
FTP wouldn't help because WLAN (802.11g) can't beat USB 2.0 speeds.In fact it is quite slow for such file sizes.You 're right though in that through ES File Explorer I can send the whole Clockworkmod folder (and the blobs) normally to my PC without the "invisible files" issue I encountered with Windows Explorer and MTP.
Thanks for suggestion!
TR-909 said:
Hey mach3.2.
FTP wouldn't help because WLAN (802.11g) can't beat USB 2.0 speeds.In fact it is quite slow for such file sizes.You 're right though in that through ES File Explorer I can send the whole Clockworkmod folder (and the blobs) normally to my PC without the "invisible files" issue I encountered with Windows Explorer and MTP.
Thanks for suggestion!
Click to expand...
Click to collapse
With MTP, copying using FTP may just be faster
And just to mention, there's 802.11N on you devices, although it's only single stream w/ 1 antenna..
Hello, I recently rooted my wifes Note 2 that was on the latest OTA 4.3. Was not easy BTW. I did a back up in recovery of boot, system, and data. I figured I was good to go and start trying out other roms.
The first one I flashed was Macks Allstar 5.0 rom. Everything was great. Then my wife informed me that she did not have all of her contacts backed up to google and some were only saved to her phone. So then I figure I could just restore the original backup and extract the contacts and be able to install them to any rom.
Thats when everything went wrong. Everytime I tried restoring the back up,it would crash and recovery would do like a reboot. After many attempts I figured id try another version of recovery. After flashing many earlier versions of twrp and trying to restore, I finally was able to complete a restore from version 2.6. I was ecstatic. But then my heart sank again when boot always hangs on samsung logo. And that is where I'm stuck. I am able to flash other roms no problem but cant restore my original backup.
Needless to say my wife is ready to kill me.
Please if anyone could help me I would really appreciate it. I have searched throughout this forum and internet for hours and can not seem to find any help with this issue.
I am thankful to have been able to get this far with the help from the XDA community posts I never needed direct help even with prior phone rootings but this one has got me stumped. Thanks in advance
You need to flash Phil's recovery version 6.0.7.9. If you cant restore your backup with Phil's then I'm thinking you might be sol. Make sure you know where you saved the backup to. It's either on the phone's internal sd or external sd card. Choose the correct location in Phil's recovery and if it isn't corrupt it should work. You may also want to copy your backup onto your pc just in case because that's your only backup and doing a full wipe or odin restore could permanently delete it. Good luck.
tx_dbs_tx said:
You need to flash Phil's recovery version 6.0.7.9. If you cant restore your backup with Phil's then I'm thinking you might be sol. Make sure you know where you saved the backup to. It's either on the phone's internal sd or external sd card. Choose the correct location in Phil's recovery and if it isn't corrupt it should work. You may also want to copy your backup onto your pc just in case because that's your only backup and doing a full wipe or odin restore could permanently delete it. Good luck.
Click to expand...
Click to collapse
Thank you for your reply. I am at work right now and left the phone with my wife with a working rom. I will try phils recovery when I get home. As far as backups, I have two copies. One on my SD card and the other on PC but if they're both fried I guess that negates my efforts in redundancy. It's hard to believe the backup got corrupt so quickly. I have another backup of the 2nd rom I flashed and that one wont install as well.
Is there something I am doing wrong? If the backup file is corrupt, is there a way to extract contacts seperately out of backup?
Method b.
http://forum.xda-developers.com/showthread.php?t=2648855
My wife does that too. Sorry
ColeTrain! said:
Method b.
http://forum.xda-developers.com/showthread.php?t=2648855
My wife does that too. Sorry
Click to expand...
Click to collapse
Life of a married man. Haha!
Well, as my backup file was done with TWRP, I tried method B with TWRP recovery and it wont work so now I'm in the process of trying method A. Will update once I tried it.
I think my problem has to do with TWRP not playing friendly with 4.3 ROMS. If that is the case method A looks like it will work.:fingers-crossed:
alexandnen said:
Life of a married man. Haha!
Well, as my backup file was done with TWRP, I tried method B with TWRP recovery and it wont work so now I'm in the process of trying method A. Will update once I tried it.
I think my problem has to do with TWRP not playing friendly with 4.3 ROMS. If that is the case method A looks like it will work.:fingers-crossed:
Click to expand...
Click to collapse
That's exactly right. Bootloader isn't playing well with TWRP recovery. Phil"s 6.0.7.9 seems to be compatible in most ROM vs bootloader situations. Don't use latest version of Phil's recovery as it doesn't work as well and most people recommend this as well.
If Phil's recovery won't flash your restore then Odin all the way back to stock unrooted LK8 ROM then root it with the Toolkit and flash TWRP from the toolkit at the same time. Then see if you can restore at that point.
Looks like this project has come to an end. My wife likes her new rom and doesn't want to let me work on her phone anymore. She was able to get most of her contacts back I will make sure she backs her contacts to google and I will try to convince her to install Titanium backup to backup all her app data.
Unfortunately all I have is a work issued iphone that I have no interest in jailbreaking. I really don't see the point.
I am still confident that I could have eventually restored her backup successfully with the help here.
Thank you tx_dbx_tx and coletrain for your help.
Apparently, TWRP v2.8.6.2 compressed images to external SD cards are damaged, and it wiped my Recovery Mode and part of my previous Stock OS LRX22G.T800XXU1BOE2 installation.
I was able to Odin a Canadian copy of T800XXU1BOCC_T800XAC1BOC4_XAC, but it isn't working properly on my SM-T800.
Can somebody please point me to a US LRX22G.T800XXU1BOE2?
Thanks,
¿GJ?
¿GotJazz? said:
Apparently, TWRP v2.8.6.2 compressed images to external SD cards are damaged, and it wiped my Recovery Mode and part of my previous Stock OS LRX22G.T800XXU1BOE2 installation.
I was able to Odin a Canadian copy of T800XXU1BOCC_T800XAC1BOC4_XAC, but it isn't working properly on my SM-T800.
Can somebody please point me to a US LRX22G.T800XXU1BOE2?
Thanks,
¿GJ?
Click to expand...
Click to collapse
Always check sammobile.com
http://www.sammobile.com/firmwares/download/47566/T800XXU1BOE2_T800XAR1BOC5_XAR/
Ramer said:
Always check sammobile.com
http://www.sammobile.com/firmwares/download/47566/T800XXU1BOE2_T800XAR1BOC5_XAR/
Click to expand...
Click to collapse
Thanks, @Ramer - I checked Sammobile earlier this morning, and it wasn't there. They must have posted it later today.
I can't get to it right now, tho, their website may be having issues. I'll try later.
What do you mean the backup was damaged, what failed and which partition?
You can reflash recovery then just restore system. No need to do a full restore.
ashyx said:
What do you mean the backup was damaged, what failed and which partition?
You can reflash recovery then just restore system. No need to do a full restore.
Click to expand...
Click to collapse
Unfortunately. @ashyx - I'm not sure exactly where now. The recovery failure was almost instant (within the first 5 to 10 steps), and I remember that the error occurred right after a progress comment about EXT4. I lost the capability to boot up, and I lost the capability to get into Recovery Mode. My only option was to stay stuck in Download Mode, and hope that my battery didn't die before I was able to get a Odin image re-installed.
It was nerve-wracking.
I wasn't sure if the tablet would be charging while in Download Mode, and there was no way (that I knew of) to get out of Download Mode. I thought there was a high probability that I was about to permanently lose my brand-new tablet.
I paid for a subscription to Sammobile to get an older image installed until someone was able to get me the more recent stock image.
I'm too nervous to try and restore the image again without need, but I will definitely do it if you want me to. I understand the urgency to make sure that TWRP makes good images 100% of the time, and I am reluctant to do anything future to my tablet if I can't make a reliable back-up.
¿GJ?
Maybe your backup somehow got corrupted.
Which partitions were you actually trying to restore? For future reference if you made a backup of recovery don't restore it. Only restore it if you want to revert to a different version.
Also don't worry about bricking your device. As long as you still get download mode you will always be able to recover. I soft brick my tablet on a daily basis lol.
The only thing you need to flash to get into a bootable state is recovery. From recovery you can usually solve most issues. Even if your battery had died you would have been able to charge it and then power it back on. Also the tablet does charge in recovery mode.
Twrp can be a funny so and so sometimes. You just get the one time when it doesn't t behave as you expect. 99% of the time though its pretty solid.
I always find its good practise to restore a backup immediately after making it to ensure its sound. You don't want to wait until its too late to find out its corrupt.
ashyx said:
Maybe your backup somehow got corrupted.
Which partitions were you actually trying to restore? For future reference if you made a backup of recovery don't restore it. Only restore it if you want to revert to a different version.
Also don't worry about bricking your device. As long as you still get download mode you will always be able to recover. I soft brick my tablet on a daily basis lol.
The only thing you need to flash to get into a bootable state is recovery. From recovery you can usually solve most issues. Even if your battery had died you would have been able to charge it and then power it back on. Also the tablet does charge in recovery mode.
Twrp can be a funny so and so sometimes. You just get the one time when it doesn't t behave as you expect. 99% of the time though its pretty solid.
I always find its good practise to restore a backup immediately after making it to ensure its sound. You don't want to wait until its too late to find out its corrupt.
Click to expand...
Click to collapse
Thanks, @ashyx - Good advice on the partition recovery steps. Normally, I have automatically accepted the three defaults, and swiped. I will not do that anymore.
I have found TWRP to be very reliable in the past: If it's working fine, I always get a good backup. If it's failing on something, I always get a bad backup image, or always can't restore. I haven't had a random corruption yet. There was a problem I saw with TWRP and my Samsung GS3 a few years back where it would corrupt compressed archives, but uncompressed archives were fine. Maybe this is a replay on that problem.
I will backup my current CM12.1 image uncompressed, and then try just restoring my system & data partitions from the previous backup, and let you know what happens.
¿GotJazz? said:
Thanks, @ashyx - Good advice on the partition recovery steps. Normally, I have automatically accepted the three defaults, and swiped. I will not do that anymore.
I have found TWRP to be very reliable in the past: If it's working fine, I always get a good backup. If it's failing on something, I always get a bad backup image, or always can't restore. I haven't had a random corruption yet. There was a problem I saw with TWRP and my Samsung GS3 a few years back where it would corrupt compressed archives, but uncompressed archives were fine. Maybe this is a replay on that problem.
I will backup my current CM12.1 image uncompressed, and then try just restoring my system & data partitions from the previous backup, and let you know what happens.
Click to expand...
Click to collapse
I can assure you compressed backups should work fine. I have done it countless times. Probably just a one off for whatever reason, could be a failing sd card. You may find the backup is fine and will be ok to restore. I wouldn't be afraid to try again. When a backup fails to restore you usually only get an error message not a sudden crash and reboot.
Try making a compressed test backup by just backing up the cache partition then restore.
ashyx said:
I can assure you compressed backups should work fine. I have done it countless times. Probably just a one off for whatever reason, could be a failing sd card. You may find the backup is fine and will be ok to restore. I wouldn't be afraid to try again. When a backup fails to restore you usually only get an error message not a sudden crash and reboot.
Try making a compressed test backup by just backing up the cache partition then restore.
Click to expand...
Click to collapse
Well, as a point of reference, I just tried to restore system & data from my older (apparently corrupted) image.
I saw:
...
Wiping System...
Formatting System using make_ext4s function.
Restoring System...
E:extractTarFork() process ended with ERROR=255
I will follow your suggestion, and try writing a compressed Cache backup to see what happens.
¿GotJazz? said:
Well, as a point of reference, I just tried to restore system & data from my older (apparently corrupted) image.
I saw:
...
Wiping System...
Formatting System using make_ext4s function.
Restoring System...
E:extractTarFork() process ended with ERROR=255
I will follow your suggestion, and try writing a compressed Cache backup to see what happens.
Click to expand...
Click to collapse
Is this backup also encrypted. I have seen that error with encrypted backups in the official twrp. However this was fixed with an update pushed to the twrp repo which I have incorporated into the latest build.
Does your version of Twrp show your model number at the top?
ashyx said:
Is this backup also encrypted?
Click to expand...
Click to collapse
Yes.
ashyx said:
Does your version of Twrp show your model number at the top?
Click to expand...
Click to collapse
No, it just shows Team Win Recovery Project v2.8.6.2. It doesn't show any Samsung model numbers (If that is what you are asking).
I installed it using your All-In-One Root/Recovery tool.
Ok I think you're actually running an earlier build. I have updated builds below.
Install one of the f2s versions from the link below.
http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
ashyx said:
Ok I think you're actually running an earlier build. I have updated builds below.
Install one of the f2s versions from the link below.
http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Click to expand...
Click to collapse
Thanks, @ashyx! I'll download the SM-T800 F2FS version right now.
BTW, I've been really interested in installing F2FS. One thing I have been worried about, though, is that once I go down the F2FS path, it may be easy to really mess things up. For example, if I update a ROM, I would always need to use a F2FS ROM, or I might lose all my data - is that right?
Normally you would only format the data and cache partition to f2fs. There isn't much point formatting system to f2fs.
Also f2fs requires a special kernel. Myself and Tkkg1994(Iron Rom) have been working together to get this working properly. Still testing.
We are almost there.
Once formatted to f2fs you would need to reformat back to ext4 and flash a kernel to return back to normal. You could then flash your backup.
Hi at all,
with my new phone Xiaomi Mi A2 lite, I wanted doing the backup of my phone with TWRP, because in case of problem I will ready to restored it.
But I have discovery that the partition "data" is not visible because is encrypted and is impossible with TWRP to do the backup of it.
Is impossible use the storage of phone for make the backup beacuse it is also encrypted.
Is there anyone that has found a solution to decrypt and copy the partition in question?
Sorry by poor english and thanks all wonderfull team for the working doing.
If I were you, I would forget about our TWRP. It's just a half baked version which got official status by sponsorship. At best it's an early alpha version far from beeing useable.
thorin0815 said:
If I were you, I would forget about our TWRP. It's just a half baked version which got official status by sponsorship. At best it's an early alpha version far from beeing useable.
Click to expand...
Click to collapse
Thank you for the reply, I sad to reading this. So we must hope an next update for our TWRP. Now is impossible decrypted the partition entering the correct password or pattern.
So today is impossible do the full backup of app and setting....
liboriof said:
Thank you for the reply, I sad to reading this. So we must hope an next update for our TWRP. Now is impossible decrypted the partition entering the correct password or pattern.
So today is impossible do the full backup of app and setting....
Click to expand...
Click to collapse
i think you flashed the twrp image instead of booting it and then using the zip to install it. just redo the twrp installation exactly how it is written on the thread, encryption will work. restoring a backup however, does not (doesn't boot). for this you have to restore the data backup and then reflash the same rom the backup was made with from fastboot with the "flash_all_except_storage.bat". I would also recommend to do this before you try to reinstall twrp.
thorin0815 said:
If I were you, I would forget about our TWRP. It's just a half baked version which got official status by sponsorship. At best it's an early alpha version far from beeing useable.
Click to expand...
Click to collapse
Yes, it is far from usable but at least he built a working tree anyone could build a booting twrp from. it defenitely does not deserve the official status bcs this would mean it is maintained and working propperly.
wertus33333 said:
i think you flashed the twrp image instead of booting it and then using the zip to install it. just redo the twrp installation exactly how it is written on the thread, encryption will work. restoring a backup however, does not (doesn't boot). for this you have to restore the data backup and then reflash the same rom the backup was made with from fastboot with the "flash_all_except_storage.bat". I would also recommend to do this before you try to reinstall twrp.
Click to expand...
Click to collapse
Thank you for reply, I will try to do as you say and later I will write what happened.
I have used the guide by wertus33333 and it working. Thank you for your advice.