Related
Is it possible to pull an app out of a Nandroid Backup and copy it into the current rom? Just one of those random thoughts!
teenum said:
Is it possible to pull an app out of a Nandroid Backup and copy it into the current rom? Just one of those random thoughts!
Click to expand...
Click to collapse
yeah if you know how to open the system.img
teenum said:
Is it possible to pull an app out of a Nandroid Backup and copy it into the current rom? Just one of those random thoughts!
Click to expand...
Click to collapse
As long as they're not protected, you could just make backups of all your apps(using ES, Astro, etc.) and then theyd be on your sd card. Then you could just re-install them on any ROM you want. It'd be a lot easier.
how do you open the system img? I am windows user not familiar with linux or android codes.
teenum said:
how do you open the system img? I am windows user not familiar with linux or android codes.
Click to expand...
Click to collapse
it's not android code; it's linux. you have to unyaffs it using a linux box.
gomorrah said:
As long as they're not protected, you could just make backups of all your apps(using ES, Astro, etc.) and then theyd be on your sd card. Then you could just re-install them on any ROM you want. It'd be a lot easier.
Click to expand...
Click to collapse
it sounds more like he was asking cause there might be an older app version on a nandroid backup as opposed to just backing the current apps. also you can backup protected apps if you really wanted to.
theresthatguy said:
it sounds more like he was asking cause there might be an older app version on a nandroid backup as opposed to just backing the current apps. also you can backup protected apps if you really wanted to.
Click to expand...
Click to collapse
Sorry, I wasn't too clear on what I meant. Since he has the nandroid, he could just restore the old backup, and make a copy of the app. Then restore to his current set up and then use the File Manager. If it was an older version of an app that he's currently using, then he'd have to clear the newer one out first of course. Not everybody has a Linux box.
gomorrah said:
Sorry, I wasn't too clear on what I meant. Since he has the nandroid, he could just restore the old backup, and make a copy of the app. Then restore to his current set up and then use the File Manager. If it was an older version of an app that he's currently using, then he'd have to clear the newer one out first of course. Not everybody has a Linux box.
Click to expand...
Click to collapse
Two words: live distro
theresthatguy said:
Two words: live distro
Click to expand...
Click to collapse
you mean like a "live CD"?
There's an unyaffs for Windows, too. (Download from my Dropbox: http://dl.dropbox.com/u/1161808/unyaffs.exe)
Just make a temp/working directory, copy the system.img file from your nand backup into it, copy or move unyaffs.exe into that same directory, drag the img file onto unyaffs.exe in Explorer. Wait a few moments for the window to refresh and unyaffs to finish.
Ta-dah.
Can some one provide some instructions on how to go about making a CW zip file to flash and install all the apps that is on my phone?
I've seen a few of these floating around in the forum, and wanted to make my own to save time after every ROM flash
Do I just grab all the APK files throw them into a folder and Zip & Sign it?
or do I have to do a Nandroid backup first, then only use the app files from the backup?
I would like to know this too....
Would be nice as well instead of restoring
Sent from my Nexus S using XDA App
Take an existing update.zip type file. Add a folder to it with the full proper path for your apps you want to pre-install (typically this will be /data/app) and put all the apps in that folder. Should look something like this in a windows/mac explorer window:
Code:
META-INF
/com/google/android/updater-script
data
/app/myfirstapp.apk
/app/mysecondapp.apk
Then use a text editor to edit the META-INF/com/google/android/updater-script file to include the commands to copy over your stuff. It would something along the lines of:
Code:
ui_print("Installing New App Files to /data");
package_extract_dir("data", "/data");
Edit out anything in the update template you're working out of that you don't want to happen (ie., format or symlinks, etc).
Repackage the zip file and make sure nothing else got in there by mistake by re-opening it (like those pesky Mac .ds-store files).
You can re-sign it with the android tools, but I don't believe you need to with Clockwork.
I would have a fresh nandroid before testing anything, of course.
You feel this approach is better than just using Titanium to restore apps? You won't get back any app data that isn't stored on the sdcard.
Thanks!
yes, now that makes sense, i recall reading that some where else to add extra APK to the ROMs
so it's the same idea, just without the ROM portion
now i get it
distortedloop said:
Take an existing update.zip type file. Add a folder to it with the full proper path for your apps you want to pre-install (typically this will be /data/app) and put all the apps in that folder. Should look something like this in a windows/mac explorer window:
Code:
META-INF
/com/google/android/updater-script
data
/app/myfirstapp.apk
/app/mysecondapp.apk
Then use a text editor to edit the META-INF/com/google/android/updater-script file to include the commands to copy over your stuff. It would something along the lines of:
Code:
ui_print("Installing New App Files to /data");
package_extract_dir("data", "/data");
Edit out anything in the update template you're working out of that you don't want to happen (ie., format or symlinks, etc).
Repackage the zip file and make sure nothing else got in there by mistake by re-opening it (like those pesky Mac .ds-store files).
You can re-sign it with the android tools, but I don't believe you need to with Clockwork.
I would have a fresh nandroid before testing anything, of course.
You feel this approach is better than just using Titanium to restore apps? You won't get back any app data that isn't stored on the sdcard.
Click to expand...
Click to collapse
Ya essentially this method is doingan advanced nandroid restore for data only except without the settings.
Sent from my MattedBlues CM7 Nexus S from the XDA Premium app.
kenvan19 said:
Ya essentially this method is doingan advanced nandroid restore for data only except without the settings.
Sent from my MattedBlues CM7 Nexus S from the XDA Premium app.
Click to expand...
Click to collapse
I suppose if you want the app data restored as well, you would just need to identify it's location in the /data directory and add it to the /data folder in the update you're making. Seems like most of the app data goes into /data/data.
Just thinking out loud here...
So for a sample app on my phone I have called jefit pro I'd put the following in the update file.
Code:
/data/je.fit.pro-1.apk <---apk itself
/data/data/je.fit.pro <--the folder
/data/data/je.fit.pro/databases/data
/data/data/je.fit.pro/lib
/data/data/je.fit.pro/preferences/preferences.xml
I'd just pull the whole folder for the /data/data/je.fit.pro from the phone via adb.
I'm not sure how useful putting the data back is, since that's not a static set of files on many apps, but for some apps where the data is just some settings or preference files it may be a nice touch.
I don't really see any advantage to this over just use Titanium to restore apps and data, but it should work.
(<<---- this would be the whole folder and its subfolders that I pulled via adb off the phone)
distortedloop said:
I don't really see any advantage to this over just use Titanium to restore apps and data, but it should work.
Click to expand...
Click to collapse
AllGamer, I'm glad you brought this up, while I don't personally have any apps I want to put on the phone in this method, except perhaps titanium itself, I just realized we could of course do the same thing for all those little custom tweaks we put on our phones, like for me I push my personalized ringtones/notification sounds to /system. That's easy enough with adb or rootexplorer, but why not just flash them from a zip while in CW after a wipe or install of a new rom?
distortedloop said:
AllGamer, I'm glad you brought this up, while I don't personally have any apps I want to put on the phone in this method, except perhaps titanium itself, I just realized we could of course do the same thing for all those little custom tweaks we put on our phones, like for me I push my personalized ringtones/notification sounds to /system. That's easy enough with adb or rootexplorer, but why not just flash them from a zip while in CW after a wipe or install of a new rom?
Click to expand...
Click to collapse
the idea came up from several places, first Titanium Backup itself offers to create a signed .zip installer for CW
and i've seen other devices forums with people packing up like 100+ apps/tweaks/mods into it to flash after CW is done flashing the new ROM
yes, of course we can use TI, i have TI pro and it's very easy, but Ti is slow.... at restoring 300+ Apps
but everytime i see CW restoring a Zip file or even a full Nandroid backup, it does it so fast and quickly, that i though... hell might as well keep an updated signed .zip wtih all my must have apps, and flash it along right after any new ROM flash (when testing out different Custom ROMs) then i don't need to spend like an hour everytime restoring + configuring the phones
i noticed that Ti works a hell of a lot faster if the apps are already installed, and you only need to restore the data.
and that is the main reason i want to compile a list of all the apps
once they are all installed, then i can use any of the good market utilities that can do mass Apps2SD and i'll be up and running in as quickly as 15min vs. a whole hour waste on a restore/config everytime you change the ROM
using Ti i found most of the System settings can be restored safely without corrupting the new ROM
email
accounts & syncs
bluetooth pairings
wifi
... ah shoot forgot the rest
only do not restore settings for:
launcher,
wireless network (phone company)
android market
and anything that has to do with default settings
probably this weekend i'll dissect the CW zip created by Ti itself, and add more to it
Sounds like a good plan...but you've got 300+ apps if I recall correctly. I imagine that will take a long time to restore either method!
The Titanium update zip is a good place to start. Use the setting to make it a "user" app and it will put it in /data, where you want the rest of your apps as well. You could just dump what you want right into the zip file there in the folder that has titanium's apk itself and not even worry about messing with the updater-script file.
I extracted all my files from my data.img backup and made it into a .zip. Is there anyway
i can cwm flash that data.zip to get all my data back? I tried just flashing the zip and it says,
"(bad) Installation Aborted."
Any help would be greatly appreciated
mafo5000 said:
I extracted all my files from my data.img backup and made it into a .zip. Is there anyway
i can cwm flash that data.zip to get all my data back? I tried just flashing the zip and it says,
"(bad) Installation Aborted."
Any help would be greatly appreciated
Click to expand...
Click to collapse
Here's a few things you could do assuming that what you want is even in this zip file.
1) Get a working cwm format zip file and take a close look at it because you need to use it as a template if this is going to work. In particular, check out updater-script in META-INF\com\google\android\*. Updater-script is what directs the restore operation so it needs to match what you want to do. You can get the idea by looking at one that restores say, some data or system files, like a kernel will always restore some /system/lib/module files.
2) Since you've got some sort of zip file, make sure it matches the general format of a working cwm zip file and then just make sure step 1) is right.
3) I don't know if this is still a search for .android_secure folder on /sdcard, but if it is you're probably not going to get there from here, because the tf101 generallyl doesn't have that file since there's no need for tf101 -> sdcard app storage. For example, mine never had that folder either on internal or external storage.
4) Kernels aren't in the data or system archives from cwm, so that is possibly some sort of show-stopper too. I'm working on the cwm source today a bit to try to create a boot.img (or in the newer cwm lingo, boot.*.tar) archive. That archive will use blob and boot tools to be able (via the direction in updater-script) burn the blob onto block m*4.
I hope that helps.
Oh yeah, another thing you can try: If you wanted just the 'apps' from the cwm archive, you shouldn't even need the zip file. All you need to do is run Titanium Backup (assuming you've got it or can get it), and use the new feature in options called restore from cwm backup (or something like that). I've used it and it works fine on 3.x and 5.x cwm backups.
-- good luck
hachamacha said:
Here's a few things you could do assuming that what yowant is even in this zip file.
1) Get a working cwm format zip file and take a close look at it because you need to use it as a template if this is going to work. In particular, check out updater-script in META-INF\com\google\android\*. Updater-script is what directs the restore operation so it needs to match what you want to do. You can get the idea by looking at one that restores say, some data or system files, like a kernel will always restore some /system/lib/module files.
2) Since you've got some sort of zip file, make sure it matches the general format of a working cwm zip file and then just make sure step 1) is right.
3) I don't know if this is still a search for .android_secure folder on /sdcard, but if it is you're probably not going to get there from here, because the tf101 generallyl doesn't have that file since there's no need for tf101 -> sdcard app storage. For example, mine never had that folder either on internal or external storage.
4) Kernels aren't in the data or system archives from cwm, so that is possibly some sort of show-stopper too. I'm working on the cwm source today a bit to try to create a boot.img (or in the newer cwm lingo, boot.*.tar) archive. That archive will use blob and boot tools to be able (via the direction in updater-script) burn the blob onto block m*4.
I hope that helps.
Oh yeah, another thing you can try: If you wanted just the 'apps' from the cwm archive, you shouldn't even need the zip file. All you need to do is run Titanium Backup (assuming you've got it or can get it), and use the new feature in options called restore from cwm backup (or something like that). I've used it and it works fine on 3.x and 5.x cwm backups.
-- good luck
Click to expand...
Click to collapse
OK Ill see if the titanium backup way works. I'll report back to you if it works. Also if I do get all my apps back is there a way to get the app data?
Hi - If Titanium is bringing up the selections screen then the usual choices for each app are data/app/data+app, so yes.
The titanium back option is called "extract from Android backup" I can't do
It right now because I don't have my tf with me. But I don't think it will work because
The Android backup I made was currupted. I would get the .android_secure error
And couldn't restore. So if titanium takes the data.img from my Android I'm thinking
It won't work but if I can give it the zip it probably will. I won't be home for a couple
Hours.
thank you so much i got all my stuff back using titanium backup!
mafo5000 said:
thank you so much i got all my stuff back using titanium backup!
Click to expand...
Click to collapse
Cool! --
Congrats.
So, I just flashed CleanROM 4.5. Everything went smoothly, except I've lost all my sms/mms messages from both Go SMS and the default Messaging app.
I have a TWRP backup here on the computer, as well as a TiBu backup of all user apps.
I can't seem to find the SMS database in the TiBu backup at all, and I can't figure out how to browse the TWRP backup to find it.
Nandroid Explorer doesn't read TWRP backups either...
Anyone have a solution?
silentecho13 said:
So, I just flashed CleanROM 4.5. Everything went smoothly, except I've lost all my sms/mms messages from both Go SMS and the default Messaging app.
I have a TWRP backup here on the computer, as well as a TiBu backup of all user apps.
I can't seem to find the SMS database in the TiBu backup at all, and I can't figure out how to browse the TWRP backup to find it.
Nandroid Explorer doesn't read TWRP backups either...
Anyone have a solution?
Click to expand...
Click to collapse
Not sure if it's available in the Free Version but Titanium Backup allows you to extract from a Nandroid backup.
I just checked and it gave me a listing of all the apps I have installed and there was one listed as Messages, I can only assume that it's my texts.
Yes I do have the paid version. I tried restoring both Go SMS and the Messages app from TiBu using my TWRP backup, but they basically just reinstall the app. I still have no messages in either app :/
I didn't realise TiBu was Titanium - how retarded of me... haha
Any chance of backing this one up restoring the other nandroid and then backing up the txt's from within the stock messaging app then restoring?
Unless someone else knows how open .win files
I did think of that, but I don't want to run the risk of a corrupted restore. I've had it happen s bunch of times, unfortunately.
Sent from my HTC One X using xda premium
silentecho13 said:
So, I just flashed CleanROM 4.5. Everything went smoothly, except I've lost all my sms/mms messages from both Go SMS and the default Messaging app.
I have a TWRP backup here on the computer, as well as a TiBu backup of all user apps.
I can't seem to find the SMS database in the TiBu backup at all, and I can't figure out how to browse the TWRP backup to find it.
Nandroid Explorer doesn't read TWRP backups either...
Anyone have a solution?
Click to expand...
Click to collapse
Yep, it's fully possible. Just get the nandroid backup file, and make a copy and change the extension to .zip After that just unzip, and volia. A bit of searching (should be in the apps file, I forgot the details).
Sent from my HTC One XL using xda premium
TheNightHawk223 said:
Yep, it's fully possible. Just get the nandroid backup file, and make a copy and change the extension to .zip After that just unzip, and volia. A bit of searching (should be in the apps file, I forgot the details).
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
....so I saw this too late.
I went and restored my backup, grabbed the files, and restored the new backup hoping that neither were corrupted.
It all went smoothly, but I'll definitely remember this for the next time I mess up...haha.
Thanks!
silentecho13 said:
....so I saw this too late.
I went and restored my backup, grabbed the files, and restored the new backup hoping that neither were corrupted.
It all went smoothly, but I'll definitely remember this for the next time I mess up...haha.
Thanks!
Click to expand...
Click to collapse
Glad I could help, almost everything that uses the term "compressed" seems to be able to be turned into a .zip
Sent from my HTC One XL using xda premium
Sorry I'm not following this. I made a twrp backup using 2.5.0.0 and I got a bunch of .WIM files.
7-Zip recognizes those and opens them to have a .ext4 file. However every ext browser and mounter (in windows) I've tried can't seem to browse them. I tried renaming them zip, but I'm guessing I'm doing something wrong.
With old CWM releases, my backups were tars which were easily browsable.
Am I missing something?
Thanks!
eldamobo said:
Sorry I'm not following this. I made a twrp backup using 2.5.0.0 and I got a bunch of .WIM files.
7-Zip recognizes those and opens them to have a .ext4 file. However every ext browser and mounter (in windows) I've tried can't seem to browse them. I tried renaming them zip, but I'm guessing I'm doing something wrong.
With old CWM releases, my backups were tars which were easily browsable.
Am I missing something?
Thanks!
Click to expand...
Click to collapse
I know this is an old post, but it's the first Google result.
What you want to do is rename the .wim file to .tar.gz, then extract the file (command line is tar -xvzf filename.tar.gz). If you look at the TWRP logs it indicates that it uses tar to create the archive file.
uberamd said:
I know this is an old post, but it's the first Google result.
What you want to do is rename the .wim file to .tar.gz, then extract the file (command line is tar -xvzf filename.tar.gz). If you look at the TWRP logs it indicates that it uses tar to create the archive file.
Click to expand...
Click to collapse
Thanks uberamd. I'll give this a shot. I guess I should have checked the logs. Tar would be great!
hi there.. i made backup too.. now i want to bring back the boot.img and recovery.img..
most of guys said to me the " boot.emmc.win " is the stock boot.img.. but this one is 16 MB and other boot.img i saw till now are 6 MB..
and how can i restore the stock recovery? does the backup contain the recovery?
any idea?
N5 TWRP Backups
I made a backup with TWRP, and copied the .WIN files to my PC. Tried renaming those to .ZIP or .tar.gz, but 7zip could not open either of those!?
Are you guys sure the backups are actual zip or tar/gz files?
EDIT: Nevermind, I renamed to .tar and it opened. I suppose compression is not enabled by default
Except the data.ext4 is splitted in two files: data.ext4.win000 and data.ext4.win001 and renaming either of those to .tar, .zip or .tar.gz doesn't help
Just a guess here but what if you concatenated the files together?
If you can post the details from the twrp log that would also probably help.
eldamobo said:
Just a guess here but what if you concatenated the files together?
If you can post the details from the twrp log that would also probably help.
Click to expand...
Click to collapse
Yes concatenating can help however all those .WIN files are either .tar files or .tar.gz (if compression is enabled). That's quite simple in the end, except that 7zip doesn't always recognize the format properly. If I open the system.win file, it only shows about 60MB of files, whereas the whole .win file is 600MB uncompressed, hence I was confused about the format.
I've been able to update my app to read those .tar, .tar.gz and extract any file from it now Pretty cool!
Be advised though, for some reason when I rename the backup to .tar or .tar.gz for twrp 2.6.3.1, it doesn't want to open or extract. I don't know if it's only happening only for t-mobile sgs3 or the developer removed the ability for us to do it. But I did revert it back 2.6.3.0 and it's working fine for me. Thought I want to just throw it out there.
-VIPLightning
VIPLightning said:
Be advised though, for some reason when I rename the backup to .tar or .tar.gz for twrp 2.6.3.1, it doesn't want to open or extract. I don't know if it's only happening only for t-mobile sgs3 or the developer removed the ability for us to do it. But I did revert it back 2.6.3.0 and it's working fine for me. Thought I want to just throw it out there.
-VIPLightning
Click to expand...
Click to collapse
That's interesting. Which app are you using to open those TWRP backups? Asking because I found out that many extractor are unable to open those in the first place! 7zip for example showed me a 80MB content while the file was 600MB! And I'm using a very old 2.6.0.0 TWRP, so I got to try this last version out
Would you mind trying Android Tuner Free, last update allows opening those .tar and .tar.gz files, but got to rename the TWRP backup to either of those first. It won't open the tar inside the gz file, but you should be able to extract it and then open it If you don't have the time, I can understand, but hopefully you still have a 2.6.3.1 backup file around?
3c said:
That's interesting. Which app are you using to open those TWRP backups? Asking because I found out that many extractor are unable to open those in the first place! 7zip for example showed me a 80MB content while the file was 600MB! And I'm using a very old 2.6.0.0 TWRP, so I got to try this last version out
Would you mind trying Android Tuner Free, last update allows opening those .tar and .tar.gz files, but got to rename the TWRP backup to either of those first. It won't open the tar inside the gz file, but you should be able to extract it and then open it If you don't have the time, I can understand, but hopefully you still have a 2.6.3.1 backup file around?
Click to expand...
Click to collapse
I should have no problem giving it a try. Yeah I deleted my backup. I'll go ahead and update the recovery when I get a chance to later on. Then I'll make another backup And the program I used for extracting and opening was WinRAR. Everytime I tried to, the 2.6.3.1 backup would always come up as corrupted or damaged.
EDIT: So I tried out your app. Indeed the explorer does work. Thanks so much. Even though first it took some time, I was able to get to my stuff. But it was worth it. I've never seen an app that can actually do so much. Thanks again.
-VIPLightning
What are WIN files?
Along with win and md5 files TWRP creates recovery.log file. If you look inside this file, you can see the full log of what TWRP has done. There you can notice that win file with the boot partition is in fact a result of the dd command, so that's a bit-to-bit copy of the boot partition, sometimes named as .img file.
Other partition win files are tar files. If you used compression, you got .tar.gz files.
So .win files are raw partition data, .tar, or .tar.gz files. See recovery.log
If you use compression in TWRP, just rename the .win to .tar.gz
i.e data.ext4.win to data.ext4.tar.gz , then use tar -xvzf , extracts perfectly fine.
I used this to extract my apps from a TWRP backup just now.
So I think I made a stupid mistake.
I was trying to reset google wallet and It hung at 97% and wasn't able to reset. I used the google wallet installer to basically change my build prop to the nexus build prop. I figured it would just overwrite my original wallet app anyway, and once my build prop was changed to the nexus build prop I could simply reset the app from there.
Anyways, phone rebooted and it's stuck in a bootloop and isn't getting passed the boot animation screen. I can get into recovery mode and download mode just fine. I tried restoring a backup I had with CWM and it says "md5 mismatch error". I really have no idea what to do at this point, and would rather not go completely to stock since I know my data is still there. Also I'm concerned to even restore a backup because i'm pretty sure my build prop was changed. I'm also wondering if it would be possible to simply factory reset and flash a new rom on top of it.
Any help would be greatly appreciated.
which rom are you using?
extract its build.prop and flash manually (if you know how to create a flashable zip)
if you are using a cm based rom, just reflash the rom without deleting anything..
and avoid using space while renaming backups... it gives md5 mismatch error
Khizar Amin said:
which rom are you using?
extract its build.prop and flash manually (if you know how to create a flashable zip)
if you are using a cm based rom, just reflash the rom without deleting anything..
and avoid using space while renaming backups... it gives md5 mismatch error
Click to expand...
Click to collapse
No idea how to create the flashable zip. However I did notice a tutorial, I guess now would be a good time to learn.
I'm using darthstalker X1, it's a touchwiz based rom so I can't simply flash the rom again.
I saved all of my backups on my external SD card, can I just simply hook it up to my computer and change the backup names? And is my build.prop included in the backup I made?
Thank you for responding.
BadUsername said:
No idea how to create the flashable zip. However I did notice a tutorial, I guess now would be a good time to learn.
I'm using darthstalker X1, it's a touchwiz based rom so I can't simply flash the rom again.
I saved all of my backups on my external SD card, can I just simply hook it up to my computer and change the backup names? And is my build.prop included in the backup I made?
Thank you for responding.
Click to expand...
Click to collapse
renaming the backups again might not fix
i believe to have seen a script for sgy which fixes md5 mismatch error. but you need to give commands from terminal emulator.
if you have more than one backup of the rom, try to restore system only
if any one of them works your phone will boot up again
Edit: your backups contain the build.prop file in system.(partition type).tar
just extract this
and partition type may be rfs or ext4
Khizar Amin said:
renaming the backups again might not fix
i believe to have seen a script for sgy which fixes md5 mismatch error. but you need to give commands from terminal emulator.
if you have more than one backup of the rom, try to restore system only
if any one of them works your phone will boot up again
Edit: your backups contain the build.prop file in system.(partition type).tar
just extract this
and partition type may be rfs or ext4
Click to expand...
Click to collapse
No idea how that is even done. I think I need windows and ADB in order to extract the build.prop, I have a mac.
I found a restore that worked, I just forgot to rename it and it wasn't too old thankfully.
I really appreciate you helping. And now I know of this mismatch error so I can name my backups correctly.
BadUsername said:
No idea how that is even done. I think I need windows and ADB in order to extract the build.prop, I have a mac.
I found a restore that worked, I just forgot to rename it and it wasn't too old thankfully.
I really appreciate you helping. And now I know of this mismatch error so I can name my backups correctly.
Click to expand...
Click to collapse
to extract backups u need a tar extractor
if the backup format is something like .tar.a or .tar.md5 rename it to .tar first
and restoring the system only of your working backup would have booted your phone (in advance restore in recovery)
anyway this was an experience too for you.. so you would be carefull next time
Khizar Amin said:
to extract backups u need a tar extractor
if the backup format is something like .tar.a or .tar.md5 rename it to .tar first
and restoring the system only of your working backup would have booted your phone (in advance restore in recovery)
anyway this was an experience too for you.. so you would be carefull next time
Click to expand...
Click to collapse
Restoring my system partition only from advanced restore worked perfectly. All my apps stayed how they were and I didn't have to update all of my apps after I restored. Way better than doing a full restore in this case.
Thank you for this advice, this will be a very helpful method to me if I make any mistakes while messing with anything in my system folder. And yes, it was certainly an experience for me.
Sent from my SCH-I535 using Tapatalk 2