Database Develop

[Q] How can I completely wipe the internal storage?

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

23GB on 64GB Nexus running M Dev Preview

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

[SOLVED] Soft Bricked, Unlocked + Fastboot

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

Lost storage

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.

No Mobile Data after Nandroid Restore

I don't think I can edit the title so I'll write it here for anyone who wants to help: This problem is SOLVED. (Y)
So the matter is a bit complicated and I can't guarantee I even remeber everything I did but I'll try to include as much detail as I can:
I had the Stock Rom (OOS4.0.0) running, OEM unlocked & rooted when the OOS4.0.1 OTA notification kept nagging in the back of mind. I thought I should just leave it ago because I already had a feeling it would go wrong...
So I download the Full .zip and flashed it through TWRP 3.03-1 and after that it was stuck on the boot screen for more than 15 minutes or so. So I restarted it again and this time it booted butall my data was deleted and it gave me an error about the encryption having failed. But as you probably know, one can't flash anything on an encrypted phone so I checked back in TWRP and it was really encrypted. Checked back in the phone's settings: Also encrypted. I then used a tool to force decryption (it also wipes all the data) and I was back to square one.
From that moment on I tried: 1. restore nandroid (all partitions included [that includes EFS]). It got me to the booting screen, but when I unplugged it shut down and a reboot got me to the battery screen. I had 72% left so at this moment I thought it had nothing to do with it not booting at 72%. Then I wiped everything (checked every box in TWRP) and was left without any OS. Then I let my phone charge to 100% and re-restored the nandroid OOS4.00 and it worked but I had the Unlock-Bug, I was able to fix that. Then it booted but it wasn't able to recognize any SIM cards, so I fixed that by re-re-restoring with TWRP 3.03-0 (which automatically replaced 3.0.3-1 after the nandroid) and everything worked fine. until I went out today and realized I had no mobile data. I doubt it has something to do with EFS because everything else is working fine (calling, checking IMEI wih *#06#).
I then proceeded to check the APN and it looked ok, I then tried another SIM card (from the same provider) and it didn't change anything.
My provider is the german company 1&1 (1und1) but it uses vodafone APN.
I have no clue what to do right now so I am asking you guys for help.
Thanks in advance!

Well, first things first. On rooted devices with stock rom always flash a full/complete zipped image - never, never, never use an official partial image. And always wipe Dalvik/Art and common cache before reboot.
In your case now I would probably try to clean re-flash the current OOS image version (4.0.1). You'll find guides and downloads in the guides and rom section of this forum. Clean flashing your device requires you to completly wipe the data partition before flashing (the internal partition remains untouched). Don't forget to wipe Dalvik/Art and cache before rebooting. This will hopefully completly reset your device.

Inciter said:
Well, first things first. On rooted devices with stock rom always flash a full/complete zipped image - never, never, never use an official partial image. And always wipe Dalvik/Art and common cache before reboot.
In your case now I would probably try to clean re-flash the current OOS image version (4.0.1). You'll find guides and downloads in the guides and rom section of this forum. Clean flashing your device requires you to completly wipe the data partition before flashing (the internal partition remains untouched). Don't forget to wipe Dalvik/Art and cache before rebooting. This will hopefully completly reset your device.
Click to expand...
Click to collapse
First of all: Thanks for your reply.
I don't know if there was a misunderstanding but I only ever flashed the full 1,4gb .zips.
Also I am running 4.00, because I had to restore it as the 4.0.1 flash ruined my phone. Just now I flashed 3.03-1, wiped dalvik & cache and flashed the 4.02 .zip which I got from this [https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074] thread but it left me stuck on "patching image uncoditionally" or something and then I rebooted and now I am stuck on the +1 booting screen (not even the animation, just the +1 logo witht he "powered by android" signature in the bottom).
I have the feeling it's a software bug not related to what I did with my phone. it was just luck that I did not havfe that problem prior to my nandroid restore or something. I mean: Looking at it from a logical perspective: When you restore your phone with a full nandroid backup it should be exactly the same phone, shouldn't it?

