Hey guys, I hope you could answer some questions about nandroid backup and custom/stock ROMS.
Currently I have installed on my Note 3 SM N900 Android Lollipop 5.0, it is a stock samsung ROM. I've never flashed a custom ROM before. Recently I flashed a Custom Recovery and Rooted my phone. I would like to install a CM 12.1 ROM, I really hate all the bloatware on samsung stock ROM (Although I used Root Uninstaller, I'd like a clean android OS).
Searching on Google I found that doing a Nandroid Backup is as easy as going into recovery mode (Custom Recovery) and make a Back Up of everything, I mean "boot, System, Data, Cache, EFS, Radios", that is how is showed on TWRP v2.8.7.0. But there are other things showing up below this options, like "enable compression, skip MD5 generation during back up, disable free space check"
which options do I need to select if a want to make a full nandroid backup?
what does "skip MD5 generation during back up, disable free space check" options mean?
let's say I do a full nandroid backup, and a EFS folder (which I did the second I rooted my phone), and then I flash a Custom ROM, but there are too many bugs, or I just miss samsung stock ROM and I wanna go back to my previous ROM.
I'd just need to enter in recovery mode and do a restore of my previous nandroid backup (a stock ROM backup) and that's it? It'd be that simple? I'm thinking I'm missing something here.
Hope you can answer these doubts of mine. Thanks in advanced! :good:
YES Its that simple backup to ext sd card restore that backup .
.
"skip MD5 generation exactly what it says it generated no MD5 signature ( see Google md5)
Skipping MD5 generation means that you won't be able to check file integrity when restoring it. Not advised.
Disable free space check means that recovery won't check if it can store the backup files in the available space. Again, not advised.
totalnoob34 said:
Skipping MD5 generation means that you won't be able to check file integrity when restoring it. Not advised.
Disable free space check means that recovery won't check if it can store the backup files in the available space. Again, not advised.
Click to expand...
Click to collapse
JJEgan said:
YES Its that simple backup to ext sd card restore that backup .
.
"skip MD5 generation exactly what it says it generated no MD5 signature ( see Google md5)
Click to expand...
Click to collapse
Thank you very much for answering my questions!
Related
I am on stock, but rooted, nexus 7 4.2.2. I got notification of the software update sometime last week. I decided I would update. First, of course, I made a full nandoid backup, and titannium backup of all my apps and data. I downloaded rootkeeper and using rootkeeper "unrooted" and set about updating.
The Nexus rebooted, and entered the custom recovery mode (I think it is Amon RA) and then the update failed.
How can I update? What are your thoughts on the update? If I should avoid updating, how can I get rid of the software upgrade nag?
wiredwrx said:
I am on stock, but rooted, nexus 7 4.2.2. I got notification of the software update sometime last week. I decided I would update. First, of course, I made a full nandoid backup, and titannium backup of all my apps and data. I downloaded rootkeeper and using rootkeeper "unrooted" and set about updating.
The Nexus rebooted, and entered the custom recovery mode (I think it is Amon RA) and then the update failed.
How can I update? What are your thoughts on the update? If I should avoid updating, how can I get rid of the software upgrade nag?
Click to expand...
Click to collapse
You would need stock Android recovery for it to work I believe, so if you have a custom recovery, that is why it failed.
RMarkwald said:
You would need stock Android recovery for it to work I believe, so if you have a custom recovery, that is why it failed.
Click to expand...
Click to collapse
Thanks. I will look into that. Any thoughts on the update?
wiredwrx said:
Thanks. I will look into that. Any thoughts on the update?
Click to expand...
Click to collapse
You'd have to get stock Android recovery on there somehow, but if you're doing the official update and you removed any /system/app apps with Titanium Backup or anything, it'll also fail. If you flashed a custom kernel, it'll fail as well. Official updates run system checks to see that the stock files are all there and the correct versions.
You could backup everything you want to save on internal sd card (pictures/music etc), and flash the official factory Google images via fastboot. Or flash custom recovery and flash a 4.2.2 ROM. Either way, you'll have to wipe everything so you'll loose apps and app data, which you'll have to re-install again.
wiredwrx said:
The Nexus rebooted, and entered the custom recovery mode (I think it is Amon RA) and then the update failed.
Click to expand...
Click to collapse
The reason it failed is given in the recovery log file located at /cache/recovery/recovery.log
In general, OTAs are meant for 100% stock devices. When someone attempts an OTA on a rooted device, it can fail for hundreds of independent reasons - usually files in /system that got altered or removed by various root-privileged apps. (Sometimes it is not apparent to the end user that their root-using apps have even made such changes). In the current JOP40D -> JDQ39 OTA, the boot partition is also checked, so the OTA will certainly fail if you are using a custom kernel (in addition to any issues with modified files in /system).
Sounds like you are a person who makes Nandroid backups; good for you. If you have a Nandroid backup taken immediately after rooting (before any of these changes took place), it is possible that you could replace the altered files (by pulling the unaltered versions out of the old Nandroid Backups). Unfortunately, it is hard to know how much work this will be**, because during the initial check sequence that the OTA performs, it halts on the first error encountered. There could be only a single altered file causing trouble, several, or many.
** If you use TWRP recovery, the system (& data) image backups are tar files - you don't even need to restore an old backup to retrieve files from other backups.
As you mentioned TiBu, it sounds like your are farmiliar with all this stuff already. Rather than hand-patching your existing ROM, perhaps the right thing to do is to
- Make your TiBu & Nandroid Backups of your current ROM
- Install 4.2.2 factory image & Re-Root
- Make a Nandroid Backup of this (vanilla stock) ROM before you even boot it
- Boot it and restore your Market Apps. (I'm not a big fan of restoring System Apps or their data).
good luck
bftb0 said:
The reason it failed is given in the recovery log file located at /cache/recovery/recovery.log
In general, OTAs are meant for 100% stock devices. When someone attempts an OTA on a rooted device, it can fail for hundreds of independent reasons - usually files in /system that got altered or removed by various root-privileged apps. (Sometimes it is not apparent to the end user that their root-using apps have even made such changes). In the current JOP40D -> JDQ39 OTA, the boot partition is also checked, so the OTA will certainly fail if you are using a custom kernel (in addition to any issues with modified files in /system).
Sounds like you are a person who makes Nandroid backups; good for you. If you have a Nandroid backup taken immediately after rooting (before any of these changes took place), it is possible that you could replace the altered files (by pulling the unaltered versions out of the old Nandroid Backups). Unfortunately, it is hard to know how much work this will be**, because during the initial check sequence that the OTA performs, it halts on the first error encountered. There could be only a single altered file causing trouble, several, or many.
** If you use TWRP recovery, the system (& data) image backups are tar files - you don't even need to restore an old backup to retrieve files from other backups.
As you mentioned TiBu, it sounds like your are farmiliar with all this stuff already. Rather than hand-patching your existing ROM, perhaps the right thing to do is to
- Make your TiBu & Nandroid Backups of your current ROM
- Install 4.2.2 factory image & Re-Root
- Make a Nandroid Backup of this (vanilla stock) ROM before you even boot it
- Boot it and restore your Market Apps. (I'm not a big fan of restoring System Apps or their data).
good luck
Click to expand...
Click to collapse
Thanks for the detailed breakdown. I may just update with your instructions. Are you aware of a way to suppress the nag screen.
Hi
When I attempt to make a backup using TWRP v2.3.2.3 from Matt's 1.20 Utility I get this message:
"[BACKUP STARTED]
* Backup Folder: /external_sd/TWRP/
E: Unable to locate sd-ext partition.
Updating partition details..."
It finishes almost instantly and under the white text "Backup Complete" at the top of the screen it displays in red Failed.
I have 100% battery charge
Stock 4.1.2 with out the latest OTA
I already made one successful backup right after installing TWRP v2.3.2.3 on my phone from Matt's Utility the other day.
Phone is Rooted utilizing Matt's Utility
Bootloader is unlocked (Matt's Utility)
Under Settings I have checked Force MD5 check on all zips. and Enable MD5 verification on backup files.
Under Mount Menu all but Mount System are checked.
I am attempting to save the backup to my External SD. But it also fails when I try the internal storage
I don't know if this is a major issue but my time zone doesn't select the proper time.
Under the Advanced tab I selected Fix Permissions and it still fails.
I haven't messed with much else because I'm not sure what they will do. ADB Sideload, Reload Theme etc,...
I find this extremely odd. I have used Hash-code's Safestrap 3.12 for nearly a year with flawless performance always made a back up when I needed it to. when I unlocked my bootloader i was under the impression that TWRP was way better than SS, but here I am having problems the second attempt at making a backup?
Does it only save one backup at a time?
Is there a setting that I need to adjust?
Do I need to update/Upgrade to a new version?
Is there a version of Safestrap users like me with an unlocked bootloader?
Why cant it find the ext partition the TWRP folder is there and even tho it fails it places an empty folder in the proper location with the name I gave to my failed backup?
My SD card is partitioned for use with Link2SD. But that was never an issue with SS or the first TWRP backup I made the other day.
I have plenty of space (42 GB) on my external. so that shouldn't be the issue.
I'm starting to miss Safestrap. But I really want this to work. Help please. Thank you.
SARM1084 said:
Hi
When I attempt to make a backup using TWRP v2.3.2.3 from Matt's 1.20 Utility I get this message:
"[BACKUP STARTED]
* Backup Folder: /external_sd/TWRP/
E: Unable to locate sd-ext partition.
Updating partition details..."
It finishes almost instantly and under the white text "Backup Complete" at the top of the screen it displays in red Failed.
I have 100% battery charge
Stock 4.1.2 with out the latest OTA
I already made one successful backup right after installing TWRP v2.3.2.3 on my phone from Matt's Utility the other day.
Phone is Rooted utilizing Matt's Utility
Bootloader is unlocked (Matt's Utility)
Under Settings I have checked Force MD5 check on all zips. and Enable MD5 verification on backup files.
Under Mount Menu all but Mount System are checked.
I am attempting to save the backup to my External SD. But it also fails when I try the internal storage
I don't know if this is a major issue but my time zone doesn't select the proper time.
Under the Advanced tab I selected Fix Permissions and it still fails.
I haven't messed with much else because I'm not sure what they will do. ADB Sideload, Reload Theme etc,...
I find this extremely odd. I have used Hash-code's Safestrap 3.12 for nearly a year with flawless performance always made a back up when I needed it to. when I unlocked my bootloader i was under the impression that TWRP was way better than SS, but here I am having problems the second attempt at making a backup?
Does it only save one backup at a time?
Is there a setting that I need to adjust?
Do I need to update/Upgrade to a new version?
Is there a version of Safestrap users like me with an unlocked bootloader?
Why cant it find the ext partition the TWRP folder is there and even tho it fails it places an empty folder in the proper location with the name I gave to my failed backup?
My SD card is partitioned for use with Link2SD. But that was never an issue with SS or the first TWRP backup I made the other day.
I have plenty of space (42 GB) on my external. so that shouldn't be the issue.
I'm starting to miss Safestrap. But I really want this to work. Help please. Thank you.
Click to expand...
Click to collapse
first, I would recommend to uninstall SS via the app (not using the OS manage apps interface). secondly, I almost always mount system prior to making a backup - not sure if that makes a difference or not. thirdly, I have gotten the "failed" message before - and that usually happens when I have 3+ backups and/or running out of room on my external SD card. typically, I will delete one of the backups, and then it will back up. also, the process takes about 20 minutes, so I usually plug in my phone during this time (sometimes when the phone is plugged in, it performs better).
another issue could be that you are using 2.3.2.3 with the latest OTA - you mean the latest TWRP version. however, that said, I'm still using 2.3.2.3
hope this helps.
jco23 said:
first, I would recommend to uninstall SS via the app (not using the OS manage apps interface). secondly, I almost always mount system prior to making a backup - not sure if that makes a difference or not. thirdly, I have gotten the "failed" message before - and that usually happens when I have 3+ backups and/or running out of room on my external SD card. typically, I will delete one of the backups, and then it will back up. also, the process takes about 20 minutes, so I usually plug in my phone during this time (sometimes when the phone is plugged in, it performs better).
another issue could be that you are using 2.3.2.3 with the latest OTA - you mean the latest TWRP version. however, that said, I'm still using 2.3.2.3
hope this helps.
Click to expand...
Click to collapse
jco23
Thanks for the help brother. I appreciate it. But I found the answer on an older post on another forum. What corrected my issue was going to settings and pressing restore defaults. That's it! lol but after that it worked like a charm. thanks again.
respectfully:victory:
Ladies and gentlemen,
Recently, whilst flashing a new ROM, I had an issue. I tried to restore a backup that I created with TWRP 2.6.0 with the same version. I got to the "Restore data" stage in the logs, and it failed.
I have two data.ext4 files in my TWRP backup folder: the first is data.ext4.win000 and data.ext4.win001. I'm thinking this is the issue.
I have already flashed a ROM and booted, so I am out of the woods. Just wanted to know if anyone has had any success with split data files in a TWRP recovery.
Thanks for your time.
richardpunch said:
Ladies and gentlemen,
Recently, whilst flashing a new ROM, I had an issue. I tried to restore a backup that I created with TWRP 2.6.0 with the same version. I got to the "Restore data" stage in the logs, and it failed.
I have two data.ext4 files in my TWRP backup folder: the first is data.ext4.win000 and data.ext4.win001. I'm thinking this is the issue.
I have already flashed a ROM and booted, so I am out of the woods. Just wanted to know if anyone has had any success with split data files in a TWRP recovery.
Thanks for your time.
Click to expand...
Click to collapse
Look for TWRP-Recovery-jfltespr-2.5.0.2 seems to be the most reliable for backup and restores right now.
The 'splitting of the EXT/data is NOT the problem. That's the way twrp is compressing the images.
Also there are some ROMs that have partition problems with certain kernels, so take note of that.
I make a crap load of nandroids and switch back and forth pretty often. 2.5.0.2 has been the most reliable for me.
Once more thing I do is verify the nadroid via the AFV app. I boot to recovery, create backup (always of every partition) then boot to ROM and run the AFV app on the backup and make sure it verifies. Then I'll boot back to recovery and wipe/format and flash away according to the dev's instructions.
Leader,
Thanks for such an informative write up. I will check into rolling back to a different twrp build. It's an unpleasant solution, but if it works I'll have to bite the bullet.
Thanks again!
-Mobile post
heloo guys
i have n910f 5.1.1 with custom nameless rom
and i have TWRP installed
my qustion is
is the TWRP options of backup .. back every thing on device like apps system and etc.. ? or should i need download aroma ZIP and flash it with twrp and do the backup?
and the second Q is the TWRP install md5 rom / or just ZIP FILES ?
thanks alot
Anyone?? Up
bahaa119 said:
heloo guys
i have n910f 5.1.1 with custom nameless rom
and i have TWRP installed
my qustion is
is the TWRP options of backup .. back every thing on device like apps system and etc.. ? or should i need download aroma ZIP and flash it with twrp and do the backup?
and the second Q is the TWRP install md5 rom / or just ZIP FILES ?
thanks alot
Click to expand...
Click to collapse
1)TWRP Backup includes EVERYTHING. It creates an exact image of your phone. All apps, their data, sms, call logs, just everything, lol.
2)only Zip
aks_pk said:
1)TWRP Backup includes EVERYTHING. It creates an exact image of your phone. All apps, their data, sms, call logs, just everything, lol.
2)only Zip
Click to expand...
Click to collapse
So let me understand if I backup with twrp and I installed another rom and restore the backup of the old rom will not happen any thing wrong to new rom? Cause what I understood it's make Image for the rom it self and the data ....
bahaa119 said:
So let me understand if I backup with twrp and I installed another rom and restore the backup of the old rom will not happen any thing wrong to new rom? Cause what I understood it's make Image for the rom it self and the data ....
Click to expand...
Click to collapse
Nope the TWRP backup the system and rom also almost everything if you installed another rom and used the backup it will go back to the rom you had I think but if you can check backup data and apps only that will backup your apps and data only
Sent from my SM-N910C using XDA Free mobile app
Hey guys and gals!
After a few weeks of using the phone, I now feel comfortable doing a Nandroid Backup (TWRP).
I used to do it all the time on my OPO Kitkat, but now with Android Marshmallow, it's quite different.
Here is my situation:
A2017U (us version)
TWRP 3.0.2.2 Installed
Bootloaded Unlocked
Rooted
Xposed Framework v87 installed
Update B29 installed
Inside TWRP>Backup I have many options:
1- Boot (64MB)
2- Cache (2MB)
3- Data(6969MB)
4- Recovery (64MB)
5- System (3723MB)
6- System Image (6144MB)
7- EFS (4MB)
By default, the "Boot", "Data" and "System" are selected, but after some reading I could also backup "System Image" for a near-perfect restore.
Also, some said to backup the EFS in-case it gets corrupted/damage, but some say it can brick your device.
Could anyone tell me what should I backup in case I get stuck somewhere in the future.
Thank you !!
P.S: I have removed any fingerprints and set the lock screen to "Swipe" (no pattern).
First, make sure to flash the official twrp. Do not keep the one we use to unlock bootloader.
There is no harm in backing up efs, in fact it is a good idea to do so. Just do not select it during a restore unless something has wiped your current efs and its the only way to fix.
I don't see a need to back up a full system image but couldn't hurt to at least have one for safe keeping.
Boutchoo said:
Hey guys and gals!
After a few weeks of using the phone, I now feel comfortable doing a Nandroid Backup (TWRP).
I used to do it all the time on my OPO Kitkat, but now with Android Marshmallow, it's quite different.
Here is my situation:
A2017U (us version)
TWRP 3.0.2.2 Installed
Bootloaded Unlocked
Rooted
Xposed Framework v87 installed
Update B29 installed
Inside TWRP>Backup I have many options:
1- Boot (64MB)
2- Cache (2MB)
3- Data(6969MB)
4- Recovery (64MB)
5- System (3723MB)
6- System Image (6144MB)
7- EFS (4MB)
By default, the "Boot", "Data" and "System" are selected, but after some reading I could also backup "System Image" for a near-perfect restore.
Also, some said to backup the EFS in-case it gets corrupted/damage, but some say it can brick your device.
Could anyone tell me what should I backup in case I get stuck somewhere in the future.
Thank you !!
P.S: I have removed any fingerprints and set the lock screen to "Swipe" (no pattern).
Click to expand...
Click to collapse
lafester said:
First, make sure to flash the official twrp. Do not keep the one we use to unlock bootloader.
There is no harm in backing up efs, in fact it is a good idea to do so. Just do not select it during a restore unless something has wiped your current efs and its the only way to fix.
I don't see a need to back up a full system image but couldn't hurt to at least have one for safe keeping.
Click to expand...
Click to collapse
How do I know which TWRP I installed ?
Do you have a link for the official TWRP for the Axon 7 ?
Its in the dev forum titled official twrp.
lafester said:
Its in the dev forum titled official twrp.
Click to expand...
Click to collapse
This? :
https://twrp.me/devices/zteaxon7.html
https://dl.twrp.me/ailsa_ii/
Edit: Looks like there's twrp-3.0.3-0-ailsa_ii Out for the Axon 7
But the official XDA Forum Page it's twrp-3.0.2-0-a2017u
After flashing the 3.0.2-0-a2017u, I now have in the backup sections: Modem (NON-HLOS) (95MB), I don't know if I should back it up.