Database Info

{TIP] Restoring TWRP backup after complete data wipe

Ok so I had a problem recently and found a solution which might help. I googled, looked in this and a bunch of other android forums and didn't find the solution I had, so maybe my way is not the best way to do it - but it solved my problem maybe it might help you.
When I flash a new rom with a different framework to the rom I'm currently on I take care to make a full TWRP back-up of my current system move that across to my PC, then proceed to wipe everything on my phone, data, system, factory reset and numerous cache and dalvik wipes. (I use the Awesome scripts superwipe and kernel cleaners which do the trick really well).
Anyway recently I installed a rom which really didn't work for me, so i wanted to get back to where I was before I installed it. I booted into TWRP cleaned the data, system factory reset wiped the caches. I mount my PC move my nandroid across to my SDcard and go to restore. But of course TWRP looks in the restore folder for the backup and I have wiped this so the file structure does not exist.
So after telling myself what an idiot I was for not remembering what the file system was, here's what I did:
1 - Stopped panicking!
2 - Ran the back-up utility in TWRP - this recreates the file structure for the back-ups and places a back-up of your empty system in the folder
3 - Move the original full back-up I placed in the empty SDcard into the file system next to the empty back-up I'd just created
4 - Go to restore and the full back-up is there. Swiped to restore it and my One S is back to it's old self
Lessons learnt: Don't panic - there is an answer. Just think about it.
Good luck!

Or you could just copy the whole twrp folder to your hdd. thats what I do anyway and restore without a problem.

Yep that would have prevented me ending up in that predicament for sure.
So would not flashing roms. The point of the post is really about what to do if you find yourself in that situation and the value of keeping a cool head and thinking through a solution rationally, using your own resources.
The way I see it is: it's my mess I got into it, how am I going to solve it....
Sent from my HTC One S using xda app-developers app

Lost my Backup
Good advice which I'm trying to follow but my TWRP Recovery cannot see the TWRP ROM Backups that I created with ROM Customizer which ROM Customizer has placed in the folder
/data/media/0/TWRP/Backups/4df1bd936aae7f4b
but when my Samsung Galaxy S3 i9300 is in Recovery Mode it is obviously looking somewhere else........I just can't figure out where because then I can just move the backup to where ?Recovery Mode is looking.
Anyone any ideas please?

matrixmainframe said:
Good advice which I'm trying to follow but my TWRP Recovery cannot see the TWRP ROM Backups that I created with ROM Customizer which ROM Customizer has placed in the folder
/data/media/0/TWRP/Backups/4df1bd936aae7f4b
but when my Samsung Galaxy S3 i9300 is in Recovery Mode it is obviously looking somewhere else........I just can't figure out where because then I can just move the backup to where ?Recovery Mode is looking.
Anyone any ideas please?
Click to expand...
Click to collapse
Do what the op says and do a backup and you will know where to put it.
Sent from my HTC One S using Tapatalk 2

Plz HELP!!!
ACtually im in deep deep trouble please i would be really grateful to the person who helps me. OK so last night i flashed cyanogen mod10 on my htc one x and when i did everything booted the boot.img and all i factory reseted from cm10 because it gave me the error that unfortunately android.process.phone has stopped nevertheless now everythings gone and no supersu root file is gone which is obvious that i dont have root now. Plz tell me how to go back to my factory settings with htc sense on it now i just want my phone back, i did another factory reset wiping off the rom but it says no OS installed and it gets stuck on htc quitly brilliant screen plz plz plz plz help me any one plz.

abdullah.imran2158 said:
ACtually im in deep deep trouble please i would be really grateful to the person who helps me. OK so last night i flashed cyanogen mod10 on my htc one x and when i did everything booted the boot.img and all i factory reseted from cm10 because it gave me the error that unfortunately android.process.phone has stopped nevertheless now everythings gone and no supersu root file is gone which is obvious that i dont have root now. Plz tell me how to go back to my factory settings with htc sense on it now i just want my phone back, i did another factory reset wiping off the rom but it says no OS installed and it gets stuck on htc quitly brilliant screen plz plz plz plz help me any one plz.
Click to expand...
Click to collapse
1. wrong forum, if you have a one x device
2. calm down
3. relock your bootloader (fastboot oem lock)
4. download and run latest ruu for your phone (search for a suitable one for your cid and carrier if you are branded)
5. you also can flash a custom sense based rom, which gives you sense back (viper one s or trickdroid or android revolution hd)
6. if you want to flash one of these,dont forget to flash the boot.img too
7. before flashing a rom, wipe system, data and cache 3xtimes to be sure you do a clean install