Well, flashing the TugaPower rom might break the alert slider. To fix this you have to simply backup and recover the data partition. I don't know why this is happening but I believe that sometimes permissions to files and folders remain untouched in certain situations. Maybe someone else knows more details on this topic.
If you are absolutly sure that your nandroid contains all required partitions just try to wipe all cashes, data and system partition before recovery. But like I said before I would then clean re-flash your current OOS image version. In your case the error might possibly be some error resulting from faulty permission on configuration data. If it was a common bug more people would have reported it already.
If something broke and it can't be easily fixed... trying to return to point zero and resetting everything to defaults will possibly your best chance.

Inciter said:
Well, flashing the TugaPower rom might break the alert slider. To fix this you have to simply backup and recover the data partition. I don't know why this is happening but I believe that sometimes permissions to files and folders remain untouched in certain situations. Maybe someone else knows more details on this topic.
If you are absolutly sure that your nandroid contains all required partitions just try to wipe all cashes, data and system partition before recovery. But like I said before I would then clean re-flash your current OOS image version. In your case the error might possibly be some error resulting from faulty permission on configuration data. If it was a common bug more people would have reported it already.
If something broke and it can't be easily fixed... trying to return to point zero and resetting everything to defaults will possibly your best chance.
Click to expand...
Click to collapse
I have no problem with that, but my device does.
I can't flash anything because TWRP (bot 3.03-0 and 3.03-1) will be stuck at "patching system image unconditionally", ( I tried the full 4.02 .zip and the ful 3.54 .zip that I am 10000% sure used to work, because I used it before the Nougat release).
Wiping everything but Internal and USB OTG changes nothing.
If you have any idea how I can get to a fresh start, I would really appreciate it.
EDIT: I am sorry, I don't know what you mean by TugaPower Rom. I never installed anything like that - atleast not knowingly.

Due to encryption returning to OOS 3.X after having upgraded to Nougat is difficult. Just flashing wouldn't do. There's still an option to format data - not just to wipe it. Was boot, EFS and firmware partition included in your nandroid? Does the recovery still work now? Another Approach would be to use the Unbrick Tool.

Inciter said:
Due to encryption returning to OOS 3.X after having upgraded to Nougat is difficult. Just flashing wouldn't do. There's still an option to format data - not just to wipe it. Was boot, EFS and firmware partition included in your nandroid? Does the recovery still work now? Another Approach would be to use the Unbrick Tool.
Click to expand...
Click to collapse
So, I have the means to decrypt my device through a tool I found here on the forums last month. It does wipe all your data, though. Anyways: I was able to restore mobile data through an older nandroid backup (and yes: all my back ups include all partitions; glad I was smart enough to do that haha). That worked for me and made me come to the conclusion that the back up I used first was somehow corrupted. Then I restored the data partition using my most recent nandroid back up and now I am back in the game. Thanks for all your help so far!
The only thing that kind of makes me worry is that I only get ~60mbit/s through speedtest even though I should get 200. I know I was able to get 200Mbit/s at some point using that phone, but I don't remember if it was with OOS 3xx or the OOS 4.00 update. So I can't tell whether it has something to do with me restoring the phone, my WiFi connection (a speedtest with my lan-connected desktop gave me 200) or just an android bug.
I'll wait until weekend when I have the means to test it with another 200k connection - and imho 60k is enough for anything I do with my phone anyways and I don't plan on reselling the phone in the future, so it won't kill me even if it is nandroid-related.

Linux/Android backups aren't always that satisfying. I often experienced diffences between what was saved and what or how it was restored. Most problems resulted in faulty permissions or missing file execution attributes.
Nevertheless, I'm glad your devices is working again. Keep that backup save, you'll might need it again... or hopefully not.

Inciter said:
Linux/Android backups aren't always that satisfying. I often experienced diffences between what was saved and what or how it was restored. Most problems resulted in faulty permissions or missing file execution attributes.
Nevertheless, I'm glad your devices is working again. Keep that backup save, you'll might need it again... or hopefully not.
Click to expand...
Click to collapse
Thank you, I just checked the wifi-speed with an iPhone 6 and it even got lower results (>30k) so I assume it has something to do with the WiFi itself at the moment and not with the OP3t.
And even if the backups are not always satisfying: I want to quote someone I read on some forums doing my research to fix this phone: "The seasoned user knows: A backup makes the difference between an awesome phone and a beautiful brick." That is a most evident truth to me now haha.