Database Users

This is probably a stupid question, but I'll ask anyway...

OK so, I was getting ready to flash to a new rom. I performed a factory reset, wiped cache, data, dalvic, etc...twice. But not paying attention, I accidentally selected reboot system before flashing a different rom...
...it rebooted normally, except as a fresh install. So by wiping the system, I'm really only clearing user data? How do I get rid of the rom entirely? Let's say the new rom I try to flash is considerably smaller with a lot less bloat. Wouldn't simply overwriting old rom still leave behind all of that extra data?
Is it possible to completely wipe the system partition and flash a new rom with cwm and have it boot?
Sent from my Amazon Kindle Fire using xda premium

new roms usually format the system partition - so nothing is left behind

In addition to what b63 said (which is correct), I think you're just getting hung up on some of the terminology. Doing a factory reset only wipes out userdata (data, cache, .android_secure) and doesn't touch your system partition. The ROM itself is still completely intact after a factory reset.
If you want to manually wipe your system partition you can do that, but you usually don't need to. In CWM go to "Mounts and Storage" and then select "Format /system" to do it. TWRP has an equivalent that I can't remember offhand, but it's something to the same effect (might be under "Advanced" or something). If you flash a ROM after you format /system manually it will boot fine, but obviously it won't boot if you format and reboot without installing a new ROM.

You're right, I just misspoke. The rom is only contained in the system folder, correct? I just couldn't understand why it would boot if I presumably wiped everything.
Sent from my Amazon Kindle Fire using xda premium

yes - if you look into the zip file of a rom you'll see there is mainly the system folder - that is /system
some have a data folder also - that are additional preinstalled apps in /data/apps
if your question is answered please mark the subject of the topic (edit first post) with [Solved]

Yes, the ROM's applications and binaries all live on the system partition, which is why it has no trouble booting after a factory reset. The data partition is basically reserved for user settings, apps, and other files.

[Q] Accidentally Wiped /data, Stuck in TWRP..

Well, it looks like I unintentionally wiped the /data partition using TWRP right after I did my first backup after rooting. Now I obviously can't boot since system, data, cache, etc. are wiped. The backup I just made was also wiped. As others mentioned in the TWRP thread, it's a bit different for the Nexus 10 compared with other devices - out of the 11 android devices I've had I've never done this!
Anyhow, can anyone a solution to getting a ROM back on my device? I can't seem to mount anything to my PC using TWRP. I can get fastboot working, but not ADB or file system mounting.
Thanks

Ehm, does the Nexus 10 have a ad card? If yes, use another phone to put a Rom on it and then flash it trough twrp
Sent from my awesome fridge

have you tried mount sd storage? or you can try the toolkit in the sticky thread.
Sent from my ADR6425LVW using xda premium

Get a stick drive, sd card reader, etc. Put a rom on it & transfer via twrp file manager
Sent from my Nexus 7 using Tapatalk 2

Just boot into fast boot and flash the stock images.
Sent from my Nexus 10 using Tapatalk HD

can you use adb to push a rom to flash?

TWRP allows you to adb sideload ROMs. Google TWRP adb sideload and it'll walk through the steps. You can also search the Original Development section and find MSkip's toolkit which I believe can flash ROMs and whatnot from your computer. It will also automate installing the proper drivers if that hasn't already been done.

Thanks for all the help. ADB wasn't working in TWRP - I believe it was a driver issue on my PC though. However, as jellydroid13 mentioned, I was able to use fastboot to flash the stock 4.2 image from google, and then boot up from there. Thanks again!

chompone said:
Well, it looks like I unintentionally wiped the /data partition using TWRP right after I did my first backup after rooting. Now I obviously can't boot since system, data, cache, etc. are wiped. The backup I just made was also wiped. As others mentioned in the TWRP thread, it's a bit different for the Nexus 10 compared with other devices - out of the 11 android devices I've had I've never done this!
Anyhow, can anyone a solution to getting a ROM back on my device? I can't seem to mount anything to my PC using TWRP. I can get fastboot working, but not ADB or file system mounting.
Thanks
Click to expand...
Click to collapse
Add me to the list of people who have wiped data over 9000 times in CWM and after updating to twrp and doing it there, have lost everything. I have backups, but am having no device found with adb sideload and suffice to say im a little confused. Confused why "wipe data" and wipe SD card and wipe SD EXT all do the same thing.
"

