Database Users

TWRP Backup location?

I am running stock rom on Android version 5.0. I have rooted and installed T WRP recovery. After I did a backup through TWRP to my internal phone storage, I cannot find the folder where the backup is stored yet my file manager shows is that the storage has been used.
Secondly, I put in a SD card and performed another backup (storing it to the sdcard). After TWRP completed that backup was able to find the folder for it easily using my file manager. I still cannot find the location of the first backup that I did. And it's taking up 10 gigs worth of space on my phone's internal memory.
Has anyone else had a problem with TWRP?
Does anyone know how to resolve this issue?
Any input would help. Thanks.

GM83 said:
I am running stock rom on Android version 5.0. I have rooted and installed T WRP recovery. After I did a backup through TWRP to my internal phone storage, I cannot find the folder where the backup is stored yet my file manager shows is that the storage has been used.
Secondly, I put in a SD card and performed another backup (storing it to the sdcard). After TWRP completed that backup was able to find the folder for it easily using my file manager. I still cannot find the location of the first backup that I did. And it's taking up 10 gigs worth of space on my phone's internal memory.
Has anyone else had a problem with TWRP?
Does anyone know how to resolve this issue?
Any input would help. Thanks.
Click to expand...
Click to collapse
Should be in twrp folder. Just if you can't find it, enter recovery and delete the backup in internal storage. Just keep the 1 in external.
Sent from my SM-N920C

Problems after extending SD Card as Internal memory- can't Backup (and others)

I have an unlocked bootloader, but I'm not rooted. I upgraded to MM via OTA and set my SD Card to be used as internal memory. I've had some problems since:
1) The first real issue is that Evernote is giving me a database read/write error and not working. It seems that to resolve that, I'll probably need to root. So, I went to do a MM nandroid before rooting
2) When i went into TWRP (i a had flashed 2.8.7.1-clark), and tried to create a backup, I received a Failure: E: Unable to mount storage (one note: the top of my screen shows TWRP 2.8.7.0, not .1, so i double-checked that i was using the correct version from https://dl.twrp.me/clark/, and I am. The file name is 2.8.7.1, but it appears on screen as .0. Is anyone else seeing this?)
3) When i go into the Mount screen and select storage, it is showing Internal as just 2+GB free (which is correct), but 0MB for my Micro SDCard. So, it can't mount it.
4) Looking around, the fixes for this seem to be a bit severe in terms of formatting the SD Card again, etc. (ex. http://forum.xda-developers.com/showthread.php?t=2354029)
So, my questions are:
1) If anyone knows of a solution to that Evernote issue, that would be great
2) More importantly, what my options are for fixing the Backup problems
3) Specifically, with my SDCard now supposedly acting as internal memory, if i format the card per the common fixes, will that cause other unexpected problems with apps and other functions that are now using my SD Card as usable storage?

How did you set SD card as internal storage. Me: stock, no root, MM
Sent from my XT1575 using Tapatalk

I'm giving up on combined storage until twrp is fixed.

You just go into settings, storage, then click on the SD card. I'm back to lollipop at the moment, so I cant say exactly what to do next, but I think from there it should be clear. It may be an option up in the overflow menu at the top right. It will make you reformat your card as part of the process .

Thanx Chuck! Need to b.u. before formatting as internal...

I had the same issue with the SD card set as internal, couldn't make a twrp backup, so I had to reformat as storage and it works. Only bad part is now I can't move apps to SD
Is there a twrp fix in the works??

