[Q] Internal Storage is showing too less - Nexus 4 Q&A, Help & Troubleshooting

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.

Related

[Q] Nexus 10 won't boot, CWM can't mount filesystem, TWRP factory reset fails

Hi,
Today I was trying to root my Nexus 10 (android 4.4.2), following this tutorial I had found earlier: au.ibtimes.com/articles/530367/20131216/root-android-4-2-kot49h-kitkat-install (add .htm, can't post urls yet).
Everything went fine until I tried to backup my system to the SD card with CWM. In CWM I got the message that several points in the filesystem could not be mounted. Not knowing how to proceed, I tried to reboot - since then I am stuck in a loop and would like to at least be able to boot into my stock rom again. Googling around for a while, I found several posts suggesting a factory reset might do the trick, however, since CWM is unable to mount anything, I can't perform such a reset. I tried wiping cache and all that, did not work.
Then I flashed TWRP (2.6.3.1 for nexus 10) using the fastboot flash recovery command. Again, I tried to perform a factory reset, which fails (the log just says
updating partition details...
Formatting Cache using make_ext4fs function.
So, I don't quite know what to do. Could anyone tell me how to best proceed? How can I get the Nexus 10 to boot again?
Thanks in advance!
EDIT: Ok, just fixed it by flashing the re-flashing the stock rom from the google page. So, how do I root the device now without running into the same troubles once again?
Wugfresh nexus root toolkit has always worked for me:
http://www.wugfresh.com/nrt/
tjupille said:
Wugfresh nexus root toolkit has always worked for me:
http://www.wugfresh.com/nrt/
Click to expand...
Click to collapse
+1 safe and easy
Thanks, that worked great!
Seems that same issue happened to me, but even after restoring Factory Image and re-flashing custom recovery I still have this problem:
{
"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"
}
Tried also on TWRP with no luck..any suggestions?
Inviato dal mio LG-D802 utilizzando Tapatalk
AleCai said:
Seems that same issue happened to me, but even after restoring Factory Image and re-flashing custom recovery I still have this problem:
Tried also on TWRP with no luck..any suggestions?
Inviato dal mio LG-D802 utilizzando Tapatalk
Click to expand...
Click to collapse
Hi,
I will suggest you to try formatting cache again, as it is the problem there. If it doesn't work, and you don't mind refashing the stock rom, then I'd like to ask you trying wiping every partition and install the after this.
I had a similar issue with Xoom, I needed to reboot several times in recovery and after some many times it finally mounted system (I had a bootloop) and I formatted it.
Good luck,
~Lord
"This Story Ends Where It Began"
Sent from my monstrous Xperia Z1

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

Anyone have a XT1575 7/19/2016 update TWRP package?

Anyone have a XT1575 7/19/2016 update TWRP package?
{
"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"
}
Please post if you do, my rooted phone now enters boot-loop because I accidentally hit "Yes, I am in"....
Thanks in advance!!!
I had the boot loop too. Went to twrp and wiped dalvik and cache and no more boot loop.
captainmalcolm said:
I had the boot loop too. Went to twrp and wiped dalvik and cache and no more boot loop.
Click to expand...
Click to collapse
Do you still have root, etc.?
captainmalcolm said:
I had the boot loop too. Went to twrp and wiped dalvik and cache and no more boot loop.
Click to expand...
Click to collapse
HeatR216 said:
Do you still have root, etc.?
Click to expand...
Click to collapse
Yes i would like to know! I would love to be able to run the OTA update without causing issues, and if all i have to do is wipe dalvik n cache on boot after the OTA update that would be awesome!
Sorry should have been more clear, the update does not work. Wrong signing keys. It sends the system into a boot loop. You boot back into the O's but after about 30 seconds it begins applying the update again and send you into twrp and updates fails, reboot, wait 30 apply again twrp, etc. Etc. The way I got out of the loop was wiping dalvik and cache and now I can use the phone again without boot loop. We need to wait until someone creates a twrp zip for the update.
Mine is full wipe >> flash stock 24.49-18-3 >> update 24.49-18-4 via OTA then flash Su 2.62-3 >> Done.
captainmalcolm said:
Sorry should have been more clear, the update does not work. Wrong signing keys. It sends the system into a boot loop. You boot back into the O's but after about 30 seconds it begins applying the update again and send you into twrp and updates fails, reboot, wait 30 apply again twrp, etc. Etc. The way I got out of the loop was wiping dalvik and cache and now I can use the phone again without boot loop. We need to wait until someone creates a twrp zip for the update.
Click to expand...
Click to collapse
I still dont get you, first you say the update does not work, then you said it worked after you cleared dalvik and cache in twrp after it had been applied making it work?
Not TWRP flashable, but someone posted the full firmware here.
I could not get the OTA to go on my phone, kept failing.
I just fastboot flashed everything in that zip according to the flash script that came with the zip except recovery and didn't wipe userdata. Booted into new system to confirm everything was ok, then TWRP flashed systemless supersu and Frankenclark. All is good. Not as simple as TWRP flashable, but way less disruptive than restoring to bare bones stock to take an OTA.
How long does it usually take on a new twrp zip?
oh someone please get this going! i hate this annoying update notification every day! twrp zip would be awesome!
nd4spdbh said:
oh someone please get this going! i hate this annoying update notification every day! twrp zip would be awesome!
Click to expand...
Click to collapse
yep. just waiting for twrp zip.

decryption unsuccessful

Hey everyone,
So I have been using Oreo beta B12 on my A2017U for a few weeks and wanted to check out Lineage and after having some qualms about Oreo and stability, decided to go for Lineage 14.1.
Using TWRP I wiped (standard wipe) and flashed the bootloader, modem, lineage, gapps, and Magisk. In that order. Upon finish and reboot it tells me, Decryption unsuccessful, I must reset my phone. But when it goes to wipe it fails, i see the following:
{
"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"
}
It seems to be stuck like this, and I don't know what to do to proceed. I could try some things, but I don't want it to get worse because I wiped something crucial.
Thanks in advance.
Tre916 said:
Hey everyone,
So I have been using Oreo beta B12 on my A2017U for a few weeks and wanted to check out Lineage and after having some qualms about Oreo and stability, decided to go for Lineage 14.1.
Using TWRP I wiped (standard wipe) and flashed the bootloader, modem, lineage, gapps, and Magisk. In that order. Upon finish and reboot it tells me, Decryption unsuccessful, I must reset my phone. But when it goes to wipe it fails, i see the following:
It seems to be stuck like this, and I don't know what to do to proceed. I could try some things, but I don't want it to get worse because I wiped something crucial.
Thanks in advance.
Click to expand...
Click to collapse
Flash B12 Beta again and flash 3.2.1-8 and decrypt data (format data )with 3.2.1-8 and flash LOS14.1( bootloader.modem,los,twrp 3.2.2-0 ) you must install twrp before reboot system.
atakan33 said:
Flash B12 Beta again and flash 3.2.1-8 and decrypt data (format data )with 3.2.1-8 and flash LOS14.1( bootloader.modem,los,twrp 3.2.2-0 ) you must install twrp before reboot system.
Click to expand...
Click to collapse
Thanks, that worked. I appreciate your help!
atakan33 said:
Flash B12 Beta again and flash 3.2.1-8 and decrypt data (format data )with 3.2.1-8 and flash LOS14.1( bootloader.modem,los,twrp 3.2.2-0 ) you must install twrp before reboot system.
Click to expand...
Click to collapse
So, would you mind explaining what actually went wrong? Did I just fail to decrypt/format the data before imaging? Should I just be sure to format /data every time I flash a new rom?
Tre916 said:
So, would you mind explaining what actually went wrong? Did I just fail to decrypt/format the data before imaging? Should I just be sure to format /data every time I flash a new rom?
Click to expand...
Click to collapse
in oreo you must decrypt data with 3.2.1-8 thats it ( if you are encrypted )

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