[Q] lost my storage after update to 4.4.3 - Nexus 7 Q&A, Help & Troubleshooting

Hi, I have a Nexus 7 2012 32 GB. Today I updated to 4.4.3 but after update only 6.02 GB of 32 GB is shown on storage.
What should I do?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

mkhp70 said:
Hi, I have a Nexus 7 2012 32 GB. Today I updated to 4.4.3 but after update only 6.02 GB of 32 GB is shown on storage. What should I do? ,,,
Click to expand...
Click to collapse
First, a bit more details - is yours rooted/unlocked, what was running before & using custom recovery (latest CWM or TWRP) ? Did you do a Factory Reset after backing up user files & data? Wipe Dalvik Cache, Cache and Factory Reset/Wipe?
Reboot into Custom Recovery, wipe dalvik cache & cache first, then reset & check your storage again?
Post your steps, results & we will go from there.

rooted/unlock/TWRP 2.6 / I did factory reset after backing up user files & data but I didnt Wipe Dalvik Cache, Cache
updating through the factory image with nexus toolkit
now i do wipe dalvik cache and cache and full wipe but not fix

Something is seriously messed up if all it's telling you you have is 6gb of internal storage. If you have a 32gb like me, then it should show around 27 to 28 gb storage (mine is the 2012 WiFi version of N7).
Something got seriously borked during the upgrade.
My question is, did you get an OTA and do it that way or did you download the full image from Google and then flashed it that way?