chuck-fu said:
2) When i went into TWRP (i a had flashed 2.8.7.1-clark), and tried to create a backup, I received a Failure: E: Unable to mount storage (one note: the top of my screen shows TWRP 2.8.7.0, not .1, so i double-checked that i was using the correct version from https://dl.twrp.me/clark/, and I am. The file name is 2.8.7.1, but it appears on screen as .0. Is anyone else seeing this?)
Click to expand...
Click to collapse
I don't have MM installed, so I don't know about the rest of it. But I've flashed the 2.8.7.1 IMG twice now and my TWRP still says 2.8.7.0 on the top of the screen. So either we're both making the same mistake, or TWRP didn't update their version number in the recovery.

ScaryBugThing said:
I don't have MM installed, so I don't know about the rest of it. But I've flashed the 2.8.7.1 IMG twice now and my TWRP still says 2.8.7.0 on the top of the screen. So either we're both making the same mistake, or TWRP didn't update their version number in the recovery.
Click to expand...
Click to collapse
It's a known issue that the version displayed stays on 2.8.7.0 after updating.
Sent from my Moto XPE

16 Gb of memory instead of 32

I've updated to .253 with all the wipes last week and today I discovered I only have 16 Gb of internal memory now.
Has anybody encountered the same issue? What can cause such a problem? And how can I solve it?

I've been getting this issue but some reason, I'm not limited to 16, I'm limited to 22? I'm not sure.

Is the same information as the picture, if you check memory with a file explorer(Es file explorer for example)? On a computer what is the situation with memory?

Monipeev said:
Is the same information as the picture, if you check memory with a file explorer(Es file explorer for example)? On a computer what is the situation with memory?
Click to expand...
Click to collapse
I noticed it on a computer initially. It showed 16 Gb instead of 32 Gb.
Now it shows something even worse! Total irrelevance.

It is absolutely illogical. In file explorer? What about if restart your phone? Any differents?

No difference, reloading doesn't change anything.
I'm so puzzled.

Also getting this issue @ 16GB internal storage.
FWIW i'm using the XPower 3 debloat with the .253 kernal.

@jufofu, What will show if despite the small remaining space, continue to copy more information in the internal memory? Whether it will continue to collect more data in memory, which means just bad reporting of information on available memory ? Maybe factory reset or repair with Xperia Companion. If problem still there, then the option is service. If you decide to do this, copy your information from phone to computer before this steps.

@Poag, was the problem there on the previous firmware? Do you have any ideas about its origins?
@Monipeev, it doesn't copy files from PC when the small memory is filled.
I will try to flash it again this week. If it doesn't work properly I'll have to restore TA backup and go the the service.

To be honest, i can't remember. I just flashed .224 from Flashtool wiping everything and TWRP reports only 8GB for internal.....booting into system atm....
Would someone with a 32GB internal mind posting a df?
[edit] Ok thats given me back my 32GB internal storage, currently sat on a freshly imaged device with 10GB of 32Gb used internal.

Poag said:
To be honest, i can't remember. I just flashed .224 from Flashtool wiping everything and TWRP reports only 8GB for internal.....booting into system atm....
Would someone with a 32GB internal mind posting a df?
[edit] Ok thats given me back my 32GB internal storage, currently sat on a freshly imaged device with 10GB of 32Gb used internal.
Click to expand...
Click to collapse
How did you go about fixing this?
I have the same problem.

So this is supposedly a bug in .253? I'm glad that it can be solved by reflashing.
@MattyCurrann, you too got this problem after flashing .253?

So i
1- Downloaded the UK Customised 224 in Flashtool - XperiFirm
2- Flash this wiping everything in the 'Wipe' box.
3- Booted into Fastboot and flashed the .253+TWRP kernal listed in the XPower thread post #312
4- Booted in system and then set about resetting up the device from TitaniumBackups.
---------- Post added at 10:30 AM ---------- Previous post was at 10:23 AM ----------
MattyCurrann said:
How did you go about fixing this?
I have the same problem.
Click to expand...
Click to collapse
I dont think you have the problem. 22GB is were you are meant to be.
10GB is system 22GB is user space.

jufofu said:
So this is supposedly a bug in .253? I'm glad that it can be solved by reflashing.
@MattyCurrann, you too got this problem after flashing .253?
Click to expand...
Click to collapse
nope, NOT a bug in .253,
afaik it's been there on Lollipop as well,
existed on Lollipop firmwares, 185, 224, 253 MM firmwares
(I got it too on Z5).
It sometimes occured during flashing Firmwares via XperiFirm + Flashtool or flashing new ones via TWRP,
really weird "bug"

There is another thread regarding this bug:
http://forum.xda-developers.com/z5-compact/help/how-storage-t3398804/post67849319#post67849319
You can fix it without flashing anything - if you have TWRP recovery, just Repair /data partition in Wipe menu. If that doesn't help, try Repairing /system partition (that helped in my case).

Another cases of the same issue: http://forum.xda-developers.com/xpe...-repack-stock-kernel-dm-t3301605/post67317647
Edit: posted it without refreshing the page, basically the previous post covers it all.

flashtools sucks nowadays!

Repairing didn't help, but resizing /data works perfectly. I've got my memory back.

jufofu said:
Repairing didn't help, but resizing /data works perfectly. I've got my memory back.
Click to expand...
Click to collapse
A little "how to" would be nice.
EDIT:
As TWRP kept giving me Errror 4. I did figure out what it meant by that.
It needs manual handling (answering questions) in cli.
I went on with "adb shell" on my computer while the device was started up in TWRP/recovery mode.
There I unmounted everything, and then I ran this command from adb shell:
Code:
e2fsck -f /dev/block/mmcblk0p42
There I had to answer a bunch of questions about orphaned inodes and other corruptions. (Tookl a while to answer them all. I could have used "-y").
Once done, the fs was marked as clean, and the rezise command in TWRP worked flawlessly. Problem solved.
Strange that it had so many corruptions/orphaned inodes, considering it was a new fresh flash made just recently with flashtool.

how did you update your phone?

Encrypted internal Memory. Unable to install zip files using TWRP.

Hello everybody/anybody?
I have managed to wipe my phone with the intention of installing a zip file which I placed in the internal memory. However,I foolishly wiped my phone without checking I could access the zip file and it turns out that my internal memory is encrypted and I cannot see any files. So I can't access the Zip files to restore any ROMs. I have tried sideloading this: no-verity-opt-encrypt-5.1.zip, But it failed...
Any help gratefully received.

atinw said:
Hello everybody/anybody?
I have managed to wipe my phone with the intention of installing a zip file which I placed in the internal memory. However,I foolishly wiped my phone without checking I could access the zip file and it turns out that my internal memory is encrypted and I cannot see any files. So I can't access the Zip files to restore any ROMs. I have tried sideloading this: no-verity-opt-encrypt-5.1.zip, But it failed...
Any help gratefully received.
Click to expand...
Click to collapse
Ok. i have wiped the internal memory now, but is now bootlooping...

atinw said:
Hello everybody/anybody?
I have managed to wipe my phone with the intention of installing a zip file which I placed in the internal memory. However,I foolishly wiped my phone without checking I could access the zip file and it turns out that my internal memory is encrypted and I cannot see any files. So I can't access the Zip files to restore any ROMs. I have tried sideloading this: no-verity-opt-encrypt-5.1.zip, But it failed...
Any help gratefully received.
Click to expand...
Click to collapse
atinw said:
Ok. i have wiped the internal memory now, but is now bootlooping...
Click to expand...
Click to collapse
Solved: deleted everything inc vendor etc...

Internal memory suddenly read-only

Hi,
I suddenly have a very strange problem. My internal memory changed for some reason to read-only. The built-in file browser can't modify files anymore, nor can any app. With Root explorer (root access) I can still modify files. I could just use Root explorer, but some apps actually crash because they can't access the internal memory, so that's no solution.
Here's the situation:
I have the SM-N9005, on Android Kitkat (4.4.2). I was rooted with CF Auto Root. I wanted to try Magisk (not realising that you needed at least Android 5.0 for it). I uninstalled Busybox, Xposed, and then did a full unroot via the SU app. Then I installed TWRP recovery, tried installing Magisk. Of course that didn't work. So then, with Odin, I reinstalled CF Auto Root. After that I reactivated Busybox and Xposed. TWRP seemed to have disappeared, so installed that again as well. Everything was back to the way it was, except for that internal memory issue.
Does anyone has any idea how to fix this?
I made nandroid backup, so I could just revert to that backup but I'd prefer to find a solution and know why it happened.
Thanks!

After installing and running twrp, did it ask to make changes to internal storage?

audit13 said:
After installing and running twrp, did it ask to make changes to internal storage?
Click to expand...
Click to collapse
It did not. And I've just found out that everything on the SD card can't be opened via the built in file explorer. I can create new folders and such, I just cannot open any files.
I says: "Not able access to external SD card. Try again if SD card is successfully mounted"

It's been a while since I used twrp but I recall being asked if I want to allow modifications to the file system.
Maybe it's time to flash back to stock using Odin and then restore your backup?

audit13 said:
It's been a while since I used twrp but I recall being asked if I want to allow modifications to the file system.
Maybe it's time to flash back to stock using Odin and then restore your backup?
Click to expand...
Click to collapse
Weird, I don't think it asked.
Yeah I guess is if no one comes up with a solution I won't have another choice.