I originally installed Lollipop on my phone on 5/14 using Santod's Stock Rooted ROM. A couple of days later I reverted back to my NANDROID backup of Kit Kat. Yesterday I reflashed Santod's Lollipop ROM and now I'm "missing" several directories on my internal storage/SDCard and some files have older time stamps.
I know the "missing" directories are actually there because when I try to copy the files back to the phone I get an error message stating that the files already exist and then the copy fails with an error.
I'm using Root Explorer and have selected to show all hidden files.
Is this some strange permissions issue? Should I just reflash to Lollipop and then wipe the internal storage and recopy everything?
Any help and/or insights are greatly appreciated.
Try the fix from the following post: http://forum.xda-developers.com/showpost.php?p=57288835&postcount=2
Thanks for the link, jabrown84, I'll give it a try.
What's strange is that the files are missing while viewing on the phone and on the PC. However if I revert back to Kit Kat or use the File Manager from within TWRP I can see everything.
I may just wipe the entire phone (including internal storage). A deep cleaning never hurt anyone before.
Worked like a charm!
Related
I was wondering whether anyone has experienced the following:
I was on Team Sonic-Free GS3 v.3.0.0. Everything was setup the way i wanted it. I booted into Recovery and created a Restore point.
Right after, I did the following:
- Wipe Data/Factory Reset
- Wipe Cache partition
- Wipe Dalvik Cache
- Format /System
- Format /Data
- Format /Cache
I installed the latest Nightly from Cyanogenmod 10 (12.26). Initially I used an older version of gapps-jb but immediately flashed the correct one. Everything went fine. The system loaded and nothing seemed wrong. After some messing around I noticed it was a big sluggish on my phone. So I decided to restore the phone back to its original setting.
When I went to backup/restore and hit the Restore option, it told me that I had no recovery points! :crying::crying: At this point I started freaking out.
I tried to see if I could flash from the SDCard and I noticed one thing. This was in order to get to the main folder of the SDCard i needed to enter a folder named "0". All the files were there including my CMW recover file. Although it was on the card the recovery option was unable to see it.
After this I decided to do the following. I clean swiped again and installed the Free GS3 version i had on the SDCard already. I booted into the system and saw that the folder "0" was there but also in the main directory there were still folders. In the main portion of the card i loaded my copy of the recovery.
I went back into recovery and and tried again. The restore file was there! :good::good: I was able to recovery my original setup. Unfortunately, all of my pictures and music were still located within the newly created "0" folder. I just copied those back.
Can anyone explain why this happened? I'm very curious!
I do apologize if this has been answered before. I have done a search and have only found scenarios for the SDcard is not seen as mounted. (also dont know if the icons mean anything for the post)
*Update - Folder "0" cannot be deleted. Root explorer says "failed" and Windows Explorer says "Cannot delete 0: THe storage is write-protected". Any ideas on this also?
solidhound said:
I was wondering whether anyone has experienced the following:
I was on Team Sonic-Free GS3 v.3.0.0. Everything was setup the way i wanted it. I booted into Recovery and created a Restore point.
Right after, I did the following:
- Wipe Data/Factory Reset
- Wipe Cache partition
- Wipe Dalvik Cache
- Format /System
- Format /Data
- Format /Cache
I installed the latest Nightly from Cyanogenmod 10 (12.26). Initially I used an older version of gapps-jb but immediately flashed the correct one. Everything went fine. The system loaded and nothing seemed wrong. After some messing around I noticed it was a big sluggish on my phone. So I decided to restore the phone back to its original setting.
When I went to backup/restore and hit the Restore option, it told me that I had no recovery points! :crying::crying: At this point I started freaking out.
I tried to see if I could flash from the SDCard and I noticed one thing. This was in order to get to the main folder of the SDCard i needed to enter a folder named "0". All the files were there including my CMW recover file. Although it was on the card the recovery option was unable to see it.
After this I decided to do the following. I clean swiped again and installed the Free GS3 version i had on the SDCard already. I booted into the system and saw that the folder "0" was there but also in the main directory there were still folders. In the main portion of the card i loaded my copy of the recovery.
I went back into recovery and and tried again. The restore file was there! :good::good: I was able to recovery my original setup. Unfortunately, all of my pictures and music were still located within the newly created "0" folder. I just copied those back.
Can anyone explain why this happened? I'm very curious!
I do apologize if this has been answered before. I have done a search and have only found scenarios for the SDcard is not seen as mounted. (also dont know if the icons mean anything for the post)
*Update - Folder "0" cannot be deleted. Root explorer says "failed" and Windows Explorer says "Cannot delete 0: THe storage is write-protected". Any ideas on this also?
Click to expand...
Click to collapse
Was it registering a different recovery version when you flashed CM10 from the FreeGS? If so that would be why it didn't register the backup that you made. (I had this issue or similar to on my Touch) flashed a different rom that used CVM 5.something.. and original was a newer version. Caused me some issues. As for the folder being write protected. Try using root explorer, mount as R/W and then try to delete from there. Just ensure you have everything out of it you want tho.
milky1112 said:
Was it registering a different recovery version when you flashed CM10 from the FreeGS? If so that would be why it didn't register the backup that you made. (I had this issue or similar to on my Touch) flashed a different rom that used CVM 5.something.. and original was a newer version. Caused me some issues. As for the folder being write protected. Try using root explorer, mount as R/W and then try to delete from there. Just ensure you have everything out of it you want tho.
Click to expand...
Click to collapse
hey milky1112.
Thanks for reading and providing your input!
I actually used the sames recovery when creating and trying to restore. That's the odd part. I did recently flash the newer version within the old recovery. Do you think that may have been it? Although the new one was used to create a nandroid and restore it.
I just tried deleting using Root Explorer and the same result. It's not a big deal since its only 69mb but it's quite annoying knowing I can't.
thanks again!
solidhound said:
hey milky1112.
Thanks for reading and providing your input!
I actually used the sames recovery when creating and trying to restore. That's the odd part. I did recently flash the newer version within the old recovery. Do you think that may have been it? Although the new one was used to create a nandroid and restore it.
I just tried deleting using Root Explorer and the same result. It's not a big deal since its only 69mb but it's quite annoying knowing I can't.
thanks again!
Click to expand...
Click to collapse
That is very possible, still odd that it will not let you delete even with R/W permissions set. But as long as everything is working.. Then i wouldn't fuss too much
The new rom you installed is on 4.2 not 4.1 which is probably what you had originally. The new 4.2 releases by Google move everything into the O folder its part of the new Android set up to dual boot devices. If the recovery is not set up to correct for this your phone will not recognize where the files have been moved to. In my understanding only TWRP is corrected to do this, we'll at least in the Gnex it is. Anyone on Cwm has had issues with this. The fix is to copy and paste your files back into its original location. You can not delete O folder it is an essential part now of your system and it's where it will reference everything from and originals must remain.
Transmitted with a portable device using Xparent Blue Tapatalk 2
edfunkycold said:
The new rom you installed is on 4.2 not 4.1 which is probably what you had originally. The new 4.2 releases by Google move everything into the O folder its part of the new Android set up to dual boot devices. If the recovery is not set up to correct for this your phone will not recognize where the files have been moved to. In my understanding only TWRP is corrected to do this, we'll at least in the Gnex it is. Anyone on Cwm has had issues with this. The fix is to copy and paste your files back into its original location. You can not delete O folder it is an essential part now of your system and it's where it will reference everything from and originals must remain.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Thanks for clarification Ed. I've been on TPR for a while so haven't flashed any 4.2 roms.
edfunkycold said:
The new rom you installed is on 4.2 not 4.1 which is probably what you had originally. The new 4.2 releases by Google move everything into the O folder its part of the new Android set up to dual boot devices. If the recovery is not set up to correct for this your phone will not recognize where the files have been moved to. In my understanding only TWRP is corrected to do this, we'll at least in the Gnex it is. Anyone on Cwm has had issues with this. The fix is to copy and paste your files back into its original location. You can not delete O folder it is an essential part now of your system and it's where it will reference everything from and originals must remain.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
hey edfunkycold,
thanks a ton for the response and clarification! i was thinking about swapping recoveries but i already reverted back to the original nandroid image i had at that point.
and you are correct. i was on 4.1 and not 4.2. i didn't know such changes were made but its great to see dual boot is coming up.
i will make sure to THANK both responses once i reach 10 posts. i'm trying hard to participate in these forums but haven't had time until recently.
I've found myself stuck trying to flash a ROM. I'm a newbie, this was my first attempt at something like this, I though I read enough about the process but I guess I screwed up something. I will try to be to the point.
Phone: Samsung Galaxy S3 AT&T i747
Rooted phone with Casual, installed ROM Toolbox and purchased the pro upgrade.
installed TWRP 2.5 and made a nandroid backup, the only place this backup existed was in internal storage.
used ROM toolbox to backup user apps and user data
selected cyanogenmod 10.1 RC5 from within ROM Toolbox and there was a requester for gapps and a checked the box for that also. When the DL was complete I installed the ROM queue with those two items and I checked the boxes Wipe Data & Cache and Wipe dalvic-cache.
Phone went to recovery mode (i guess) and appeared to clear the memory and load the new rom, the phone rebooted and I got the cyanogenmod boot screen but then it went to a requester saying:
Unfortunately , the process com.google.process.gapps has stopped.
When you hit ok you get:
Unfortunately, setup wizard has stopped.
this requester never goes away, just keeps popping up when you hit ok.
So I removed the battery and booted the phone in recovery mode and try to restore but the restore nandroid file in not shown. If I hit the center button in the restore window it says "updating partition details" but never returns.
Whenever you power it up normally now you end up in this gapps loop.
My searching suggested I may have tried to install the wrong version of google apps somehow. What are my options for trying to recover from this? Does my backup still exist somewhere?
If process.gapps is your only warning you can try to reflash the gapps zip from here. http://goo.im/gapps/gapps-jb-20130301-signed.zip If this does not fix your problem, you will have to head deeper into the rabbit hold
You can look for your back with a file explorer. Should be in sdcard/TWRP/BACKUPS/******** (random number). If you dont see them here, check your ext-sd in the same location. If you don't see them, they are gone. Do a Nandroid backup now just to be sure you have one. You should chose to back it up to external in TWRP. As for your FC problem, it would appear that you have not wiped fully. You will likely need to factory reset. the problem is this will remove everything. Titanium back up is a great product for situations like this. If you have used it, you can transfer your backup from the internal storage while connected to your pc. Also copy your DCIM folder as it will contain your photos. This is why you will need to do another Nandroid, because worst case scenario, you can just restore this one.
Thanks for the reply. I will try to reflash the gapps file from the external as soon I can download it, the site is having some trouble right now. I made another Nandroid of the phones current state and stored it to external. I did also have Titanium backup and had backups of the whole system with it. Unfortunately they are also only on the internal storage.
Re-installing the gapps zip file off the extSD from within TWRP did the trick. All the data and backups I created are also still there and are now backed up in several places.
Something that compounded the problem was the 64GB sd card I have for the phone. I was not able to mount it on either of my linux mint machines or an XP machine. Some oddness with the exFAT file system on it, I used a 4GB card I had laying around and it worked fine.
Thank you for the help, the phone is now running CM which is what I wanted and I learned a few things too.
theaxis695 said:
Re-installing the gapps zip file off the extSD from within TWRP did the trick. All the data and backups I created are also still there and are now backed up in several places.
Something that compounded the problem was the 64GB sd card I have for the phone. I was not able to mount it on either of my linux mint machines or an XP machine. Some oddness with the exFAT file system on it, I used a 4GB card I had laying around and it worked fine.
Thank you for the help, the phone is now running CM which is what I wanted and I learned a few things too.
Click to expand...
Click to collapse
I just bought a 64GB card as well. You may be having troubles mounting it due to a partition that comes factory in the SD. If this is the case, you can look at post #57 on the following page http://forum.xda-developers.com/showthread.php?t=1915385&page=6
It helped me tremendously.
Hi, I just installed CM10.1.0 on my GS3 using CWM recovery from the device after rooting. I'm thinking this may be part of the problem, since it didn't seem like it entirely formatted the internal SD, but I'm not entirely certain. View the first attachment to see what I'm talking about (btw, Misc. got cut off but says 7.07MB).
As you can see, my total space is 12.05GB and it's saying that only 2.38GB is available, though the status bar and storage categories don't support that information (adversely, only about 2 gigs should be used). When connected to my laptop, it says that all this space is being used (view second attachment).
Am I correct about the way I installed it being a problem? Or, is there really phantom storage on my device? It seems that the phantom storage would be coming from the \data folder, but I'm unable to find any problems via SD Maid.
If it's a problem with the way I installed it, I was unable to get Heimdall running properly (on my Windows 7 laptop) with the instructions provided by Cyanogenmod or several threads on XDA, so if anybody could help me get it installed properly I'd be grateful!
Edit: I also flashed Gapps from ROM Manager w/ CWM Recovery after I finished CM10.1.0 installation. Could this be part of the problem?
i'm assuming you came from stock firmware. make sure you have everything backup up and follow the wipe procedures outlined in this thread: http://forum.xda-developers.com/showthread.php?t=2179330 before flashing the ROM and gapps again. cheers
xBeerdroiDx said:
i'm assuming you came from stock firmware. make sure you have everything backup up and follow the wipe procedures outlined in this thread: http://forum.xda-developers.com/showthread.php?t=2179330 before flashing the ROM and gapps again. cheers
Click to expand...
Click to collapse
Ok, so you're suggesting to flash from recovery so everything is wiped properly and CM10.1.0/Gapps will be installed at the same time? The first time I tried this, I thought I had put the CM zip file in but couldn't locate it, so I flashed stock/rooted and did it through ROM manager. If you really think that will help, I'll give it a try.
I don't think the wipe recovery actually wipes user's data. Just the applications and settings.
I've noticed that when I wiped my GS3 after I initially installed CM10.1 and even yesterday when I installed LiquidSmooth and did a wipe afterwards it created a folder called 0 and moved everything in there instead.
When I had the phone connected to the computer. Folder 0 properties would show there is nothing inside. but when I browse into it. I can see that my wallpapers, ringtones, music files were still there. So I cut and pasted it to the main \sdcard folder and deleted the folder 0.
Perhaps the same thing has happened to you? Use a file browser on your phone or connect it to the computer and see if you see the 0 folder. if you do your previous data files might be the reason why your phone reports low storage available.
1. when you're changing android versions, for example from 4.1.1 to 4.2, it is always recommended to do a full wipe before flashing.
2. when you're changing from one 4.2 ROM to another 4.2 ROM, you will also often see this multiple 0 folder issue when not fully wiping.
3. never flash a rom from anything other than a custom recovery - TWRP or CWM
please understand what you're doing before you continue.
Espada04 said:
I don't think the wipe recovery actually wipes user's data. Just the applications and settings.
I've noticed that when I wiped my GS3 after I initially installed CM10.1 and even yesterday when I installed LiquidSmooth and did a wipe afterwards it created a folder called 0 and moved everything in there instead.
When I had the phone connected to the computer. Folder 0 properties would show there is nothing inside. but when I browse into it. I can see that my wallpapers, ringtones, music files were still there. So I cut and pasted it to the main \sdcard folder and deleted the folder 0.
Perhaps the same thing has happened to you? Use a file browser on your phone or connect it to the computer and see if you see the 0 folder. if you do your previous data files might be the reason why your phone reports low storage available.
Click to expand...
Click to collapse
xBeerdroiDx is right that I was flashing from a stock rom and I'm definitely not having the same problem as you, but if I were you, I'd use the link he posted above to make sure you were fully wiping before installing CM and Gapps. Looks like I'm going to have to do the same thing to fix my own problem though.
xBeerdroiDx said:
i'm assuming you came from stock firmware. make sure you have everything backup up and follow the wipe procedures outlined in this thread: http://forum.xda-developers.com/showthread.php?t=2179330 before flashing the ROM and gapps again. cheers
Click to expand...
Click to collapse
I followed your instructions and it didn't work... still shows 2.75GB available after reboot. Any other ideas?
For anyone who may be experiencing this problem, I fixed it by following xBeerdroiDx's instructions and then by formatting sdcard. Be sure to put the rom and Gapps on an external sd and remove from the device before booting into recovery. After all that's stuff wiped, you may put the external sd back in and load the zip files from the external sd.
I have flashed a CM11 unsuccesfully and today sucessfully flashed AOSP Kitkat. I have found the file system is screwing with my sdcard. I have emulated/o, emulated/legacy, SD0, and SD1. I always run a Nandroid before flashing and that completely disappeared from my internal storage, it was not in any of the directories.
Not only that but after I booted up only a few of my apps were restored by Google restore. I installed Titanium and it had nothing. It informed me that the phone ID had changed and asked me if I wanted to change back for compatibility. I let it do it and ended up with a Titanium backup from a couple phones ago.
What the hell is going on and what is the best way to deal with the storage file system after a flash when one has these extra directories? Can I merge? I'm afraid to delete one because I do not know that it will not have some data I might need.
Thanks
So here's what I am working with. A Rooted, S-OFF Verizon M7. The ROM I have been using up until now is here: http://forum.xda-developers.com/showthread.php?t=2485319. I have been running v6.22.605.4 and everything has been working well. Well, sorta. There was something eating up the storage space. To the point I only had 1GB of storage left and had no music, pictures, downloads, or anything personal on the SD. Yet it was shown as full and no file manager could show me what was taking up space. I figured some app had gone off the reservation and since it had been a while since my last reset, a refresh would be good to do anyway. I backed everything up and used TWRP to do a factory reset. That's when the trouble began.
Once I was booted back into the system and accounts were all set up I noticed my files and folders were nowhere to be found. I used ES and the HTC file manager and both show used space on the SD partition but there were no files or folders visible. Odd. So I went back into TWRP and used the file explorer there. Lo and behold, everything was still there in the sdcard folder. Files, folders, everything. Weird. So I thought I would start over from a clean device. I wiped the cache, dalvik, and data partitions, including the SD. After that was complete and verified I pushed over the 6.22.605.6 ROM, did a firmware upgrade, and flashed the ROM. Completely started over, good to go.
Well, not quite. The problem is still there. TWRP shows the usual folders on the SD that must have been created when the ROM first set up. "Pictures", "Music", etc. But when booted into the system, nothing. Oh, and now I have the apps System UI, Package Access Manager, and a host of others crashing upon startup. I tried downgrading and flashing 6.22.605.4 like I had before and still have the same issues with storage and app crashes. Which leads me to believe there is something derped in the underlying system but I can't figure out what it is.
Any help I can get is greatly appreciated!
armorer243 said:
So here's what I am working with. A Rooted, S-OFF Verizon M7. The ROM I have been using up until now is here: http://forum.xda-developers.com/showthread.php?t=2485319. I have been running v6.22.605.4 and everything has been working well. Well, sorta. There was something eating up the storage space. To the point I only had 1GB of storage left and had no music, pictures, downloads, or anything personal on the SD. Yet it was shown as full and no file manager could show me what was taking up space. I figured some app had gone off the reservation and since it had been a while since my last reset, a refresh would be good to do anyway. I backed everything up and used TWRP to do a factory reset. That's when the trouble began.
Once I was booted back into the system and accounts were all set up I noticed my files and folders were nowhere to be found. I used ES and the HTC file manager and both show used space on the SD partition but there were no files or folders visible. Odd. So I went back into TWRP and used the file explorer there. Lo and behold, everything was still there in the sdcard folder. Files, folders, everything. Weird. So I thought I would start over from a clean device. I wiped the cache, dalvik, and data partitions, including the SD. After that was complete and verified I pushed over the 6.22.605.6 ROM, did a firmware upgrade, and flashed the ROM. Completely started over, good to go.
Well, not quite. The problem is still there. TWRP shows the usual folders on the SD that must have been created when the ROM first set up. "Pictures", "Music", etc. But when booted into the system, nothing. Oh, and now I have the apps System UI, Package Access Manager, and a host of others crashing upon startup. I tried downgrading and flashing 6.22.605.4 like I had before and still have the same issues with storage and app crashes. Which leads me to believe there is something derped in the underlying system but I can't figure out what it is.
Any help I can get is greatly appreciated!
Click to expand...
Click to collapse
Copy everything off while in twrp. Format SD (internal). Copy back files. Continue on.
Sent from my SM-T810 using Tapatalk
dottat said:
Copy everything off while in twrp. Format SD (internal). Copy back files. Continue on.
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. Unfortunately it didn't work. I did a total format and it didn't seem to help. I was able to get it back by using a RUU and then adding TWRP back in. Just finished about an hour ago and everything seems to be coming back as expected.
Thank you for the help!