Database Info

cwm cant mount /system and /data

Hey guys I need your help
I've been using cm7 for a couple of weeks now. I havnt had problems until today.
I flashed build 32 over and for some reason it wasn't booting up. It was on the splash screen for a while (it usually does that and when I take battery out and restart it boots) so then I took the battery out. Next thing I know is that my phone is stuck on the mytouch screen... I went to recovery and when it booted into cwm 3. I got a error saying it couldn't open system/recovery/log or something like that... it still went to cwm and I checked the mounts and it said /system and /data wasn't mounted. I clicked it to mount and it gave me an error saying it couldn't ... therefore it wouldn't let me install cm7 or do a wipe... is there anything I can do to fix this? It seems to be that the nand. Is corrupted or something...

I think, based on your description, that pulling the battery at the particular instant caused the secondary problem.
A "factory reset" reformats /data and /cache. But not /system. You can do that manually from the mounts and storage menu, then either restore a nandroid backup or install cm7 and gapps.
HTC Glacier running CM7 #33

Hmm I font think its just two directories... I think my whole internal storage is messed up. I tried using the reformat option from cwm but no luck

Time to discover what you might be able to accomplish with Fastboot and a USB cable.
HTC Glacier running CM7 #33

I think a lot of people are having problems with clockwork 3 in the nexus forums, and more specifically with it screwing up partitions. I was luck just to lose my ext position on my sd...
Reformat and reflash seems to be the easiest fix...
Sent from my Nexus One using XDA App

i dont know how to repartition the phone storage :/
i tried doing it off cwm and it wouldn't let me... is there anyway to do this through adb? i think adb is working...

Reformat the whole card, and then try to repartition. This will write your data, so back up first...
Sent from my Nexus One using XDA App

how do i do that? o_o through cwm? i tried formating everything including system data cache... and i dont know how to repartition through cwm. cwm is the only thing i can get to right now :/

Sorry, looks like the only option in clockwork is to partition. Can you not do it from your pc?
Sent from my Nexus One using XDA App

yeah it gives me error when i try to do :
fastboot erase system -w :/ is there anything else?

