[Q] Where did my files go? - Nexus 7 Q&A, Help & Troubleshooting

Long story short, I cleared userdata and rebooted to a fresh install of android 4.3, and my own files aren't visible anymore. I know they are still there as internal storage reports much less space than 16GB (it reports 6GB to be exact).
Is there any way to recover those files?

Similar experience
Out of curiosity, what ROM were you coming from before attempting to go back to stock. I had the same experience when resetting from ParanoidAndroid. My fix is here: http://forum.xda-developers.com/showpost.php?p=47254050&postcount=2

Related

4.2.2 OTA update, now my 32GB Nexus 7 has 6GB free

Not sure how this happened, but I had ~27GB free until the OTA update to 4.2.2. Clockworkmod correctly detected that SU and it were trying to be replaced, so I still have root. But now I have only 6GB free! Sounds like it might be an issue with what image was applied, but I had no choice in the matter.
Any way to get my space back without flashing a stock image?
Apparently not. Had to download factory image. But at least I have 27GB free again.
Be careful with the OTA upgrade!
i did my upgrade via factory image but got the same issue! now i dont know what to do :/
EDIT: reflashed system image in toolkit and all good. shame i had to lose my data!
This happens even when flashing roms customs.
I identified this problem at the beginning that I had the Nexus 7. It can occur on 8, 16 and 32GB.
I have not found the reason, but must complete a minimum internal storage. If you flash the empty shelf or very stingy, this problem can occur.
I suggest you fill in the data storage, movies, music, etc. and try once again a complete restauration using a toolkit.
It can also work without completing the internal storage but it will then try several.
Why a toolkit? because with fastboot, I never succeeded to get my total storage.
This problem has existed since 4.1.1.
You have been warned for your next flash.
I have basic Android programming skills. Would an application that automatically filled "most" of the disk prior to upgrade, then deleted it post-upgrade, be of any value?
We'd have to define "most" since there's probably some overhead needed to do the upgrade, but my guess if is you take a bit more than the size of the next lowest model (e.g. 9GB of the 16GB model) it's enough to trigger the behavior you say.

[Q] The phone thinks my 32GB G2 is 16 GB. How to solve?

This is interesting. Not sure if it'is normal but after restoring my phone so I could access the full memory I played with G3 ROM and decided to go back to stock flashing the same 32GB ROM I have previously used to restore my phone. After I flashed the *.kdz file using LG Flash Tool and rebooted the phone I was back to the 10Gb of storage available. I obviously managed to restore it back to the full 24.80 GB now but I am not quite sure why this is happening. I am using European German) ROM.
Has anyone else experienced this? If so do you know whether this is normal and if there is a fix to permanently restore full memory? Or does it have something to do with the ROM itself?
After successfully flashing the .kdz, do you do a factory reset? That should solve most of the issues. I doubt your partitions are messed up, but that could also be the cause.

[Q] Apps can't write to SD card after using CM and then going back to recovery.

I've been trying to fix this issue for about 4 hours now, so this is my last resort.
A while ago I rooted and installed CM on my phone since my galaxy s4 was bought from dubai so it didn't receive the regular android updates (it's still 4.3). I used CM for a while but realised that my phone was overheating a lot and battery life was a lot worse. So I decided to go back to my recovery.
After going back to my recovery everything worked fine but apps can no longer save to SD card, I can't recieve pictures, download podcasts or use anything that requires SD card.
I'm not very familiar with android coding but I tried using ADB and I just got confused, I also checked permissions in platform.xml and I've tried that solution and it still doesn't work. I've tied unmounting and mounting the sdcard I've tried formatting it in the phone itself and formatting it via recovery. I have no idea what else to do.
It's standard in the later version of Android. So it has nothing to do with CM or custom roms.
Google for "i9505 write sd kitkat' and you find plenty of guides how to solve it.
Why didn't you just download the latest version of CM and use that?

Increasing system storage with every update?