Thanks Man
ATSPerson said:
Ok so I had a problem recently and found a solution which might help. I googled, looked in this and a bunch of other android forums and didn't find the solution I had, so maybe my way is not the best way to do it - but it solved my problem maybe it might help you.
When I flash a new rom with a different framework to the rom I'm currently on I take care to make a full TWRP back-up of my current system move that across to my PC, then proceed to wipe everything on my phone, data, system, factory reset and numerous cache and dalvik wipes. (I use the Awesome scripts superwipe and kernel cleaners which do the trick really well).
Anyway recently I installed a rom which really didn't work for me, so i wanted to get back to where I was before I installed it. I booted into TWRP cleaned the data, system factory reset wiped the caches. I mount my PC move my nandroid across to my SDcard and go to restore. But of course TWRP looks in the restore folder for the backup and I have wiped this so the file structure does not exist.
So after telling myself what an idiot I was for not remembering what the file system was, here's what I did:
1 - Stopped panicking!
2 - Ran the back-up utility in TWRP - this recreates the file structure for the back-ups and places a back-up of your empty system in the folder
3 - Move the original full back-up I placed in the empty SDcard into the file system next to the empty back-up I'd just created
4 - Go to restore and the full back-up is there. Swiped to restore it and my One S is back to it's old self
Lessons learnt: Don't panic - there is an answer. Just think about it.
Good luck!
Click to expand...
Click to collapse
Thanks Man, been stuck in TWRP for about two hours now, thought I soft bricked my Droid Dna forever. I had a backup, and adb pushed it to the /sdcard directory, but it wouldn't show up in the restore section. This empty-backup method worked fine. Thanks, you saved me $400.:good:

Saved my HTC One!
ATSPerson said:
Ok so I had a problem recently and found a solution which might help. I googled, looked in this and a bunch of other android forums and didn't find the solution I had, so maybe my way is not the best way to do it - but it solved my problem maybe it might help you.
When I flash a new rom with a different framework to the rom I'm currently on I take care to make a full TWRP back-up of my current system move that across to my PC, then proceed to wipe everything on my phone, data, system, factory reset and numerous cache and dalvik wipes. (I use the Awesome scripts superwipe and kernel cleaners which do the trick really well).
Anyway recently I installed a rom which really didn't work for me, so i wanted to get back to where I was before I installed it. I booted into TWRP cleaned the data, system factory reset wiped the caches. I mount my PC move my nandroid across to my SDcard and go to restore. But of course TWRP looks in the restore folder for the backup and I have wiped this so the file structure does not exist.
So after telling myself what an idiot I was for not remembering what the file system was, here's what I did:
1 - Stopped panicking!
2 - Ran the back-up utility in TWRP - this recreates the file structure for the back-ups and places a back-up of your empty system in the folder
3 - Move the original full back-up I placed in the empty SDcard into the file system next to the empty back-up I'd just created
4 - Go to restore and the full back-up is there. Swiped to restore it and my One S is back to it's old self
Lessons learnt: Don't panic - there is an answer. Just think about it.
Good luck!
Click to expand...
Click to collapse
I'd just like to say a MASSIVE THANK YOU for this post! I had a major issue and thought I'd lost my 1-day old HTC One (M7). I wasn't so much panicking as I knew i'd find a way, but a cold sweat had started to break!
The biggest lesson I can take from this is simply this... MAKE SURE YOU BACKUP YOUR ORIGINAL ROM BEFORE YOU DO ANYTHING! It's such an obvious thing, but without this simple step, I'd be in trouble right now as HTC haven't an RUU for my specific device yet (plus I'm on a Mac, making running .exe files more painful still)
What had happened was that as a result of a corporate email policy, I had to encrypt my device. I did this after flashing to a new ROM. Unfortunately after I had done so, the new ROM wasn't playing nicely with Exchange (using native HTC Mail app). Of course the issue here is that when you so into TWRP, you can't see the files to restore (because TWRP is opened before the device asks you for the passcode to decrypt... another learning!). To remove the encryption, I had no choice but to do a full format of the device, so I was basically left with a brick
Anyway, once again, thank you for this post, you just saved me AU$700!