guys... ((((( am i totally effed up? i couldn't find anything i could do.. no matter what i did, the /system and /data would NOT mount... so i cant format it

I have never tried this, but you might consider it.
In this thread is a method to return your phone to stock -- it uses the bootloader's ability to repartition and reformat everything somewhat automatically, using a file called PD15IMG.ZIP from the SD card's root folder.
http://forum.xda-developers.com/showthread.php?p=11011692&highlight=pd15img.zip#post11011692
There's a link in the thread to the .zip file -- look to post signatures. Put the file on an SD card (with another phone, or camera, or Micro-SD to SD adapter, etc.) and boot into the bootloader with that file on the SD card.
I do not know if you can rename the .zip it to update.zip and force it to flash with Fastboot's update command, because the PD15IMG.ZIP is a specific thing this phone's bootloader looks for. As stated, I have never tried this, and do not recommend this. It might work, or, it might cause more damage. Putting the file on an SD card without Fastboot will be safer.

You could try to boot your phone into fastboot,
and then type
fastboot erase -w system
Your phone wont boot after that, but you should be able to flash a new rom from clockwork.

ive tried both the pd15img.zip method. it says "partition update fail"
and i also tried the "fastboot erase system -w" and it did not work.. it says that it can't be done. i also tried to format /system through adb and cwm, and both says it can't because it must be mounted before

From your description, it seems to me that the internal flash memory has a damaged partition table -- easy enough to repair if this were a hard drive you could remove and take to a linux system somewhere. But it's a phone, and a bit of flash memory that can't be removed.
Flashboot has an "erase <partition>" command. I don't know what it does, since it's not well documented. Does it reformat an existing partition? Or does it remove the partition from the partition table? There is no commensurate "create <partition>" command, so perhaps it recreates an empty partition. But I tend to doubt it.
I would think such work might be done from an engineering bootloader or engineering recovery system -- one available to HTC service technicians, for example.
Since you're not getting a great deal of help in the MT4G subforum, you might post your question in the top level Questions and Answers forum.
Sorry I'm not much help with this.

One last thought. The bootloader itself has a Factory Reset. That might do it. Might not. But like chicken soup, it probably couldn't hurt. Boot into the bootloader (volume down while powering up), select BOOTLOADER with the volume control and then the power button, then select FACTORY RESET. Perhaps it will do something positive.

eh.. i couldnt do anything. i tried all options. its like impossible to reformat or repartition the drive..
i actually called up insurance and they'll be sending me a new mytouch 4g..
we have just told them that it doesnt go past the mytouch screen.. would they figure out that it is rooted? i mean.. choosing recovery from the bootloader menu takes it right into cwm lol

Just flash the stock recovery back via fastboot...
Sent from my Nexus One using XDA App

ive tried

dumbkkid said:
ive tried
Click to expand...
Click to collapse
you are sending the fastboot commands while in the bootloader right? I would imagine you are but I just want to make sure.

SD Card Error Message

Code:
[B]E:unknown volume for path [/sd-ext] [/B]
This is the error I get using Revolutionary and am flashing a new rom using the 'correct' method spoken of here.
This error message occurs after I've wiped Dalvic Cache. The phone still performs as normal without any issues. But I'd like to get rid of this error if i can.
Can anyone help with this or has anyone had or seen it before?

BigPickle80 said:
Code:
[B]E:unknown volume for path [/sd-ext] [/B]
This is the error I get using Revolutionary and am flashing a new rom using the 'correct' method spoken of here.
This error message occurs after I've wiped Dalvic Cache. The phone still performs as normal without any issues. But I'd like to get rid of this error if i can.
Can anyone help with this or has anyone had or seen it before?
Click to expand...
Click to collapse
Try re-formatting the sd-ext partition using 4EXT recovery. Failing that, backup your entire SD card contents and re-format the whole thing, then copy your files back. I had a 512MB EXT3 partition on my card for ages from my old Desire days and A2SD+ ROMs. Never got your message but that's what I would try.

Isn't that SD partition? I also have that (when flashing, or doing backup) and I thought it was normal coz I don't have partition of my SD.
BigPickle80 said:
Code:
[B]E:unknown volume for path [/sd-ext] [/B]
This is the error I get using Revolutionary and am flashing a new rom using the 'correct' method spoken of here.
This error message occurs after I've wiped Dalvic Cache. The phone still performs as normal without any issues. But I'd like to get rid of this error if i can.
Can anyone help with this or has anyone had or seen it before?
Click to expand...
Click to collapse

Thanks for your answers guys.
@wnp_79 I always format my sd card when i flash a new rom.
@MarlIX I'll try formatting again and making a partition using the whole sd card size to see if it solves it.

I guess that it depends on situation in which you're extending main partition with SD card (as HTC Desire users have to do in order to install ROM which doesn't fit on internal memory). In normal cases you'll have such warning because you don't have extended partition on SD (But someone please correct me if I'm wrong)

ah ok so i shouldnt worry about it then really unless the rom i want to flash requires extended partition?
I can make a partition on Revolutionary i get these options 128m,256m,512m etc etc and then i brings up a menu saying swap size 0m,32m,64m,128m or 256m.
Any guesses on the best way to set my card up?

If you are not using it then use either choose the smallest size, our use 4ext recovery to remove it.
Whenever i did it, a 0MB swap was just fine.
Sent from my HTC Desire S using xda premium

I see an option to remove all partitions and start from scratch so next time i flash i'll select that and maybe that will sort it out.

[Q] Error formatting /data/system/packages.xml on ICS

So I installed the latest wingray ICS nightly for my xoom, #48 and after that it wasn't responding so I went to restore from a nandroid backup. After the backup I noticed that none of my apps where there so I did a factory reset and it's giving me the error in the title. It gives me the same error with anything that has to format /data. I managed to delete the file but it seems to appear again when I try to format. Some help would be appreciated because I'm out of ideas. I'm using the reccomended recovery and everything like that, nothing fancy, I just had the rom and Gapps installed and it had all worked fine up until that point.
Thanks

Well I ended up using fastboot to format it. Got rid of everything on my sd card but at least I can use my xoom now. Still wondering if anyone knows why that happened or a better way to deal with it next time if it happens again.

GET YOUR DATA /data/media WITHOUT loss: error in /data/system/packages.xml format
did you try using adb pull C:\xoommedia /data/media/ ? that wouldve recursively grabbed it all.. i had to do something similar recently.. so long as the partition isnt corrupt it can be pulled recursively using adb pull command and dumping it into a local directory. i pulled my data, then tried using eraseData in /sdcard/clockworkmod/ as solarnz mentioned in the clockworkmod thread but that still didnt format /data fully to the point of rewrite so i did like you and fastboot -w ..
sorry i realize this may have come too late but hopefully it will help someone else.
if this ever helps you hit thanks! thanks!

I actually had it working enough that I could transfer files from in the actual OS. Forgot to copy over my wallpapers though Ah oh well. Thanks anyway

mz601 same xml error
What fastboot commands did you use ? Help can't install properly ..no market ..arrrrrr

fastboot erase userdata
It'll format your entire internal sd

"Error removing /data/system/packages.xml"
I had the same exactly on this file.
In CWM, Factory reset didn't work, restoring a backup neither, only a lower level operation with fastboot did the trick
Probably ext4 corruption?
My problems began when the tablet started rebooting while being in market..
h ttps://github.com/TDR/android_bootable_recovery/blob/stingray/roots.c#L302
ret = remove (path) returned -1.
remove() from stdio.h:
On success, zero is returned. On error, -1 is returned, and errno is set appropriately.
Adding a display of errno could help. Or fsck before formating?

[Q] Emmc got write-protected or frozen

About a month ago my Xoom (MZ605, EOS 3.0) froze and I had to do a hard reset. After that the tablet became unusable due to the neverending stream of Closed Force dialogs. First I thought the fs and or partition table were buggered, but now I have discovered that whatever I do to the emmc, nothing changes at all: Fastboot flash, SBF flashing, fsck and gdisk in recovery (using adb shell). In all cases, the writing and flashing completes without any errors, but when checking for the results, nothing has changed at all.
Any idea on what might have caused this? Or even better: how to make to emmc writable again? If necessary I'm willing to open it up and mess with the hardware.
Thanks!

Have you tried locking and then re-unlocking the boot loader? Just a suggestion, not promising anything.
It will, normally, wipe your internal storage so make sure you backup any necessary data to a computer.
Sent from my SAMSUNG-SGH-I747 using xda premium

Hi d3athsd00r,
I tried that several times, but just be sure I tried it again. Unfortunately it didnt help Thanks for the suggestion anyway! If you or anyone else has any other ideas, please let me know. The personal data on the tablet isn't important btw (just music), so there's no problem if everything is lost.

Have you tried to format everything in cwm under the mounts menu? (Remove sdcard before doing so)
Sent by Samsung Galaxy Nexus (SCH-I515 Verizon LTE) using Tapa2

I use TWRP, but that one seems to do an rm -rf instead of a real format. Either way it has no effect: even after wiping everything several times, nothing changes: all files are still there. The same goes for using an adb shell in recovery and manually doing an ext4 format. No matter what I do, the data on the internal storage seems frozen or write protected.

ioish said:
I use TWRP, but that one seems to do an rm -rf instead of a real format. Either way it has no effect: even after wiping everything several times, nothing changes: all files are still there. The same goes for using an adb shell in recovery and manually doing an ext4 format. No matter what I do, the data on the internal storage seems frozen or write protected.
Click to expand...
Click to collapse
I would say your recovery is faulty. Try an earlier version or a different kind
Sent from my Xoom

Hi cdexsw
The problem is that flashing has no effect: when I do a fastboot flash or even RSD Lite, the commands complete without error. However after that nothing seems to have changed: the recovery stays the same, the rom (EOS 3 at the moment) stays the same and all my personal data is still there even although I did an oem lock and then oem unlock several times. It seems that whatever I do, the internal storage doesn't change a single byte. I even used dd if=/dev/zero =/dev/block/mmcblk0p10 (and also on the system and cache partitions) in an adb shell to wipe the userdata completely, but it doesn't do anything at all. So I simply can't seem to replace the recovery since not even flashing has any effect.

ioish said:
Hi cdexsw
The problem is that flashing has no effect: when I do a fastboot flash or even RSD Lite, the commands complete without error. However after that nothing seems to have changed: the recovery stays the same, the rom (EOS 3 at the moment) stays the same and all my personal data is still there even although I did an oem lock and then oem unlock several times. It seems that whatever I do, the internal storage doesn't change a single byte. I even used dd if=/dev/zero =/dev/block/mmcblk0p10 (and also on the system and cache partitions) in an adb shell to wipe the userdata completely, but it doesn't do anything at all. So I simply can't seem to replace the recovery since not even flashing has any effect.
Click to expand...
Click to collapse
odd indeed....have u looked to see if any other devices from other makes have had a similar issue?
Sent by Samsung Galaxy Nexus (SCH-I515 Verizon LTE) using Tapa2

I looked a lot on google, but didn't find anything relevant to my case. I even tried to find the datasheet of the chip to if there's a pin (ball) that controls the read-only, like a switch would. Unfortunately it doesn't seem to be publicly available on the internet.
The only topics I found to remotely relevant is:
http://discussions.nokia.com/t5/Maemo-and-MeeGo-Devices/Memory-In-Readonly-Cannot-Flash-EMMC/td-p/1030885
bu that doesn't have any relevant info.

Are you familiar with linux?
If you are, check out the first post on page 2 of this thread.
http://forum.xda-developers.com/showthread.php?t=1609825&page=2
Sent from my SGH-I747 using xda premium

Yep, quite familiar
That indeed sounds the same as my problem, but I already ran fsck a million times and everytime it complains that there are problems with the journal and won't continue. Either way, there do seem to be FS errors, because when mounting the partition it says it's fixing certain errors (very few) and then continues to mount it RW. After trying to change anything, the kernel drops the partition into RO mode. "mount" continues to show it as rw though.
That's why I tried doing an mke2fs, which completes succesfully, but it seems that the changes are only in RAM and never persisted to emmc.

ioish said:
Yep, quite familiar
That indeed sounds the same as my problem, but I already ran fsck a million times and everytime it complains that there are problems with the journal and won't continue. Either way, there do seem to be FS errors, because when mounting the partition it says it's fixing certain errors (very few) and then continues to mount it RW. After trying to change anything, the kernel drops the partition into RO mode. "mount" continues to show it as rw though.
That's why I tried doing an mke2fs, which completes succesfully, but it seems that the changes are only in RAM and never persisted to emmc.
Click to expand...
Click to collapse
Very odd indeed. I might have missed this but have you tried installing CWM (not TWRP as it only does the rm) and attempting to do a format from there?
Sent from my SGH-I747 using xda premium

I did try installing CWM using fastboot flash and also a newer version of TWRP and the command completes succesfully, no errors on the screen. When booting into recovery, the same TWRP is still there, as if I never flashed anything

Same problem with my Moto G. Nothing gets flashed. emmc is just write protected and I cannot mount anything

[Q] Soft Bricked tab, no custom recovery and no way of selecting USB debugging option

So i soft bricked my device while trying to install the latest 4.0.1 image. I tried hard wiping the device and wipe cache partion from Stock Recovery but didn't help, still wouldn't boot. I tried installing the image in Stock Recovery from Apply Update From External SD Card, but i got a few errors first "E:Failed to map file Operation aborted", i took a look at the file and it had about 1.67gb extra in "Userdata" i tried deleting that file and reinstalling from external sd card but then i got "E:footer is wrong" "E:signature verification failed" Operation Aborted.
Now i'm trying to install update from ADB (Surprisingly if i have the tab connected and im in Apply Update from ADB the tab is recognized in ADB
Code:
adb devices
serial # sideload and i have updated the drivers) But if i try to flash the recovery file 4.0.1 (provided from the developers site [cant post links]) "i just get waiting for device"
Anyone know how to get around this issue in ADB or properly install from external sd card without getting errors?
(Alternative read to my problem posted in the Nvidia Forums 98% sure i soft bricked my device [cant post links]

Did you ever find a fix? I'm having a similar problem.

Try to use fastboot restore everything.

I can't get it to connect to fastboot. When it loads the boot loader and I try to select fastboot protocol it fails.

Wow this thing sucks! I'm really appreciating my Samsung with Odin right now! So I finally got it to connect to fastboot (don't ask me how, I don't know) unlocked the bootloader and flashed twrp. Now it won't flash supersu in adb sideload so I put it on an SD card (which now magically mounts and works now) and flashed the zip in recovery but it says at the very end of the process while trying to update the partitions that it can't mount the data and system partitions so I'm not sure if I'm actually getting root or not and if so if it's permanent I have no way to tell. I think this is because they have been accidentally wiped. Do you think it is safe to try to flash a rom in recovery from external sd card? And if so which one? I have no idea which version bootloader, kernel, or os is or was on this device...
Update: I think I may start a new thread in the Q&A/Help section so that I can try to get a vast concensus. Thanks!

rom fiend said:
Wow this thing sucks! I'm really appreciating my Samsung with Odin right now! So I finally got it to connect to fastboot (don't ask me how, I don't know) unlocked the bootloader and flashed twrp. Now it won't flash supersu in adb sideload so I put it on an SD card (which now magically mounts and works now) and flashed the zip in recovery but it says at the very end of the process while trying to update the partitions that it can't mount the data and system partitions so I'm not sure if I'm actually getting root or not and if so if it's permanent I have no way to tell. I think this is because they have been accidentally wiped. Do you think it is safe to try to flash a rom in recovery from external sd card? And if so which one? I have no idea which version bootloader, kernel, or os is or was on this device...
Update: I think I may start a new thread in the Q&A/Help section so that I can try to get a vast concensus. Thanks!
Click to expand...
Click to collapse
Yes flash a ROM in recovery.
Try Resurrection Remix. It'll resurrect your device

Just tried flashing bliss 6.2 and it won't get past the nvidia screen. It says it flashes successfully but I still get a bunch of "can't mount such and such partition" errors during the flash sequence. Not sure what to do, I can post pics if you guys want.

If you got/can get TWRP on there now, the advanced wipe menu will allow you to check /data for errors. As for /system, wipe it. If you get errors that e2fsck can't fix in your TWRP log, you'll have to put on your data recovery hat on. If it's that important to you, my advice is to adb pull the right file under /dev/block. You won't get a block device, you'll get an exact image of your data partition. Once it's fully pulled (it'll be 10 GB or more on a 16GB device), make a copy of it first thing, and use data recovery tools (testdisk, or if you really know what you're doing, debugfs). If you don't have anything valuable on /data (remember that any backups you took from recovery go in /data/media by default), just format that and be done with it.
Pray that there are no errors after you format everything, because that usually means your NAND is toast.
If your errors are hardware ones, you're royally screwed. Same thing happened to my Nexus 7 2013 model a year ago. Only way to use it is to flash a modified kernel that will use an attached USB drive exclusively as storage. If the NAND is toast inside the boot partiti,try replacing recovery, otherwise, you have to tether boot it (fastboot boot) every time you want to run it, unless you have the guts to try repartitioning the NAND (unlike on PCs, messing up there is an instabrick).
Since the Shield Tablet can use SD cards, you're better off. No USB drive needed.