Hello to everyone. I am using Xperia M and can not mount data, system mount via TWRP Recovery. I also can not load the stock version and kernel with Flashtool. The device goes into recovery mode, is charged and is recognized as a nickname when connected to a PC. I will be glad if you help me.
didyou said:
Hello to everyone. I am using Xperia M and can not mount data, system mount via TWRP Recovery. I also can not load the stock version and kernel with Flashtool. The device goes into recovery mode, is charged and is recognized as a nickname when connected to a PC. I will be glad if you help me.
Click to expand...
Click to collapse
Your device got ebola. There is no solution. Sorry mate.
Use internal storage 0 mb problem in TWRP Recovery. No flashing kernel and roms.
didyou said:
Hello to everyone. I am using Xperia M and can not mount data, system mount via TWRP Recovery. I also can not load the stock version and kernel with Flashtool. The device goes into recovery mode, is charged and is recognized as a nickname when connected to a PC. I will be glad if you help me.
Click to expand...
Click to collapse
i am having same problem . but my internal storage is mounted as android os and my actual storage is not visible please help me.
fix for 0MB internal storage problem
Your device is still recoverable if you can boot into twrp successfully
Go to advanced --> terminal
Check your partition table with
fdisk -l /dev/block/mmcblk0
it will print out the partition table, last 3 should be system, cache and data
format system with ext4, for me that was /dev/mmcblk0p25 - YOURS MAY DIFFER
make_ext4fs /dev/block/mmcblk0p25
format data with ext4, for me that was /dev/mmcblk0p27
make_ext4fs /dev/block/mmcblk0p27
For me, this was met with errors, so format it with exfat first, mkfs.exfat /dev/mmcblk0p27, reboot into recovery, then format with make_ext4fs.
You cannot do this through advanced wipe, because twrp tries to guess your partitions AFTER mounting them, then reads /system is mounted on /dev/block/mmdblk0p25, but it's not mounted, so no repairing/formatting through that. Use the terminal instead, then reboot, twrp will find the partitions then.
afterwards reboot again into recovery. I didn't have to reformat cache, but you may have to. try mkfs.ext2 on that. You will always want to go with make_ext4fs though.
internal storage should show up again now, wiping and installing zips will work again.
rak-zero said:
Your device is still recoverable if you can boot into twrp successfully
Go to advanced --> terminal
Check your partition table with
fdisk -l /dev/block/mmcblk0
it will print out the partition table, last 3 should be system, cache and data
format system with ext4, for me that was /dev/mmcblk0p25 - YOURS MAY DIFFER
make_ext4fs /dev/block/mmcblk0p25
format data with ext4, for me that was /dev/mmcblk0p27
make_ext4fs /dev/block/mmcblk0p27
For me, this was met with errors, so format it with exfat first, mkfs.exfat /dev/mmcblk0p27, reboot into recovery, then format with make_ext4fs.
You cannot do this through advanced wipe, because twrp tries to guess your partitions AFTER mounting them, then reads /system is mounted on /dev/block/mmdblk0p25, but it's not mounted, so no repairing/formatting through that. Use the terminal instead, then reboot, twrp will find the partitions then.
afterwards reboot again into recovery. I didn't have to reformat cache, but you may have to. try mkfs.ext2 on that. You will always want to go with make_ext4fs though.
internal storage should show up again now, wiping and installing zips will work again.
Click to expand...
Click to collapse
Thank you for your message I just saw. I tried, but I still see the internal memory of 0MB when I try to Wipe.
https://imgyukle.com/i/Rk24Gt
https://imgyukle.com/i/Rk264c
https://imgyukle.com/i/Rk2fyR
didyou said:
Thank you for your message I just saw. I tried, but I still see the internal memory of 0MB when I try to Wipe.
Did you reboot after? You can try the advanced format in twrp, maybe you need to use exfat for your partition 27 (data) or ext3 not ext4 for system. Try some combinations.
Which twrp version is installed?
I checked mine and partitions 25 to 27 are formatted with ext4. I have latest twrp 3.0.2.0 and use lineage 14.1. from here.
Partition table looks fine, same sizes as me.
Click to expand...
Click to collapse
rak-zero said:
didyou said:
Thank you for your message I just saw. I tried, but I still see the internal memory of 0MB when I try to Wipe.
Did you reboot after? You can try the advanced format in twrp, maybe you need to use exfat for your partition 27 (data) or ext3 not ext4 for system. Try some combinations.
Which twrp version is installed?
I checked mine and partitions 25 to 27 are formatted with ext4. I have latest twrp 3.0.2.0 and use lineage 14.1. from here.
Partition table looks fine, same sizes as me.
Click to expand...
Click to collapse
I am using TWRP version 3.1.1.0. I tried to make Wipe after it restarted after operations but it still seems to be 0MB. I tried to change the file system, but not through the terminal.
Click to expand...
Click to collapse
Related
I have a problem with my phone.
I believe that the internal partitions are messed up.
I have tried a couple of guides to fix this but no luck. I get "error formatting /data!" on recovery. I also tried using the formatting tools from adb shell (e2fsck, gparted).
The main problem is that when i restart my phone the /data partition gets wiped, and the phone reboots in blank, no apps no setting (some of them remain).
I wonder if i can solve this by setting my sd-card to be the new /data. I doesn't matter if i have to leave the sd-card on all the time. i mainly use this phone for developing apps.
Thanks.:good:
Felivel said:
I have a problem with my phone.
I believe that the internal partitions are messed up.
I have tried a couple of guides to fix this but no luck. I get "error formatting /data!" on recovery. I also tried using the formatting tools from adb shell (e2fsck, gparted).
The main problem is that when i restart my phone the /data partition gets wiped, and the phone reboots in blank, no apps no setting (some of them remain).
I wonder if i can solve this by setting my sd-card to be the new /data. I doesn't matter if i have to leave the sd-card on all the time. i mainly use this phone for developing apps.
Thanks.:good:
Click to expand...
Click to collapse
It could probably be done if you could get the sdcard to mount at boot, not sure if thats possible. You would need to create a flashable much like the ext4 mod, that edits the init.inc.rc file to mount the sdcard and /data to it. You would want to partition your sdcard with an ext3 or ext4 partition and use that for data.
Yes it can be done. That's how boot manager works, by modifying the ramdisk to load images from sdcard or emmc instead of the partition. I think I have an idea on how to make your request work.
Edit: If you feel like trying a project, what needs to be done is create a file data.img and mount it as loopback using busybox (ROM needs a working busybox).
Then the boot.img needs to be updated replacing the mount /data entry in init.inc.rc with the location of the loopback device and a loopback setup prior to this. The data.img created needs to be formatted ext3 or ext4. I know it's not too detailed but rather just a summary.
Ok, here is the problem, i woke up today, my phone battery was empty, i connected the phone battery was loading, but i couldn't get to the system, after kernel load it stops, like there was no system installed. Everything worked fine day before,my configuration was: Doomkernel and Existenz_2.0.5 ROM.
So, i got to recovery (recovery works,CWM), and there i saw "can't mount cache" error. I got into shell with adb (this works too), and there is no way i can mount any system partition (/system, /cache, /data), what's more important /sdcard does not mount either. So, i'm in recovery, can't install or restore from sdcard,cause /sdcard does not mount.
I'v tried sideload, no go.
I've tried fastboot flash new kernel, and here's interesing thing, fastboot reported that flashing was ok, but i still have Doomkernel (i was trying to flash 6.0-TUX-Core-HD kernel. So seems like fastboot did not write anything at all.
I've tried flashtool with stock tft. It breaks with "final verification error", when i turn "final verification off" it goes all the way, says everything is installed, but when i restarted, still only Doomkernel.
Any ideas ? I take any advice.
Maybe you have already tried it, but format your phone's data, THEN the cache, and finally the internal storage (SD card). In XS's CWM, there's a bug, which causes sometimes an unformatable and unusable cache parition. But this method can be help on this. Maybe this problem causes those unformatable partitions.
Szatyor said:
Maybe you have already tried it, but format your phone's data, THEN the cache, and finally the internal storage (SD card). In XS's CWM, there's a bug, which causes sometimes an unformatable and unusable cache parition. But this method can be help on this. Maybe this problem causes those unformatable partitions.
Click to expand...
Click to collapse
Thank you for your reply. Haven't tried that but i have now and, unfortunately, no go. With /data and /cache seems like format was success but it didn't ( still can't Mount) and with /sdcard format fails (error mounting /sdcard).
Maybe my sdcard really died ?
qrto said:
Thank you for your reply. Haven't tried that but i have now and, unfortunately, no go. With /data and /cache seems like format was success but it didn't ( still can't Mount) and with /sdcard format fails (error mounting /sdcard).
Maybe my sdcard really died ?
Click to expand...
Click to collapse
Well, I don't think so. The "SD Card" is a part of the memory chip, which includes the system, the data and the cache partitions too. Because you cannot copy anything now to the internal storage, try to install a ROM from ADB Sideload if you can. Once it done, your phone can be boot maybe again. If it happens, try to format the internal storage by the Android. If it fails, connect the phone to your computer, and try to format with Windows or (it can be better) Linux to fat32 filesystem.
Szatyor said:
Well, I don't think so. The "SD Card" is a part of the memory chip, which includes the system, the data and the cache partitions too. Because you cannot copy anything now to the internal storage, try to install a ROM from ADB Sideload if you can. Once it done, your phone can be boot maybe again. If it happens, try to format the internal storage by the Android. If it fails, connect the phone to your computer, and try to format with Windows or (it can be better) Linux to fat32 filesystem.
Click to expand...
Click to collapse
Thank you for your ideas. Thing is, all i can start is cwm recovery. As i wrote, i can't install anything with sideload. And no partition is working. When i start parted /dev/block/mmcblk and try to list partitions, i get unrecognized disk label error, when i try to manually set disk label to msdos, there's I/O Error.
And i can't format sdcard, because when in recovery, phone is not detected by Linux nor Windows. But i tried formatting partitions internally, with mke2fs, and with fastboot command. No go.
I know that /sdcard is just a partition, but what i meant was that probably my phone memory chip died, like hardware died. but i'm still looking for new ideas i want to try everything before giving up.
qrto said:
Thank you for your ideas. Thing is, Alp i can start iż cwm recovery. As i wrote, i can't install anything with sideload. And no partition is working. When i start parted /dev/block/mmcblk and try to list partitions, i get unrecognized disk label error, when i try to manually set disk label to msdos, there's I/O Error.
And i can't format sdcard, because when in recovery, phone is not detected by Linux nor Windows. But i tried formatting partitions internally, with mke2fs, and with fastboot command. No go.
I know that /sdcard is just a partition, but what i meant was that probably my phone memory chip died, like hardware died. but i'm still looking for new ideas i want to try everything before giving up.
Click to expand...
Click to collapse
Then maybe it's a HW error really. But maybe just the partition table is corrupted. At this point, I don't know. I have only one suggestion left: Take the phone to the nearest SONY Center or GSM shop/service to investigation. But I think they will say you'll need to replace the phone's motherboard. Anyway, it's an too expensive solution I think, because this phone is a "retired" modell without any update, but with a "blacksheep (Snapdragon S3) SoC.
Hello,
My first gen Kindle Fire has been setup in the OtterX format and has been running well on the CM STG7 ROM. I decided to update to the latest version last week and since then, my OtterX has not recognized the SDCard.
TWRP does see the SDcard and will view it's contents when browsing the file manager, but it won't mount the SDcard to my computer desktop. Nothing happens when I click the mount button.
When the OtterX boots, the System > Storage sees the SDcard and contents, but when I try to browse to it with a file manager, it says the path is invalid.
ADB shell sees the /sdcard/ directory and I can browse it from the shell as well.
I've tried formatting the entire device, including wiping the internal storage and formatting data (where you have to type in "yes") and nothing has resolved this issue.
Any idea what's going on?
I have had similar problem, rebooting a couple of this times seemed to fix.
But may need to reformat in twrp or do otter x partitions in bootloader
sd_shadow said:
I have had similar problem, rebooting a couple of this times seemed to fix.
But may need to reformat in twrp or do otter x partitions in bootloader
Click to expand...
Click to collapse
I'll try reformatting again.
My partitions became corrupted a couple years ago and I had to rebuild them manually, following a tutorial. OtterX partitions in the bootloader doesn't work on my device. I'm guessing it's because the partitions are spot-on with the sizing.
Do you know of a way to rebuild the partitions manually so they match the stock specs - maybe that way the bootloader partitioning would work?
Just restore amazon partitions in bootloader, reboot, restore otter x partitions.
sd_shadow said:
Just restore amazon partitions in bootloader, reboot, restore otter x partitions.
Click to expand...
Click to collapse
Bingo! That seemed to fix it. CM11 is seeing the SDcard just fine now. Thank you!
sd_shadow said:
Just restore amazon partitions in bootloader, reboot, restore otter x partitions.
Click to expand...
Click to collapse
For some reason after trying a different ROM (can't remember which one), I lost my SD card again and I can't seem to get it back. I even reverted the bootloader to FFF and did the "OEM Format", then followed the steps back to OtterX.
Attached is my partition table. I don't see a 'media' table, which is the SDcard, correct?
Any idea what else to do?
Otterx utilizes space that was already there, but reserved for the system. In order to better use available space for user data, the storage is placed elsewhere on the tree. The sd card should be located under storage on the otterx tree.
Ixthusdan said:
Otterx utilizes space that was already there, but reserved for the system. In order to better use available space for user data, the storage is placed elsewhere on the tree. The sd card should be located under storage on the otterx tree.
Click to expand...
Click to collapse
The strange thing is TWRP sees and accesses the SD card just fine.
I have a feeling the SD card isn't formatted in the correct format. Any idea how to format (or check/change format type) of the SD card through ADB?
Did you try the Repair file system in TWRP?
In OtterX Twrp 2.7.1.0 not 2.7.0.1
Wipe>advanced wipe
check data>current file system should be f2fs
tap Repair or change file system if you want to change back to ext4
sd_shadow said:
Did you try the Repair file system in TWRP?
In OtterX Twrp 2.7.1.0 not 2.7.0.1
Wipe>advanced wipe
check data>current file system should be f2fs
tap Repair or change file system if you want to change back to ext4
Click to expand...
Click to collapse
Just checked the partitions with TWRP 2.7.1.0...
Dalvik Cache - Invalid partition selection
Data - f2fs
Internal Storage - Invalid partition selection
Cache - f2fs
System - ext4
I then formatted data as ext4 and the ROM still doesn't see the SD partition.
MrBrady said:
Just checked the partitions with TWRP 2.7.1.0...
Dalvik Cache - Invalid partition selection
Data - f2fs
Internal Storage - Invalid partition selection
Cache - f2fs
System - ext4
I then formatted data as ext4 and the ROM still doesn't see the SD partition.
Click to expand...
Click to collapse
did you try the repair option?
sd_shadow said:
did you try the repair option?
Click to expand...
Click to collapse
Yup! Didn't seem to fix the issue.
Is there a way to put the Kindle back to 100% factory specs, like SBF for the Droid X or Odin for Galaxy S3?
VZW SGSIII
Is this what you used to re-partition the system, data, and cache partitions?
[HOW TO] Fix "Failure to mount" sdcard, system, data or cache
Hey dudes,
accidentially i formatted /system in f2fs, TWRP crashed and since then its gone.
gyazo.c o m/d977dd6dfe5d4e2f78f10ac2f0695609
Thats the output of the fstab file
I see no way how to restore partitions, just for SD card, someone knows what to do?
greetings
celtaV
celtaV said:
Hey dudes,
accidentially i formatted /system in f2fs, TWRP crashed and since then its gone.
gyazo.c o m/d977dd6dfe5d4e2f78f10ac2f0695609
Thats the output of the fstab file
I see no way how to restore partitions, just for SD card, someone knows what to do?
greetings
celtaV
Click to expand...
Click to collapse
TWRP / Wipe / Advanced Wipe / Format Data
Reboot Recovery
Flash a Rom
If that doesn't work you'll need a RUU.zip
rename the RUU.zip to 0PJAIMG.ZIP, place it on a ext sd card formatted in FAT32 (a 16 or 32gig one should work), reboot into DOWNLOAD_MODE, agree and it should flash.
I tried to install a RUU but i have not renamed it to 0PJAIMG and pushed it on the device
anyway, i got help by the #twrp IRC channel, i formatted the /system partition with ext4 via adb again, because it was emmc (there was no filesystem on it) and not f2fs.
greetings
celtaV
Hello,
I am unable to modify the partition table. I tried parted and gdisk. Both seems working, that means I didnt get any error message. For example I deleted a userdata partition via gdisk a tried to write changes to disk, it finished with success but when I reopened the table, there was the old one.
In addition, system, cache, userdata partitions seems to have 0mb and cant be mounted. In gdisk,fdisk when I view the partition table, these partitions have normal size according to the start and end sector.
I use TWRP 3.0.2-0 , I can go ADB - recovery, sideload. To fastboot. But I cant chcange the recovery, or remove TWRP, when I fastboot flash other recovery on boot, nothing change at all and TWRP boot again.
It seems to me that the phone is read only, but on the other hand I can upload files by adb push cmd.
Do u have any idea what to do?
jirikolar said:
Hello,
I am unable to modify the partition table. I tried parted and gdisk. Both seems working, that means I didnt get any error message. For example I deleted a userdata partition via gdisk a tried to write changes to disk, it finished with success but when I reopened the table, there was the old one.
In addition, system, cache, userdata partitions seems to have 0mb and cant be mounted. In gdisk,fdisk when I view the partition table, these partitions have normal size according to the start and end sector.
I use TWRP 3.0.2-0 , I can go ADB - recovery, sideload. To fastboot. But I cant chcange the recovery, or remove TWRP, when I fastboot flash other recovery on boot, nothing change at all and TWRP boot again.
It seems to me that the phone is read only, but on the other hand I can upload files by adb push cmd.
Do u have any idea what to do?
Click to expand...
Click to collapse
hi.. use aparted app "link https://play.google.com/store/apps/details?id=com.sylkat.AParted" ... for me works perfectly and you can choose a lot of type partitions " but you have to reading message in app when saying that you have to unmount sd card "
olibub said:
hi.. use aparted app "link https://play.google.com/store/apps/details?id=com.sylkat.AParted" ... for me works perfectly and you can choose a lot of type partitions " but you have to reading message in app when saying that you have to unmount sd card "
Click to expand...
Click to collapse
Currently I have no ROM installed because I cant mount userdata and system partition. So I cant use your app.