Today, I have experienced a very "odd" problem. I have just found out that there is a folder called "storage" visible in my Internal Storage.
When I thought that, since it was visible, it did not contain much useful files (Only 2 xml files I found which would be in both internal and external storage) so I deleted that folder and everything in my SD Card and Internal Storage vanished.
I found out that the "storage" folder had a link to both storage devices but the weird thing is, why was that there and why is it visible? I could of sworn that I have never seen that before on my Xperia Z...
Can anyone else see their "storage" folder in the internal storage or is it just me?
ZeroInfinity said:
Today, I have experienced a very "odd" problem. I have just found out that there is a folder called "storage" visible in my Internal Storage.
When I thought that, since it was visible, it did not contain much useful files (Only 2 xml files I found which would be in both internal and external storage) so I deleted that folder and everything in my SD Card and Internal Storage vanished.
I found out that the "storage" folder had a link to both storage devices but the weird thing is, why was that there and why is it visible? I could of sworn that I have never seen that before on my Xperia Z...
Can anyone else see their "storage" folder in the internal storage or is it just me?
Click to expand...
Click to collapse
Hi.
At root, i have sdcard and sdcard1 and storage. Inside storage folder i have sdcard0 and sdcard1. I have seen this before for long time ago.
CiscoX said:
Hi.
At root, i have sdcard and sdcard1 and storage. Inside storage folder i have sdcard0 and sdcard1. I have seen this before for long time ago.
Click to expand...
Click to collapse
but this is totally different from what I have experienced.
From Windows, Internal Storage would have a folder called "storage" with another folder called "01" inside the storage folder. So "Internal Storage/storage/01/" if it was read on a Windows PC. inside the storage folder, there is just 1 folder called "01", nothing else. inside "01" folder, there are ONLY 2 .xml files which are the same as the 2 .xml files you would have by default in the root of your Internal and External Storage.
In short- Internel Storage has a folder called storage, inside storage has a folder called 01, inside 01 there are only 2 .xml files. The strange thing is, if it were linked to Internal/External Storage, why only 2 .xml files are visible in the 01 folder?
EDIT: When I tried to delete the storage folder (At the time I did not know that it was linked) Windows loading bar for deleting files did not move so I had to cancel it. Once cancelled, everything in my external/internal storage was wiped off. Thankfully, I recovered most of my lost pictures with Recuva
Not sure but I think this folder came somehow from the recovery maybe a bug.
I hope you didn't lost important things.
Sent from my GT-I9500 using xda premium
ZeroInfinity said:
but this is totally different from what I have experienced.
From Windows, Internal Storage would have a folder called "storage" with another folder called "01" inside the storage folder. So "Internal Storage/storage/01/" if it was read on a Windows PC. inside the storage folder, there is just 1 folder called "01", nothing else. inside "01" folder, there are ONLY 2 .xml files which are the same as the 2 .xml files you would have by default in the root of your Internal and External Storage.
In short- Internel Storage has a folder called storage, inside storage has a folder called 01, inside 01 there are only 2 .xml files. The strange thing is, if it were linked to Internal/External Storage, why only 2 .xml files are visible in the 01 folder?
EDIT: When I tried to delete the storage folder (At the time I did not know that it was linked) Windows loading bar for deleting files did not move so I had to cancel it. Once cancelled, everything in my external/internal storage was wiped off. Thankfully, I recovered most of my lost pictures with Recuva
Click to expand...
Click to collapse
Yes, this is very strange. I remember when i did see this after i bought my phone i was thinking this must be an bug. Another thing, in root i also have a folder named: ext_card and it is the same as sdcard1 here. Sdcard1 is my microSD card i have, but why so many folder linked to the same folders.
At root i go to storage, inside i have folders: emulated, removable, sdcard0, sdcard1 usbdisk.
Inside emulated i have 0 and legacy. etc etc
All of them are linked and goes to the same internal card and external card,
gm007 said:
Not sure but I think this folder came somehow from the recovery maybe a bug.
I hope you didn't lost important things.
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
If it really is a bug, we need to know what did actually cause this to happen.
And yeah, Recuva was really useful for me
CiscoX said:
Yes, this is very strange. I remember when i did see this after i bought my phone i was thinking this must be an bug. Another thing, in root i also have a folder named: ext_card and it is the same as sdcard1 here. Sdcard1 is my microSD card i have, but why so many folder linked to the same folders.
At root i go to storage, inside i have folders: emulated, removable, sdcard0, sdcard1 usbdisk.
Inside emulated i have 0 and legacy. etc etc
All of them are linked and goes to the same internal card and external card,
Click to expand...
Click to collapse
Too many linked folders make it confusing, why would there be a linked folder visible in the Internal Storage though? this is what is really confusing me right now.
Need more reports if any one else has found this mysterious "storage" folder in their Internal Storage...
im not sure but if everyone with this folder are running 4.2.2 it is for the multiuser or multitasking feature of jellybean 4.2.2
skinsfanbdh said:
im not sure but if everyone with this folder are running 4.2.2 it is for the multiuser or multitasking feature of jellybean 4.2.2
Click to expand...
Click to collapse
Strange, this is the first time I have ever seen this. I only saw this folder today and I have been on custom roms based on stock xperia firmware android 4.2.2 for ages now... Why would it appear just today? I don't think multitasking will cause this to happen since it doesn't create any folders/files related to it (afaik).
I've had something like this happen where in emulated/0 (my main internal SD storage) there was another 0 folder that freaked out recoveries and such. I had the similar "can't delete from windows" thing, but using a in-recovery file manager I just deleted it, problem solved. tl;dr if you want to delete it and its causing problems delete it from recovery.
Sent from rooted carbon note 2, with the xda app.
shbaldw said:
I've had something like this happen where in emulated/0 (my main internal SD storage) there was another 0 folder that freaked out recoveries and such. I had the similar "can't delete from windows" thing, but using a in-recovery file manager I just deleted it, problem solved. tl;dr if you want to delete it and its causing problems delete it from recovery.
Sent from rooted carbon note 2, with the xda app.
Click to expand...
Click to collapse
exactly what im talking about. lots of threads in the htc one forum about it and being this device was released with 4.1.2(like the htc one) and has recently been updated to 4.2.2(like the htc one) maybe its the same thing, not saying it is because i dont know. just sounds like the same thing
shbaldw said:
I've had something like this happen where in emulated/0 (my main internal SD storage) there was another 0 folder that freaked out recoveries and such. I had the similar "can't delete from windows" thing, but using a in-recovery file manager I just deleted it, problem solved. tl;dr if you want to delete it and its causing problems delete it from recovery.
Sent from rooted carbon note 2, with the xda app.
Click to expand...
Click to collapse
Windows did not make any progress in deleting it, it was stuck on the Preparing to delete... window. Once I cancelled it because it took too long, everything from sd card/ internal storage was gone. All because of that storage folder inside my Internal Storage...
I know about the emulated/0 issue (From previous HTC One X Android 4.2.2 AOSP roms) but this seems to be completely different from it.
skinsfanbdh;44594029...and being this device was released with 4.1.2(like the htc one) and has recently been updated to 4.2.2(like the htc one)...[/QUOTE said:
hmm, I updated my phone from 4.1.2 to 4.2.2 prior to seeing this. This might be the cause. Anyone else have this happen?
Sent from rooted carbon note 2, with the xda app.
Click to expand...
Click to collapse
shbaldw said:
hmm, I updated my phone from 4.1.2 to 4.2.2 prior to seeing this. This might be the cause. Anyone else have this happen?
Sent from rooted carbon note 2, with the xda app.
Click to expand...
Click to collapse
I don't think it has anything to do with an upgraded android version. Like I said before, I have been on Android 4.2.2 a long time now (Upgraded when the firmware first came out) and I have never seen this folder before. I have just seen it yesterday. Another strange thing is that after I attempted to delete the storage folder, Everything was gone INCLUDING that storage folder. I haven't seen the storage folder after that happened. I'm going to go flash another rom and full wipe to see if the storage folder pops up again.
EDIT: Right, no there is no more storage folder in Internal Storage after a full wipe and formatted everything! Very strange indeed...
Wierd storage folder symlink inside internal storage!
ZeroInfinity said:
I don't think it has anything to do with an upgraded android version. Like I said before, I have been on Android 4.2.2 a long time now (Upgraded when the firmware first came out) and I have never seen this folder before. I have just seen it yesterday. Another strange thing is that after I attempted to delete the storage folder, Everything was gone INCLUDING that storage folder. I haven't seen the storage folder after that happened. I'm going to go flash another rom and full wipe to see if the storage folder pops up again.
EDIT: Right, no there is no more storage folder in Internal Storage after a full wipe and formatted everything! Very strange indeed...
Click to expand...
Click to collapse
I know this is a very old thread but I face the same issue in Android 5.1.1 now and I too deleted the folder named storage only to see that all the data from the sd card has vanished because of that. Any idea what caused this buggy symlink to be created?
All my data is now gone because I just deleted one folder inside my sdcard, and I didn't even think to backup anything since I didn't even dream that deleting a single folder will delete the parent folder! Again recuva was my friend but still I am not able to recover everything in internal storage, any suggestions on what to use to scan the internal storage?
anantharam said:
I know this is a very old thread but I face the same issue in Android 5.1.1 now and I too deleted the folder named storage only to see that all the data from the sd card has vanished because of that. Any idea what caused this buggy symlink to be created?
All my data is now gone because I just deleted one folder inside my sdcard, and I didn't even think to backup anything since I didn't even dream that deleting a single folder will delete the parent folder! Again recuva was my friend but still I am not able to recover everything in internal storage, any suggestions on what to use to scan the internal storage?
Click to expand...
Click to collapse
Did you upgrade to newer firmware using a zip? That's a common bug when upgrading via zip.
The only proper way is to backup ur entire internal storage and flash a full ftf. Then you will not have the annoying symlink.
langeveld024 said:
Did you upgrade to newer firmware using a zip? That's a common bug when upgrading via zip.
The only proper way is to backup ur entire internal storage and flash a full ftf. Then you will not have the annoying symlink.
Click to expand...
Click to collapse
I did do a factory reset before flashing a new firmware. Not sure what else I should do..
And as for the internal storage recovery, I followed these different guides but raw file using vhdtool and recuva did not give me any single file that was last present in my internal memory and even extundelete didn't return any single file that was in the internal storage, some of these tools return hundreds of text files and images that I had no idea was in my internal storage but none of them return me any of the hundreds of images and videos that I was sure were in my internal storage.
anantharam said:
I did do a factory reset before flashing a new firmware. Not sure what else I should do..
And as for the internal storage recovery, I followed these different guides but raw file using vhdtool and recuva did not give me any single file that was last present in my internal memory and even extundelete didn't return any single file that was in the internal storage, some of these tools return hundreds of text files and images that I had no idea was in my internal storage but none of them return me any of the hundreds of images and videos that I was sure were in my internal storage.
Click to expand...
Click to collapse
Yes but if you factory reset on 4.4.2 (for example) and then flash 5.0.2 fw via zip in recovery, you will get the annoying folder symlink.
The only way to upgrade to lollipop is by flashing a full ftf (which will wipe internal sd) after that you won't have the annoying symlink.
But you flashed zip instead of ftf and discovered the folder symlink which seemed not harmful to delete so you deleted it. Right?
Then there's no chance in getting the data (photos etc) back.
I was the same situation as you, twice, I tried every possibility to recover my photos but it ended up with nothing. Everything was gone.
On a mechanical harddrive, when you wiped data, the data will only be gone when the wiped sectors are overwritten (e.g. format harddrive, which overwrite with empty buffer).
As long as the wiped data in those sectors are not overwritten, you'll be able to recover almost all - if not all - data you deleted.
On flash memory instead, (such as ssd drives and internal storage of our phone) deleted data is immediately deleted.
(that's also one of the reasons on Android, you never have to defragment the internal sd, same story for an ssd)
I'm sorry for u to say but I'm afraid you're unfortunately lost the photos and there's no way to get it back.
But my advice to you is:
Never upgrade between android versions (e.g. 4.4 > 5.0) using a zip installable.
Only use full factory images (ftf), they will wipe internal sd in order to get correct mappings so backup everything before flashing.
Once u on a firmware, an update to the same firmware is allowed (e.g. from one 5.0.2 rom to another 5.0.2 rom).
I hope it helps u in the future.
Regards
langeveld024 said:
Yes but if you factory reset on 4.4.2 (for example) and then flash 5.0.2 fw via zip in recovery, you will get the annoying folder symlink.
The only way to upgrade to lollipop is by flashing a full ftf (which will wipe internal sd) after that you won't have the annoying symlink.
But you flashed zip instead of ftf and discovered the folder symlink which seemed not harmful to delete so you deleted it. Right?
Then there's no chance in getting the data (photos etc) back.
I was the same situation as you, twice, I tried every possibility to recover my photos but it ended up with nothing. Everything was gone.
On a mechanical harddrive, when you wiped data, the data will only be gone when the wiped sectors are overwritten (e.g. format harddrive, which overwrite with empty buffer).
As long as the wiped data in those sectors are not overwritten, you'll be able to recover almost all - if not all - data you deleted.
On flash memory instead, (such as ssd drives and internal storage of our phone) deleted data is immediately deleted.
(that's also one of the reasons on Android, you never have to defragment the internal sd, same story for an ssd)
I'm sorry for u to say but I'm afraid you're unfortunately lost the photos and there's no way to get it back.
But my advice to you is:
Never upgrade between android versions (e.g. 4.4 > 5.0) using a zip installable.
Only use full factory images (ftf), they will wipe internal sd in order to get correct mappings so backup everything before flashing.
Once u on a firmware, an update to the same firmware is allowed (e.g. from one 5.0.2 rom to another 5.0.2 rom).
I hope it helps u in the future.
Regards
Click to expand...
Click to collapse
Thank you very much for the detailed explanation, after wasting two whole days trying everything described anywhere in the internet for recovering data from internal storage, I have also learnt it the hard way that it won't be possible to recover my data. Anyways the good news is google photos had backed up most of my photos, so it would actually be the call recordings, whatsapp history and other documents that I would have to loose permanently.
langeveld024 said:
Never upgrade between android versions (e.g. 4.4 > 5.0) using a zip installable.
Click to expand...
Click to collapse
As for the upgrade issue, is this only for lollipop or any android version? I have never seen anything similar when I upgraded from 4.0 to 4.1 or 4.2 to 4.4 e.t.c. If I shouldn't use zip installable to upgrade android versions how else do I upgrade to kitkat or lollipop? I don't think there are any factory images published for lollipop for my phone since support for it ended long time ago.
ZeroInfinity said:
Today, I have experienced a very "odd" problem. I have just found out that there is a folder called "storage" visible in my Internal Storage.
When I thought that, since it was visible, it did not contain much useful files (Only 2 xml files I found which would be in both internal and external storage) so I deleted that folder and everything in my SD Card and Internal Storage vanished.
I found out that the "storage" folder had a link to both storage devices but the weird thing is, why was that there and why is it visible? I could of sworn that I have never seen that before on my Xperia Z...
Can anyone else see their "storage" folder in the internal storage or is it just me?
Click to expand...
Click to collapse
Am again reviving this old thread as today I deleted a folder named sdcard inside my oneplus 3's internal storage and lost everyrhing. Though I had never upgraded my phone using any zip file and always went with the OTA update
I also made a thread https://forum.xda-developers.com/oneplus-3/help/strange-t3537998
Dear community,
About a year after i really wanted to root my htc one mini 2, i decided I wanted to factory reset my phone.
So after this year I forgot everything i knew, and managed to wipe the whole OS...
I would really appreciate any hints that might help me to fix my phone again.
Info on where i'm standing with the problem:
1. I tried to find my stock ROM on this site and couldn't because under "firmware" i can only find 2.18.161.2, though mine is 2.18.166.1 - does this matter? It's the vodafone one, and they even have a nandroid backup for my version, but not the stock firmware.
2. I have TWRP installed, and the site tells me i need to have my bootloader locked to flash stock roms. I have no problem relocking or unlocking it, but in the relocked state, i can not access TWRP recovery and use the sideload feature to flash the rom. The phone always goes back to the bootloader screen and the title says " **security warning** ".
3. i would really like to get my phone back as close to it's stock state as possible.
I am kind of afraid of flashing the available stock firmware, as I don't know how to proceed from there without TWRP.
I read a lot about this topic, but i'm kind of loosing it right now...
Can some kind soul lend me their wisdom and help me out?
Would be much appreciated
mfG Montor
Hi,
You can either get put back everything to stock, as in flash stock recovery, relock the bootloader, get the available version from their site but the version number should be higher than the one already installed, however with S-Off you can flash any version.
Or
Leave everything as it is and perform a Nandroid restore.
What file are you getting from the website, is it RUU file, ROM, is it exe or zip ?, RUU will be beneficial to put back to complete stock with proper conditions met ?
WITH CUSTOM RECOVERY YOU CANNOT FLASH STOCK ROM.
TryllZ said:
Hi,
You can either get put back everything to stock, as in flash stock recovery, relock the bootloader, get the available version from their site but the version number should be higher than the one already installed, however with S-Off you can flash any version.
Or
Leave everything as it is and perform a Nandroid restore.
What file are you getting from the website, is it RUU file, ROM, is it exe or zip ?, RUU will be beneficial to put back to complete stock with proper conditions met ?
WITH CUSTOM RECOVERY YOU CANNOT FLASH STOCK ROM.
Click to expand...
Click to collapse
I would actually really like to put everything back to stock, because the reason for the root is somewhat gone now.
As already mentioned, I sadly can not find the stock recovery that i need.
I need the Vodafone x.xx.166.x format, and the closest i get would be the Vodafone x.xx.161.x format of the stock recovery.
What happens if i try to flash the available one? Do I brick my phone once again, or does it say something like "recovery version not matching device version" ?
Also, if by any chance the flash is successfull and the stock recovery x.xx.161.x is on my phone, how can i flash the stock firmware without TWRP?
Though I really like the idea of a more or less complete stock phone, I could totally go with the nandroid backup too.
The problem is, I already downloaded the files but as my OS is gone and i didn't turn on usb-debugging, i can not move a single file onto my device. (I assume that's the issue, because my adb push file /sdcard/TWRP/Backups didn't quite work...
Edit: Because you asked, I don't actually know what would be the best solution right now, but the only file fitting my device version is the nandroid backup, but there are RUUs for x.xx.161.x - which, as already mentioned, is the closest i can get to x.xx.166.x
Montor said:
I would actually really like to put everything back to stock, because the reason for the root is somewhat gone now.
As already mentioned, I sadly can not find the stock recovery that i need.
I need the Vodafone x.xx.166.x format, and the closest i get would be the Vodafone x.xx.161.x format of the stock recovery.
What happens if i try to flash the available one? Do I brick my phone once again, or does it say something like "recovery version not matching device version" ?
Also, if by any chance the flash is successfull and the stock recovery x.xx.161.x is on my phone, how can i flash the stock firmware without TWRP?
Though I really like the idea of a more or less complete stock phone, I could totally go with the nandroid backup too.
The problem is, I already downloaded the files but as my OS is gone and i didn't turn on usb-debugging, i can not move a single file onto my device. (I assume that's the issue, because my adb push file /sdcard/TWRP/Backups didn't quite work...
Edit: Because you asked, I don't actually know what would be the best solution right now, but the only file fitting my device version is the nandroid backup, but there are RUUs for x.xx.161.x - which, as already mentioned, is the closest i can get to x.xx.166.x
Click to expand...
Click to collapse
Here's how you can do it without developer option enabled.
- Make sure device is 100% charged, if you don't know how much charge exists, leave the device on charge for about 1-2 hours.
- Find an MMC of 4GB (Hoping your MMC slot is working)
- You will need Serial Number of your device for Nandroid restore, you can get it from the device box with IMEI stickers.
For RUU (zip file)
- Download the available RUU and rename it to 0P8BIMG.zip (I'm assuming its the same a normal HTC One Mini 2)
- Copy the file into the root of the MMC
- Insert MMC into device
- Boot up device and enter boot loader
- As the device enters bootloader it will automatically start flashing, if all conditions are met.
NB: I frankly can't remember if this will work with TWRP installed.
For Nandroid restore.
- THIS STEP NEEDS BE DONE FROM A PC, Extract all files from the Nandroid restore zip, connect the MMC to the PC.
- In the root folder of the MMC create a TWRP folder and inside it create a folder named BACKUPS and inside this create a folder named YOUR DEVICE SERIAL NUMBER (I haven't tested it with a different named folder so I don't know) inside this folder create a folder with the OS version number of your device and inside this folder place all extracted files.
- Put the MMC into the device.
- Enter TWRP and choose restore
- Locate the folder created in the earlier step, the TWRP Backup folder with files extracted in it.
- Let TWRP restore.
- As far as my knowledge goes it should work fine.
I will advise that you do a restore from Nandroid, because you have TWRP working this is the easiest method, to get the phone up and running then you can decide to go for RUU by enabling developer options and more.
I'm using a Nnadroid restore more than 6 months now, no problem whatsoever.
Good Luck
TryllZ said:
Here's how you can do it without developer option enabled.
- Make sure device is 100% charged, if you don't know how much charge exists, leave the device on charge for about 1-2 hours.
- Find an MMC of 4GB (Hoping your MMC slot is working)
- You will need Serial Number of your device for Nandroid restore, you can get it from the device box with IMEI stickers.
For Nandroid restore.
- THIS STEP NEEDS BE DONE FROM A PC, Extract all files from the Nandroid restore zip, connect the MMC to the PC.
- In the root folder of the MMC create a TWRP folder and inside it create a folder named BACKUPS and inside this create a folder named YOUR DEVICE SERIAL NUMBER (I haven't tested it with a different named folder so I don't know) inside this folder create a folder with the OS version number of your device and inside this folder place all extracted files.
- Put the MMC into the device.
- Enter TWRP and choose restore
- Locate the folder created in the earlier step, the TWRP Backup folder with files extracted in it.
- Let TWRP restore.
- As far as my knowledge goes it should work fine.
I will advise that you do a restore from Nandroid, because you have TWRP working this is the easiest method, to get the phone up and running then you can decide to go for RUU by enabling developer options and more.
I'm using a Nnadroid restore more than 6 months now, no problem whatsoever.
Good Luck
Click to expand...
Click to collapse
That is exactly where I'm stuck with my nandroid backup.
I just can't seem to find a way to push the folder with all the files onto my sd-card.
I tried with "adb push \myfolder /sdcard/TWRP/Backups/myphonesnumberthingy", but it gives me "Device not found" error.
The device is connected, and with "fastboot devices" it shows in the list.
Did I miss something important here?
All the drivers are installed, and I shouldn't be able to lock and unlock the bootloader if the device wasn't properly connected right?
Edit: Nevermind, it seems I can't read. I will try to put my sd-card out of my phone and connect it to my pc somehow
Montor said:
That is exactly where I'm stuck with my nandroid backup.
I just can't seem to find a way to push the folder with all the files onto my sd-card.
I tried with "adb push \myfolder /sdcard/TWRP/Backups/myphonesnumberthingy", but it gives me "Device not found" error.
The device is connected, and with "fastboot devices" it shows in the list.
Did I miss something important here?
All the drivers are installed, and I shouldn't be able to lock and unlock the bootloader if the device wasn't properly connected right?
Edit: Nevermind, it seems I can't read. I will try to put my sd-card out of my phone and connect it to my pc somehow
Click to expand...
Click to collapse
Use an MMC reader for working your MMC with a PC.
Your device connecting to your PC in the bootloader does not mean your commands will work, ADB works with device switched on, in bootloader its fastboot and NOT ADB.
TryllZ said:
Use an MMC reader for working your MMC with a PC.
Your device connecting to your PC in the bootloader does not mean your commands will work, ADB works with device switched on, in bootloader its fastboot and NOT ADB.
Click to expand...
Click to collapse
So i have an adapter for connecting the MMC to my PC.
I plug it in, and it shows me THIS.
Inside my recovery, if I use the file manager, I can't seem to access/find a single set of directories that looks like the one above...
Montor said:
So i have an adapter for connecting the MMC to my PC.
I plug it in, and it shows me THIS.
Inside my recovery, if I use the file manager, I can't seem to access/find a single set of directories that looks like the one above...
Click to expand...
Click to collapse
Have you extracted files from the Nandroid Backup zip and placed them into TWRP>Backups>Phone Serial Number>OS Version Number folder
Now, in TWRP choose Restore from the main screen, and locate the folder where your files are placed.
When in Restore, make sure you choose Storage: Micro SDCard at the top below Time, Battery and CPU.
TryllZ said:
Have you extracted files from the Nandroid Backup zip and placed them into TWRP>Backups>Phone Serial Number>OS Version Number folder
Now, in TWRP choose Restore from the main screen, and locate the folder where your files are placed.
When in Restore, make sure you choose Storage: Micro SDCard at the top below Time, Battery and CPU.
Click to expand...
Click to collapse
Yes i did extract the files in the zip, and placed them in TWRP/BACKUPS/serial/osversion.
But there is no way to locate it or access it.
When i open the file manager in TWRP, i see directories like "boot, cache, data, dev, devlog" etc, and also sdcard and external_sd.
External_sd is empty, and opening sdcard gives me only the directory created by my own nandroid backup, with the path /sdcard/TWRP/BACKUPS/HT533WR02324/2016-07-17--08-52-32.
Edit: Okay now we are getting closer to solving this.
I tried to change TWRP backup from internal storage to micro sdCard - but it shows (0MB) beside it.
Choosing it either way, does nothing. The checkbox internal storage stays checked.
I'm going to restart my phone and see if something changes...
Edit2: Did nothing, unfortunately.
If i remove the card, the box can't be checked.
If i insert it again and tap on it, it stays highlighted for about 4 seconds and then internal storage is still checked :/
Montor said:
Yes i did extract the files in the zip, and placed them in TWRP/BACKUPS/serial/osversion.
But there is no way to locate it or access it.
When i open the file manager in TWRP, i see directories like "boot, cache, data, dev, devlog" etc, and also sdcard and external_sd.
External_sd is empty, and opening sdcard gives me only the directory created by my own nandroid backup, with the path /sdcard/TWRP/BACKUPS/HT533WR02324/2016-07-17--08-52-32.
Edit: Okay now we are getting closer to solving this.
I tried to change TWRP backup from internal storage to micro sdCard - but it shows (0MB) beside it.
Choosing it either way, does nothing. The checkbox internal storage stays checked.
I'm going to restart my phone and see if something changes...
Edit2: Did nothing, unfortunately.
If i remove the card, the box can't be checked.
If i insert it again and tap on it, it stays highlighted for about 4 seconds and then internal storage is still checked :/
Click to expand...
Click to collapse
Firstly it shouldn't show you 0MB for SDCard, anyway, place the extracted Nandroid files in the /sdcard/TWRP/BACKUPS/HT533WR02324/2016-07-17--08-52-32 folder and then try again, if this folder is accessible then it should work.
MB: YOUR CONSTANT USE OF THE TERM FILE MANAGER IN TWRP IS GIVING ME AN IMPRESSION THAT YOU ARE ACCESSING THE FILE MANAGER IN TWRP WHERE AS YOU HAD TO PRESS THE RESTORE BUTTON FROM THE MAIN SCREEN, THE FILE MANAGER BUTTON IS DIFFERENT ALTOGETHER IN TWRP.
TryllZ said:
Firstly it shouldn't show you 0MB for SDCard, anyway, place the extracted Nandroid files in the /sdcard/TWRP/BACKUPS/HT533WR02324/2016-07-17--08-52-32 folder and then try again, if this folder is accessible then it should work.
MB: YOUR CONSTANT USE OF THE TERM FILE MANAGER IN TWRP IS GIVING ME AN IMPRESSION THAT YOU ARE ACCESSING THE FILE MANAGER IN TWRP WHERE AS YOU HAD TO PRESS THE RESTORE BUTTON FROM THE MAIN SCREEN, THE FILE MANAGER BUTTON IS DIFFERENT ALTOGETHER IN TWRP.
Click to expand...
Click to collapse
Oh it appears I didn't mention this.
The folder i CAN see, is inside the internal storage under "/sdcard/TWRP/BACKUPS/HT533WR02324/2016-07-17--08-52-32" - and I can't access the internal storage, i would have pushed the files if that was possible.
No no, I use the backup function to locate my nandroid backup files.
But with the backup function, I couldn't change directories and look for files so I used the file manager to do that.
The file manager doesn't allow me to change to sd card either way, so that doesn't work.
Edit:
The sd-card i have inside my phone right now is 64gb big - is it possible that this is too big to be recognized?
I also have a 32gb one, would that make a difference?
Montor said:
Oh it appears I didn't mention this.
The folder i CAN see, is inside the internal storage under "/sdcard/TWRP/BACKUPS/HT533WR02324/2016-07-17--08-52-32" - and I can't access the internal storage, i would have pushed the files if that was possible.
No no, I use the backup function to locate my nandroid backup files.
But with the backup function, I couldn't change directories and look for files so I used the file manager to do that.
The file manager doesn't allow me to change to sd card either way, so that doesn't work.
Edit:
The sd-card i have inside my phone right now is 64gb big - is it possible that this is too big to be recognized?
I also have a 32gb one, would that make a difference?
Click to expand...
Click to collapse
As per spec, this device supports 64GB too but I myself use a 32GB one, so yes you can try that and again you will need to access TWRP restore through the RESTORE button in TWRP main screen and NOT BACKUP button.
What you can do is copy the /sdcard/TWRP/BACKUPS/HT533WR02324/2016-07-17--08-52-32 folder into you SDCard TWRP folder and place the extracted files in this folder and try a restore.
TryllZ said:
As per spec, this device supports 64GB too but I myself use a 32GB one, so yes you can try that and again you will need to access TWRP restore through the RESTORE button in TWRP main screen and NOT BACKUP button.
What you can do is copy the /sdcard/TWRP/BACKUPS/HT533WR02324/2016-07-17--08-52-32 folder into you SDCard TWRP folder and place the extracted files in this folder and try a restore.
Click to expand...
Click to collapse
Okay it seems my 32gb one is broken, it's showing up but not as a mass storage.
Well if I could access the sd card with twrp at all, that would really help me - but I can't.
Backup botton and restore button behave the same when choosing the Micro SDcard (0MB).
And with the file manager, accessing the sd card gives me an empty directory...
Edit: Googling this problem tells me I need to format my card, as TWRP doesn't recognize it.
I read FAT32 somewhere, I read exFAT somewhere, what format does TWRP work with?
Montor said:
Okay it seems my 32gb one is broken, it's showing up but not as a mass storage.
Well if I could access the sd card with twrp at all, that would really help me - but I can't.
Backup botton and restore button behave the same when choosing the Micro SDcard (0MB).
And with the file manager, accessing the sd card gives me an empty directory...
Edit: Googling this problem tells me I need to format my card, as TWRP doesn't recognize it.
I read FAT32 somewhere, I read exFAT somewhere, what format does TWRP work with?
Click to expand...
Click to collapse
First can I know if you can see any file/folder in SD when accessing it through Restore in TWRP ?
Format it as exFat, hopefully it should work..
You mentioned its not showing as Mass Storage, what is it showing up as ?
TryllZ said:
First can I know if you can see any file/folder in SD when accessing it through Restore in TWRP ?
Format it as exFat, hopefully it should work..
Click to expand...
Click to collapse
First, through restore I can't navigate to other folders at all.
All I can do there, is tapping on Internal storage and choosing micro SDcard - which doesn't work.
It's like TWRP knows there is a sd card in my phone, but somehow can't access it.
That's why I assume it's due to it's formatting.
Switching folders/directories is only possible with the file manager with the advanced button - but this only shows me two things.
1. External_sd --> shows me an empty directory
2. sdcard --> shows me the folder where TWRP created the backup folder when I did the backup myself. (I assume that's the internal storage because under the restore button, this is the only thing that i shows up)
I read somewhere, that exFAT is only recognized by TWRP if you have a newer version of the recovery installed.
I don't know exactly but the version i'm using is definitely on of the first versions that came out.
Also, I checked my SD-card on my laptop, and apparently it allready is exFAT.
Edit: I was talking about the 32gb card not showing up.
I don't think it really matters, but my description wasn't very accurate.
The SD-card (32gb) is shown as the SD-card like it should, but the PC doesn't show any kind of used/free space bar underneath it.
Also, opening it gives a message like "There is no card connected"
Montor said:
First, through restore I can't navigate to other folders at all.
All I can do there, is tapping on Internal storage and choosing micro SDcard - which doesn't work.
It's like TWRP knows there is a sd card in my phone, but somehow can't access it.
That's why I assume it's due to it's formatting.
Switching folders/directories is only possible with the file manager with the advanced button - but this only shows me two things.
1. External_sd --> shows me an empty directory
2. sdcard --> shows me the folder where TWRP created the backup folder when I did the backup myself. (I assume that's the internal storage because under the restore button, this is the only thing that i shows up)
I read somewhere, that exFAT is only recognized by TWRP if you have a newer version of the recovery installed.
I don't know exactly but the version i'm using is definitely on of the first versions that came out.
Also, I checked my SD-card on my laptop, and apparently it allready is exFAT.
Edit: I was talking about the 32gb card not showing up.
I don't think it really matters, but my description wasn't very accurate.
The SD-card (32gb) is shown as the SD-card like it should, but the PC doesn't show any kind of used/free space bar underneath it.
Also, opening it gives a message like "There is no card connected"
Click to expand...
Click to collapse
The SDCard not showing free space bars is windows could possibly mean SDCard error.
FAT, FAT32 and exFAT work for Android so yes if you format it in any of these it ought to work. exFAT format is most commonly used in mobile devices in terms of SDCard.
Card disconnecting in Windows, I am guessing your card is having I/O issues, what this means is that if you try and format it and the MMC disconnects during the format process there is a chance it will be permanently damaged.
What you can do is just use Quick Format, this will not check for any errors, however if there is any sector errors in the MMC, flasing through TWRP could cause unexpected problems if that sector is accessed.
Advisably get a working 4GB SDcard to avoid any hiccups.
TryllZ said:
The SDCard not showing free space bars is windows could possibly mean SDCard error.
FAT, FAT32 and exFAT work for Android so yes if you format it in any of these it ought to work. exFAT format is most commonly used in mobile devices in terms of SDCard.
Card disconnecting in Windows, I am guessing your card is having I/O issues, what this means is that if you try and format it and the MMC disconnects during the format process there is a chance it will be permanently damaged.
What you can do is just use Quick Format, this will not check for any errors, however if there is any sector errors in the MMC, flasing through TWRP could cause unexpected problems if that sector is accessed.
Advisably get a working 4GB SDcard to avoid any hiccups.
Click to expand...
Click to collapse
I have the 64gb one i was always using, and the not working 32gb one.
Both are exFat.
I just wanted to know if it might work formatting the 64gb one
Edit: Concerning formatting, this is the thread I was referring to.
Montor said:
I have the 64gb one i was always using, and the not working 32gb one.
Both are exFat.
I just wanted to know if it might work formatting the 64gb one
Edit: Concerning formatting, this is the thread I was referring to.
Click to expand...
Click to collapse
The device supports 64GB and so does TWRP, now concerning your SDCard, yes it would work (as long as its hardware-error free)..
I'm using TWRP version 2.8.5.0 and my SDCard is exFAT and works fine with TWRP..could be that older versions of TWRP might not support exFAT but I personally can't confirm that as which is the older version that you are using.
TryllZ said:
The device supports 64GB and so does TWRP, now concerning your SDCard, yes it would work (as long as its hardware-error free)..
I'm using TWRP version 2.8.5.0 and my SDCard is exFAT and works fine with TWRP..could be that older versions of TWRP might not support exFAT but I personally can't confirm that as which is the older version that you are using.
Click to expand...
Click to collapse
Update!
I realized, it's probably really the 64gb sd card, that's the issue here.
I took the 4gb one out of my fathers phone - bam.
TWRP recognized it immediately and restore is in progress!!!
Will keep updating!
Edit: IT F*ING WORKED!
Thank you SO much for your help!!!
Is there any way I can give you somethign in return?
Montor said:
Update!
I realized, it's probably really the 64gb sd card, that's the issue here.
I took the 4gb one out of my fathers phone - bam.
TWRP recognized it immediately and restore is in progress!!!
Will keep updating!
Edit: IT F*ING WORKED!
Thank you SO much for your help!!!
Is there any way I can give you somethign in return?
Click to expand...
Click to collapse
Great...:good::good::good:
Frankly I never imagined it could be the 64GB, I was purely under the assumption TWRP would accept 64GB MMC, anyway I lacked that information but now I know.
Nope, its working now is more than enough for me.