Database Info

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

[Q] CWM Backup Folder not showing - CWM sees backups

Okay, so I am rooted on stock with ElementalX and philz touch recovery. I typically alternate between elementalX and stock kernel. About 2 weeks ago whenever I make a backup it backups fine, however when I go to my clockworkmod folder via root explorer it is not there. However Philz touch/CWM sees the backup folder and can restore and backup to it. I have wiped everything, I have flashed back to stock with the firmware and fastboot, where it completely wipes everything with a fresh install. Same results. I am out of ideas. If I try to copy over a clockworkmod folder with backups I have on my PC or even try to create a clockworkmod folder it gives me an error that its unable to create this folder and or copy it from my PC to my Nexus 5.
Anyone have any ideas as to what is happening? I even tried philz touch to make backups as if they were made in TWRP, so it creates a TWRP folder, but that does not do anything either. Any help would be appreciated as I am out of ideas.

ozzmanj1 said:
Okay, so I am rooted on stock with ElementalX and philz touch recovery. I typically alternate between elementalX and stock kernel. About 2 weeks ago whenever I make a backup it backups fine, however when I go to my clockworkmod folder via root explorer it is not there. However Philz touch/CWM sees the backup folder and can restore and backup to it. I have wiped everything, I have flashed back to stock with the firmware and fastboot, where it completely wipes everything with a fresh install. Same results. I am out of ideas. If I try to copy over a clockworkmod folder with backups I have on my PC or even try to create a clockworkmod folder it gives me an error that its unable to create this folder and or copy it from my PC to my Nexus 5.
Anyone have any ideas as to what is happening? I even tried philz touch to make backups as if they were made in TWRP, so it creates a TWRP folder, but that does not do anything either. Any help would be appreciated as I am out of ideas.
Click to expand...
Click to collapse
CWM is outdated.
"Internal Storage" on the Nexus 5 is /data/media/0 (which is what /sdcard is also symlinked to)
CWM uses the outdated legacy location of /data/media/clockworkmod (note the lack of /0)
Therefore you cannot see CWM backups if you look in the internal storage while booted into Android.
Development on Philz Touch has also come to an end - you should use TWRP.

Lethargy said:
CWM is outdated.
"Internal Storage" on the Nexus 5 is /data/media/0 (which is what /sdcard is also symlinked to)
CWM uses the outdated legacy location of /data/media/clockworkmod (note the lack of /0)
Therefore you cannot see CWM backups if you look in the internal storage while booted into Android.
Development on Philz Touch has also come to an end - you should use TWRP.
Click to expand...
Click to collapse
Flashed TWRP and redid a new backup, went to the root explorer and no folder fo TWRP is present, if I go back into TWRP it sees the backup I made but that is it. For some reason I am unable to see the folder.... any ideas?

ozzmanj1 said:
Flashed TWRP and redid a new backup, went to the root explorer and no folder fo TWRP is present, if I go back into TWRP it sees the backup I made but that is it. For some reason I am unable to see the folder.... any ideas?
Click to expand...
Click to collapse
Try deleting the TWRP folder using TWRP itself, reboot the recovery, change a setting or two then make a backup again.
Also make sure you're using a newer version of TWRP if you aren't already.

Sounds like a job for restorecon

rootSU said:
Sounds like a job for restorecon
Click to expand...
Click to collapse
OP says he completely wiped everything while flashing factory images though, so I dunno

Lethargy said:
OP says he completely wiped everything while flashing factory images though, so I dunno
Click to expand...
Click to collapse
If recovery can see it in /data/media/0.but android cant, it must mean storage isn't aligned correctly. Root cause? Unknown. Workaround has to be restorecon though
Easy test. Browse to /data/media/0/TWRP with a root explorer

rootSU said:
If recovery can see it in /data/media/0.but android cant, it must mean storage isn't aligned correctly. Root cause? Unknown. Workaround has to be restorecon though
Easy test. Browse to /data/media/0/TWRP with a root explorer
Click to expand...
Click to collapse
Guess its still possible but wouldn't really expect it to happen after a full wipe. Worth a shot anyways now that you've mentioned it.

