Hi, i didn't use my m8 for a while. I had flashed a Liquid-Smooth Lollipop-Rom and wanted to setup the phone again until i noticed that the external SD card is not mounted and not recognized at all.
SD card itself is not the issue, i tried it on different phones and computers, it worked all fine, formatted it in FAT32 etc.. It's working on any other system, but not with the m8. Also other cards are not working with the phone.
I tried PhilzRecorvery and TWRP and the Cyanogenmod 12+13 (using adb sideload), no changes at all.
My Phone is S-ON, at the moment i use TWRP v2.8.7.0 and Cyanogenmod 12.1.
Using the partitioning function of TWRP it says
E: Unable to locate device or partition
Click to expand...
Click to collapse
If i go to the Wipe menue and select "Micro SDcard" and "SD-Ext" it says:
E: mkdosf process emded with ERROR=1
E: Unable to wipe ' /external_sd' .
E: Unknown MTP message type: 1
E: Unable to wipe 'external_sd'
Updating partition details...
...done
Updating partition details...
...done
Click to expand...
Click to collapse
I hope these are all the necessary infomations. I am not very experienced in modding android, but at least i know how to flash roms and the basic sdk-plattform tools, whatever.
Thank you very much and please be kind, i am not an expert!
Related
Tried to install the RCMixHD v0.13 rom today and the installation fails. I get:
-- Installing:SDCARD:RCMixHD_v013 .zip
Finding update package...
Opening update package...
Installing update...
Formatting CACHE:...
Formatting SYSTEM:...
Deleting files...
E:Can't mount /dev/block/mmcb1k0p2
(File exists)
Deleting files...
Deleting files...
Copying files...
E:Can't mount /dev/block/mmcb1k0p2
(File exists)
E:Can't mount SDEXT:
E:Failure at line 11:
copy_dir PACKAGE:data SDEXT:
Installation aborted.
Click to expand...
Click to collapse
Is this me doing it wrong or is there some bug? I'm able to install roms just not this one.
EDIT: i've tried the desireZ rom aswell and that failed. I also noticed the line "E:Can't mount SDEXT:" and tried an sd card with an ext3 partition but it then failed to mount the fat32 (/sdcard) partition but was able to mount the ext partiton (/sd-ext). From what I've been reading its because it doesn't have an ext partition, but as I said when I do it then doesn't mount the non-ext partition.
I too was having similar issues and found that re-partitioning and formatting the card did the trick. Also I had a 700mb partition before which I have increased to 1gb.
Phil
Had the same problem myself.I ended up putting a stock rom on to access market place, installed rom manager which I partitioned with then ran hd rom and it worked.Only problem I have now is its stuck in a boot loop lol and not sure how to fix it but hey good luck.
Cool. Got it to work, using stigslim's method of using ROM manager had a slight issue with it saying the Rom wasn't signed but I turned off the verification then it worked fine. No boot loop.did use the wrong SD card though. *Facepalm*
thanks
Can you tell me what procedure you went through in recovery, if I follow your tracks I might get rid of the restart problem I have.cheers
pnw said:
Cool. Got it to work, using stigslim's method of using ROM manager had a slight issue with it saying the Rom wasn't signed but I turned off the verification then it worked fine. No boot loop.did use the wrong SD card though. *Facepalm*
thanks
Click to expand...
Click to collapse
what did u do ?
Exact same error as I got yesterday.. had to restore my sd card and restore to previous state. I assume there's something causing this rom to fail.
Hi there,
I was about to flash a new rom on my Dinc, and right after I formatted /system, the sdcard became unable to mount and now I can't access the .zip for the new rom. I've tried flashing 3 versions of CWM as well as one of TWRP but none of them can access my SD card. I also reformatted it in my PC with no success. I currently don't have any operating system on it so all I can work with is hboot and recovery.
Can anyone help me fix this?
egunth said:
Hi there,
I was about to flash a new rom on my Dinc, and right after I formatted /system, the sdcard became unable to mount and now I can't access the .zip for the new rom. I've tried flashing 3 versions of CWM as well as one of TWRP but none of them can access my SD card. I also reformatted it in my PC with no success. I currently don't have any operating system on it so all I can work with is hboot and recovery.
Can anyone help me fix this?
Click to expand...
Click to collapse
Did you format it fat32 with the pc? If the cards fine (can be used by pc and fat32) and recovery and hboot still cant find it, then id venture to say the sdcard slot is damaged or went out.
Using adb in recovery, you should be able to push a rom file to emmc and flash it from there.
cmlusco said:
Did you format it fat32 with the pc? If the cards fine (can be used by pc and fat32) and recovery and hboot still cant find it, then id venture to say the sdcard slot is damaged or went out.
Using adb in recovery, you should be able to push a rom file to emmc and flash it from there.
Click to expand...
Click to collapse
I did format it FAT32, and the SD card is definitely fine. I don't think that the slot is the problem either because other things won't mount either.
Actually the only thing I can mount in recovery is /system, everything else is inaccessible. It was having mounting problems before which is why I decided to flash it with a new rom (was running Jellybean very poorly). I also tried flashing the original recovery, doing "clear storage" that way, and reflashing with CWM but it had no effect. During the storage wipe it said that /datadata doesn't even exist. It also shows errors that it can't mount the files /dev/block/mmcblk01 and /dev/blk/mmcblk0p2
This is what the log shows when I did the CLEAR STORAGE using the stock recovery
Restore factory NV setting...
Formatting DATA:...
E: format_root_device: can't find mtd partition "datadata"
Formatting EMMC:...
Formatting CACHE:...
Wipe ALL failed.
E:Can't mount DATADATA:recovery/log
E:Can't mount /dev/block/mmcblk0p2 (or /dev/block/mmcblk1)
(No such file or directory)
The same thing happened to me long back. What I did was that I cleared data, cache, and dalvik cache... Worked for me... You can try but i wont take any responsibility
Sent from my HTC Salsa C510e using XDA
Hello friends, i hope you can help me because i ****ed up real bad today... I was in cwm recovery, and press some button that said something like "format for rom" or something like that... Now i dont have any SO installed, no rom on my phone, and it says i have 0mb avalaible. So i flashed the TWRP recovery because im more familiar with it, i have tried sideload but get this error con the cmd window after it gets to 100% * failed to write data 'protocol fault (no status)' *
On the phone i have: E: No valid storage partitions.
Any help please? Already tried adb push rom.zip /data or /sdcard but since i have 0mb for storage on my phone i think any of that will work. I can flash recoverys, but cant move any rom to my phone to flash Help please
Ok it seems that i was able to push the rom.zip to my /system but when i try to flash it, it says:
E: Unable to mount /data
E: Unable to find storage partition to mount to usb
worms45 said:
Ok it seems that i was able to push the rom.zip to my /system but when i try to flash it, it says:
E: Unable to mount /data
E: Unable to find storage partition to mount to usb
Click to expand...
Click to collapse
What carrier are you on?
How does that matter? The phone was originally at&t. I need to format my storage or my /data or something to be able to install the rom
Hello everyone,
I have a little problem with TWRP on my LG G3 (D855, 32 GB).
I installed TWRP two months ago and flashed CyanogenMod 12.1.
Now I've noticed that TWRP (2.8.6.0) shows the Internal Storage with 0MB.
When I tap the middle Icon on the bottom of the TWRP Main screen, I get an (maybe helpful?) output:
Code:
E: Could not mount /data and unable to find crypto footer.
E: Unable to mount '/data'
E: Unable to recreate /data/media folder.
Updating partition details...
E: Unable to mount '/data'
...done
E: Unable to mount storage
E: Unable to mount /data/media during GUI startup.
Full SELinux support is present.
E: Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
E: Unable to mount '/data'
MTP Enabled
I'm a bit confused. Could this be, because I used CyanogenMod's Device Encryption?
I'm planning on reverting to Stock Rom (...i quite liked it. And considering the camera quality, CM isn't really any better), but i fear this (or flashing anything different) could brick my phone, since there seems to be something strange.
Is there any way to debug or even fix this?
Is it safe to revert to Stock, when TWRP doesn't even detect the Internal Storage? (following this Guide: http://forum.xda-developers.com/showthread.php?t=2785089)
I'd be glad about any help oder hint, about how to proceed. Thanks in advance!
First, update your TWRP version to 2.8.7.0 (available here: http://forum.xda-developers.com/lg-g3/orig-development/recovery-twrp-touch-recovery-2-8-2-0-t2966129 )
Then, boot into TWRP, go to Wipe and choose "Format Data".
After done that, reboot your device into recovery again.
Thank you very much. I will try this.
i had that , but dont remember what i did ,, but i do know you need to format , by fastboot or twrp and repair partitions
It happens often to me when I upgrade.
I use 3 phones: Xperia Z2, LG G3, Samsung Galaxy S2 and when I've updated to Lollipop it happened all three times.
Recently I noticed that also on the S2 happened this and I suppose it's because partitions are not initialized.
I was unable to write to internal partition (0 MB) and I've solve this way:
I've flashed CyanogenMod, mounted the internal memory as flashdrive under windows and simply formated it.
When I've disconnected the phone from the pc, Android was able to write normally to the internal storage and everything worked like a charm.
I know it's not possible (AFAIK) to mount internal memory on stock roms as Mass Storage, but perhaps someone will point you on how to correctly fix partitions without using my method.
Looks like Kill Switch Wiped
Did you find any solution, even i am struggling with same problem. I think LG G3 has kill switch that wiped out everything, but not sure just guess.
Have same problem any help?
Hi,
I tried to flash viperOS using squid twrp for moto G5S, but something in the process i think i did wrong.
My phone model is montana xt1790.
I unlocked the bootloader.
I tried to install the recovery, but had same problem than @dau999
dau999 said:
Bootloader gives me a notification that the img is not signed or corrupt (squids one)
Click to expand...
Click to collapse
I tried to flash "no-verity-opt-encrypt-5.1.zip" file posted as solution here https://forum.xda-developers.com/showpost.php?p=74813124&postcount=23.
After this i have working the recovery, but i believe this is what did wrong:
With debug mode enabled, after a wipe clean (Cache, Data, Dalvik/ART and system) and format data (wipe all your apps, backups, pictures, videos, media and removes encryption on internal storage) got this errors:
Code:
Could not mount /data and unable to find crypto folder.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Unable to mount storage.
Unable to mount /data/media/TWRP/.twrps
Failed to mount '/data' (Invalid argument)
After this errors i flashed ViperOS, but after first boot it, first thing viper OS ask me was the phone password, after i enter it, the phone show up a message saying that password is ok but data is corrupt, restarting and trying to fix my phone without success (same errors like failed to mount /data)
Also i tried to use the "repair or change file system" selecting Data partition, twrp show me this: http://oi65.tinypic.com/2prin8y.jpg, also i got this errors:
Code:
/sbin/fsck.f2fs /dev/block/mmcblk0p54 process ended with ERROR: 255
Unable to repair Data
What should i do?, i don't know is related with an encryption on data partition, or if this can be solve.
EDIT:
Found the solution in reddit: www.reddit.com/r/AndroidQuestions/comments/7w5c75/used_the_format_data_option_in_twrp_recovery_on/
Just fixed the issue after making a second format in TWRP ( WIPE > FORMAT DATA)