Related
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..
Hi all,
I like to do a complete back up of my stock Note 2 before I change anything.
Are the following procedures enough?
1) use CF-autoroot to root it
2) install CWM or TWRP (with either Odin or Rom Manager or Rom Toolbox)
3) do Nandroid backup (this will backup ROM+kernel, but not the radio/modem)
4) backup /efs with 'dd' command from a terminal shell prompt on Note 2 ( save everything from /dev/block/mmcblk0p3)
5) backup radio/modem with 'dd' command from a terminal shell prompt on Note 2 (save everything from /dev/block/mmcblk0p10)
I like to do this so that in the future I can restore it to the exact state as it is today (same ROM/kernel/radio/modem).
I'm still not sure how to restore /efs and radio/modem if I want to? Do I just 'dd' back from the saved image file?
Something like 'dd if=<my_save_img> of=/dev/block/mmcblk0p3' (to restore /efs)? Please advise.
Did I miss anything? Are the procedures correct?
Thank you very much for any comment/input.
mike
TWRP lets you choose what to backup.
It supports
EFS
Boot
Recovery
Modem
Cache
System
Data
CF autoroot is easy to use.
TWRP for n7100
http://teamw.in/project/twrp2/115
trintoidz said:
TWRP lets you choose what to backup.
It supports
EFS
Boot
Recovery
Modem
Cache
System
Data
CF autoroot is easy to use.
TWRP for n7100
http://teamw.in/project/twrp2/115
Click to expand...
Click to collapse
Thank you so much for your reply. I truly appreciate it. I did not know. I did read TWRP's project page
and it did not say what it backs up.
The reason I asked is that I like to make a complete 100% backup of my own phone, as it comes back from Samsung.
The GPS did not work on my Note 2 and I flashed the latest stock ROM from sammobile and it did not work either.
So I sent it back to Samsung and they said they found a software problem (can't download PRL. Preferred Roaming List, I think) and they updated the software on the phone. If it works (I will know later today), then I want to have a complete backup of my phone,
in case I need to restore it in the future.
I don't see it anywhere, just info about the ZVA -> ZVC update. I've made too many modifications to my root partition to try to switch them all back and just want to flash ZVC...
fldash said:
I don't see it anywhere, just info about the ZVA -> ZVC update. I've made too many modifications to my root partition to try to switch them all back and just want to flash ZVC...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2702422
Havnt seen one, Just unroot, flash, reroot or is your phone not able to un root?
As I said, too many changes to the system partition, there is no way it's going to flash the OTA even if I unroot. If I use the TOT everything gets wiped including sdcard space... Not ideal even if I take a Titanium Backup.
fldash said:
As I said, too many changes to the system partition, there is no way it's going to flash the OTA even if I unroot. If I use the TOT everything gets wiped including sdcard space... Not ideal even if I take a Titanium Backup.
Click to expand...
Click to collapse
What about a nandroid backup and then tot then restoring from the nandroid with titanium backup. To be honest though I'm
not sure how exactly the nandroid titanium backup restore process works though as I haven't done it myself.
That may be an option but never used a nandroid to restore in Titanium Backup either...
Your best bet is to use the ZVC tot method. Here's what I did:
Backup apps & settings with Titanium Backup.
Copy the contents of internal SD card to a PC (or Dropbox, etc)
Photos, Titanium Backup files, anything else you want to save
Restore via the .tot method.
Root your phone with IOROOT.
Put the copied SD card contents back on the phone.
Reinstall Titanium Backup from Play Store.
Restore all your apps/settings via Titanium.
I didn't have any problems. You also don't need to have a custom recovery this way, either.
hotbbq said:
Your best bet is to use the ZVC tot method. Here's what I did:
Backup apps & settings with Titanium Backup.
Copy the contents of internal SD card to a PC (or Dropbox, etc)
Photos, Titanium Backup files, anything else you want to save
Restore via the .tot method.
Root your phone with IOROOT.
Put the copied SD card contents back on the phone.
Reinstall Titanium Backup from Play Store.
Restore all your apps/settings via Titanium.
I didn't have any problems. You also don't need to have a custom recovery this way, either.
Click to expand...
Click to collapse
This is the method I took as well. It seemed to be the easier approach rather than trying to undo all of the system partition modifications.
hotbbq said:
Your best bet is to use the ZVC tot method. Here's what I did:
Backup apps & settings with Titanium Backup.
Copy the contents of internal SD card to a PC (or Dropbox, etc)
Photos, Titanium Backup files, anything else you want to save
Restore via the .tot method.
Root your phone with IOROOT.
Put the copied SD card contents back on the phone.
Reinstall Titanium Backup from Play Store.
Restore all your apps/settings via Titanium.
I didn't have any problems. You also don't need to have a custom recovery this way, either.
Click to expand...
Click to collapse
Can you do this using any current version of ROM or recovery? I'm on youdug's ZVA rooted version with TWRP 2.6.3.3 and some mods (camera and hotspot). Plus I have some frozen apps, etc. Don't know what that necessarily means as far as aboot, etc., but I would like to get on ZVC. Sorry for the newb questions.
Thanks.
esoh said:
Can you do this using any current version of ROM or recovery? I'm on youdug's ZVA rooted version with TWRP 2.6.3.3 and some mods (camera and hotspot). Plus I have some frozen apps, etc. Don't know what that necessarily means as far as aboot, etc., but I would like to get on ZVC. Sorry for the newb questions.
Thanks.
Click to expand...
Click to collapse
I've used this guide with out any problems
http://forum.xda-developers.com/showthread.php?t=2432476
They have the files also.
One thing I have noticed, you don't have to power phone off after you get it set to com 41, while in download mode. Just pull the USB, and reconnect.
I've tot'ted at least 10 times without issue. I've even had a buddy use the same thing no problem. If you have a question just ask
Sent from my Nexus 7 using Tapatalk
After upgrading to Lollipop FOB6 firmware using full odin and then rooting and installing TWRP, I have never been able to successfully restore a backup, ever!
From reading the dev forums it seems no one else has been able to do so either. Does anyone know what the heck is going on? Is there any toggle (like compression?) that we cant use?
This is a bit of a pain but not the end of the world. Certainly makes me hesitate to mess around with new roms though if I cant go back to my solid daily without having to start from scratch.
khanam said:
After upgrading to Lollipop FOB6 firmware using full odin and then rooting and installing TWRP, I have never been able to successfully restore a backup, ever!
From reading the dev forums it seems no one else has been able to do so either. Does anyone know what the heck is going on? Is there any toggle (like compression?) that we cant use?
This is a bit of a pain but not the end of the world. Certainly makes me hesitate to mess around with new roms though if I cant go back to my solid daily without having to start from scratch.
Click to expand...
Click to collapse
I think what is going on is that the directory structure in Lollipop is a little different from the one in Kitkat. To give you an example, the user installed applications in Kitkat are placed under /data/app like this:
/data/app/com.my.application.apk
But in lollipop the same app is installed as:
/dats/app/com.my.application.apk/base.apk
So a backup taken from your data partition in Kitkat cannot be readily restored in Lollipop. The directory structure is just wrong and nothing works. The solution is for someone to ether write a conversion script or for the TWRP people to incorporate such a script in their future releases.
najoor said:
I think what is going on is that the directory structure in Lollipop is a little different from the one in Kitkat. To give you an example, the user installed applications in Kitkat are placed under /data/app like this:
/data/app/com.my.application.apk
But in lollipop the same app is installed as:
/dats/app/com.my.application.apk/base.apk
So a backup taken from your data partition in Kitkat cannot be readily restored in Lollipop. The directory structure is just wrong and nothing works. The solution is for someone to ether write a conversion script or for the TWRP people to incorporate such a script in their future releases.
Click to expand...
Click to collapse
Thats true - I did read about that. And that would definitely explain being unable to restore a kitkat rom.
However, I cant even restore a lollipop backup after flashing a different lollipop rom! Even if they are both derived from the same FOB6 base! That is what is even more confusing. Try it - backup, wipe all the partitions except int and ext sd of course and then try to restore... it just doesnt work!
Way I dit it just use factory reset only don't wipe anything specialy internal storage and don't use format. While restoring TWRP formats partition that been restored. I'm using TWRP 2.7.2.0
I've had no problem restoring from a TWRP Backup on Lollipop numerous times.
najoor said:
I think what is going on is that the directory structure in Lollipop is a little different from the one in Kitkat. To give you an example, the user installed applications in Kitkat are placed under /data/app like this:
/data/app/com.my.application.apk
But in lollipop the same app is installed as:
/dats/app/com.my.application.apk/base.apk
So a backup taken from your data partition in Kitkat cannot be readily restored in Lollipop. The directory structure is just wrong and nothing works. The solution is for someone to ether write a conversion script or for the TWRP people to incorporate such a script in their future releases.
Click to expand...
Click to collapse
I noticed that in every folder in /data/app/ there is an apk called base and a folder lib, can i backup just the apk? Or when i need to share an apk or take an apk i need to take also rhe lib?
dugryce said:
I've had no problem restoring from a TWRP Backup on Lollipop numerous times.
Click to expand...
Click to collapse
What is your TWRP version? Also, did you do any wipes before you fully restored a backup?
khanam said:
After upgrading to Lollipop FOB6 firmware using full odin and then rooting and installing TWRP, I have never been able to successfully restore a backup, ever!.
Click to expand...
Click to collapse
Does yours ever end up losing touch screen sensitivity when you restore a backup? Mine always looks like it has fully restored everything, but then no response to screen taps.
senozlu1 said:
Way I dit it just use factory reset only don't wipe anything specialy internal storage and don't use format. While restoring TWRP formats partition that been restored. I'm using TWRP 2.7.2.0
Click to expand...
Click to collapse
Oh I'll try this and report back. Thanks
Sent from my SM-N900T using XDA Free mobile app
yummymango said:
What is your TWRP version? Also, did you do any wipes before you fully restored a backup?
Does yours ever end up losing touch screen sensitivity when you restore a backup? Mine always looks like it has fully restored everything, but then no response to screen taps.
Click to expand...
Click to collapse
Mine just fails. But then again I've been wiping the partitions before restoring. Maybe that impacts it?
Sent from my SM-N900T using XDA Free mobile app
khanam said:
Mine just fails. But then again I've been wiping the partitions before restoring. Maybe that impacts it?
Click to expand...
Click to collapse
One of the devs, who runs the Lollipop ROM I've been using, warned against restoring data. He suggested backing up apps + data through Titanium Backup instead. Maybe it depends on the ROM?
najoor said:
I think what is going on is that the directory structure in Lollipop is a little different from the one in Kitkat. To give you an example, the user installed applications in Kitkat are placed under /data/app like this:
/data/app/com.my.application.apk
But in lollipop the same app is installed as:
/dats/app/com.my.application.apk/base.apk
So a backup taken from your data partition in Kitkat cannot be readily restored in Lollipop. The directory structure is just wrong and nothing works. The solution is for someone to ether write a conversion script or for the TWRP people to incorporate such a script in their future releases.
Click to expand...
Click to collapse
Hi
I have a rooted S4 running Carbon. Im using TWRP 2.8.5.0 and can backup and restore any
KK rom with no issues. I can flash Lollipop and backup but it will not restore this backup.
Its says restore successful but then just boots back into recovery. If someone could resolve
this it would be great
Hello all,
TB doesn't seem to pick up the apk file when backing up which is quite frustrating. Does anyone have a solution?
i had backup using TWRP 2.8.7.0 my stock TW lollipop rom...Now i had flashed Dirty Unicorns v9.5...If i wanted to goto stock rom that nandroid backup wont work??? thats what people are complaining over here??
Hi,
I recently tried a custom rom on my old phone and it worked pretty well. I liked the OS and now want to also do that on my current phone. But i do still have a few questions i hope you can help me with.
- Can i make a full backup of my phone (with app data) to my PC or maybe to my old phone? I am currently not rooted and tried helium backup but saw that sadly not all apps allow a backup.
- I know about titanium backup. Is there some way (if the above cant be done) i can root my phone without wiping the phone? So i can then use titanium backup to make a proper backup with data, then install the custom rom and after restore the apps+data.
In short: I hope i can somehow make a full backup with app data so i can install the custom rom and restore my app data again.
Looking forward to your replies.
Thanks in advance.
Nothing? No one ? =(
To root you need to unlock the bootloader, which wipes all user data. So you can't use root to backup your data. This is why I unlock the bootloader immediately after getting a phone.
You can try an adb backup though.
razr96 said:
To root you need to unlock the bootloader, which wipes all user data. So you can't use root to backup your data. This is why I unlock the bootloader immediately after getting a phone.
You can try an adb backup though.
Click to expand...
Click to collapse
Thank you for your reply and thx for the tip. Ill be doing that too from now on when i get a phone.
As long as i can make a full backup with abd (with app data), Im fine with wiping to root it. But just wanted to make sure i can get app data back after the root process.
Do you happen to have a link to a proper backup using abd guide?
Thanks
no
sm00th4f3 said:
https://forum.xda-developers.com/android/general/how-to-backup-restore-android-device-t3602583
You might wanna read this and try it
https://forum.xda-developers.com/android/help/adb-fastboot-commands-bootloader-kernel-t3597181
Click to expand...
Click to collapse
Well with a few side searches i was able to open the cmd (admin), do a adb devices (which found a device) and then run the app + data command.
('adb backup -apk -shared -all -system -f C:\backup.ab')
I saw the screen on my phone to start it, which i did but it stays on Shared Storage (where before this mentioned the apk's that were being backed up). This is taking pretty long (as in hours). Is this normal or did something went wrong and is it stuck on that part?
Edit (Update): I stopped the whole thing and tried again. Now it finished in about 10 - 15 min. I did get a message "backup finished". However in the folder i gave up, there is nothing to see. folder is still empty
Edit2 (update): Found the backup.ab file. Apparently it was in a different folder i thought it would be. So if i then also make a copy of the internal storage and do this command, i should be good right? After doing that, unlock and root, i can use the 'adb restore C:\backup.ab' and have all apps + app data back as it was before the unlock/root ?
no
sm00th4f3 said:
In a sense. Yes, but you might wanna read some threads about that first.. Otherwise. No one would wanna go back after unlocking his phone. Since restoring a backup from a locked phone on an unlocked phone can cause some issues.
Click to expand...
Click to collapse
I'm not really sure what you mean though.
If i unlock my phone with my code and then make the backup with adb and just in case, a copy of my internal storage, can't i use restore on the unlocked/rooted phone to have the apps + their data back and use them again ?
no
sm00th4f3 said:
No you can't. It will brick your device. The backup can only be used when your phone is still locked. So it is basically not needed at all.
Click to expand...
Click to collapse
So you are saying that there is no possibility to backup my apps+data, unlock/root/custom rom, and then restore my apps+data at all?
That was some what the question of my first post.
So its either, fully wipe with everything lost, then root etc. etc. or just keep it the way i have it now?
no
sm00th4f3 said:
The normal procedure is as follows:
After an unlock.- your data always gets formatted. So a backup is totally wasted time.
The backup isn't wasted time - if it is done after unlocking your phone, while it still has stock rom.
In case flashing goes wrong, make the backup while not having flashed twro etc at all.
You don't have to wipe anything if you just want root, since the phone will reset-wipe your data on its very own.
Just unlock it, let it reboot, Flash twrp, install root zip file. Reboot
In case of flashing a custom rom. Flash twrp, boot to twrp. Use the Reboot menu and reboot again into recovery
Reboot->Recovery (in twrp menu).
Then Wipe-> Factory Reset
Wipe-> Advanced Wipe-> Wipe System partition only
Wipe-> Advanced wipe-> select Data partition-> Change file system to ext4
Reboot Menu in TWRP->Recovery
Wipe Dalvik and Cache
Flash Rom
Flash Gapps if not stated otherwise in Instructions of Rom Thread
Flash Magisk or SUperSu , depends if you want root or not. If you don'T want encryption on older Roms, flash one of the two.
Encryption will later on be optional through Phone Security Options.
Wipe dalvik and cache.
Reboot.
Wait a bit.
Setup phone, done.
Click to expand...
Click to collapse
Yes but as you mentioned, unlocking means a full wipe. And i cant restore apps + their data from a stock phone backup to an unlocked phone as it can cause issues.
In my very first post i asked if i could make a backup of the apps + their data to restore them after unlocking/rooting/custom rom or whatever. Simple answer then is no.
So i either have to just wipe my phone and basically start all over, only unlock/root etc etc first.
Or just keep my phone stock like how it is now and just do nothing and wait until i get a new phone (which will be in a long time still)