Since rooted phones can't take OTA's, we have special considerations before updating. (flash/wipe/then recover ... ). Google restores a lot but I've discovered not many system or app settings. TWRP makes full backups, but if your data is full of pics and videos there's not enough available space for backups.
I have Titanium Backup Pro but I'm not sure 'when' to use it for recovery. Individual app restores sure, but what about a complete restore? After a flash and boot, should I bypass the Google setups, install TiB, and restore with that? Will that give me a 100% restored device (all system and app settings)?
Will this work? Is there a better strategy? Or is it impossible to get 100% recovery.
Insight/ Advice are appreciated.
Can't systemless root take OTAs?
Keithn said:
Can't systemless root take OTAs?
Click to expand...
Click to collapse
From my limited understanding ... no! Any boot, recovery, or system mods cause OTAs to fail when trying to apply. Getting AP working is a different issue.
since i'm not comfortable using command line programs i find myself using NRT when an update is due. in the end it's just a graphical frontend with some instructions but it makes me feel more secure.
enough rambling, your question is answered in one of the FAQs in wugs homepage:
http://www.wugfresh.com/faqs/how-to-update-ota-not-working/ said:
If you use Titanium Backup it is recommended to only backup user apps + data (not system apps), because when you update to the new android version, the system apps are most likely updated, so restoring an old system app backup will overwrite your new system app with the legacy version; and if you were just to restore the data, it may be incompatible with the new version of the system app. There are some exceptions to this rule; as in – you might be able to get away with restoring some system data, however if you chose to go this route then make sure you just restore the data (not the app), you do so selectively (as in – one system app at a time), and you know how to delete that app data if it doesn’t work properly (Settings > Apps > All > navigate to the particular app > clear data > reboot your device.)
Click to expand...
Click to collapse
following that link, i mostly find my self making complete backups with TiBa and then following option #1 for smaller updates and #2 for bigger ones.
Broken303 said:
...
following that link, i mostly find my self making complete backups with TiBa and then following option #1 for smaller updates and #2 for bigger ones.
Click to expand...
Click to collapse
Thanks for the valuable info. It appears a full restore (all system settings) is impossible after an upgrade/update. Maybe restoring app data with a TiBackup is possible, but I'm still confused about the 'when' to do this - after the Google restore? Bypass the Google restore?
I recently moved away from Apple where their update/upgrade restore was almost 100%. Maybe some day Google will follow and this will be a moot point.
Mesmurized said:
Thanks for the valuable info. It appears a full restore (all system settings) is impossible after an upgrade/update. Maybe restoring app data with a TiBackup is possible, but I'm still confused about the 'when' to do this - after the Google restore? Bypass the Google restore?
I recently moved away from Apple where their update/upgrade restore was almost 100%. Maybe some day Google will follow and this will be a moot point.
Click to expand...
Click to collapse
google is certainly impoving on that part, it's only a matter of time until this kind of backup is fully implemented.
if you took a look at the link, you may have realised that at least with option 1 you would not have to go through the setup/restore process again.
in my case, i usually go for the restore option given, as it restores some of the system settings in a compatible way, which TiBa can not as already said.
another option, to carry over all of your settings to the update is to:
make a full backup with TiBa
unroot/reflash your current build (if you are using NRT choose 'no wipe mode' similar to the description in the FAQ. this way you don't have to restore anything and can ignore the next step.)
restore your full backup without fear of compatibility issues(never mind, can't restore system settings without root. stupid me.)
take OTA or trigger the update otherwise
in this case it would of course be pretty much useless to restore the google backup.
Broken303 said:
google is certainly impoving on that part, it's only a matter of time until this kind of backup is fully implemented.
if you took a look at the link, you may have realised that at least with option 1 you would not have to go through the setup/restore process again.
in my case, i usually go for the restore option given, as it restores some of the system settings in a compatible way, which TiBa can not as already said.
another option, to carry over all of your settings to the update is to:
make a full backup with TiBa
unroot/reflash your current build (if you are using NRT choose 'no wipe mode' similar to the description in the FAQ. this way you don't have to restore anything and can ignore the next step.)
restore your full backup without fear of compatibility issues(never mind, can't restore system settings without root. stupid me.)
take OTA or trigger the update otherwise
in this case it would of course be pretty much useless to restore the google backup
Click to expand...
Click to collapse
I checked out Option #1 and the rest of NRT for that matter. In fact I have NRT installed. What is does mostly depends upon stock and I have Pure Nexus. In addition, it's a toolkit. Toolkits isolate users from an "understanding" of the process. However, it's the understanding that is necessary to have a fully integrated backup/restore process and to respond to issues/problems that may arise. Bottom line, I don't use toolkits.
Mesmurized said:
I checked out Option #1 and the rest of NRT for that matter. In fact I have NRT installed. What is does mostly depends upon stock and I have Pure Nexus. In addition, it's a toolkit. Toolkits isolate users from an "understanding" of the process. However, it's the understanding that is necessary to have a fully integrated backup/restore process and to respond to issues/problems that may arise. Bottom line, I don't use toolkits.
Click to expand...
Click to collapse
ok then, i thought your switch to android was very recent and therefore you had very little experience. indeed toolkits are in the way of a learning curve when it comes to android.
to my knowledge the closest thing you can get to a full backup/restore process for manual updates is to use the google backup to restore the system settings and use TiBa to restore your own (user)apps and data (possibly overwriting the apps google may have tried to restore/-install). with pure nexus afaik being very close to stock using the tag to not wipe user data should in theory still work without causing problems.
Broken303 said:
ok then, i thought your switch to android was very recent and therefore you had very little experience. indeed toolkits are in the way of a learning curve when it comes to android.
to my knowledge the closest thing you can get to a full backup/restore process for manual updates is to use the google backup to restore the system settings and use TiBa to restore your own (user)apps and data (possibly overwriting the apps google may have tried to restore/-install). with pure nexus afaik being very close to stock using the tag to not wipe user data should in theory still work without causing problems.
Click to expand...
Click to collapse
If I understand correctly, do you recommend allowing Google to restore everything it wants, then running TiB restore after that?
Mesmurized said:
If I understand correctly, do you recommend allowing Google to restore everything it wants, then running TiB restore after that?
Click to expand...
Click to collapse
yes, basically. i would still be cautious when it comes to sms/mms and make a copy of every important file on the sdcard aswell.
the only problem i ever encountered this way was with whatsapp, which i had to reinstall and then manually move over its folder on the sd card from the previous installation.
Broken303 said:
yes, basically. i would still be cautious when it comes to sms/mms and make a copy of every important file on the sdcard aswell.
the only problem i ever encountered this way was with whatsapp, which i had to reinstall and then manually move over its folder on the sd card from the previous installation.
Click to expand...
Click to collapse
I have a separate app for call logs and SMS/text messages. I'll use it!
I always have everything on /sdcard backed up .... It's just those darn system/app settings that are missing. Oh well, thanks for your help. Think I've come a little closer to a full 100% restore.
Mesmurized said:
Since rooted phones can't take OTA's, we have special considerations before updating. (flash/wipe/then recover ... ). Google restores a lot but I've discovered not many system or app settings. TWRP makes full backups, but if your data is full of pics and videos there's not enough available space for backups.
I have Titanium Backup Pro but I'm not sure 'when' to use it for recovery. Individual app restores sure, but what about a complete restore? After a flash and boot, should I bypass the Google setups, install TiB, and restore with that? Will that give me a 100% restored device (all system and app settings)?
Will this work? Is there a better strategy? Or is it impossible to get 100% recovery.
Insight/ Advice are appreciated.
Click to expand...
Click to collapse
Just follow #10 from Heisenberg's rooting guide & your apps/data stay intact.
ING3NIEUR said:
Just follow #10 from Heisenberg's rooting guide & your apps/data stay intact.
Click to expand...
Click to collapse
That's the easy part! Restoring app settings and all of system settings is the hard part
Mesmurized said:
That's the easy part! Restoring app settings and all of system settings is the hard part
Click to expand...
Click to collapse
As long as you follow the guide and don't wipe your phone, then there's no need to restore your apps/settings. They should still be there on your phone. The only thing you have to restore is TWRP/root.
ING3NIEUR said:
... The only thing you have to restore is TWRP/root.
Click to expand...
Click to collapse
If a flash update is performed, do you still restore TWRP/root? I would think not as it would overwrite the newly flashed update and likely make the system unstable in the least or unbootable at the worst!
Mesmurized said:
If a flash update is performed, do you still restore TWRP/root? I would think not as it would overwrite the newly flashed update and likely make the system unstable in the least or unbootable at the worst!
Click to expand...
Click to collapse
If you are rooted, your phone will not take an OTA update. So you have two options....flash the new factory image or wait for somebody to upload a flashable update zip. The easiest way is to just download and flash the new factory image. If you follow the guide, you are also flashing stock recovery. So, you have to re-flash TWRP and root. Your data/apps stay intact.
ING3NIEUR said:
If you are rooted, your phone will not take an OTA update. So you have two options....flash the new factory image or wait for somebody to upload a flashable update zip. The easiest way is to just download and flash the new factory image. If you follow the guide, you are also flashing stock recovery. So, you have to re-flash TWRP and root. Your data/apps stay intact.
Click to expand...
Click to collapse
Thanks for you input, but after all this, at the least many system settings are lost even after Google does it's full restore. I know, I've done it many times. I'm looking for a process/strategy that restores system settings (and all data settings) after an upgrade.
Mesmurized said:
Thanks for you input, but after all this, at the least many system settings are lost even after Google does it's full restore. I know, I've done it many times. I'm looking for a process/strategy that restores system settings (and all data settings) after an upgrade.
Click to expand...
Click to collapse
Im very confused by this whole thread you have unlocked bootloader rooted phone running twrp and wondering how to stay up to date with latest google factory images?
You dont have to backup your phone to install the factory images and you can flash the new one over the current one. You can simply download the latest factory image from google and manually flash the files from fastboot or use the flashall.bat. just make sure to edit the flash allscript so it doesn't flash userdata or recovery as the flashing of userdata will delete your user data)
Flash the following from the factory image. Dont flash recovery or userdata (recovery will over write twrp and userdata will wipe your data partition.
Boot.img
Cache.img
System.img
Vendor.img
Radio.img
Then boot into recovery and reinstall su.
The_Automator said:
Im very confused by this whole thread you have unlocked bootloader rooted phone running twrp and wondering how to stay up to date with latest google factory images? ...
Click to expand...
Click to collapse
No. Please re-read post #1.
I want to restore all system and app settings AFTER a flash update. It is possible to retain many (most) app settings if the internal storage is not wiped, but this does not apply to system settings.
Mesmurized said:
No. Please re-read post #1.
I want to restore all system and app settings AFTER a flash update. It is possible to retain many (most) app settings if the internal storage is not wiped, but this does not apply to system settings.
Click to expand...
Click to collapse
Updates modify the system partition of the phone i have found that using titanium backup to restore system apps has always caused issues for me as the files have been modified by the update and you are then overwriting the update with settings from a previous version this can make settings copied incorrectly or cause issues with new features that have been implemented to the system partition. Personally I think it could create more issues than it solves is there a specific setting or thing you are trying to preserve?
Related
So heres a noob question.
If I use (Rouge currently) to do a "backup" under options. And then start flashing ROMs, if I restore that backup I did, does that get me 100% back to the point of when I did the backup? Meaning, it restores -everything- like it never happened?
I've always wondered this, so if I'm flashing things, I can always get back to my fully stable setup exactly like it never happened by restoring? Or does the backup via Rouge( or CWM, or whatever ) only back certain things and I'll have to do more setup after restoring to get back up and running exactly like I had the phone before?
Sorry for the noob question, just want to make sure I got this straight.
It will restore everything 100%. You also have the option to restore other partitions separate, system, boot, and the most important , data.
Sent from a phone with kNOw CIQ ...
TeamERA said:
It will restore everything 100%. You also have the option to restore other partitions separate, system, boot, and the most important , data.
Sent from a phone with kNOw CIQ ...
Click to expand...
Click to collapse
This is what I assumed, thank you for the confirmation!
Here is a follow up question:
If I do a Titianium Backup for apps and sys data. Then I flash a new ROM, I usually do a Titanium restore of both Sys and App data ... It gets me up and running the quickest.
1.) Is this safe, or will sys data mess with the ROM
2.) Is there a better, more supportable way to do this?
RubenRybnik said:
Here is a follow up question:
If I do a Titianium Backup for apps and sys data. Then I flash a new ROM, I usually do a Titanium restore of both Sys and App data ... It gets me up and running the quickest.
1.) Is this safe, or will sys data mess with the ROM
2.) Is there a better, more supportable way to do this?
Click to expand...
Click to collapse
1) It's always best NOT to restore system data when flashing a new rom. All your system data is specific to the rom you are flashing, so you don't want anything to conflict with the new data you are using now. Will cause a lot of problems in the long run.
2) TB is the best way to restore apps and apps+data that I know of. MyBackUp Pro is another good one, but TB works best for me. I'm sure there are others in the market also.
And I moved this to the Q&A section.
Well, this is what I thought too in fact I rooted my phone, installed CWM and the next step I performed was a nandroid backup thinking I could get my stock setup back if I ever wanted it. All was good. Then I flashed for a while and found a setup I liked and before proceeding I did another nandroid. THEN a while later I got to a point were I found myself, for time purposes wanting to fall back to my second backup so I thought: "hey, lets try restoring from this nandroid file I so maticulously spent time creating"!
That's when, for me at least, this whole nandroid Backup/Restore exercise falls on its face. Because when I tried to restore the backup I made it gave me a MD5 error..and I know there's a workaround that you can use by modifying the file I think that's basically what your doing? I didn't try it, I figured if the file needed to be modified before it could be restored what was the point anyway.? I just used my plan B which was Titanium Backup.
Anyway I keep my eyes open for an answer to this mystery, I think it has to do with the different CWM versions from one ROM to the next? Still not sure though?
Oh and hopefully this post wont just get rudely deleted like my first post on the same subject did? I made the same mistake you have by posting in the "General" area instead of the Q&A section!
the only time I have had a Android fail for md5 was when I changed the name of the backup. so maybe that's what you did?
RubenRybnik said:
So heres a noob question.
If I use (Rouge currently) to do a "backup" under options. And then start flashing ROMs, if I restore that backup I did, does that get me 100% back to the point of when I did the backup? Meaning, it restores -everything- like it never happened?
I've always wondered this, so if I'm flashing things, I can always get back to my fully stable setup exactly like it never happened by restoring? Or does the backup via Rouge( or CWM, or whatever ) only back certain things and I'll have to do more setup after restoring to get back up and running exactly like I had the phone before?
Sorry for the noob question, just want to make sure I got this straight.
Click to expand...
Click to collapse
I have done many restores and everything comes back just like it was before.
---------- Post added at 12:40 PM ---------- Previous post was at 12:28 PM ----------
RubenRybnik said:
Here is a follow up question:
If I do a Titianium Backup for apps and sys data. Then I flash a new ROM, I usually do a Titanium restore of both Sys and App data ... It gets me up and running the quickest.
1.) Is this safe, or will sys data mess with the ROM
2.) Is there a better, more supportable way to do this?
Click to expand...
Click to collapse
I only use Titanium backup to backup and restore specific apps on my phone. I use CWM for the system.
patrao_n said:
the only time I have had a Android fail for md5 was when I changed the name of the backup. so maybe that's what you did?
Click to expand...
Click to collapse
nope. I followed step by step...pretty hard to mess it up with qbking77 video's? Is there any other possible reason, you can think of?..and really, how many people test out thier restores? I'm just wondering?
Just one quick point of clarification regarding the Nandroid backup/restore. From what I've read, the restore will bring back your kernel and ROM but NOT the modem version. If the modem is important to you you'll have to flash that back separately.
Magicspell said:
Just one quick point of clarification regarding the Nandroid backup/restore. From what I've read, the restore will bring back your kernel and ROM but NOT the modem version. If the modem is important to you you'll have to flash that back separately.
Click to expand...
Click to collapse
Good point ... Thanks to everyone for the replies, got a much better understanding on the backup/restore process in both cwm and titanium now ) Thanks!
One more question about the MD5 ... So you can not change the name of the backup of CWM? I didn't think name change would effect how MD5 is generated.
RubenRybnik said:
Here is a follow up question:
If I do a Titianium Backup for apps and sys data. Then I flash a new ROM, I usually do a Titanium restore of both Sys and App data ... It gets me up and running the quickest.
1.) Is this safe, or will sys data mess with the ROM
2.) Is there a better, more supportable way to do this?
Click to expand...
Click to collapse
You can also use your latest nandroid back up to restore data. I just tried this as a test with my wife's phone (i also did a separate back up in TB just in case) and it works well.
She was on one of Calks ROMs, and I wanted to switch her to the bare version of the ROM. I wiped data/cache/dalvik, installed the bare rom and rebooted. Once booted, I verified everything was gone (apps, contacts, sms, settings, ect). Then I went back to CWM and went to back up and restore->advanced restore-> restore data. When I booted back up, all her apps, contacts, sms, settings were back. I guess this would be a quick and dirty way to restore your stuff when jumping between a lot of ROMS.
s9amme said:
You can also use your latest nandroid back up to restore data. I just tried this as a test with my wife's phone (i also did a separate back up in TB just in case) and it works well.
She was on one of Calks ROMs, and I wanted to switch her to the bare version of the ROM. I wiped data/cache/dalvik, installed the bare rom and rebooted. Once booted, I verified everything was gone (apps, contacts, sms, settings, ect). Then I went back to CWM and went to back up and restore->advanced restore-> restore data. When I booted back up, all her apps, contacts, sms, settings were back. I guess this would be a quick and dirty way to restore your stuff when jumping between a lot of ROMS.
Click to expand...
Click to collapse
So just to be clear ... "Restore Data" in CWM is just Apps and Apps data, no system data is restored correct?
RubenRybnik said:
So just to be clear ... "Restore Data" in CWM is just Apps and Apps data, no system data is restored correct?
Click to expand...
Click to collapse
Yes on apps and data.
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..
I got a few battery saving apps and one or two of them required xposed. now my phone keeps boot-looping. i tried deleting what i could find of the apps in twrp, it did not help. i dont want to remove my root, custom kernel, and all my custom stuff in general.. and i have apps that i cant log out of without losing everything, such as chats, unread messages, etc. so basically i REALLY dont want to factory reset. ive done that probably 5 times over the past few months of having an android phone. what should i do? help
stiarlitserenity said:
I got a few battery saving apps and one or two of them required xposed. now my phone keeps boot-looping. i tried deleting what i could find of the apps in twrp, it did not help. i dont want to remove my root, custom kernel, and all my custom stuff in general.. and i have apps that i cant log out of without losing everything, such as chats, unread messages, etc. so basically i REALLY dont want to factory reset. ive done that probably 5 times over the past few months of having an android phone. what should i do? help
Click to expand...
Click to collapse
Can you mount userdata partition in TWRP? If so back up right away and move the backup data off your phone before continuing.
Do you have a TWRP backup you can restore? Start with system and boot. If you are lucky the bootloop is because of changes you made in system and this will get you booting.
If not, see if you can restore boot and system from factory images.
Worse case, you might need to factory reset again and reinstall yet another time.
Reflash rom, kernel and supersu. You shouldn't lose anything doing that.
sfhub said:
Can you mount userdata partition in TWRP? If so back up right away and move the backup data off your phone before continuing.
Do you have a TWRP backup you can restore? Start with system and boot. If you are lucky the bootloop is because of changes you made in system and this will get you booting.
If not, see if you can restore boot and system from factory images.
Worse case, you might need to factory reset again and reinstall yet another time.
Click to expand...
Click to collapse
im a newbie to all of this.. what will mouting user data partition do, and how do i do it?
backups dont work because i dont have enough free storage. i do have one backup but it was back when i restored my phone to factory settings.
what will restoring boot and system from factory images do, and how do i do it? will i lose all the customization i have on my phone?
stiarlitserenity said:
im a newbie to all of this.. what will mouting user data partition do, and how do i do it?
backups dont work because i dont have enough free storage. i do have one backup but it was back when i restored my phone to factory settings.
what will restoring boot and system from factory images do, and how do i do it? will i lose all the customization i have on my phone?
Click to expand...
Click to collapse
Lesson learned bud. Half of the reason for TWRP and CWM is to have a full recent/current backup. Its always been like this. All roms, tweaks, xposed, write-ups or threads all say "make a backup" A backup is needed when something goes wrong. Notice the word "when" its not a if something goes wrong. Playing with androids involves way to much stuff and things do go wrong. Everytime your gonna do something just make a backup and delete your previous backup. Keep the backup on a sd card and delete the previous one. You put yourself in a situation like street racing on the freeway in a thunderstorm on new years eve. Not being a **** but for years and years now there a thousands of tutorials on this stuff. How to use adb, fastboot, twrp, soft brick, hard brick, de-brick tool. I don't know where the link is but I have a xposed script to flash in recovery that disables xposed and all modules from recovery in case of a bad module. If that can be found still I suggest that using xposed
FYI. The two replies before this told you what to do. If your looking for a easy everything is 100% going to be ok and you won't lose your text messages its probably not going to happen.
stiarlitserenity said:
what will restoring boot and system from factory images do, and how do i do it? will i lose all the customization i have on my phone?
Click to expand...
Click to collapse
If you are on the stock rom, flash the stock boot.img and stock system.img either in TWRP or via fastboot will erase any mods in /system (including Xposed). This will return you to a stock setup. Your apps, sms, and data would be retained.
To do this, download the factory image that matches your rom base. The July OTA is MTC19Z by the way. June is MTC19V, you'll have to remember which one you were on. This can be found on Google's Nexus factory image website. Next, unzip the downloaded file then flash the boot.img and system.img in TWRP (transfer the files to your phone). Alternatively, you could learn to use fastboot. Follow section 10 of this amazing guide by Heisenberg, but flash only boot.img and system.img.
You *should* be able boot up and learn from your mistakes as others have said. If you still have issues, factory reset and charge this loss to the game.
Sent from my Nexus 5X using Tapatalk
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)
CHANGED: You must flash the dm-verity.zip on ROM install to use the backup/restore feature of TWRP. It won't work if /data is encrypted. I jumped the gun when making this thread.
EDIT2: I had also flashed dm-verity on install so /data wasn't encrypted.
Which Dm Verity did you use which version??
Does this mean even today with the latest versions of twrp and magisk you cant restore the backups made of an encrypted phone? I just got a new Moto G7 Power and got it setup with those two things and made a backup - havnt tried restoring yet. Does your solution of flashing the dm-verify.zip thing mean the phone will be unencryped then? Because I cant have that, I rather not have backups. What about the old "adb backup" type command line does that still work?
I've had my phone since the day they were available at metro and I can't and don't even try to backup or restore anything anymore. On roms it always has broken lockscreen where you cannot secure phone. Because of this I stay encrypted and setup my **** all over again when I change roms.
flash713 said:
I've had my phone since the day they were available at metro and I can't and don't even try to backup or restore anything anymore. On roms it always has broken lockscreen where you cannot secure phone. Because of this I stay encrypted and setup my **** all over again when I change roms.
Click to expand...
Click to collapse
I see, too bad it's a nice function to backup/restore I guess I'll just backup my important data individually and try not to mess up my Rom.
TaZeR369 said:
I see, too bad it's a nice function to backup/restore I guess I'll just backup my important data individually and try not to mess up my Rom.
Click to expand...
Click to collapse
Check this out. I haven't used it yet but I'm about to try it. Join «Migrate - Custom ROM Migration Tool» on Telegram: https://t.me/migrateApp
https://forum.xda-developers.com/android/apps-games/app-migrate-custom-rom-migration-tool-t3862763
There's a new add-on for it on telegram link
TaZeR369 said:
I see, too bad it's a nice function to backup/restore I guess I'll just backup my important data individually and try not to mess up my Rom.
Click to expand...
Click to collapse
Me too. I haven't a bit of luck with encrypted stock restores. I was told it would work if you don't restore /data, but when I made a backup without /data, it failed to restore. I HAVE been able to restore unencrypted customs though. I only backed up system, data, and boot when I succeeded. It's been a while. I think you have to wait a long time for the 1st boot after the restore, as if it were rebuilding ART or something. Haven't had any luck stopping stock from encrypting either. I hate not messing up my ROM. Boring.....
Perhaps I am missing a critical detail, but I just successfully restored my latest LOS(lineage-17.1-20200524-UNOFFICIAL-ocean) & older CRD(crDroidAndroid-10.0-20200405-ocean-v6.4) backups(*) using TWRP(twrp-installer-3.3.1-2-ocean).
SELinux is NOT enforced, but "Trust"(lulz) claims the phone is encrypted.
My methodology requires installing the same base f/w I used when originally installing the ROM(former newest RETAIL for CRD & newest RETUS for LOS), root, flash copy partitions zip, flash>factory reset>1st boot of the original ROM zip, enable debug, install TWRP, boot into TWRP, wipe all & restore backup(*).
I just restored successfully 2x's on my xt1955-5.
I loaded LOS 10 & 3rds from scratch, made all my settings tweaks & made Titanium b/u(JIC), made TWRP b/u(*) then restored my previous CRD daily install using steps above. Then I repeated the above steps(again) to go back to my new, fresh LOS. It is annoying to have to reload f/w, et al, but def easier than reloading & retweaking the OS & all 3rds from scratch... Titanium fails to restore most settings + other nits.
To restore a backup(*) of a ROM I am currently running, I just boot to TWRP, wipe all & restore.
*: To make the original TWRP backup, I will run it & it will fail. I open the log file and find the last file/folder that "error"ed, delete the offender & re-run backup(boot, data & system). It works for me, no DM-verity flash required.
As always, YMMV.
Edit: PS: The problems seem to be stemming from beta testing the new "Trust"(lulz) framework, on all 10 ROMs(?). Would be nice to get that ironed out. A new Recovery wouldn't hurt, either. AFAIK, these problems exist in OFR, too.
googleverifysux said:
Perhaps I am missing a critical detail, but I just successfully restored my latest LOS(lineage-17.1-20200524-UNOFFICIAL-ocean) & older CRD(crDroidAndroid-10.0-20200405-ocean-v6.4) backups(*) using TWRP(twrp-installer-3.3.1-2-ocean).
SELinux is NOT enforced, but "Trust"(lulz) claims the phone is encrypted.
My methodology requires installing the same base f/w I used when originally installing the ROM(former newest RETAIL for CRD & newest RETUS for LOS), root, flash copy partitions zip, flash>factory reset>1st boot of the original ROM zip, enable debug, install TWRP, boot into TWRP, wipe all & restore backup(*).
I just restored successfully 2x's on my xt1955-5.
I loaded LOS 10 & 3rds from scratch, made all my settings tweaks & made Titanium b/u(JIC), made TWRP b/u(*) then restored my previous CRD daily install using steps above. Then I repeated the above steps(again) to go back to my new, fresh LOS. It is annoying to have to reload f/w, et al, but def easier than reloading & retweaking the OS & all 3rds from scratch... Titanium fails to restore most settings + other nits.
To restore a backup(*) of a ROM I am currently running, I just boot to TWRP, wipe all & restore.
*: To make the original TWRP backup, I will run it & it will fail. I open the log file and find the last file/folder that "error"ed, delete the offender & re-run backup(boot, data & system). It works for me, no DM-verity flash required.
As always, YMMV.
Edit: PS: The problems seem to be stemming from beta testing the new "Trust"(lulz) framework, on all 10 ROMs(?). Would be nice to get that ironed out. A new Recovery wouldn't hurt, either. AFAIK, these problems exist in OFR, too.
Click to expand...
Click to collapse
Have u tried the new 3.5 twrp
Lol...and here it is a couple years later and I'm still searching whether a force-encrypted twrp backup of stock has been figured out how to restore...Pulled up my own thread. Lol.
i miss being able to backup android properly. it made me behave completely differently with my phone. it was a toy instead of just some tool. i'd just install every single rom, kernel modem operating system i could find or i'd just plagiarize the hell out of you guys for sh*ts and giggles and man i loved android so much back then but now its my cell phone. :\ i just liked the colorful language, i wasn't signing anybody else's code.
it's such a tedious thing now, even compared to before and i suppose that's their intention perhaps.