I have been using TWRP for a while and have been saving backups regularly on the external SD-card. I have restored many times after testing some custom ROM.
Today I tried to restore my most recent backup and after it was done, it throws me back into the boot screen.
I can see a long list of previous backups but when I select them I observe the following, which I had not paid attention to before:
1) the most recent backup involves the partitions System and Data
2) the three next backups show no partitions and TWRP refuses to restore them (and I could swear I had restored from them in the past)
3) a very old backup shows System, Data and Boot
4) an older custom ROM backup also shows System, Data and Boot
Can someone please tell me what you think the problem is here? I cannot go back to my most recent backup.
Make sure you've not somehow ended up with 2 twrp folders with different id's as twrp will only recognize the current Id.
If that's the case copy the backups into that folder.
There is only one TWRP folder. It seems some backups contain "Boot" "Data" and "System" and some backups contain only "System" and "Data" and are missing "Boot".
As I only followed the "defaults" when I did the backups, I need to understand why in some cases it did not save "Boot".
Would you know why?
Zilliman said:
There is only one TWRP folder. It seems some backups contain "Boot" "Data" and "System" and some backups contain only "System" and "Data" and are missing "Boot".
As I only followed the "defaults" when I did the backups, I need to understand why in some cases it did not save "Boot".
Would you know why?
Click to expand...
Click to collapse
I've no idea, never come across it, unless you accidentally unchecked those partitions?
In any case none are full backups.
You should make a backup of EFS and modem too.
ashyx said:
I've no idea, never come across it, unless you accidentally unchecked those partitions?
In any case none are full backups.
You should make a backup of EFS and modem too.
Click to expand...
Click to collapse
I have managed to restore an older backup which had Boot, Data and System partitions. I then restored the latest backup which only had Data and System. It now seems to work. I started it up and it all appears to be in place.
I then booted into TWRP and selected to do a backup and it had automatically selected the Data, System and Boot partitions. Why did it leave Boot out of the previous backups I do not understand but will keep an eye on it from now on.
Regarding the EFS partition: Originally I installed the stock ROM using ODIN. Does this mean that all the partitions were created during that initial installation? Or was the EFS partition present beforehand?
EFS partition is not part of the firmware, so is extremely important to back up, probably the most important of all to backup as it contains a lot of information that could render your device useless if it gets corrupted.
OK, thanks, will do it now.
ashyx said:
EFS partition is not part of the firmware, so is extremely important to back up, probably the most important of all to backup as it contains a lot of information that could render your device useless if it gets corrupted.
Click to expand...
Click to collapse
Can we make EFS checked by default? I had no idea that it's that important..
alexeyp said:
Can we make EFS checked by default? I had no idea that it's that important..
Click to expand...
Click to collapse
"Important" - is there anything other than the IMEI to worry about? On my other, dual-SIM Chinese phones, I used to change the IMEI as I liked.
Yes. And it's ONLY 20MB, compared to the other partitions which are many GB in length.
And Restore should be made to have the partition unchecked by default.
Zilliman said:
"Important" - is there anything other than the IMEI to worry about? On my other, dual-SIM Chinese phones, I used to change the IMEI as I liked.
Yes. And it's ONLY 20MB, compared to the other partitions which are many GB in length.
And Restore should be made to have the partition unchecked by default.
Click to expand...
Click to collapse
Check it and it should stay checked.
And yes it contains a lot of important stuff related to imei, wifi, network, Bluetooth.
Lose it and you could be in trouble.
Search Google for more info.
Related
So here's the thing: I made a TWRP backup of my 16GB nexus before I returned it yesterday (multitouch issues, dead pixels) but see now that people are reporting an OTA update that fixes the multitouch issue. I would rather not restore that backup since it is the JSS15J system, so is there a way I can get the data of at least a few apps and restore them individually somehow?
Thanks!
Titanium Backup can do that.
danvee said:
Titanium Backup can do that.
Click to expand...
Click to collapse
Ok, can it read the data in the TWRP folder? I have used TB a lot in the past but didn't think it might be able to use the TWRP data.
If it's not compressed (I never do), TiBu can do it perfectly.
In Titanium backup pro in it's menu is the option to 'extract from nandroid backup' .
Did it just last week, so I know the current version works.
danvee said:
If it's not compressed (I never do), TiBu can do it perfectly.
In Titanium backup pro in it's menu is the option to 'extract from nandroid backup' .
Did it just last week, so I know the current version works.
Click to expand...
Click to collapse
Ah, need the pro version. Hmm, thanks. I'll check it out.
Coronado is dead said:
Ah, need the pro version. Hmm, thanks. I'll check it out.
Click to expand...
Click to collapse
Use Nandroid Backup Manager. It's free.
It can restore apps and/or data, SMS messages, Call logs and more from your nandroid backup. It can also decompress the backup if it's compressed.
Advance Restore and just click restore data only on twrp
danvee said:
If it's not compressed (I never do), TiBu can do it perfectly.
In Titanium backup pro in it's menu is the option to 'extract from nandroid backup' .
Did it just last week, so I know the current version works.
Click to expand...
Click to collapse
thank you man thank you. i just had this http://forum.xda-developers.com/showpost.php?p=49548141&postcount=136 problem and your post is gonna help me i hope thanks. btw im on 4ext recovery
MrPhilo said:
Advance Restore and just click restore data only on twrp
Click to expand...
Click to collapse
Good day: Are you indicating that TWRP has an advanced restore feature?
Advance Restore and just click restore data only on twrp ????
I don't see any advanced menu in TWRP (Looks like all or nothing)?
Or, did you mean that Nandroid Manager has an advanced menu?
Regards
galearned said:
Are you indicating that TWRP has an advanced restore feature?
Advance Restore and just click restore data only on twrp ????
I don't see any advanced menu in TWRP (Looks like all or nothing)?
Click to expand...
Click to collapse
TWRP backups each partition separately, thus it can also restore any single partition so also /data
tetakpatalked from Nexus 7
tetakpatak said:
TWRP backups each partition separately, thus it can also restore any single partition so also /data
tetakpatalked from Nexus 7
Click to expand...
Click to collapse
"so is there a way I can get the data of at least a few apps and restore them individually somehow?"
Pfeffernuss said:
"so is there a way I can get the data of at least a few apps and restore them individually somehow?"
Click to expand...
Click to collapse
Of course. TWRP has no advanced backup&restore features because it doesn't need them: you will be prompted before each backup&restore action about the partitions.
For data of just single apps use better Titanium Backup. It can extract them from your nandroid backups
tetakpatalked from N7100
MrPhilo said:
Advance Restore and just click restore data only on twrp
Click to expand...
Click to collapse
does it restore gapps too?
javigbox said:
does it restore gapps too?
Click to expand...
Click to collapse
I think some of the gapps data is flashed to system, so it won't be able to completely restore it but after flashing gapps, you should be able to extract google apps with data intact from TWRP backup
jassalmithu said:
I think some of the gapps data is flashed to system, so it won't be able to completely restore it but after flashing gapps, you should be able to extract google apps with data intact from TWRP backup
Click to expand...
Click to collapse
Exactly what I do.
marsmallow 6 will update apps + data from your google account. Not sure it's fully implemented yet but it's supposed to work. I've tried it yesterday with a Mm6.0.1 on nexus 7 2013 and many apps were already configured. Not all of them. Going from MM6 to MM6.0.1 might complicate it so maybe it's better to restore with google and do a little work by yourself, to make sure. I gave up on those restore apps. It also give you the opportunity to do a clean up
Coronado is dead said:
So here's the thing: I made a TWRP backup of my 16GB nexus before I returned it yesterday (multitouch issues, dead pixels) but see now that people are reporting an OTA update that fixes the multitouch issue. I would rather not restore that backup since it is the JSS15J system, so is there a way I can get the data of at least a few apps and restore them individually somehow?
Thanks!
Click to expand...
Click to collapse
I'm sure somebody is already aware of this;just sharing coz this awed me![emoji33]
You need to ..extract/restore individual data files from nandroid backup?
Restore data to an app when switching between ROMs or OS versions?
Well TWRP IS THE ONLY THING YOU NEED! And a PC of course.
Bless the Devs[emoji7][emoji28]
Forget Nan managers, tar.extractors & the insanely complex Bash terminal commands
1. Go to File manager on TWRP recovery, it can read the system data i.e. data/data/ file (while your other file managers can,only data files on SD or ext.SD)
2.Go to data/data and locate the data folder of the app you wish to extract; will be in the format 'com.app name'
3.Push 'Select folder' tab on the screen; it gives you option to COPY the file
4.Move up & paste the data/data file on your readable memmory: sd/ext.SD
And that's it!! Just connect to the PC & pull the file & there u have: your APP DATA FILE!
I was tired using zip extractors, changing file names & struggling with command prompts; then found this[emoji4]
Hope it helps[emoji106]
Sent from my GT-N5110 using Tapatalk
---------- Post added at 08:57 AM ---------- Previous post was at 08:24 AM ----------
DIGVIJAY24 said:
I'm sure somebody is already aware of this;just sharing coz this awed me![emoji33]
You need to ..extract/restore individual data files from nandroid backup?
Restore data to an app when switching between ROMs or OS versions?
Well TWRP IS THE ONLY THING YOU NEED! And a PC of course.
Bless the Devs[emoji7][emoji28]
Forget Nan managers, tar.extractors & the insanely complex Bash terminal commands
1. Go to File manager on TWRP recovery, it can read the system data i.e. data/data/ file (while your other file managers can,only data files on SD or ext.SD)
2.Go to data/data and locate the data folder of the app you wish to extract; will be in the format 'com.app name'
3.Push 'Select folder' tab on the screen; it gives you option to COPY the file
4.Move up & paste the data/data file on your readable memmory: sd/ext.SD
And that's it!! Just connect to the PC & pull the file & there u have: your APP DATA FILE!
I was tired using zip extractors, changing file names & struggling with command prompts; then found this[emoji4]
Hope it helps[emoji106]
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
And believe me, I could repack the data into my new ROM just like that!
Not sure if this messes up with your system but I'm going great so far.
So you Upgraded to a higher OS and find some of your apps to be crashing on your new ROM & have a nandroid of your stock:
You are going to switch data files between stock & custom ROM!
1.Flash the Stock ROM & copy app data from the system files to readable memory, as mentioned above, just add a letter & Rename the copy(which again you can do with TWRP!) so that TWRP may not confuse with the new folder
2.Flash the new ROM, uninstall the app that crashes & install the compatible version from the store
3.Allow storage permission from settings; open the app & perform some action so that a storage directory is created,if not already, in the system storage
4.Boot to TWRP recovery in the new ROM , so now you have the data/data folder of the new app you just installed(which is empty) as well as the data/data folder from your stock ROM on your SD/Ext.SD
5. You know were this is going[emoji16] Delete the data/data folder on your running ROM & MOVE(again with TWRP only!) the one from SD ,after restoring its original name, to the data folder from were you just deleted the other.
6.Wipe Dalvik/caches & reboot
7. Other than receiving a pop up that there may be some trouble with your android system, on startup, everything works just fine for me & the App is fully restored!![emoji7]
Didn't even use a PC!!
Such a tool TWRP is[emoji7][emoji120][emoji120][emoji120]
Forgive me, but try this at your own risk, coz as a newbie Im completely unaware of the consequences
Hope this helps somebody[emoji4]
Sent from my GT-N5110 using Tapatalk
DIGVIJAY24 said:
1. Go to File manager on TWRP recovery, it can read the system data i.e. data/data/ file (while your other file managers can,only data files on SD or ext.SD)
Click to expand...
Click to collapse
I don't understand this step. I go to file manager, then navigate to /external_sd/TWRP/BACKUPS/... and there are files like data.f2fs.win009. Now what?
Hello everyone!
Yesterday, I tried to upgrade to a Kit Kat rom. I used the Galaxy nexus toolkit, and did a full backup... plus an EFS backup. Afterwards, I did the full format/wipe from CWM recovery, and installed the ROM.
Well, apparently one of the options wipes your EFS file folder; I have no way of connecting to my network. My IMEI is the stock number, and I've spent hours scouring the internet trying to find a way to restore it. The majority of the responses are "try a factory reset and restore" or "too bad so sad, should've backed up". Well, I did try several options. The first being the EFS restore. Apparently, the backup is stored on the phone and wasn't sent to my computer, like the rest of the normal backups. That option is now out. Oh, how I miss SD storage.
The second was a full restore to stock, again, nothing. Third, I had an old nandroid backup. After doing these I saw that the EFS tree is left untouched, as it is so delicate. The only way to do this is give up and send it in for servicing, or to do a phone NV Backup swap with QPST.
I need to get access to the service menu (or any way to change the USB/Modem) as listed here: http://forum.xda-developers.com/showthread.php?t=1946915
Unfortunately, *#7284# does nothing on an i9250, nor does anything besides *#*#4636#*#*... which isn't what I need. The terminal command doesn't appear to work, either.
I don't understand very well but, have you tried to restore your EFS backup from recovery? Did you make the backup from recovery or from toolkit?
lkeops said:
I don't understand very well but, have you tried to restore your EFS backup from recovery? Did you make the backup from recovery or from toolkit?
Click to expand...
Click to collapse
I have done a recovery from the toolkit (as the files are stored on the computer and not the phone) which is where I made the backup from, as well.
However, the EFS partition is apparently never included in this backup, as it is supposed to be immune to changes and formatting. I proved them wrong.
Well I did that same blunder last month with my nexus and then I tried all remedies plus own experiments but couldn't get results. All I heard is that to send phone to service centre. If you find any other solution so do mention here, I gave up after so many tries
what9000 said:
I have done a recovery from the toolkit (as the files are stored on the computer and not the phone) which is where I made the backup from, as well.
However, the EFS partition is apparently never included in this backup, as it is supposed to be immune to changes and formatting. I proved them wrong.
Click to expand...
Click to collapse
@what9000 you may want to check out this thread http://forum.xda-developers.com/showthread.php?t=2508320
Specifically post #6 AND #9
I have personally never used the nexus backup tool, but if it does does backup the /radio folder, you may be in luck.
Well, it has been repaired. Thank you all for your help, in the end I managed to pull some things together in a mash up of fixes.
It appears that upon a new restore from a nandroid backup, I was still getting no signal. However, I did a *#06#, and my IMEI was intact. I read that the Radio folder gets backed up, but not the factory folder. Upon a new install, I imagine the radio folder is wiped, which is why every install from then on had a bunk imei (it had nothing to pull from as my factory folder is toast)
However, it looks like the efs backup I had *did* save the folder structure... I found the efs.tar backup in my galaxy nexus toolkit folder. It had the folder zip, but couldn't restore it due to permissions... didn't feel like messing with that at the moment. I copied them in with root explorer, grabbed the nv_data files from the /radio/ folder, deleted the files from /radio, and restarted. Lo and behold, they were restored from the factory folder with the correct IMEI.
I just put a fresh copy of kit kat 4.4.2 on and have cell service again. Oh happy day, I don't have to use my old HTC Sensation! :highfive:
This also marks the first time a backup actually saved my skin. Usually I vaporize the backup accidentally before it has an opportunity to prove itself useful.
So I found myself wondering how can I make life difficult for myself... I did a software upgrade in Kies on my T805 and now I have a default IMEI...
I was on cm11 before doing the upgrade to 5.0.2
Has this happened to anyone or does anyone have any idea how to fix it?
Many thanks for any reply.
That shouldnt have happened but youre not the first person to state that cm has messed with the partitions. Id stick with stock based roms in future.
Download EFS professional then under the samsung tools tab select other tools then 'Repair NV data from internal file backup'
If youre lucky it will be restored.
Now some friendly advice, ALWAYS make a full backup via recovery before messing with anything custom on your device, especially make sure the EFS partition is backed up.
ashyx said:
That shouldnt have happened but youre not the first person to state that cm has messed with the partitions. Id stick with stock based roms in future.
Download EFS professional then under the samsung tools tab select other tools then 'Repair NV data from internal file backup'
If youre lucky it will be restored.
Now some friendly advice, ALWAYS make a full backup via recovery before messing with anything custom on your device, especially make sure the EFS partition is backed up.
Click to expand...
Click to collapse
Thanks for the reply, sadly it restore a different default IMEI ending in /01 instead of /17.
I was 100% sure I had backed-up my efs, turns out I did but on my phone x(.
Any other suggestions?
Try this. Make a backup in recovery of the efs partition.
Boot into android then using a root file explorer open the efs folder then delete nv_data.bin and nv_data.bin.md5 then reboot.
See if this replaces the deleted files with the backup.
ashyx said:
Try this. Make a backup in recovery of the efs partition.
Boot into android then using a root file explorer open the efs folder then delete nv_data.bin and nv_data.bin.md5 then reboot.
See if this replaces the deleted files with the backup.
Click to expand...
Click to collapse
It does but not with the correct imei. Thanks for the reply!
What IMEI does it give?
ashyx said:
What IMEI does it give?
Click to expand...
Click to collapse
A default imei ending in / 17 instead of / 01
DieZz said:
A default imei ending in / 17 instead of / 01
Click to expand...
Click to collapse
You may as well post it as its not a valid imei, it's a generic imei.
Is it 004999010640000?
Please somebody could explain exactly what i need to backup in twrp? The system image and vendor image are needed? What they are in def? Thanks in advance...
From this forum, "the /vendor partition would only need backing up if you manually made changes to it yourself (for instance, if you use Layers). Otherwise, you can just use the vendor.img from the factory image if you need to restore /vendor."
From this forum, "According to TWRP in regards to System Image... this is a system read-only option that's intended to help you make a pure backup of your system image that you can later flash to receive over-the-air updates after having rooted or ROMed your device."
"The default backup options in TWRP are system, data, and boot. For most cases, this is sufficient for backing up a ROM. (Note that in some rare cases, boot isn’t available for backup on certain devices). If your device has the option, backing up android_secure and/or sd-ext may be a good idea. There’s usually no reason to back up cache or recovery (recovery not available for backup on some devices)." Answer found here.
enzippo said:
Please somebody could explain exactly what i need to backup in twrp? The system image and vendor image are needed? What they are in def? Thanks in advance...
Click to expand...
Click to collapse
Also make sure you backup your efs and keep atleast 2 copies eg 1 on phone and another on computer or in the cloud etc.
You only need to restore this if you loose your imei number due to corruption etc.
Hi,
Where can I find an explanation of the Nexus 5X partitions, and which of those are changed during use and are a good idea to back up?
Coming from Nexus 7 3G 2012, I see the 5X has quite a few more partitions. I've searched this site and the wider Internet for their purpose but have come up only with a parted listing without explanation.
E.g. what typically goes into "vendor", why do "system" and "vendor" have "... image" counterparts, and what exactly goes into the crucial "EFS" partition?
Following from that, it seems that an unlocked but otherwise unmodified device can be fully restored from the factory image and a data partition backup (apart from perhaps needing to restore EFS in extreme cases), right?
Or are there other partitions that may get modified during normal use and need to be backed up too?
I've come across one of the answers.
It seems the vendor partition contains the platform-specific drivers/binaries that were previously stored in the /system partition: https://plus.google.com/+JeanBaptisteQueru/posts/akHWypRNEn3.
...and according to this the "... image" selections aren't device partitions, but TWRP options to add fastboot flashable image backups of the corresponding partitions.
fvisagie said:
what exactly goes into the crucial "EFS" partition?
Click to expand...
Click to collapse
Continuing the monologue, although I haven't found a definitive source, most authorative-sounding ones like this one and this one claim it contains device-specific IDs, mostly connectivity, such as IMEI/ESN, Wi-Fi and Bluetooth MAC addresses, network unlock information etc.
fvisagie said:
Following from that, it seems that an unlocked but otherwise unmodified device can be fully restored from the factory image and a data partition backup (apart from perhaps needing to restore EFS in extreme cases), right?
Or are there other partitions that may get modified during normal use and need to be backed up too?
Click to expand...
Click to collapse
I recall from a previous experience that to be completely safe, user data/internal storage (/sdcard) needs to be backed up and restored too. Most Android apps that had been run and had created data on /sdcard before the backup will fail to run if restored without their /sdcard content.