So, I went and installed the developer preview and when I rebooted it said I only had 23 GB of space... Is anyone else having this problem. And if there is any way to get it back? I installed everything from the Google link
n6
mrgoodpaul said:
So, I went and installed the developer preview and when I rebooted it said I only had 23 GB of space... Is anyone else having this problem. And if there is any way to get it back? I installed everything from the Google link
Click to expand...
Click to collapse
this happened to me running multirom...you need to have stock recovery...no multirom...and factory reset...
then the usable storage shows 55gb ~58gb or usable storage
I flashed everything including recovery and userdata
fastboot format userdata is the only fix with a custom recovery. With stock recovery, factory reset may be sufficient.. Youll lose all data including sdcard
Related
So I was playing around yesterday loading a few different roms, and much to my chagrin i was having issues with twrp continually asking me for a password even though i did a data format, factory reset, etc. Eventully i gave up and, using wugfresh's kit, flashed stock and unrooted (which im fine with since 5.1 has been running like a dream) and now all of a sudden it says i only have a 32gb hard drive. I tried flashing LMY47D and LMY47E and it still says the same thing. What have i done to myself? And how the hell can i fix it?
Thanks in Advance
hotrodotb said:
So I was playing around yesterday loading a few different roms, and much to my chagrin i was having issues with twrp continually asking me for a password even though i did a data format, factory reset, etc. Eventully i gave up and, using wugfresh's kit, flashed stock and unrooted (which im fine with since 5.1 has been running like a dream) and now all of a sudden it says i only have a 32gb hard drive. I tried flashing LMY47D and LMY47E and it still says the same thing. What have i done to myself? And how the hell can i fix it?
Thanks in Advance
Click to expand...
Click to collapse
Factory reset through settings not twrp
jiv101 said:
Factory reset through settings not twrp
Click to expand...
Click to collapse
Thanks man. I guess i just assumed that when i flashed stock/unrooted that was good enough but i guess OEM Data reset TRUMPS ALL.
Same issue - I am charging my phone now to do the same. Hope it works! I thought this was very weird.
Part A) tool kits are satan.
Part B) the stupid ****ing userdata.img partition that flashall flashes is ONLY for 32gig devices. Its ridiculous, the stock images and directions google supplies are for 32 gig devices, with no notice or warning, so if you flash them blindly it will format your userdata (basically the partition mounted as /sdcard) to be the size it should for a 32 gig device.
Best is to manually flash, and leave out userdata, then wipe internal with custom recovery.
If you wanna fix with out extra wiping and work, see this thread
http://forum.xda-developers.com/nexus-6/general/phone-gb-storage-to-factory-reset-t3225492
scryan said:
the stupid ****ing userdata.img partition that flashall flashes is ONLY for 32gig devices. Its ridiculous, the stock images and directions google supplies are for 32 gig devices, with no notice or warning, so if you flash them blindly it will format your userdata (basically the partition mounted as /sdcard) to be the size it should for a 32 gig device.
Best is to manually flash, and leave out userdata, then wipe internal with custom recovery.
If you wanna fix with out extra wiping and work, see this thread
http://forum.xda-developers.com/nexus-6/general/phone-gb-storage-to-factory-reset-t3225492
Click to expand...
Click to collapse
Excellent. Exactly what I needed. Had to flash a newer TWRP, but then this worked perfectly. Cheers.
I was using Android M preview. Downgraded it to 5.1.0 to flash with a custom rom, but now its only showing 23gb of storage? Its a Nexus 6 64gb version? Anyone who knows how to fix this?
EDIT: Reflashing stock AGAIN, with wipe data/cache fixed it
Factory reset
Oniska said:
I was using Android M preview. Downgraded it to 5.1.0 to flash with a custom rom, but now its only showing 23gb of storage? Its a Nexus 6 64gb version? Anyone who knows how to fix this?
EDIT: Reflashing stock AGAIN, with wipe data/cache fixed it
Click to expand...
Click to collapse
When you installed the factory sysimage, you installed a preformatted 32GB empty data partition image. They really shouldn't include that at all. When you wiped, you re-formatted the data partition to its actual capacity.
I updated to 6.0 today but must of flashed an image that gives me 32 gigs of storage, TWRP has the resize feature but I can't figure it out (ID10T error no doubt) I found this but it did no good http://forum.xda-developers.com/nexus-10/development/mod-reclaim-free-space-partition-t3029605 do I need to wipe again or is there a way around this?
Thanks,
Latheman said:
I updated to 6.0 today but must of flashed an image that gives me 32 gigs of storage, TWRP has the resize feature but I can't figure it out (ID10T error no doubt) I found this but it did no good http://forum.xda-developers.com/nexus-10/development/mod-reclaim-free-space-partition-t3029605 do I need to wipe again or is there a way around this?
Thanks,
Click to expand...
Click to collapse
i dont know about the twrp option(it might be easier) but you should reflash the factory image. btw, all the factory images are the same, regardless of how much storage you have.
Thx, I figured out TWRP though, worked great.
simms22 said:
i dont know about the twrp option(it might be easier) but you should reflash the factory image. btw, all the factory images are the same, regardless of how much storage you have.
Click to expand...
Click to collapse
If all factory images are the same, and flashing the factory image with its 32gig formated userdata.IMG is what got him here in the first place... What would reflashing that image fix?
I see you got it sorted... But if others find themselves in the same place, here is a thread on it
http://forum.xda-developers.com/showthread.php?t=3225492
scryan said:
If all factory images are the same, and flashing the factory image with its 32gig formated userdata.IMG is what got him here in the first place... What would reflashing that image fix?
I see you got it sorted... But if others find themselves in the same place, here is a thread on it
http://forum.xda-developers.com/showthread.php?t=3225492
Click to expand...
Click to collapse
its a very common issue when flashing a nexus, happened on every single nexus. i dont know why it happens, maybe it reads the phone wrong? but reflashing the factory image usually fixes it.
simms22 said:
its a very common issue when flashing a nexus, happened on every single nexus. i dont know why it happens, maybe it reads the phone wrong? but reflashing the factory image usually fixes it.
Click to expand...
Click to collapse
From all I have seen, if you do a flash all, or manually flash all....
Well really if you flash the userdata.img to a 64 gig phone you and up a 32 gig nexus. As you said the images are all the same, so you are essentially flashing your /sdcard to be the one from a 32 gig phone... Like sticking a 64 gig flash drive into a compute and formatting it to 32gig. You end up with un-partitioned space and need to expand the userdata portion to get it back.
Better move when trying to do a full wipe/clean install to stock image is to skip flashing userdata, and just do a fastboot format userdata instead.
scryan said:
From all I have seen, if you do a flash all, or manually flash all....
Well really if you flash the userdata.img to a 64 gig phone you and up a 32 gig nexus. As you said the images are all the same, so you are essentially flashing your /sdcard to be the one from a 32 gig phone... Like sticking a 64 gig flash drive into a compute and formatting it to 32gig. You end up with un-partitioned space and need to expand the userdata portion to get it back.
Better move when trying to do a full wipe/clean install to stock image is to skip flashing userdata, and just do a fastboot format userdata instead.
Click to expand...
Click to collapse
if you want you can. but this error happens so rarely that i never put any thought into it when flashing. ive been with android for 7 years, and its never happened here.
Hello everyone. I just flashed CM12.1 in my Fire 7, which was version 5.1.1, usingh the FlashFire app.
It worked first time, but somehow the gApps wasn't installed and I wanted to wipe the internal storage as well to get rid of some crap there.
However when I tried to flash again, an this time I wiped the internal storage, I got stuck on the Amazon logo. Is this because the internal storage wipe or could be other issue?
Now the main question is, can I recover the device from this or is it bricked?
Thanks a lot!
luccasvr said:
Hello everyone. I just flashed CM12.1 in my Fire 7, which was version 5.1.1, usingh the FlashFire app.
It worked first time, but somehow the gApps wasn't installed and I wanted to wipe the internal storage as well to get rid of some crap there.
However when I tried to flash again, an this time I wiped the internal storage, I got stuck on the Amazon logo. Is this because the internal storage wipe or could be other issue?
Now the main question is, can I recover the device from this or is it bricked?
Thanks a lot!
Click to expand...
Click to collapse
Reload FireOS 5.1.1 (or higher) assuming you can access stock recovery via <power>+<vol-up>. Otherwise you scored a brick.
Apologies for duplicating this post but the original forum was apparently the wrong spot for this.
I need either some pointers or a reference to a how-to, if you please.
My Nexus 6 is currently running Pure Nexus 6.0.1-2060821-official, security patch 8/5/2016 with ElementalX kernel 3.10.40-ElementalX-N6-3-20.
I've updated Pure Nexus before through TWRP and all went well, but those efforts never involved updating the kernel too. I've attempted to flash the new kernel, the rom and the google apps, but the phone goes into a never ending boot effort and it's a tussle getting back to recovery mode as it tends to boot loop. The flashes are preceded by clearing Delvik and cache and cleared again after the flash.
Is the order of flashing off or perhaps not enough clearing of other items such as system? Or is a factory reset needed?
Kind of lost on this one and can't seem to string together enough search terms to find help specific to the problem.
Any help would be appreciated.
The kernel is most likely not updated to work with the rom. Each rom comes with its own kernel so you really don't have to flash a new one. I would flash the rom and gaps and see what happens. Leave the kernel out of it for now. You have to remember that not all kernels work on all roms. Many roms are making it so only their kernel works properly.
zelendel said:
The kernel is most likely not updated to work with the rom. Each rom comes with its own kernel so you really don't have to flash a new one. I would flash the rom and gaps and see what happens. Leave the kernel out of it for now. You have to remember that not all kernels work on all roms. Many roms are making it so only their kernel works properly.
Click to expand...
Click to collapse
Still no-go. Freshly downloaded purenexus_shamu-7.1.1-20170215-OFFICIAL and Full_Dynamic_GApps-7.1.x-20161215, checked the MD5s, and flashed both after cache/Dalvik. Still got the same 4-color bouncing dots. Let it run like that for about 40 minutes before getting back into recovery.
Ran the same flash but this time also wiped system. Same result.
Is 40 minutes enough time? Impatience maybe?
Now back to original 6.0.1, PureNexus 6.0.1-20160821 and 3.10.40-ElementalX-N6-3.20 kernel.
Any ideas?
jlfesslerkc said:
Still no-go. Freshly downloaded purenexus_shamu-7.1.1-20170215-OFFICIAL and Full_Dynamic_GApps-7.1.x-20161215, checked the MD5s, and flashed both after cache/Dalvik. Still got the same 4-color bouncing dots. Let it run like that for about 40 minutes before getting back into recovery.
Ran the same flash but this time also wiped system. Same result.
Is 40 minutes enough time? Impatience maybe?
Now back to original 6.0.1, PureNexus 6.0.1-20160821 and 3.10.40-ElementalX-N6-3.20 kernel.
Any ideas?
Click to expand...
Click to collapse
You are doing a full wipe right? Wiping system and data before flashing?
Also encryption could be an issue. If your device in encrypted or the kernel did not remove the force encryption flag. That could take awhile as well.
jlfesslerkc said:
Still no-go. Freshly downloaded purenexus_shamu-7.1.1-20170215-OFFICIAL and Full_Dynamic_GApps-7.1.x-20161215
Click to expand...
Click to collapse
Get the Feb 15 GApps too instead of the Dec 15 GApps. Don't use old GApps.
https://forum.xda-developers.com/android/software/gapps-dynamic-gapps-t3487192
Also make sure that the GApps are 7.1.x and not 7.x.x or you get a SDK mismatch. What does the recovery log show?
Pkt_Lnt said:
Get the Feb 15 GApps too instead of the Dec 15 GApps. Don't use old GApps.
https://forum.xda-developers.com/android/software/gapps-dynamic-gapps-t3487192
Also make sure that the GApps are 7.1.x and not 7.x.x or you get a SDK mismatch. What does the recovery log show?
Click to expand...
Click to collapse
Got the Feb GApps, wiped Dalvik and cache... this time I let it run for a bit over an hour in case the encryption was an issue. There's a little over 19 GB in files. I figured an hour would be enough but no luck. Had to recover again from backup.
TWRP gives 5 items that can be wiped, Dalvik, System, data, Internal Storage and Cache. I was of the understanding that data pertained to user data (photos, notes, etc). Most all of that is backed up but I'm unclear on what needs wiping for this Nougat upgrade. When I wiped system, it didn't seem to help - although I was using the older GApps at that point. I've seen documentation that says to wipe these items at the outset and others that suggest after the flash is complete. Both? Which ones?
I don't want to resort to drastic measures if it's something simple that I've missed.
Needs Nougat bootloader and latest radio--flash in TWRP. This allows flashing N ROMs while will still work with all MM or even 5.1 ROMs
http://batakang.com/ftp/devs/mhous33/shamu/bootloaders/shamu_bootloader_moto-apq8084-72.01.zip
http://batakang.com/ftp/devs/mhous33/shamu/7.1.1/shamu_baseband_D4.01-9625-05.44+FSG-9625-02.115.zip
jlfesslerkc said:
Got the Feb GApps, wiped Dalvik and cache... this time I let it run for a bit over an hour in case the encryption was an issue. There's a little over 19 GB in files. I figured an hour would be enough but no luck. Had to recover again from backup.
TWRP gives 5 items that can be wiped, Dalvik, System, data, Internal Storage and Cache. I was of the understanding that data pertained to user data (photos, notes, etc). Most all of that is backed up but I'm unclear on what needs wiping for this Nougat upgrade. When I wiped system, it didn't seem to help - although I was using the older GApps at that point. I've seen documentation that says to wipe these items at the outset and others that suggest after the flash is complete. Both? Which ones?
I don't want to resort to drastic measures if it's something simple that I've missed.
Click to expand...
Click to collapse
What TWRP version? Old one cause problems on newer ROMS. Newest is 3.1.0, but 3.0.3 or 3.0.2 should be ok.
Wipe everything - /system, /data, /cache. /dalvik. Do NOT wipe Internal Storage (camera photos, downloads, etc.) before flashing. Data is usually app data, so make a nandroid first to save it, but app data can usually be restored with Titanium Backup or Google will restore it on setup. Just do not restore any system data.
Bootup on clean flash does take time, but normally no more than 20-25 minutes.
Try reverting to stock
Install stock firmware using adb
TWRP version might be the glitch.... Mine reports 2.8.5.0 in recovery mode. I'll update to the latest and retry after wiping all but internal storage. If that fails, I'll flash the boatloader and radio.
Once more into the breach.
jlfessler said:
TWRP version might be the glitch.... Mine reports 2.8.5.0 in recovery mode. I'll update to the latest and retry after wiping all but internal storage. If that fails, I'll flash the boatloader and radio.
Once more into the breach.
Click to expand...
Click to collapse
Hi... Save your internal storage before processing. Just in case... TWRP 2.8.5.0 is pre nougat and incompatible.
jlfessler said:
TWRP version might be the glitch.... Mine reports 2.8.5.0 in recovery mode. I'll update to the latest and retry after wiping all but internal storage. If that fails, I'll flash the boatloader and radio.
Once more into the breach.
Click to expand...
Click to collapse
You should really update the bootloader/radio to the latest once you update the TWRP. Updating the bootloader/radio will not affect your internal storage.
Pkt_Lnt said:
What TWRP version? Old one cause problems on newer ROMS. Newest is 3.1.0, but 3.0.3 or 3.0.2 should be ok.
Wipe everything - /system, /data, /cache. /dalvik. Do NOT wipe Internal Storage (camera photos, downloads, etc.) before flashing. Data is usually app data, so make a nandroid first to save it, but app data can usually be restored with Titanium Backup or Google will restore it on setup. Just do not restore any system data.
Bootup on clean flash does take time, but normally no more than 20-25 minutes.
Click to expand...
Click to collapse
Wiping system, data, cache and Dalvik seems to have gotten me to Nougat but apparently root did not come along for the ride. Wasn't expecting that. Is that par for the course?
jlfesslerkc said:
Wiping system, data, cache and Dalvik seems to have gotten me to Nougat but apparently root did not come along for the ride. Wasn't expecting that. Is that par for the course?
Click to expand...
Click to collapse
yup
Item 1.8 and 1.9 here
Pkt_Lnt said:
yup
Item 1.8 and 1.9 here
Click to expand...
Click to collapse
Thanks. 1.9 refers to SuperSU which is what I used earlier.
Also I take it reinstalling TitaniumBackup will then let me restore the apps. Still on track?
jlfesslerkc said:
Thanks. 1.9 refers to SuperSU which is what I used earlier.
Also I take it reinstalling TitaniumBackup will then let me restore the apps. Still on track?
Click to expand...
Click to collapse
That is what Titanium Backup (and Restore) does, yes.