Database Info

[Q] Unable to mount data partition read/write

Hey
I'm trying to change from Prime to Revolution ROMs, but during wiping, I seem to be hitting a problem. When coming to wipe /data, it says it can't remove bootanimation.zip. I'm trying to go in via adb and do this manually, but it won't seem to let me mount /data as read write.
I'm using adb shell while in recovery, and it isn't giving an error message, just constantly staying as ro. This is using clockword recovery 3.2.0.1.
Anyone know what else I can try?
Thanks for your help.

Do you want to give it a try with root explorer?

Forgot to mention, since I've tried wiping, it now just bootloops. Recovery is all I can get into.
edit:
Just to make it clearer what's happening, I'll do it step by step:
- Load recovery, and open adb shell on my PC
-Mount data in recovery, check it in adb shell and it shows it as read/write
-Go to delete a directory or file, and it say's it's read only, check mounts and it's gone back to ro
-If I unmount and remount, it will go back to being RW, but then the same as above happens.
-My problem is when I try to wipe or format in recovery, it gives an error saying it can't delete a certain file

Managed to fix it now. It appears that while using the Superwipe Full script for Revolution ROM, the file table got completely messed up. I used parted to reformat the data partition as ext2, and I can boot now.

I've managed to get that awful Rom (Destroyer) Manager off of my TF101G and have got Rogue on via PERI and now I'm trying to flash the stock ASUS ICS Rom but can't delete the Dalvik Cache because I'm unable to mount /data
Code:
- - Wiping all user data - -
Formatting /data...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure
Cache wipe complete.
Formatting /cache...
Cache wipe complete.
Wiping dalvik-cache...
Error mounting /data!
I'm assuming that /data is stuck on read only?
Manually fixing permissions and then mounting /data also shows the same error.
HELP :crying:

[Q] Bootlooping with a locked bootloader and unmountable sdcard

Is this phone salvageable? I have quite the odd problem. I have plenty of backups, so I'm not worried about fully wiping the Nexus S.
I was running CM9 Alpha 11 when I heard about the ICS 4.0.4 OTA update for the I9020A. I rebooted into my recovery to make a nandroid backup. That's when the problems started. Mounting /sdcard, /system and /data fail, but mounting /cache works. Attempting to mount to USB Storage gives a "Unable to write to ums lunfile" error. When I noticed that the backups weren't taking, I tried to reboot normally but encountered bootlooping. As a last resort, I tried "fastboot oem unlock" but it freezes. Battery pull gives "FAILED (status read failed (too many links))" on windows.
Model: Nexus S I9020A
HW Version: Rev 16
Bootloader: I9020XXKA3
Baseband: I9020UCKF1
Carrier: ATT
ROM: CM9 Alpha 11
Recovery: ClockworkMod Touch Recovery v5.8.0.2
Bootloader: Locked
Busybox: v1.19.3-cm9
Accessible: fastboot, adb, adb shell with #, busybox, and recovery.
Symptoms: Bootlooping, unmountable /sdcard, /system and /data, cannot mount to USB Storage, bootloader does not unlock.
EDIT: Found this unfortunate bit of news. Looks like I'll be sending it in for repairs and hoping they won't notice the recovery.
EDIT2: I found out that I can flash zip files through a roundabout method to mount /cache as /sdcard. Unfortunately, all I've been able to do is to flash recovery since system and everything else isn't mounted. I haven't been able to get ./flash_image to work. I've tried making the mounts executable as well as flash_image. My last option is looking for the "Android system recovery <3e>" in the form of a .zip and flashing that so it looks like my warranty is still intact.
adb push update.zip /cache
adb shell
mount /dev/block/mtdblock4 /sdcard
Click to expand...
Click to collapse
After this, you can use the recovery to flash the update. So far, I've tested going back and forth between ClockworkMod Recovery 5.0.2.0 and ClockworkMod Touch Recovery 5.8.0.2.
EDIT3: ./flash_image doesn't work. However, flash_image works because I have busybox installed on my phone.

Unable to mount /data