rootSU said:
If recovery can see it in /data/media/0.but android cant, it must mean storage isn't aligned correctly. Root cause? Unknown. Workaround has to be restorecon though
Easy test. Browse to /data/media/0/TWRP with a root explorer
Click to expand...
Click to collapse
What is restorecon?
Edit - Flashed toe factory image again and each time I run the flash factory image I get this at the end of each flash, see attached
Found this, its the same issue I am having:
http://androidforums.com/threads/twrp-lollipop-and-the-nexus-5.883331/
Now after flashing a factory image phone just hangs, bootanimation goes on forever and ever, so for now I have no working Nexus 5. Any ideas?
Edit - Flashed TWRP and used MTP mode, internal data is completely blank, no android folder, etc... just empty...

Update, flashed factory image for 4.4.4 and that flashed without errors, going to let it boot up and do its thing. Once done I will try to flash 5.0.1 again.. will report back.
Update - Guess I am stuck for now on 4.4.4. Flashing 5.0 or 5.0.1 fails on userdata as previous screenshot.

ozzmanj1 said:
Update, flashed factory image for 4.4.4 and that flashed without errors, going to let it boot up and do its thing. Once done I will try to flash 5.0.1 again.. will report back.
Update - Guess I am stuck for now on 4.4.4. Flashing 5.0 or 5.0.1 fails on userdata as previous screenshot.
Click to expand...
Click to collapse
Out of curiosity, how much ram do you have on your pc?
Sent from my Nexus 9 using XDA Free mobile app

I am running on 8gb ram

I think I may have resolved the issue, I factory flashed 4.4.4, rebooted, then flashed a recovery, rebooted, then copied over a nandroid backup from end of last month, and restored from that back to 5.0.1. All seems well now, I did not wipe anything when doing the restore. Everything seems to be working now.. will report back if I see any other issues. Thank you to all for your assistance.

rootSU said:
Sounds like a job for restorecon
Click to expand...
Click to collapse
I am back with the same issue. Flashing 4.4.4 image flashes okay, however any attempt at flashing 5.0 or 5.0.1 causes an error just as its wiping userdata. Only way around is to flash 4.4.4 and then restore with a nandroid, which I keep plenty of those laying around.
Mind if I ask what the tutorial is for restorecon? Thank you.

Root, TWRP and Flashing

I recently got an S7 (Exynos) SM-G930F and decided to root it. So I went with the typical CF-Auto-Root method... I used the latest ODIN with the correct auto root file and everything went well. I have root.
But then I noticed that I didn't have any recovery, so I installed TWRP Manager from the Play Store and flashed recovery with that. Everything works fine except for not having access to backup /Data, this was expected.
But despite everything pretty much working, I've read on a few threads here that I was supposed to wipe my phone after flashing TWRP. Now I've also read the TWRP install thread which doesn't mention anything about wiping my device, but it does offer another method of rooting the S7... Flash TWRP first using ODIN, then flash SuperSU and dm-verity/force encryption disabler.
So I have a couple of questions.
In the TWRP guides it mentions this: "By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!". I've never had this issue, does CF-Auto-Root or SuperSU resolve this issue?
Do I need to install the dm-verity/force encryption disabler?
If I do have to wipe my device, am I going for a standard (factory reset) wipe? Advanced wipe (if so, which partitions?) or format data?
Unless there's another way to gain full access to all partitions in order to perform a complete nandroid backup (including data)?
Basically, once I've completely backed up the S7 I'd like to install the Xposed Framework. Will installing this lose any data?

d3adm8n said:
I recently got an S7 (Exynos) SM-G930F and decided to root it. So I went with the typical CF-Auto-Root method... I used the latest ODIN with the correct auto root file and everything went well. I have root.
But then I noticed that I didn't have any recovery, so I installed TWRP Manager from the Play Store and flashed recovery with that. Everything works fine except for not having access to backup /Data, this was expected.
But despite everything pretty much working, I've read on a few threads here that I was supposed to wipe my phone after flashing TWRP. Now I've also read the TWRP install thread which doesn't mention anything about wiping my device, but it does offer another method of rooting the S7... Flash TWRP first using ODIN, then flash SuperSU and dm-verity/force encryption disabler.
So I have a couple of questions.
In the TWRP guides it mentions this: "By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!". I've never had this issue, does CF-Auto-Root or SuperSU resolve this issue?
Do I need to install the dm-verity/force encryption disabler?
If I do have to wipe my device, am I going for a standard (factory reset) wipe? Advanced wipe (if so, which partitions?) or format data?
Unless there's another way to gain full access to all partitions in order to perform a complete nandroid backup (including data)?
Basically, once I've completely backed up the S7 I'd like to install the Xposed Framework. Will installing this lose any data?
Click to expand...
Click to collapse
Of course you are going to want to flash .zips through your Recovery, but as you have recognised there is the DM-Verification that will stop you doing so. In order to get rid of the encryption you will have to firstly have to Factory Reset but as you know this will also delete all apps and data that you have on your Internal Storage.
Then, you need to flash a .zip called 'no-verity-encryption-opt' and this will apply a patch onto your boot so you can flash unknown images and zips through.
If you can't find this no verity zip, leave me your email and I'll try and send it to you.
Good luck!
Also, installing the Xposed Framework will not cause you to lose any of your data.