I tried searching for awhile and couldn't find anything too related to the exact question. Seems like with every update coming out storage shows the system taking up 1gb more than previous. Its as if it doesn't delete previous android versions. Its gone from 2.5gb few updates ago to now 5.6gb but the android updates are no more than 1gb. Its about when I started to notice this, 3 big updates ago all being around 1gb each.
My phone is completely stock, would a full stock flash delete everything and start the phone over? Also reading the general topic a few different methods mostly for unlocked bootloader., which one is the best for a locked bootloader? I was wanting to do this anyway because I have other unrelated issues with the phone such as gboard constantly crashing and photos not storing properly/overlapping eachother in memory that seems to happen with every update no matter what.
MadBullBunny said:
I tried searching for awhile and couldn't find anything too related to the exact question. Seems like with every update coming out storage shows the system taking up 1gb more than previous. Its as if it doesn't delete previous android versions. Its gone from 2.5gb few updates ago to now 5.6gb but the android updates are no more than 1gb. Its about when I started to notice this, 3 big updates ago all being around 1gb each.
My phone is completely stock, would a full stock flash delete everything and start the phone over? Also reading the general topic a few different methods mostly for unlocked bootloader., which one is the best for a locked bootloader? I was wanting to do this anyway because I have other unrelated issues with the phone such as gboard constantly crashing and photos not storing properly/overlapping eachother in memory that seems to happen with every update no matter what.
Click to expand...
Click to collapse
Before doing anything rash, you should probably start by clearing cached data @ Settings.>>Storage>>Cached Data. Also booting the phone to stock recovery and wiping the cache partition may help with any apps that are wigging out. Lastly, you really cannot "flash" anything with a locked bootloader. You can, and may later decide to wipe/factory reset from stock recovery. That would wipe your data and return your phone to the blank Android version you had installed last (7.1.2?) and yes, it would wipe/reclaim space, but you can do that manually without a factory reset. Before you go down that road make sure you enable the Google backup of your account so all your app/app data is saved. If you have photos, let Photos sync fully before the reset so your photos will be backed up to the Cloud. Also note that if you decide to unlock the bootloader (good choice) it will automatically perform a full wipe/factory reset. There is a sticky in General on how to do this.
v12xke said:
Before doing anything rash, you should probably start by clearing cached data @ Settings.>>Storage>>Cached Data. Also booting the phone to stock recovery and wiping the cache partition may help with any apps that are wigging out. Lastly, you really cannot "flash" anything with a locked bootloader. You can, and may later decide to wipe/factory reset from stock recovery. That would wipe your data and return your phone to the blank Android version you had installed last (7.1.2?) and yes, it would wipe/reclaim space, but you can do that manually without a factory reset. Before you go down that road make sure you enable the Google backup of your account so all your app/app data is saved. If you have photos, let Photos sync fully before the reset so your photos will be backed up to the Cloud. Also note that if you decide to unlock the bootloader (good choice) it will automatically perform a full wipe/factory reset. There is a sticky in General on how to do this.
Click to expand...
Click to collapse
Thanks for the input, but thats something I've been trying after every update already.
I found another site with clearer setup and instructions to do a stock flash with a factory rom and not OTA. Only reason why I had an issue with not wanting to unlock the bootloader was because im on windows 10 creators and it uses powershell now. So I had to figure out how to use fastboot/adb with powershell since cmdprompt wasn't the same. Doing a flash of a factory rom indeed fixed my gboard/photo storing overlapping issue that every ota update and factory reset through bootloader wouldn't solve.
Although my original question still remains, the system data in my storage is still 4.5gb with 7.1.2, better than the 5.5gb it was but I'm pretty sure its not supposed to be that big, any ideas why every update keeps taking up more space on the phone? The rom was even 1gb being flashed on the phone and I swear I remember the amount of space it took up when I first got the phone was around 2gb.
MadBullBunny said:
Thanks for the input, but thats something I've been trying after every update already.
I found another site with clearer setup and instructions to do a stock flash with a factory rom and not OTA. Only reason why I had an issue with not wanting to unlock the bootloader was because im on windows 10 creators and it uses powershell now. So I had to figure out how to use fastboot/adb with powershell since cmdprompt wasn't the same. Doing a flash of a factory rom indeed fixed my gboard/photo storing overlapping issue that every ota update and factory reset through bootloader wouldn't solve.
Although my original question still remains, the system data in my storage is still 4.5gb with 7.1.2, better than the 5.5gb it was but I'm pretty sure its not supposed to be that big, any ideas why every update keeps taking up more space on the phone? The rom was even 1gb being flashed on the phone and I swear I remember the amount of space it took up when I first got the phone was around 2gb.
Click to expand...
Click to collapse
I always flash a full images- not OTA... but I've always been unlocked on all my Nexus devices going back to the Galaxy. You cannot flash a full image without unlocking the bootloader but yet you say your bootloader is locked? For comparison, my untouched System is using 4.57 GB. I am running stock 7.1.2 ROM, rooted and EX Kernel.
PS...there is a toggle switch in Windows 10 settings to select command shell or powershell. It's as easy as a toggle to restore the command shell (or switch back).

Rescued bricked phone, but subtle instability leaves questions re EMMC/Recovery/more?

Description of issues:
Given bricked Note 4. I tortured the phone into obeying me (won't explain here how, though have elsewhere). Originally, it reported EMMC issues and would not allow Odin (any version new or old) to touch it. Finally (again, skipping how) I got it to take a TWRP flash, and then was told by TWRP that no directories existed or were wipeable. So I told TWRP to reformat the directories to ext2. This worked, absurdly. I then reformatted them back to being ext4. After that, I flashed a debloated version of the newer stock os (rooted). It worked.
I then became interested in whether or not the EMMC was/is bad in the phone. A little program for testing bad EMMC memory exists on google play. I downloaded it, and it said my phone (model SM-N910T) has no bad memory and is (I quote) "SANE."
But the phone remains unstable. It works for surfing the web, playing games, and so on but will suddenly reboot.
Here's my question, er, questions:
1. Is it possible there's a problem with the recovery partition itself on the phone? TWRP doesn't reformat that partition, does it? Or is there a way to completely wipe and restore the phone's partition structure... say, from within TWRP making sure not to shut TWRP down until one erases and then reinstalls TWRP from the ext micro-sd card? I am not a guru in such matters, but there must be a way.... OR....
2. Is it the EMMC memory anyway, despite what the program test said?
3. Or none of the above?
It's a nice phone. I'd love to have a good spare phone... esp. a Note 4. Any and all advice appreciated.

Categories

Resources