Something isn't right? I'm afraid that you need to start al over - learn ADB and forget about those Toolkit(s) unless that are specific & updated for 4.4.3 compliance. Mine is a 2012 WiFi model with 32 GB, internal storage/total space is 27.58 GB and even with apps & pix, video, etc. on the SDcard, and Apps taking up space, I have 19.1GB available.
First, might I suggest that you upgrade/try the newest recovery - either CWM or TWRP (using 6.0.4.5 on mine) to install - doing a full wipe & factory reset is best way/recommended AND yes, time-consuming, but you get it "right" almost every time - wipe three (3) times each - dalvik cache, cache and factory reset/full wipe. Then, re-flash your factory rom/image file - be patient, as it will take 5 to 10 minutes for it to finish, take a break or whatever. When it's done & without error/abort message, reboot the device & let it settle for a little while after configuring WiFi as those download Apps and update could take a while if your mobile data plan is limited. Personally, I'm "biased" toward TWRP and I don't have to deal with MD5 check/error message that pop out of nowhere with CWM. :cyclops:
If everything works as planned, you will be shown the Setup Menu to configure - profit & enjoy, check the storage size (you can see what's taking up the space) then, restore your Google Account with the Apps, and reboot when finished.
Good luck & let us know your progress or results.

mkhp70 said:
rooted/unlock/TWRP 2.6 / I did factory reset after backing up user files & data but I didnt Wipe Dalvik Cache, Cache
updating through the factory image with nexus toolkit
now i do wipe dalvik cache and cache and full wipe but not fix
Click to expand...
Click to collapse
At the last step the toolkit shows you a message that talks about this issue. I can't remember what it exactly says. But it tells you what to do incase of lost storage. Either reflash using toolkit and read the prompt about lost storage or search the Web about this message from toolkit.
Sent from my Nexus 7 using XDA Free mobile app

Related

[Q] Internal Storage is showing too less

Hi, I don't exactly know since when it's showing wrong, but I believe it has to do something with my latest "activities".
First here my storage of my 16 GB N4 device:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Okay, I decided to fully wipe my device and go back to stock 4.2.2 before flashing latest AOKP PUB rom.
Therefore I went into fastboot and used following commands to erase old data
fastboot erase cache
fastboot erase boot
fastboot erase userdata
fastboot erase system
fastboot erase recovery
Then I started with stock factory image 4.2.2 (JDQ39)
Flashed userdata, boot, system and a customrecovery (TWRP 2.4.2.0)
Rebooted phone, downloaded supersu 1.10 zip, AOKP PUB rom, and Trinity Kernel (TF107)
Booted into recovery --> wiped cache/dalvik cache --> factory reset --> flashed AOKP and TF107 --> rebooted --> set up wifi etc
Booted into recovery --> flashed supersu --> rebooted installed busybox --> rebooted into recovery and fixed permissions.
Now I was starting to set up everything like my apps etc. until I noticed my storage is too small.
What is the problem and what can I do to get my storage back?
The only unusal thing which I never did before, was the erasing stuff, could this be the problem?
Thanks!
Hi,
I think you should take a look here: [url=" http://forum.xda-developers.com/showthread.php?p=35119185'' ]
[HOW-TO] Fix internal storage if 16GB now shows 8GB[/url]
Restart from scratch... Weird it's what you done apparently...
viking37 said:
Hi,
I think you should take a look here:
[HOW-TO] Fix internal storage if 16GB now shows 8GB
Restart from scratch... Weird it's what you done apparently...
Click to expand...
Click to collapse
okay thanks, started from scratch again and with all stock it's working now.
I'll try to flash my custom recovery, rom and kernel again and hopefully it works this time.
laba86 said:
okay thanks, started from scratch again and with all stock it's working now.
I'll try to flash my custom recovery, rom and kernel again and hopefully it works this time.
Click to expand...
Click to collapse
Same thing happened to me. A total pain in the ass...
Sent from my Nexus 4 using xda premium
All I did was back up my sdcard, boot into recovery, format the sdcard, then copy everything back on to it.
Worked for me.

freedom pop sprint galaxy s4 wont start

I installed an update that automatically downloaded to my sprint samsung galaxy s4 which came with freedom pop "service", it restarted and now goes into a boot loop. With the key combo i can boot to TWRP or a Download option, however, I'm not sure how to proceed. I would like to have it without any freedom pop to use with boost service. mostly i'd like my phone back.
thanks for any help you all can offer.
Lori
lc614lewis said:
I installed an update that automatically downloaded to my sprint samsung galaxy s4 which came with freedom pop "service", it restarted and now goes into a boot loop. With the key combo i can boot to TWRP or a Download option, however, I'm not sure how to proceed. I would like to have it without any freedom pop to use with boost service. mostly i'd like my phone back.
thanks for any help you all can offer.
Lori
Click to expand...
Click to collapse
Odin the stock firmware from www.sammobile.com
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
stock recovery
i used oden to flash the stock firmware to the phone. oden completed with a Pass. it now boots to the recovery screen. offering several options such as: reboot sysem; apply update from ADB; apply update from external storage; wipe data/factory reset; wipe cache partition; apply update from cache
which one from the above choices?
Thanks
Lori
lc614lewis said:
i used oden to flash the stock firmware to the phone. oden completed with a Pass. it now boots to the recovery screen. offering several options such as: reboot sysem; apply update from ADB; apply update from external storage; wipe data/factory reset; wipe cache partition; apply update from cache
which one from the above choices?
Thanks
Lori
Click to expand...
Click to collapse
Wipe Data /Factory Reset
bilgerryan said:
Wipe Data /Factory Reset
So far so good. wiped data/cache. now i'm offered the same 6 options as before. which do i choose.
i can't say it enough, thank you
Lori
Click to expand...
Click to collapse
lc614lewis said:
bilgerryan said:
Wipe Data /Factory Reset
So far so good. wiped data/cache. now i'm offered the same 6 options as before. which do i choose.
i can't say it enough, thank you
Lori
Click to expand...
Click to collapse
After the wipe, just select reboot
Click to expand...
Click to collapse

Getting "internal" or "system" error when trying any ROM

I managed to get the stock google MDB08M build on and rooted, but I have tried several different ROMs and each time I get constant "system" or "internal" error messages when first booting up. It makes the ROMs unusable.
On top of that, if I try to restore a previous nandroid it just gets stuck at the animated android logo. In order to get it to work again I have to complete re-image the phone back to stock, re-root, re-install custom recovery.
Any ideas what could be causing this?
Thanks,
Craig
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is this the message? I get the same ****
Sent from my Nexus 6P using Tapatalk
csh8428 said:
I managed to get the stock google MDB08M build on and rooted, but I have tried several different ROMs and each time I get constant "system" or "internal" error messages when first booting up. It makes the ROMs unusable.
On top of that, if I try to restore a previous nandroid it just gets stuck at the animated android logo. In order to get it to work again I have to complete re-image the phone back to stock, re-root, re-install custom recovery.
Any ideas what could be causing this?
Thanks,
Craig
Click to expand...
Click to collapse
Have you tried flashing the MDB08M vendor image after flashing the ROM? Are you wiping properly (system, data, cache, dalvik cache)? In regards to your nandroid backup, what partitions did you back up and what partitions are you restoring?
Heisenberg said:
Have you tried flashing the MDB08M vendor image after flashing the ROM?
Click to expand...
Click to collapse
I would say no, since the only thing I flashed as the ROM. Should this be done before or after flashing the downloaded ROMs? I'm not sure where to get/which vendor image I should use either.
Heisenberg said:
Are you wiping properly (system, data, cache, dalvik cache)?
Click to expand...
Click to collapse
Here's what I did.
Complete format and wipe device
install google stock picking option 9 from [TOOL] SKIPSOFT ANDROID TOOLKIT - NEXUS 6P
Wipe dalvik and cache
Boot into android, enable dev options
Boot to fast boot
install TWRP using option 6 from [TOOL] SKIPSOFT ANDROID TOOLKIT - NEXUS 6P
Root using option 4 from [TOOL] SKIPSOFT ANDROID TOOLKIT - NEXUS 6P
Reboot to OS to check for root
make nandroid in TWRP
install custom ROM in TWRP
Wipe dalvik and cache
Reboot
After the reboot is where it gets stuck on those pop-upis. I've tried several different ROMs starting at step 1 each time and get the same result
Heisenberg said:
In regards to your nandroid backup, what partitions did you back up and what partitions are you restoring?
Click to expand...
Click to collapse
I don't remember. I think I checked all the boxes available when backing up and restoring the whole nandroid of whatever was backed up.
csh8428 said:
I would say no, since the only thing I flashed as the ROM. Should this be done before or after flashing the downloaded ROMs? I'm not sure where to get/which vendor image I should use either.
Here's what I did.
Complete format and wipe device
install google stock picking option 9 from [TOOL] SKIPSOFT ANDROID TOOLKIT - NEXUS 6P
Wipe dalvik and cache
Boot into android, enable dev options
Boot to fast boot
install TWRP using option 6 from [TOOL] SKIPSOFT ANDROID TOOLKIT - NEXUS 6P
Root using option 4 from [TOOL] SKIPSOFT ANDROID TOOLKIT - NEXUS 6P
Reboot to OS to check for root
make nandroid in TWRP
install custom ROM in TWRP
Wipe dalvik and cache
Reboot
After the reboot is where it gets stuck on those pop-upis. I've tried several different ROMs starting at step 1 each time and get the same result
I don't remember. I think I checked all the boxes available when backing up and restoring the whole nandroid of whatever was backed up.
Click to expand...
Click to collapse
Ok, it looks like you didn't wipe (system, data, cache, dalvik cache) before installing the ROM, so there's one problem. Also, when creating your backup you don't need to check all options, only system, data, and boot. You flash the stock vendor after flashing the ROM. I'd recommend you take a look at my guide, it should clear a few things up:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
You'll also find a recovery flashable version of the vendor image in my index thread under the stock firmware section:
http://forum.xda-developers.com/nexus-6p/general/index-huawei-nexus-6p-t3213583
I was getting the same error, but it didn't seem to affect he devices functions in any way.
Anyways I flashed the new vendor image since i installed a MMB29P ROM and didn't update it before.
Without wiping it did nothing the error was still there.
Then I wiped everything and started with vendor image, then the ROM, the kernel and SU.
NO ERROR.

Samsung Galaxy S7 bootloop

I tried to root my phone using odin to flash TWRP. Through that i installed SuperSU and rebooted the phone. Now it is stuck in a bootloop. What went wrong?
btw i can't wipe dalvik cache via the advanced wipe (it says invalid partition)
k1ng0fqu33n5 said:
I tried to root my phone using odin to flash TWRP. Through that i installed SuperSU and rebooted the phone. Now it is stuck in a bootloop. What went wrong?
btw i can't wipe dalvik cache via the advanced wipe (it says invalid partition)
Click to expand...
Click to collapse
First of all, boot into download mode, then install your stock firmware via odin to get out of the bootloop. Then use chainfire's autoroot to get root, then with flashify install twrp.img and you should be good to go.
TheSproker said:
First of all, boot into download mode, then install your stock firmware via odin to get out of the bootloop. Then use chainfire's autoroot to get root, then with flashify install twrp.img and you should be good to go.
Click to expand...
Click to collapse
Thanks. Though i hoped there was another method cause as far as i know installing stock firmware wipes the device and i didn't make a backup beforehand.
k1ng0fqu33n5 said:
Thanks. Though i hoped there was another method cause as far as i know installing stock firmware wipes the device and i didn't make a backup beforehand.
Click to expand...
Click to collapse
Yep, the most important thing is to always make a backup. Because without that, the only way is re-installing the stock firmware. And when you have installed twrp, be sure to format data, so that twrp could decrypt and access your internal storage (that's why you were not able to wipe cache)
TheSproker said:
Yep, the most important thing is to always make a backup. Because without that, the only way is re-installing the stock firmware. And when you have installed twrp, be sure to format data, so that twrp could decrypt and access your internal storage (that's why you were not able to wipe cache)
Click to expand...
Click to collapse
If i do a factory reset with TWRP, will it wipe any of the internal data? (pictures, messages etc.)
because the factory reset screen says that it's not included:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well, i just tried a factory reset and that fails too. Unable to mount /data.
k1ng0fqu33n5 said:
Well, i just tried a factory reset and that fails too. Unable to mount /data.
Click to expand...
Click to collapse
There is a guide you should have followed here if you have exynos s7e
https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084
Did you flash this file ?
EasyAndroidPro said:
There is a guide you should have followed here if you have exynos s7e
https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084
Did you flash this file ?
Click to expand...
Click to collapse
That's the guide i have been using to root, yes. And yes, i flashed that file along with SuperSU.
k1ng0fqu33n5 said:
That's the guide i have been using to root, yes. And yes, i flashed that file along with SuperSU.
Click to expand...
Click to collapse
I see.. if that file did not fix the bootlooping then I'm afraid the only fix is like the previous poster said
Either flash stock again with Odin
Or format data in twrp
Ok, i somehow made it so the phone booted up and initialized. Now i got the problem that the google play store keeps crashing.
Edit: I also can't download my whatsapp backup data (says insufficient storage, which is not the case)
I also can't download files with the chrome browser (it says no sd-card found). If i use the stock samsung browser it works though.

Please, help with some unexplained problems

Since the last beta OnePlus (Pie 9 for OP5) have been released, I have continued blocking and rebooting the system (using custom rom principally, but also stock rom).
Recently, I was able to replicate the problem I have with all the new pie rom (I tried LineageOs, Dirti, Omni and even stock); in practice, by opening more applications (8/10 or more) and then turning off the screen, the system freeze (with blue LED on); at other times, reboot instantly.
Can someone help me understand what the problem may be? Eventually, do you have any suggestions?
I state that I format/wipe each partition; here the complete sequence I use to format and install custom roms (a real madness!):
*Format Data and Wipe all
Flash 5.1.3 Full
*Wipe Davilk and cache
Boot OS (to create Vendor Partition)
Bootloader - fastboot flash recovery recovery.img
*Wipe Davilk and cache
OpBeta 22 firmware + vendor
*Wipe Davilk and cache
OpBeta 23 firmware (o latest)
*Wipe System, Data, Davilk and cache
Bootloader - fastboot format userdata - fastboot erase cache - fastboot flash recovery recovery.img
*Wipe Davilk and cache
Flash custom rom
*Wipe Davilk and cache
Flash OpenGapps
*Wipe Davilk and cache
Flash NoVerity
Flash Magisk
*Wipe Davilk and cache
Boot OS (finally )
I also attach some tests done with GFBench (the hardware does not seem to have problems)
Thank you, very much.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I could not understand what the problem was; anyway and for now, I solved installing the ROM stock without Magisk (among other things, I had tried different versions: 17 / 17.2 / 17.3 / 18 ... I have always had problems).
You made this way too complicated. Download the newest beta on to phone. Get total commander from play store, use it to enter(not extract) the firmware zip and delete the compatibility zip inside. Ensure magisk is on your device. Boot to twrp. Wipe EVERYTHING except internal. Now flash newest one beta, once it finishes flash magisk. It might fail. Just try again and it will work. Reboot. Now you are on pie with magisk and kept twrp. Also magisk is no verity. But you should flash decrypt before first boot if you are gonna go in and play with stuff.
Thanks, but I did that procedure just to figure out what the problem was. Magisk gave me several problems, in the meantime I try for a few days ... then I'll try.
Merry Christmas
mascian said:
Thanks, but I did that procedure just to figure out what the problem was. Magisk gave me several problems, in the meantime I try for a few days ... then I'll try.
Merry Christmas
Click to expand...
Click to collapse
OB23 with magisk 17.1 is working fine for me.
strongst said:
OB23 with magisk 17.1 is working fine for me.
Click to expand...
Click to collapse
LOL... that version is the only one I have not tried ??

Categories

Resources