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.
Related
I am having a problem. I had manual nooter complete and went to install new kernal and when I did the nook would not get past the nook color screen. It would just sit there and do nothing. I then tried to install new kernal and still nothing. My next step was to do a factory reset and I can't format data. I know this has been touched on before, but the only way I can see to get it back would be to actually boot up the system, which I can't do. Any ideas?
u wipe cache?
download the kernel again, flash it again, if still no go
might need to reinstall the rom
edit: make sure you get the right kernel
Solution!!!
I experienced the same problem as you a couple days ago and was able to fix it with this link; http://forum.xda-developers.com/showthread.php?t=1094371. Just follow the instructions. Then flash whatever rom as normal and enjoy.
The problem your experiencing is due to the different partition scheme B&N is implementing on new NCs models and refurb ones. So if you bought a nook after may 1st (not sure on exact date) you will have the new partitions that show the available user space as 1gb. Currently most roms for NC do not work with the new partition scheme so you will have to repartition it with DeanGibson's method.
If this helped you out then a thanks would be awesome.
I'm talking about wiping photos, data, apps, everything!
Make it so that the device has nothing at all on it, not even Android (I'll flash that on)
Anyway to do this? Maybe a clockwork flashable file that erases everything (I had that on my phone)
Nobody knows?
NVflash in itself does a complete wipe, so that's all you need to do.
Eh, NVFlash basically wipes the partition table, so data is technically not wiped 100%, but it makes it heck of impossible to recovery if you don't know what you are doing.
giveen said:
Eh, NVFlash basically wipes the partition table, so data is technically not wiped 100%, but it makes it heck of impossible to recovery if you don't know what you are doing.
Click to expand...
Click to collapse
I just want all my GB's back from the internal storage, and just pretty much wipe it to factory literally. So NVFlash, is it possible to get the Stock HC ROM flashed via NVFlash?
ikutoisahobo said:
I just want all my GB's back from the internal storage, and just pretty much wipe it to factory literally. So NVFlash, is it possible to get the Stock HC ROM flashed via NVFlash?
Click to expand...
Click to collapse
There use to be a copy around but it got lost.
Easy way is to use restore to 2.2 and upgrade to hc.
Do a search of the forums on how to do this. I have said it at least three times in the past week how to do this.
Sent from my Nexus 7 using Tapatalk 2
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.
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
Hello everyone, I am having a issue here after updating (dirty flash) from xtrasmooth_MRA58K to Nexus Pure.. I originally made it to the homescreen (almost), but kept getting errors etc. I tried to unbrick it in many different fashions including the use of the toolkit (wug) and eventually landed with the stuck on google boot screen. I followed: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
option 1 and 2 and still can't boot pass the google boot screen. Any help would be appreciated, as I have been trying for the past 4 hours much to no avail. I would be will to teamviewer etc as needed. Thanks!
You can't really ever dirty flash from one rom to another.
Clean flash the new rom you want to try.
4 hours with out just wiping everything in TRWP and re-installing? Your going to brick your device for real one of these times... Read through the stickies here, and do a lot more research.
there are no options 1 and 2 in that thread?
Method 1 and Method 2?
Using fastboot manually or with your little toolkit?
What was the error messages?
Thank you for the reply scryan, I have tried method 1 with it still getting stuck on the google boot screen (initial white google text) and then tried method 2 with the same results. Both times the stock rom flashed with no errors (sig errors on method 1, but not 2), and I did a "Wipe data/factory data reset" then reset which brings me to the google boot screen.
You did method 2 manually? With MRA58R downloaded straight from google?
Use fastboot to completely flash all partitions again, as method 2 shows rebooting the bootlader as needed then copy and paste directly from the command prompt all your commands and all the output.
Post it here using the [code][/code] tags.
scryan said:
You can't really ever dirty flash from one rom to another.
Clean flash the new rom you want to try.
4 hours with out just wiping everything in TRWP and re-installing? Your going to brick your device for real one of these times... Read through the stickies here, and do a lot more research.
there are no options 1 and 2 in that thread?
Method 1 and Method 2?
Using fastboot manually or with your little toolkit?
What was the error messages?
Click to expand...
Click to collapse
kalans said:
Thank you for the reply scryan, I have tried method 1 with it still getting stuck on the google boot screen (initial white google text) and then tried method 2 with the same results. Both times the stock rom flashed with no errors (sig errors on method 1, but not 2), and I did a "Wipe data/factory data reset" then reset which brings me to the google boot screen.
Click to expand...
Click to collapse
while im going to say that i always dirty flash, always, im going to agree with @scryan. first off, if you do plan on dirty flashing, ALWAYS make a backup in twrp recovery, for situations like this. i try dirty flashing from roms with similar bases, never bases that are different, or they will never boot. anyways, enought with the talk, what you need to do is download your rom, gapps, and supersu, then you want to wipe your system and data in twrp recovery, then flash your rom(gapps, and supersu as well).
simms22 said:
while im going to say that i always dirty flash, always, im going to agree with @scryan. first off, if you do plan on dirty flashing, ALWAYS make a backup in twrp recovery, for situations like this. i try dirty flashing from roms with similar bases, never bases that are different, or they will never boot. anyways, enought with the talk, what you need to do is download your rom, gapps, and supersu, then you want to wipe your system and data in twrp recovery, then flash your rom(gapps, and supersu as well).
Click to expand...
Click to collapse
This is what I would have done from the beginning. Just wipe everything from TWRP and install rom straight out.
Going back to stock, then wiping and installing rom is extra work... But good reps and since it was ****ing up in the first place always good to figure out where it was going wrong instead of just giving up and doing something else.
It looks like I wasn't allowing enough time for the transfer to happen with method 1, I tried again it and now I am rolling. Thank you both very much for trying to help And I normally keep a good nandroid for everything, but 32gb is on the smaller end for me.
kalans said:
It looks like I wasn't allowing enough time for the transfer to happen with method 1, I tried again it and now I am rolling. Thank you both very much for trying to help And I normally keep a good nandroid for everything, but 32gb is on the smaller end for me.
Click to expand...
Click to collapse
im used to 16gb, so 32gb leaves me lots of space :angel:
Yeah I am getting somewhat better living on the cloud