android01 said:
Add me to the list of people who have wiped data over 9000 times in CWM and after updating to twrp and doing it there, have lost everything. I have backups, but am having no device found with adb sideload and suffice to say im a little confused. Confused why "wipe data" and wipe SD card and wipe SD EXT all do the same thing.
"
Click to expand...
Click to collapse
+1 here
(i'll look for an OTG cable^^)

i had a similar problem several days ago
used ADB sideload to flash ROMs

why adb anything when like jellydroid said you can use fastboot and push all partitions and restore to stock?

I'm facing a similar issue but my device is Moto G5s Plus.
The problem I'm facing is that I accidently wiped out the mobile's system completely, and now it does not even have an "internal storage" partition at all (since it shows 0 MB). Hence, I cannot even transfer any files to my mobile because my computer does show the phone detected but no "internal storage exists".
Please help me out..

[Q] A200 data wipe failure -- no longer

Hi all,
I tried to update the custom ROM on my A200, but in the process, the data wipe failed.
What I did exactly, is use ROM Manager to load the latest JellyBean CM ROM for A200, selecting the option to wipe the data partition (do a factory reset). My device rebooted, and it started trying to wipe the /data partition, but it just stopped right there. No error or anything, the system just hung there for 2 hours before I turned it off. As I feared, the system was rendered unbootable.
However, CWN Recovery *is* still available, which I guess is a good thing. So, I can boot in recovery, but I can't really get it to function. I tried formatting the data partition again - system hangs. I tried installing the image from sd card - system hangs.
Does anybody know how I can recover from this? It seems to me that there's nothing *really* broken, just that my data partition is corrupt somehow -- and I suppose there has to be a way to recreate these partitions.
Thanks!

I've had CWN Recovery run for 24 hours now, and still nothing. It fails to format the data partition.
Anyone knows how to tackle this problem?

Partition damage? Not sure whats wrong...

Hey all,
I have an S4 i337m model. I've installed a custom ROM that is essentially a rooted stock ROM (I do not remember the exact build/version of the ROM). I realize having this info would be useful, but at the moment, I cannot access this info.
While running this ROM, everything was fine. Last week Friday, I attempted to install FoxHound 1.6. Had to play around with the installation options, but I got FoxHound to work. However, I need to get back on my old ROM as I needed some files that were deleted during the FoxHound install. So I wiped my phone, and restored my nandroid backup of my rooted stock ROM. again, everything was fine. No issues.
Here is where the problem is; after restoring my rooted stock ROM, I could boot into the phone and access the files needed. However, when I reboot/shut down phone, upon restarting/powering up, my phone is stuck at the 'Samsung Galaxy S4' logo right after power on. So, I boot into recovery (the latest version of TWRP) and I navigate to 'file manager' to take a look at my storage/files. And this is where I believe the issue to be; I see virtually no files at all. I can see many folders/partitions, but there are virtually no files anywhere (i.e. the system and data partitions are empty). I am assuming this is the reason why my phone doesn't boot past the Samsung Galaxy S4 logo. Now, when this happens, I wipe my phone again and restore my working nandroid backup. Everything works fine. I can get back into Android without issues. Until I reboot/power off my phone. Then this happens all over again.
I believe I may have damaged(?) the partition(s). When I installed FoxHound, I also installed an option during installation titled 'EXT4'. I know linux uses ext2/3/4 partition tables. Did I damage my storage/partition by installing EXT4 from FoxHound? Do I need to repartition my phone via Odin PIT file or something similar? Am I totally wrong with my analysis? Any help/advise/insight would be very welcomed.
Thanks

Additional info
Baseband: I337MVLUAMG1
Build number: JDQ39.I337MVLUAMG1
ROM: Rooted stock ROM 4.2.2 (with some bloatware removed)
While my phone was in the it's 'logo stuck' state, I entered into TWRP and selected the Wipe option, then Format Data. I must select 'Format Data' in order for my phone to work on it's next boot. Manually formatting System, Data, etc... will not allow my phone to boot up at next boot. And, my phone will only work on the next boot. If I power off/restart phone, it will get stuck at the logo again. So my phone is only good for 1 boot up after a wipe.
And, after I restore a working backup and boot into the phone, everything works until next power down/reboot. Once I power down/reboot phone, I must go into recovery since it will not boot into Android. When I get into TWRP, I see that my Internal Storage has 0MB free and I am unable to see any files. I can see folders/partitions, but there is nothing in any folder/partition. My external SD card shows nothing as well. My external SD card however is unaffected as all the data is still there once I get into Android and look around.
Also, I just restored a backup I had before I was having this issue. After restoring and rebooting, the same thing happens. I get stuck at the 'Samsung Galaxy S4' logo.
So I'm guessing there is some partition troubles here. Maybe I'm wrong, but I'm scratching my head as to the cause of this problem.

It could be some hardware issues too. I'd Odin back to stock and see if the problem persists. If it does its hardware.

jd1639 said:
It could be some hardware issues too. I'd Odin back to stock and see if the problem persists. If it does its hardware.
Click to expand...
Click to collapse
I thought the same thing. I'm downloading the stock ROM now and will give it a try.
One other thing I noticed during my last restore/fix attempt... After I perform a wipe -> Format Data (from TWRP), I notice that it reverts to my rooted stock ROM without me restoring anything. So, after I do a full wipe/format, and reboot my phone immediately after the full wipe/format, my phone will boot into the rooted stock ROM. I thought that wiping/formatting via TWRP totally cleans the internal storage of all data. So how can I be booting into any ROM after a wipe?
Unless I'm mistaken in my thinking and the full wipe/format option in TWRP just reverts back to the stock ROM I had installed prior to installing further custom ROMs?

If you wipe system and data there shouldn't be any rom it would boot. Don't try that though unless you have a nandroid because it shouldn't boot
What version of twrp ate you using?

Do not format data in twrp.

jd1639 said:
If you wipe system and data there shouldn't be any rom it would boot. Don't try that though unless you have a nandroid because it shouldn't boot
What version of twrp ate you using?
Click to expand...
Click to collapse
I hear ya... I have several nandroid backups. All work (minus this 'stuck at logo' issue I am having). I am using the newest TWRP version 2.6. It's very strange... after I perform a full wipe, I am able to boot into my rooted stock ROM that I flashed shortly after acquiring the phone. This was a bit over a month ago now. I do not know how this is possible.
xBeerdroiDx said:
Do not format data in twrp.
Click to expand...
Click to collapse
Why not?
_____________________________________________________________________
**Should I try using CWM instead?

Talabis said:
I hear ya... I have several nandroid backups. All work (minus this 'stuck at logo' issue I am having). I am using the newest TWRP version 2.6. It's very strange... after I perform a full wipe, I am able to boot into my rooted stock ROM that I flashed shortly after acquiring the phone. This was a bit over a month ago now. I do not know how this is possible.
Why not?
_____________________________________________________________________
**Should I try using CWM instead?
Click to expand...
Click to collapse
Use twrp 2.5.0.2 or cwm. The newer twrp has issues.

jd1639 said:
Use twrp 2.5.0.2 or cwm. The newer twrp has issues.
Click to expand...
Click to collapse
Is TWRP 2.5.0.0 ok to use?

Ok... It's really starting to look like my partition table has been damaged. Every time I flash a new ROM or restore a nandroid backup successfully, and then restart my phone, I get stuck at the S4 logo. Upon starting recovery, my internal storage reads 0MB free. It seems like my partition table is becoming corrupt after a reboot, or it has already been corrupted.
I tried flashing the stock ROM for my phone (I337MVLUAMDJ_I337MOYAAMDJ_I337MVLUAMDJ_HOME.tar is the one I used), but that didn't help at all. After installing this stock ROM, and I go into stock recovery, I get an error: E:failed to mount /data (invalid argument).
This really is looking like a partition problem. Is there some way to re-partition my phone? I remember a PIT file was used to partition my old Galaxy S i9000. Is there a PIT file for the S4 i337m?
I would also like to try CWM but I am having a hard time finding a ODIN flashable version.

I wouldn't mess with a pit file and I haven't seen one anyway. It's sounding more and more like your memory is bad. I'd keep it stock and see if you can get an exchange on the phone under warranty.

Further investigation has lead me to the culprit... sorta. It's my /data partition that is screwing everything up. If I format /data and then reboot, I can get into my phone. But if I reboot again, then my /data partition becomes corrupt and my phone hangs at the S4 logo. And then if I go into recovery, I can see that my internal storage is at 0MB free.
However, after formatting/restoring /data partition and rebooting into android successfully, everything works fine. If I reboot from this point and enter recovery, I am still able to see my /data partition and files. At this point, everything seems to be fine. Once I reboot out of recovery and let the phone boot into Android, I get stuck at the S4 logo and my /data partition screws up/becomes corrupt. It looks like my /data partition is only becoming corrupt after the 1st successful boot into Android. If I enter recovery after the 1st successful android load, I am still able to see all files and partitions. It is only trying to load android after the 1st boot that my /data partition becomes corrupt. Very strange...
So, I can always boot into my phone as long as I format my /data partition prior to loading Android. Anyone experience this before? Any ideas? I realize my memory may be damaged, but I'm leaving that as a last resort possibility since my phone was working fine up until I started installing FoxHound with the EXT4 option as well as installing 1 or 2 of the kernel's FoxHound provides. Namely Adam kernel is the one I tried.

All good... I think/hope
Well, I think I got the problem solved. After toying with this thing all day. It seems like TWRP 2.6 was the problem in some sense. Looks like TWRP 2.6 does not format the /data partition correctly. I had to get restore/install a working ROM, boot into my phone and install ClockworkMod Recovery via ROM Manager. I then used CWM to format /data. Once I did this, and loaded back into my phone, and went through the setup process since /data was formatted, everything was working fine. I just rebooted 5 times and shut down twice and my phone booted back up into android without issue.
So as one user in this thread had mentioned, formatting /data with TWRP 2.6 was the problem.
Hope this helps others avoid a similar issue.
Thanks everyone for all the help. It pointed me in the right direction.

Glad you got it fixed.

I'll be giving these steps a try, having somewhat of the same problem!

i've been having this exact same problem but with TWRP 2.5.0.2 since July. Its been driving me insane and I have not been able to find any one else having this issue until now. I think i might finally try CWM instead as a last measure before I finally give up!

Try TWRP 2.6.3.1 version. It works pretty well even though it's unofficial http://forum.xda-developers.com/showthread.php?t=2262996
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

My device shows less available storage than I know it actually has - after flashing

Hi,
I have a 16GB Nexus 4, running Android 5.1.1 LMY48I. I had recently flashed Google's stock rom (Android 5.1.1 LMY48I) on my Nexus 4. Later, I noticed that my Nexus thinks my internal storage capacity is 5.6 GB, while I know it should be a little less than 16 GB. That was really strange, and I figured that re-flashing stock rom might solve the bug. Unfortunately, my phone still believes I have less storage than I actually have.
I'd be happy if someone could explain why it happened, and more importantly - How I can fix it.
Thank you!

SOVED:
I managed to fix it by formatting the CACHE, SYSTEM and USERDATA partitions, then re-flashing the stock rom. I encountered a bootloop, so I decided to format again only the CACHE and USERDATA. Everything works now.

ido_doron said:
SOVED:
I managed to fix it by formatting the CACHE, SYSTEM and USERDATA partitions, then re-flashing the stock rom. I encountered a bootloop, so I decided to format again only the CACHE and USERDATA. Everything works now.
Click to expand...
Click to collapse
In the future, all you need to do is boot into the stock recovery after flashing the factory image and do a factory reset.
Sent from my Nexus 9 using XDA Free mobile app

I actually did tried this, but from some reason TWRP failed wiping the userdata partition...

ido_doron said:
I actually did tried this, but from some reason TWRP failed wiping the userdata partition...
Click to expand...
Click to collapse
Trwp is not the stock recovery.
Sent from my Nexus 9 using XDA Free mobile app

However, as much as I know, it should be able to wipe cache and user data. I tried to flash the stock recovery, but from some reason all I got is a green Android with exclamation mark on it... By the way, I also tried CWM and it failed too.
I ended up improvising something with ADB...