When I was using the factory international rom, my internal storage like in TWRP/install is perfectly readable. I am sure my device has everything done needed to flash a custom rom. But like when I flash Havoc's ROM or lineage, then reboot to recovery, under install the directories become a bunch of folders with illegible names, and I cannot write to/from it anymore. The rom works fine, except the same thing happens when trying to access the files in the storage through a file manager or my computer.
Please this is super frustrating. If anyone has a solution to this, it would be of great help. Especially because now I cannot even restore backups in TWRP. Same for the apps like in titanium backup, I cannot restore them because it says there is no such directory anymore. I cannot for the life of me figure out what happens to my internal storage when I flash a ROM. I really don't want to have to use the MSM tool once again to start completely over again from the very beginning like I have so many times.
Thank you if you have any sort of solution to this, it would be greatly appreciated.
EDIT: I fixed the encryption by formatting my data in TWRP. I lost everything, but it did work. I wiped all my data, then let the phone fully reboot without any lockscreen functions chosen. Then I got my internal storage directory back again. Good enough for me.
Related
Well, first day I got my tab i rooted and such.
Tried a rom (wich wiped everything obviously)
installed a couple of apps then made a backup with Titanium.
decided to go back to stock rom for the time being (wait for more bugless roms)
When i tried to restore my Backups, everything was gone.
question is, Does the backup just go in general internal storage, wich is not calculated as a SD card, so gets formated everytime we wipe??
Im used to backup and wipe, on my phone wich has internal and external SD, so no problems there.
Any input ?
If I understand right, there is no separate storage on the N10. I think /sdcard is basically just an emulated folder sitting on the data partition, so anything that wipes data, will wipe the sdcard. Might want to wait for someone else to give their input on this though.
As for backups, at the most I usually just backup app's (apk files) and put them in a folder on my computer, then just reinstall all of them with Android Commander.
I have a rather urgent issue, in which a factory reset wiped my sdcard. First of all, is that normal? This is my first device with no external microsd, and my first time using TWRP. Before, I had been using various versions of Amon-Ra or CWM, and when I factory reset they never wiped the sd card. Next, whether it was normal or not, I need a way to recover my data. I had around 8 gigs in sdcard before it got wiped.
To give you more background info on what was going on, I had a rooted 4.1.2 16GB Nexus, and I decided that I wanted to try PA. I made a nandroid backup of course, and then proceeded to flash the rom. I followed the instructions on the PA thread, first doing a factory reset followed up by the actual flashing, then a wipe of cache/davlik. After I tried the rom out for a few minutes, I noticed that there weren't any redeeming features to make it worth the time-consuming switch from stock to PA, transferring all my data and setting up my settings once more.
I rebooted back into recovery and factory reset again, and then I went to restore and saw that there were no backups. Suspicious, I went to the install menu, and found my entire sdcard folder had been wiped out. What happened?
Edit: I'm currently still on the recovery, afraid to do anything in case I lose my data forever.
Was your boot loader already unlocked or did you unlock it right before you flashed the ROM?
littleemp said:
Was your boot loader already unlocked or did you unlock it right before you flashed the ROM?
Click to expand...
Click to collapse
Thanks for the reply, especially on Christmas, but I got around the issue myself. It had been unlocked for 2 months now.
I noticed that every time I booted into recovery, it would make a "0" folder and move the contents of my sdcard into that "0" folder. Then the 0 folder would go inside another 0 folder, and so on and so forth. It was a really strange issue because I was unable to restore my backup; TWRP could not find my /sdcard/TWRP/backup folder, because it did not exist! It was in sdcard/0/0/TWRP/backup. I used the built in file manager in TWRP, and moved the contents back into the proper folder. I could then restore, and now I'm feeling relieved.
However, two issues remain; the 0 folders are still there, and storage transfer speeds seem very slow.
Edit: I got rid of the 0 folders by moving my folders out of them and then deleting the 0 folders, but the size of my files seem to have been inflated. What took up 6 gigs before is now taking up 8.8gb. Lol wut? Also, when I hook it up to a computer it tells me that 12GB has been filled. So many discrepancies.
androidwkim said:
Edit: I got rid of the 0 folders by moving my folders out of them and then deleting the 0 folders, but the size of my files seem to have been inflated. What took up 6 gigs before is now taking up 8.8gb. Lol wut? Also, when I hook it up to a computer it tells me that 12GB has been filled. So many discrepancies.
Click to expand...
Click to collapse
I am having the same problem. I think everybody has that problem, because it's caused by jelly bean 4.2 and its new emulated storage.
The only way I have found to get arround it was to copy all files on the computer from the sdcard, then formating the sdcard in recouvery and moving everything back.
Only problem I am having right now is that I can't for the love of it copy my files. Stupid MTP filesystem is really buggy and extremly slow. I constantly crashes or gives me multiple erros. The one I am having at the moment is something about a parameter error.
Very annoying the stupid filesystem under 4.2.
Btw. I can't get the adb pull command to work either. When I tell it to copy system/storage/emulated/legacy (I believe thats where the sdcard is actually loccated, right?!) it doesn't copy a single file.
If anybody could help me I would be very greatfull.
xaboren said:
I am having the same problem. I think everybody has that problem, because it's caused by jelly bean 4.2 and its new emulated storage.
The only way I have found to get arround it was to copy all files on the computer from the sdcard, then formating the sdcard in recouvery and moving everything back.
Only problem I am having right now is that I can't for the love of it copy my files. Stupid MTP filesystem is really buggy and extremly slow. I constantly crashes or gives me multiple erros. The one I am having at the moment is something about a parameter error.
Very annoying the stupid filesystem under 4.2.
Btw. I can't get the adb pull command to work either. When I tell it to copy system/storage/emulated/legacy (I believe thats where the sdcard is actually loccated, right?!) it doesn't copy a single file.
If anybody could help me I would be very greatfull.
Click to expand...
Click to collapse
I had the same fear, emotion and discovery a week ago when trying a new Rom thanks multi users feature .
You may try to switch from MTP mode to MSC in system setting to increase the speed.
Take care of the different tools because as example JROMFlasher will format the SD card for better cleaning. (I had backup!)
I think I read that the Factory Reset from the settings menu WILL erase everything.
Formatting with ClockworkMod, saves your sdcard files.
I also recommend unlocking asap just for laughs. Even if you don't plan on rooting or Modding... unlocking will ensure your files won't be deleted if you decide to or something happens that requires it
Sent from my Nexus 7 using XDA Premium HD app
Hello!
I have a major problem and I really hope you will be able to help me.
For the past several months, I've been using ParanoidAndroid (4.4.2.). Everything was great. I was using the version that had a lot of tweaks added. I used Paranoid OTA to update to versions with tweaks. Last update (04/06) had removed tweaks and the ROM had started to randomly close apps, desktop and glitching all together.
Seeing this, I decide to re-flash. So I go through the regular checklist. Launch Titanium Backup to backup all the apps that are necessary for me. Whilst backuping an app, the rom glitches and closes Titanium and starts randomly closing the desktop so the rom is not usable. I restart.
After the restart I see that all my files have disappeared from the internal storage and I see that there is 25GB of free space (I know that I have about 1GB free). I do not panic and connect the phone to the PC and it also shows that internal memory is empty. I reboot to TWRP file manager which shows original folders but no content. I get worried.
I decide to just go ahead and flash CloudyStock. I know that there is 1GB free, ROM is 1.8GB. When copying to phone, transfer freezes after about half. This tells me that files are on my phone but for some reason are not accessible. So I download the AOKP ROM which is smaller, put it on my internal storage and go through the normal flashing process.
The problem now is that this got me to a bootloop stage and the only things I can enter is "Factory Hard Reset" and "Download mode".
If I use the Factory Hard Reset, it will wipe the internal storage and my files will be lost forever. And with the Download mode I can return to full stock but it will also wipe the internal storage.
In short: ROM glitched, can't see or access my files, flashed ROM, stuck in a bootloop, internal storage is almost full but PC shows that it is empty. I cannot get into TWRP.
Is there anyway to get all the data from internal storage safely to my computer so I can go ahead with the flash to stock?
I flashed my i9500 with TWRP 2.8.1.0 using Odin and it wrote an undeletable backup onto my internal memory. To get rid of that, I backed up the "BACKUPS" folder and formatted the internal storage only for it now to cause the entire internal storage to be write protected to my android apps. I can copy and delete stuff to it through PC but my apps wont work, those that require to download pics and videos or make backups to the internal storage, web browsers can't download anything to the internal storage yet I now have over 7GB free space.
It's clear TWRP is write protecting the internal storage selectively (first it wrote protected the storage to both the phone and pc, now to the phone only). How should I sort this problem out?
I have also just tried using root explorer to change permissions to the internal storage but it doesn't work. It's failing. Titanium backup shows its own backup folder is unwrittable. It cannot be changed by Root explorer
I just tried fixing permissions in twrp but to no avail. I uninstalled Clean master only to try and re-install it and it won't install now, it gives a failed install error. Kingsoft office continually shows "stopped working" and fails to work completely. All this started with flashing Twrp. I can't view pics in whats app or send them, neither can I edit documents. Any help to rid of this issue will be gladly appreciated.
People please please avoid twrp at all costs!, i have now lost all my data and apps are all failing. I deerly deerly regret why i ever flashed twrp recover in the first place!
I seem to have solved the issue after a very grueling experience.
TWRP has its flaws and it is quite notable here. Here is how I have gotten around the issue:-
Immediately after I installed TWRP I made a system backup of the entire phone as of its state at the time.
I copied it to my pc and tried to delete the backup that TWRP had made. It was completely write protected, nothing could delete it.
I then decided to use TWRP to format my internal storage after backing it up. Then restore the data back which I did successfully.
Little did I know what had happened. TWRP had assigned the internal storage attributes that even Root explorer (paid) could not undo.
The internal storage had become unusable to the system and user apps.
Slowly my apps began to collapse one after the other failing. From frustration I tried to salvage the data the apps held at the time so that I can factory reset and restore but Titanium backup could not access its own folder. That's where all the frustration begun.
I later flashed CWM and accidentally formatted all my data instead of the data partition.. this was now hell.
One last try which was about 5 hours later I returned TWRP recovery, wiped the data partition and got hold of my prior backup with TWRP, restored it and am 9 hrs back from total loss of data. So the internal storage now has its initial attributes prior to the predicament.
Am actually back exactly to where all this mayhem began when I decided to delete the "BACKUPS" folder and there was absolutely nothing else that was wrong, which now I will attempt to delete hoping that I won't experience deja vu.
This is a problem worth reporting to TWRP developers and I don't know how
TWRP recovery Fix Permissions
I couldn't delete back ups from the internal storage at all. I couldn't even copy saved back ups from my pc to my Note 3. I went into TWRP recovery, under Advanced select Fix Permissions
Now I can delete folders in the TWRP main folder with a ES file explorer or on my PC via usb cable.
Never had any problems like this with TWRP on my S4+. For me the backups taken and its folders can be handled just fine, copied, deleted, moved etc. Must be som compatibility issue with your setup.
So, things have massively escalated today and my phone appears to be soft bricked. Joy. I'll run through what happened.
1. I encrypted my phone using the built in tool in Cyanogen Mod. After it rebooted, it was glitchy and I lost a load of apps, the phone really wasn't working well. Rebooted again, but no improvement.
2. I went into TWRP (2.8.x) to restore my old backup, which was on the SD card. After the initial wipe of the internal storage, the log showed
E: Can't mount storage
Click to expand...
Click to collapse
and the restore failed.
3. I reboot and phone goes straight into recovery mode as there is no OS installed (the recovery wipes the internal storage first). Internal Storage is now showing as '0 MB'. I cannot find a way of mounting this storage anymore. Have tried factory reset (doesn't work because file system isn't mounted), and rebooting a few times but no avail.
* There seem to be some options about flashing a .pit file using odin, but I do not have this file. My phone is the Note 4 SM-N910F Model. If I can do this through Odin then maybe this will resurrect the file structure and make this storage mountable?
* There may also be another option using ADB but I still don't know what commands to use.
Any help would really be appreciated as it seems there is some possibility of a fix. That being said my hopes are not that high...
I believe I may have fixed this. I would like to keep this up here in case in helps anyone in the future, I would imagine this is only useful for people who have encrypted their device. I'm not an Android expert so can't be responsible for any damage to devices or data loss etc.
It seems that the encryption must have gone wrong somewhat and this is likely to have impacted on the file system.
Although I couldn't wipe on the device, I was able in recovery to FORMAT data (not just wipe). Go to the wipe menu, then format. After this, reboot into recovery again and you should be able to mount again. It rebuilt the filesystem too.
This should be a quick fix that may help a few people with the issues with not being able to mount the file system. I hope this can help at least one person!
I managed to restore from my backup after and phone is now working. Thanks anyway!
Is there any way to set the default storage of play store apps to the sd card?