I've managed to get that awful Rom (Destroyer) Manager off of my TF101G and have got Rogue on via PERI and now I'm trying to flash the stock ASUS ICS Rom but can't delete the Dalvik Cache because I'm unable to mount /data
Code:
- - Wiping all user data - -
Formatting /data...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure
Cache wipe complete.
Formatting /cache...
Cache wipe complete.
Wiping dalvik-cache...
Error mounting /data!
I'm assuming that /data is stuck on read only?
Manually fixing permissions and then mounting /data also shows the same error.
HELP :crying:

I have the same problem. I know what lead me to it.
Its an Asus SL101
I have cyanogenmod correctly installed. In order to install a megatron rom I downloaded their app called megatron apps. Trying to download a rom from them I got validation error at end of download and I make the stupidity of change the download dir from /mnt/sdcard to /sdcard and then when I restart again it doesn´t load and CWM recovery give me the same errors (unable to mount /data or unable to mount /sdcard when cleaning cache or trying to restore a backup ).
The only thing I have been able to do its to install Rogue XM Recovery 1.5.0 instead of CWM 6.x ) but the problem to apply an update or restore a backup persists.
Any idea ?

Aaargh.
After a year and a half of heavy CWM and TWRP usage, this has suddenly happened to me too, possibly after flashing the updated TWRP blob from Goo Manager (although that's conjecture at best). My ROM (RaymanFX' CM10 v6) is fine in everyday use - no problems whatsoever, but now I want to update, and my recovery won't let me.
In the hope that something simply went wrong during recovery blob flash, I successfully deleted TWRP and flashed a different recovery (latest CWM) from ROM Manager, but the new recovery can't mount anything either - neither sd card, data, or cache. The error messages are more or less identical to TWRP's errors. My system MAY be readable, but I can't backup or restore or flash anything anyway, so I don't dare format it.
I don't have a Windows PC, so I haven't tried Easy Flasher. I could try it on my work computer if there's no way around it and if neither OSX or Ubuntu can help.
Any suggestions?

Error updating CM13, and others.

Hi, i have the next versions:
CyanogenMod: 13.0-20161004-NIGHTLY-osprey
Kernel: 3.10.49-MPI24.107-56-g09ff0d1
And when trying to install the 1009-NIGHTLY update i get an error without a log in the cianogenmod recovery. When I try to "Apply update" and then "Choose from emulated", it shows the next message:
"E:failed to mount /data (Invalid argument)
Installation aborted"
Then, i go to see the recovery logs, but it blanks and shows the main menu again.
Why do I want to update to the latest version, having 5 days of difference with the installed version?
Because I'm having repeatedly bugs with the Firefox browser, can't update Telegram, can't connect via Bluetooth to the most of the devices, can't update the binaries of SuperSU, and other minor errors.
Which could be the cause of some of this problems?
Sorry for my poor english, Saludos!

Download the latest nightly and before installing wipe the /system /dalvik cache and /cache partition, just be aware that you will need to reflash your gaps package.

Henriquefeira said:
Download the latest nightly and before installing wipe the /system /dalvik cache and /cache partition, just be aware that you will need to reflash your gaps package.
Click to expand...
Click to collapse
Just did what you said, wiped /cache and /system partition, and when the phone reboots it stays in the Motorola logo. Seems that I can't load the installer using USB, because there is no ROM installed.
The good news are that I have access to emulated.
What am I doing wrong?

Gonzon said:
Just did what you said, wiped /cache and /system partition, and when the phone reboots it stays in the Motorola logo. Seems that I can't load the installer using USB, because there is no ROM installed.
The good news are that I have access to emulated.
What am I doing wrong?
Click to expand...
Click to collapse
You wiped your entire internal storage? If not then there is an issue with your internal storage. I once had a similar issue to this, where my phone would keep wiping it's internal storage and crash a lot, the solution was to reflash the stock ROM. Sorry for the inconvenience that I caused to you

Just as a side question, did anyone got AICP nightlies .zip stuck at extracting image to /system? I tried clean install (wipe /system, /data, /cache and dalvik) but its just stuck there. Tried multiple nightlies. Tried deleting Android and .android_secure folders in both external and internal storage. I haven't tried wiping internal storage yet (I will do it ASAP). Any tips will be great. Thanks
Broadcasted from Zeta Reticuli