Ok so, in not so many words, ur saying " to restore a nanBU":
1. Wipe: data factory reset/cache/ delvic
Wipe system (but not sure which one(s) cause I was used to cwm and it looks diff in twrp
2. Flash the Rom that the nanbu is based from
3. Flash the nanbu
4 reboot
It's this the correct way to restore a nanbu from a diff or upgraded rom?

So I had to do a complete restore of my default Samsung Note 2 Sprint L900 firmware after an unsuccessful Rom flash of Goodness Noteworthy 1.8.1 (numerous flashes and it wouldn't boot up past opening war video, just went to black screen and hung endlessly)
-OK so I then got back to root and installed TWRP 2.6 and I had already had several backup ROMS I saved to my computer. So I placed Goodness Noteworthy 1.7 in my backup folder in TWRP on my sdcard. I then reboot into TWRP recovery and go to restore and I can't see anything there. I have the sdcard mounted and checked and after clicking the restore button I'm not seeing anything. ? When I click install it see's everything on my sdcard ? I don't get it. What am I doing wrong.
---------- Post added at 01:20 PM ---------- Previous post was at 12:42 PM ----------
cheyennemtn said:
So I had to do a complete restore of my default Samsung Note 2 Sprint L900 firmware after an unsuccessful Rom flash of Goodness Noteworthy 1.8.1 (numerous flashes and it wouldn't boot up past opening war video, just went to black screen and hung endlessly)
-OK so I then got back to root and installed TWRP 2.6 and I had already had several backup ROMS I saved to my computer. So I placed Goodness Noteworthy 1.7 in my backup folder in TWRP on my sdcard. I then reboot into TWRP recovery and go to restore and I can't see anything there. I have the sdcard mounted and checked and after clicking the restore button I'm not seeing anything. ? When I click install it see's everything on my sdcard ? I don't get it. What am I doing wrong.
Click to expand...
Click to collapse
Solved.. Copied my backup stock ROM from the TWRP folder on the phone and placed it on the SDcard, then I placed my Goodness Noteworthy 1.7 backup rom I had that I had on my computer and copied and placed that on the SDcard in the TWRP folder next to the Stock Rom backup I made. Booted back into recovery and clicked RESTORE and I was able to see both the backup rom and the Goodness Noteworthy ROM. I then wiped and did a restore and I'm back in business.

:good:

cheyennemtn said:
So I had to do a complete restore of my default Samsung Note 2 Sprint L900 firmware after an unsuccessful Rom flash of Goodness Noteworthy 1.8.1 (numerous flashes and it wouldn't boot up past opening war video, just went to black screen and hung endlessly)
-OK so I then got back to root and installed TWRP 2.6 and I had already had several backup ROMS I saved to my computer. So I placed Goodness Noteworthy 1.7 in my backup folder in TWRP on my sdcard. I then reboot into TWRP recovery and go to restore and I can't see anything there. I have the sdcard mounted and checked and after clicking the restore button I'm not seeing anything. ? When I click install it see's everything on my sdcard ? I don't get it. What am I doing wrong.
---------- Post added at 01:20 PM ---------- Previous post was at 12:42 PM ----------
Solved.. Copied my backup stock ROM from the TWRP folder on the phone and placed it on the SDcard, then I placed my Goodness Noteworthy 1.7 backup rom I had that I had on my computer and copied and placed that on the SDcard in the TWRP folder next to the Stock Rom backup I made. Booted back into recovery and clicked RESTORE and I was able to see both the backup rom and the Goodness Noteworthy ROM. I then wiped and did a restore and I'm back in business.
Click to expand...
Click to collapse
Deleted comment

Hei guys,
Please help!!!! I tried to install MaximusHD 10.0.0 | JB 4.2.2 | Sense 5.0 on my HTC One s,i got storage issue. Now my sd card is just 48MB. I have installed TWRP v2.6.3.0 and i did backup before flashing room. I decided to do factory restore by TWRP and wiped OS from MY device.Now when i do backup i get failed error: not enough free space on storage. Total size of all data 203MB, available space 48 MB.I see my sd card on pc through TWRP, but i cannot make backup and even put any new rom into my sd card to flash it because of 48MB...Is it any chance to get back any OS on my HTC One s....?

This post might help
http://forum.xda-developers.com/showthread.php?p=47744972.
Sent from my One S using xda app-developers app

StifflerServices said:
Ok so, in not so many words, ur saying " to restore a nanBU":
1. Wipe: data factory reset/cache/ delvic
Wipe system (but not sure which one(s) cause I was used to cwm and it looks diff in twrp
2. Flash the Rom that the nanbu is based from
3. Flash the nanbu
4 reboot
It's this the correct way to restore a nanbu from a diff or upgraded rom?
Click to expand...
Click to collapse
EDIT: oops, somehow thought this was a recent post. Never mind
Not really.
If you are S-off,
Restore Backup,
Wipe Caches
S-On
Restore Backup
Wipe Caches
(if the rom you were previously on had a different Boot.img you will need to fastboot your boot.img) In the backup
Assumes you are not trying to restore a backup to 2.15 if you were just on 2.16. You will need to RUU + factory reset/clear storage for that.

I'm sry not sure what "RUU" means... Probably will remember once u tell me I'm sure. But Ya I kinda just winged it, didn't flash the Rom to do the NanBU and all went fine, which is odd cause on my S2 w cwm it out me in a boot loop and had to start over, but I think TWRP may be a diff setup when restoring nanbu's. But either way it's always nice to know and find a "step by step" guide to restoring NanBU's from previous / updated / or different ROMs. For noobs that was one of the confusing things to do due to lack of that info in threads or utube vids out there.

Got a question. I've made my backup files but restore shows nothing but storage... No files to chose, no more options to restore. Is it normal?
Sent with my One S C2 Sense 5 using Taptalk

brilliant!
ATSPerson said:
So after telling myself what an idiot I was for not remembering what the file system was, here's what I did:
1 - Stopped panicking!
2 - Ran the back-up utility in TWRP - this recreates the file structure for the back-ups and places a back-up of your empty system in the folder
3 - Move the original full back-up I placed in the empty SDcard into the file system next to the empty back-up I'd just created
4 - Go to restore and the full back-up is there. Swiped to restore it and my One S is back to it's old self
Lessons learnt: Don't panic - there is an answer. Just think about it.
Good luck!
Click to expand...
Click to collapse
you my friend, are a genius! I have been so screwed trying all kind of crazy stuff the last few days.
Brilliant! May I suggest you run for Pres of the Colonies.

metropical said:
you my friend, are a genius! I have been so screwed trying all kind of crazy stuff the last few days.
Brilliant! May I suggest you run for Pres of the Colonies.
Click to expand...
Click to collapse
From one Clash fan to another, thanks for the thanks ☺
¡La lucha continua!

[Q] Newer CWM, md5 mismatch won't allow recovery.

I don't know if it has to do with having installed a newer version of ClockworkMod Recovery (6.0.3.1), but when I go to restore a previous backup, I get "md5 mismatch!" and no recovery is done.
Things that my non-developer brain can think of that might be relevant:
I may have changed the name of the folder for the recovery (I didn't think this mattered)
I am trying to go from CyanogenMod M5 to a recovery of an M2 (don't think this should matter).
The recovery was made using a previous version of ClockworkMod Recovery (an earlier, but 2013, version)
The recovery folder was stored on my computer and I put it on my phone using USB on-the-go (I have tried this twice to make sure one wasn't corrupted or whatever).
Thanks for any pointers. Do have have to install an older version of ClockworkMod Recovery or is there something simpler I could do? Thanks! :good:

LudicrousPeed said:
I don't know if it has to do with having installed a newer version of ClockworkMod Recovery (6.0.3.1), but when I go to restore a previous backup, I get "md5 mismatch!" and no recovery is done.
Things that my non-developer brain can think of that might be relevant:
I may have changed the name of the folder for the recovery (I didn't think this mattered)
I am trying to go from CyanogenMod M5 to a recovery of an M2 (don't think this should matter).
The recovery was made using a previous version of ClockworkMod Recovery (an earlier, but 2013, version)
The recovery folder was stored on my computer and I put it on my phone using USB on-the-go (I have tried this twice to make sure one wasn't corrupted or whatever).
Thanks for any pointers. Do have have to install an older version of ClockworkMod Recovery or is there something simpler I could do? Thanks! :good:
Click to expand...
Click to collapse
Changing the name for CWM backups will cause md5 mismatches. If you did this, you should switch and use TWRP which allows native nandroid renaming. Delete your CWM backups and stick to TWRP. It could also be an issue between CWM backups over different CWM versions however if you renamed your backups and each of those renamed backups failed except the ones you left alone then you found your issue.

SlimSnoopOS said:
Changing the name for CWM backups will cause md5 mismatches. If you did this, you should switch and use TWRP which allows native nandroid renaming. Delete your CWM backups and stick to TWRP. It could also be an issue between CWM backups over different CWM versions however if you renamed your backups and each of those renamed backups failed except the ones you left alone then you found your issue.
Click to expand...
Click to collapse
Thanks for the insight. Seems like I should just be able to change the folder name back to what it was named by default, if I can make sure it is correct. Do you think that's worth trying or is it deeper than that? I'll use TWRP from now on since it seems to be more robust (CWM was just the recommended recovery from Cyanogenmod)

LudicrousPeed said:
Thanks for the insight. Seems like I should just be able to change the folder name back to what it was named by default, if I can make sure it is correct. Do you think that's worth trying or is it deeper than that? I'll use TWRP from now on since it seems to be more robust (CWM was just the recommended recovery from Cyanogenmod)
Click to expand...
Click to collapse
Depends on how much you value those nandroids. I only keep two on my phone so it's no thing for me to delete my backups entirely. You can rename them to their original names and your issue should go away.
Sent from my SCH-I535 using Tapatalk 4 Beta

Make sure the name of the backup folder doesn't have any spaces. When I renamed backups and had a space in the name I would get that same "md5 mismatch!" error.

Thanks! So renaming the backup to what it was originally allowed the backup to attempt to restore, but data could not be restored. Attempting to boot it resulted in nor getting past the boot animation. I wonder if it was because I didn't have enough space left on my phone or of it had to so with the newer firmware I installed. Or something else.
Slightly of topic at this point but not really. Any ideas why data could not be restored?
Sent from my SCH-I535 using Tapatalk 2

LudicrousPeed said:
Thanks! So renaming the backup to what it was originally allowed the backup to attempt to restore, but data could not be restored. Attempting to boot it resulted in nor getting past the boot animation. I wonder if it was because I didn't have enough space left on my phone or of it had to so with the newer firmware I installed. Or something else.
Slightly of topic at this point but not really. Any ideas why data could not be restored?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I had a similar issue about a year ago. I resolved it by generating a new md5, but I don't recall what method I used. Do a search for that.

TWRP Failed to make backup folder

Today I was trying to back everything up because I needed to do a clean install. I used to have CMW, and it would work perfectly. Few days ago I switch to TWRP because of its friendly UI. Everytime I try to make a backup, I get this "Failed to make backup folder". When I go to the mount tab, or explorer, it shows my sd card and the folder named TWRP...is there any solution to this? Or should I switch back to cmw?
Thanks

elias.acab said:
Today I was trying to back everything up because I needed to do a clean install. I used to have CMW, and it would work perfectly. Few days ago I switch to TWRP because of its friendly UI. Everytime I try to make a backup, I get this "Failed to make backup folder". When I go to the mount tab, or explorer, it shows my sd card and the folder named TWRP...is there any solution to this? Or should I switch back to cmw?
Thanks
Click to expand...
Click to collapse
If you're using the version of TWRP modified to work with SELinux (needed for KitKat 4.4.x ROMs) you may need to shorten the name of the target file before starting the backup.

benyto said:
If you're using the version of TWRP modified to work with SELinux (needed for KitKat 4.4.x ROMs) you may need to shorten the name of the target file before starting the backup.
Click to expand...
Click to collapse
Thanks a lot!! that fixed my problem. One more question: TWRP backups dont have the boot.img file in their folders. I read that it automatically flashes the boot.img when Im restoring the backup. Will it still flash it even though Im s-on?
Thanks

elias.acab said:
Thanks a lot!! that fixed my problem. One more question: TWRP backups dont have the boot.img file in their folders. I read that it automatically flashes the boot.img when Im restoring the backup. Will it still flash it even though Im s-on?
Thanks
Click to expand...
Click to collapse
TWRP should backup your /boot partition to the boot.emmc.win file. As far as I know it should also be able to restore this, even if you are S-On. However, I am not positive about that

need help - how to copy TWRP nandroid backup to device?

how to copy TWRP nandroid backup to device?
I need to restore and I don't know how to copy from my hdd to the phone.
The phone is not booting but I can get to twrp recovery.

Latest TWRP has MTP mode.

but it doesn't allow me to copy one of the backup files which is: data.ext4.win000 and it's 1.5GB

You'll need to give us more information.
Why did it fail? Why did your phone stop booting?

1. flashed bigxie_hammerhead_LRX21O-signed.zip
2. flashed CF-Auto-Root-hammerhead-hammerhead-nexus5
3. booted fine but still had apps like Ti backup & TWRP not working due to root permissions
4. Went to recovery and performed Fix permission.
5. stuck in boot loop

gil80 said:
but it doesn't allow me to copy one of the backup files which is: data.ext4.win000 and it's 1.5GB
Click to expand...
Click to collapse
I have had the same problem with my motox 14 the way I found around it was to copy the file to a different fold and use twrp file explore to move it to the back up folder. That has worked for me and a few others try it out it will work.

how can you copy using twrp while in recovery? are you able to access your PC from recovery?

gil80 said:
1. flashed bigxie_hammerhead_LRX21O-signed.zip
2. flashed CF-Auto-Root-hammerhead-hammerhead-nexus5
3. booted fine but still had apps like Ti backup & TWRP not working due to root permissions
4. Went to recovery and performed Fix permission.
5. stuck in boot loop
Click to expand...
Click to collapse
You'll need to factory reset then reflash the ROM
Fix permissions was not required here. You need titanium beta from his twitter feed.

ok i got the phone working and lost my data but I have it backed on PC.
I just see that 10GB is used but when I browse the phone using file explorer, the device is empty.... what??

Is it a known issue?
when the phone is connected to PC I see that 10GB is used but when I i browse the device it shows as empty

No. Do a full flash of userdata.img

Please explain
What would I achieve by flashing it?

gil80 said:
Please explain
What would I achieve by flashing it?
Click to expand...
Click to collapse
A fix for your problem. I shouldn't really need to explain that.

Thanks!
I got it working now. Only need to figure out why it shows 16GB instead of 32 and why root permissions are not working

gil80 said:
Thanks!
I got it working now. Only need to figure out why it shows 16GB instead of 32 and why root permissions are not working
Click to expand...
Click to collapse
Well the answer in the 100 other threads about space say that you must wipe data and cache.
Root should be fine, but as already mentioned, not with official titanium release.

I already did a wipe data and cache. So I don't understand why I still get this but I'll try again.
The Ti Backup link in the twitter feed is no longer valid, but for example, ES file explorer and clean master and also TWRP app are not performing as if they are rooted.
I'll try to re-install CF-Auto-Root-hammerhead-hammerhead-nexus5

gil80 said:
I already did a wipe data and cache. So I don't understand why I still get this but I'll try again.
The Ti Backup link in the twitter feed is no longer valid, but for example, ES file explorer and clean master and also TWRP app are not performing as if they are rooted.
I'll try to re-install CF-Auto-Root-hammerhead-hammerhead-nexus5
Click to expand...
Click to collapse
ES doesn't work properly, correct. Not all apps have been updated to work with L yet either.
L is much more secure than KK. There are ways to root.
1) chain fire - makes small change in RAMdisk that allows sudaemon to work at boot
2)flash a permissive kernel - this lowers protection within selinux.
More apps work with the 2nd method, but still not all.
New titanium coming to play soon.
https://twitter.com/titaniumbackup

[XT1032] CM 12 - Flashing TWRP v2.8.6.0 has caused bootloop

Hello,
XT1032 CM 12 latest nightly (I think)
I flashed TWRP v2.8.6.0 using their manager app. I entered recovery mode and everything seemed to work fine. I made a NANDroid backup then rebooted. Unfortunately the device was then stuck at the bootlogo and kept looping. I can still access recovery and fastboot but for some reason adb doesn't see the device, nor can my device's data be access under Windows 7. I don't recall if I had USB debugging on or not. I would like to try to backup a few files to my computer (the backup for instance) but I am unable to since I can't use adb as the device is not recognized. MTP through TWRP doesn't seem to work either. I do have the Universal drive pack installed already on Windows.
Any help would be greatly appreciated. Thanks for your time.

To start with, let's make sure the files you want still exist.
1. Boot into TWRP recovery
2. Go to "Mount" and check that your "Data" partition is selected
3. Go back and then go to "Advanced" and then to "File Manager"
4. Navigate around (maybe /sdcard/ ? Depends what you're looking for) and find the files you need
If you can't find your file, you'll need some more help. Let's say you do see your file. Do you have a USB-OTG cable? You could plug a USB drive into your phone and mount that. Then you could copy your file to that drive. If you don't have the cable you do have some other options, but let us know how far you get.
EDIT: I know I haven't addressed the problem of the bootloop at all. Many of those solutions involve wiping so we need to make sure you've backed up all the files you need first.

First of all thanks for the help. :good:
I've been trying to find a solution and in fact flashing CWM worked. I was able to adb pull all the files and make a backup.
I backed up the content of the sdcard. I tried restoring the CWM nandroid with data only so it did reinstall the apps but unfortunately all their data and settings are gone. Making a full restore just goes back to bricking. So I have the nandroid and the data manually backed up to a computer but no idea how to restore it.
I've tried pushing the nandroid back to /mnt/shell/emulated/clockworkmod/backup after an unsuccessful restore but now it doesn't even work. (protocol failure, the push command fails)
honestly at this point I think the best solution is just to make a clean install. In fact it would be a good idea to just reset the whole phone and start with a clean slate with CM13 including wiping system files and maybe manually restore some key files and configuration (I've got all the .com files of relevant apps)
Do you know how to do that? :laugh:

frustratedwhiteman said:
First of all thanks for the help. :good:
I've been trying to find a solution and in fact flashing CWM worked. I was able to adb pull all the files and make a backup.
I backed up the content of the sdcard. I tried restoring the CWM nandroid with data only so it did reinstall the apps but unfortunately all their data and settings are gone. Making a full restore just goes back to bricking. So I have the nandroid and the data manually backed up to a computer but no idea how to restore it.
I've tried pushing the nandroid back to /mnt/shell/emulated/clockworkmod/backup after an unsuccessful restore but now it doesn't even work. (protocol failure, the push command fails)
honestly at this point I think the best solution is just to make a clean install. In fact it would be a good idea to just reset the whole phone and start with a clean slate with CM13 including wiping system files and maybe manually restore some key files and configuration (I've got all the .com files of relevant apps)
Do you know how to do that? :laugh:
Click to expand...
Click to collapse
I'm not really a Nandroid expert, but I can take a few shots in the dark. When you did your backup you got a TAR file for System and one for Data, etc., right? Then you convert those to IMGs? If you upgraded and then restored the system backup I can see why that would result in a boot loop. Restoring the data image shouldn't cause such problems though. Is this what you've tried so far? You're right, though. The safest method is to manually restore the data of just the apps where you need that data, and do it one at a time. This would allow you to pinpoint what is causing the issue. Of course, I may have no idea what I'm talking about. I've never actually needed to restore a Nandroid backup! Hopefully someone with more experience there will chime in.

I thought to hell with it I went and solved the issue by installing CM13
Thanks for taking the time to help and see you next time