AzzyC said:
Of course you are going to want to flash .zips through your Recovery, but as you have recognised there is the DM-Verification that will stop you doing so. In order to get rid of the encryption you will have to firstly have to Factory Reset but as you know this will also delete all apps and data that you have on your Internal Storage.
Then, you need to flash a .zip called 'no-verity-encryption-opt' and this will apply a patch onto your boot so you can flash unknown images and zips through.
If you can't find this no verity zip, leave me your email and I'll try and send it to you.
Good luck!
Also, installing the Xposed Framework will not cause you to lose any of your data.
Click to expand...
Click to collapse
Thanks for the info.
I may have already done this, I honestly can't remember. Is there any way to check if I've already installed no-verity-encryption-opt? Because I am already able to install zips in Recovery, so far I've installed a SuperSU update and AdAway. Although I do get a fair amount of 'Failed/Unable to mount /data' messages which may suggest that these zip installs didn't actually work.
I guess I still need to factory reset? And I guess that also means rooting again and installing no-verity-encryption-opt, then finally Xposed?

d3adm8n said:
Thanks for the info.
I may have already done this, I honestly can't remember. Is there any way to check if I've already installed no-verity-encryption-opt? Because I am already able to install zips in Recovery, so far I've installed a SuperSU update and AdAway. Although I do get a fair amount of 'Failed/Unable to mount /data' messages which may suggest that these zip installs didn't actually work.
I guess I still need to factory reset? And I guess that also means rooting again and installing no-verity-encryption-opt, then finally Xposed?
Click to expand...
Click to collapse
I had the same error message you are facing right now. Can you let me know what values you see when you view the Data, System and Cache partition, after clicking on 'Partition Options' - If you're on the latest TWRP you can take screenshots by hitting the Power and Vol Down.
^^^IGNORE^^^
No factory reset required. Basically, the file system of your Data partition is incorrect and that is why it can't be mounted on to.
Go to 'Wipe'->'Advanced Wipe'->Click on the Data box->'Partition Options'->(You may be seeing values like 0mb for most of the information displayed and why you can't mount to it; if you are not let me know!)->'Change File System'->(Try out different File Systems until you being to see true values for the sizes, but avoid using EXT2 and EXT3 if you can)
Doing all this you will be able to Mount to your Data partition, however your OS will be deleted! So get your phone into Download mode, open up Odin program on your PC, and flash a Bootloader (BL) and your phone will be fine.
Then flash the 'no-verity-encryption-opt.zip' and then your SU Binary and Xposed Framework etc.
Good luck again Buddy!
---------- Post added at 05:41 PM ---------- Previous post was at 05:12 PM ----------
Wait Install the No-verity zip first then, then flash a BL

AzzyC said:
I had the same error message you are facing right now. Can you let me know what values you see when you view the Data, System and Cache partition, after clicking on 'Partition Options' - If you're on the latest TWRP you can take screenshots by hitting the Power and Vol Down.
^^^IGNORE^^^
No factory reset required. Basically, the file system of your Data partition is incorrect and that is why it can't be mounted on to.
Go to 'Wipe'->'Advanced Wipe'->Click on the Data box->'Partition Options'->(You may be seeing values like 0mb for most of the information displayed and why you can't mount to it; if you are not let me know!)->'Change File System'->(Try out different File Systems until you being to see true values for the sizes, but avoid using EXT2 and EXT3 if you can)
Doing all this you will be able to Mount to your Data partition, however your OS will be deleted! So get your phone into Download mode, open up Odin program on your PC, and flash a Bootloader (BL) and your phone will be fine.
Then flash the 'no-verity-encryption-opt.zip' and then your SU Binary and Xposed Framework etc.
Good luck again Buddy!
---------- Post added at 05:41 PM ---------- Previous post was at 05:12 PM ----------
Wait Install the No-verity zip first then, then flash a BL
Click to expand...
Click to collapse
Hey man, i'm having that problem.
I want to root my phone but i am not able to acess Internal Storage, on twrp its showing 0mb.
I did what you says in this post but i always have caught in ''Encrypetd phone'' or something like this.
What are the steps? 1- format data (then deletOS) and then? Can you help me please?

build.prop modification caused loss of root, now stuck with bad build.prop

Hello,
I have a rooted Samsung Galaxy Note 3. I was experimenting with the build.prop file, having made a backup of the original version of it. After making some changes to the build.prop file and rebooting the device, the vast majority of the apps stopped working and what is worse, I somehow lost my root access. My original plan was to revert to the original version of the build.prop file if things didn't work as expected but now all I have is read-only access to the /system folder and I can't edit the build.prop file or replace it with the backup of the original I made. I also tried accessing the filesystem via an adb shell, but I still only get read-only access to the system areas. The problem is now 95% of my apps crash before they even start and I can't even run SuperSU, or playstore. I have Total Commander installed, and it is one of the very few apps that work, but again, I only get read-only access to the system area. All I need to do is delete the problem build.prop file and rename the backup file oldbuild.prop file, but how do I re-gain read/write access to the /system folder??
I would truly appreciate any help, ideas or advice
Thanks a lot
PS. I do not have a custom recovery installed. Just the Samsung stock recovery

memrah said:
Hello,
I have a rooted Samsung Galaxy Note 3. I was experimenting with the build.prop file, having made a backup of the original version of it. After making some changes to the build.prop file and rebooting the device, the vast majority of the apps stopped working and what is worse, I somehow lost my root access. My original plan was to revert to the original version of the build.prop file if things didn't work as expected but now all I have is read-only access to the /system folder and I can't edit the build.prop file or replace it with the backup of the original I made. I also tried accessing the filesystem via an adb shell, but I still only get read-only access to the system areas. The problem is now 95% of my apps crash before they even start and I can't even run SuperSU, or playstore. I have Total Commander installed, and it is one of the very few apps that work, but again, I only get read-only access to the system area. All I need to do is delete the problem build.prop file and rename the backup file oldbuild.prop file, but how do I re-gain read/write access to the /system folder??
I would truly appreciate any help, ideas or advice
Thanks a lot
PS. I do not have a custom recovery installed. Just the Samsung stock recovery
Click to expand...
Click to collapse
The solution would be flashing twrp, then using its build in terminal or adb shell to replace the infected build.prop

-Hope- said:
The solution would be flashing twrp, then using its build in terminal or adb shell to replace the infected build.prop
Click to expand...
Click to collapse
Thanks for your answer. I did manage to revert to the correct build.prop file and get rid the bad one. For some reason though, when I restarted my phone it is now getting stuck at the Samsung logo screen with a pulsing blue status LED. I know for a fact that the build.prop file is the correct/original one. So I'm clueless about what might be causing it to get stuck during boot. Any ideas or suggestions? Thanks in advance.

memrah said:
Thanks for your answer. I did manage to revert to the correct build.prop file and get rid the bad one. For some reason though, when I restarted my phone it is now getting stuck at the Samsung logo screen with a pulsing blue status LED. I know for a fact that the build.prop file is the correct/original one. So I'm clueless about what might be causing it to get stuck during boot. Any ideas or suggestions? Thanks in advance.
Click to expand...
Click to collapse
Clear cache

-Hope- said:
Clear cache
Click to expand...
Click to collapse
-Hope-, Thanks a lot for your help. I tried clearing the cache, didn't work. Tried a factory reset via Recovery mode, didn't work, so I think I will need to flash the ROM. Do you know where I can download a stock factory ROM for the Note3 that is unmodified and not tampered with (malware free), just the way Samsung released it?
Once again, thanks a lot for your help

memrah said:
-Hope-, Thanks a lot for your help. I tried clearing the cache, didn't work. Tried a factory reset via Recovery mode, didn't work, so I think I will need to flash the ROM. Do you know where I can download a stock factory ROM for the Note3 that is unmodified and not tampered with (malware free), just the way Samsung released it?
Once again, thanks a lot for your help
Click to expand...
Click to collapse
Updato.com
Sammobile.com < official site

Thanks. I flashed my Note3 with stock Lollipop ROM downloaded from Sammobile.