Henriquefeira said:
You wiped your entire internal storage? If not then there is an issue with your internal storage. I once had a similar issue to this, where my phone would keep wiping it's internal storage and crash a lot, the solution was to reflash the stock ROM. Sorry for the inconvenience that I caused to you
Click to expand...
Click to collapse
I still don't know why cm installs a recovery that it is unstable and with less tools than TWRP. I believe that they should use at least the code of TWRP.
No problem Henriquefeira, everything has it's solution. Besize, your help was too much better than silence in this post. Now, I have to focus on try to enter to the internal storage and flash the update I have.
For that, I'm using fastboot in linux. But I don't know too much about using it. Next, I'll show you the messages that the terminal sent me:
Code:
[email protected]:~$ fastboot -p xxxxxxxxxx flash /data/media /home/imperial/Android2/cmupdater/cm-13.0-20161009-NIGHTLY-osprey.zip
target reported max download size of 268435456 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 91972855 is not a multiple of the block size 4096
fastboot: /build/android-tools-hIu7Bj/android-tools-4.2.2+git20130529/core/libsparse/sparse.c:143: write_all_blocks: Assertion `pad >= 0' failed.
Abortado
Do you know what it means?

Gonzon said:
I still don't know why cm installs a recovery that it is unstable and with less tools than TWRP. I believe that they should use at least the code of TWRP.
No problem Henriquefeira, everything has it's solution. Besize, your help was too much better than silence in this post. Now, I have to focus on try to enter to the internal storage and flash the update I have.
For that, I'm using fastboot in linux. But I don't know too much about using it. Next, I'll show you the messages that the terminal sent me:
Do you know what it means?
Click to expand...
Click to collapse
You can't flash the zip of a ROM via fastboot, follow this tutorial >goo.gl/JfRzZu and on the next time avoid installing the CM bundled recovery

Solved.
I flashed vía fastboot a stable twrp, then after a lot of errors and strange things i was able to flash the ROM.
Thanks a lot for your help.
I was seeing a bricked phone already jajaja.

[A510] Can't mount /data on any recovery

Hi,
I wanted to reset my 510 to a fresh 4.4.4 install. So I decided to "restore to factory settings" within the android system settings menu.
kitkat CM12 4.4.4 by shreps was working fine before, I just wanted to get rid of the data in order to give the tablet away.
now I'm stuck with a soft bricked device, it seems:
- when starting the tablet, the CM screen shows, but freezes after a while
- flashing any CM version in CWM 6..0.5 by shreps shows a "error: can't mount /data"
- wipe cache / data shows the same error
- wipe dalvik cache doesn't seem to respond in any way
- I reflashed CWM 6.0.5 using fastboot flash recovery, but to no success..
what options do I have now? can I format and remount the /data partition via ADB? do I need to go to stock?if, so, how?
Thanks for your ideas!

ok, via
fastboot -w -v
i could reformat the data partition somehow.
I still got an
E:unknown volume for path [/sd-ext]
error, but it continued and works for now.

huedrant said:
ok, via
fastboot -w -v
i could reformat the data partition somehow.
I still got an
E:unknown volume for path [/sd-ext]
error, but it continued and works for now.
Click to expand...
Click to collapse
Glad you dot it going.
I just pulled my 701 out of retirement (broke my Sony z2 screen trying to change my battery) so taking a look in here.
The data format has always been a bit twitchy, but I run the latest version of TWRP for KK. I remember bricking my original Data partition wiping it because some bozo used the wrong partition info making the original recovery for JB. Exchanged the tab.
I recall the bootloader version had to match what version of the ROM you installed (JB, KK, etc), and maybe the recovery also (can't remember). Latest TWRP for KK seems to work for me as I installed Pac Rom before I retired it. TWRP Ver 2.7.1.0
As with the "Path to ext SD", that's always been there if I recall. Just means you have to install a ROM from internal memory. Although my TWRP seems to mount it fine.
But I will say, feels like I've entered the dark ages again.