twrp unmounting system b4 flashing. Help!!!!!!!!!! - Moto G5S Plus Questions & Answers

I'm having trouble flashing android 10 Roms as system is automatically unmounting b4 flashing and an error as shown below pops up.
please help.....
it all started after flashing the new Pitch Black recovery.
but it works fine when I flash pie ROms.
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc1./by-name/system at /system: Invalid argument
unmount of /system failed; no such volume

Amigo intenta volver a la anterior ROM debe ser algún error en la ROM

∆D!n0 said:
I'm having trouble flashing android 10 Roms as system is automatically unmounting b4 flashing and an error as shown below pops up.
please help.....
it all started after flashing the new Pitch Black recovery.
but it works fine when I flash pie ROms.
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc1./by-name/system at /system: Invalid argument
unmount of /system failed; no such volume
Click to expand...
Click to collapse
Is your problem solved??
If not reply this message

Related

CyanogenMod stuck on boot screen Xperia Z

I just installed CyanogenMod using the instructions from the CM wiki using the latest STABLE release.
When I booted my device, it was stuck on the CyanonMod loading screen (blue looping circle). I've wiped and reinstalled multiple times but cannot fix the problem.
I used the ClockWordMod "show log" command from the advanced menu, and got this:
I : Can't partition non-vfat: datamedia
I : Can't partition non-vfat: auto
I : Can't format unknown volume: /emmc
mount: mounting /dev/block/platform/msm/sdcc.1/by-name/userdata on /data failed: Invalid argument
W: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata (Invalid argument)
The last line probably refers to my attempt to wipe the dalvik cache
I've noticed that CWM can't mount /data
Solved by installing TWRP recovery. Apparently CWM does not support encrypted partitions.

Failed to change /cache file system from ext4 to f2fs

Hi guys... i want to ask whether anyone know how to solve this error,....i was succeed to change file system of /system and /data from ext4 to f2fs but i've got this error message after i'm trying to change file system of /cache by using twrp v2.8.70 :
E: mkfs.f2fs -t 1 /dev/block/mmcblk0p4 process ended with ERROR=255
E: Unable to wipe '/cache'
E: Error changing file system.
Thanks in advance for your attention

Data recovery, how to mount messed up /data - Internal SD - sda25 in Recovery/ADB

Hi:
I've messed up my Note 9 pretty bad, such that no partitions mount in TWRP except cache - I'll need to do a data wipe, but I need to save data that I have in the Internal SD.
I've discovered via fdisk in TWRP that the media part - the Internal SD is partition sda25 - however can
t mount it in the terminal through a simple: mount /dev/block/sda25 /mnt
I get an error: mount failed: Invalid argument
I've tried: mount -t sdcardfs /dev/block/sda25 /mnt
This gives me also an error: mount failed: Not a directory
Mounting with -t vfat or exfat gives the Invalid argument error.
Anyone can help me with how to mount it, so that I may copy data off of it manually? I don't want to lose it. Many thanks.
白い熊 said:
Hi:
I've messed up my Note 9 pretty bad, such that no partitions mount in TWRP except cache - I'll need to do a data wipe, but I need to save data that I have in the Internal SD.
I've discovered via fdisk in TWRP that the media part - the Internal SD is partition sda25 - however can
t mount it in the terminal through a simple: mount /dev/block/sda25 /mnt
I get an error: mount failed: Invalid argument
I've tried: mount -t sdcardfs /dev/block/sda25 /mnt
This gives me also an error: mount failed: Not a directory
Mounting with -t vfat or exfat gives the Invalid argument error.
Anyone can help me with how to mount it, so that I may copy data off of it manually? I don't want to lose it. Many thanks.
Click to expand...
Click to collapse
cant you simply wipe the affected partitions(except data of course)? then flash a rom?
have you tried;
mount /sys/block/sda25 /mydata
or
mount /dev/block/sda25 /mydata
or
adb
mount -o rw /dev/block/sda25/data /mydata
in both cases /mydata is just the mount point so I believe it can simply be called what ever you want including just /data
have you read:
https://android.stackexchange.com/q...data-partitions-in-recovery-mode-in-adb-shell
edit:
by any chance when you first flashed twrp, did you forget to format data?
if yes then flash back stock AP file(original phone's firmware) in Odin AP slot only and you should be good to go.( you shouldn't loose any files in internal storage)

K01A ME70C I can only accesso to fastboot

I all I have an old memopad that I would like to revive for using I in a project. Afetr upgrading to lollipop for mistake I tried to boot in recover through rom manager and obviously it failed
Now I am stuck , I can load fastboot mode and it show unknow bootloader. How Can I revive it?
update:
I followed this tutorial https://forum.xda-developers.com/memo-pad-7/general/downgrade-asus-memo-pad7-me70c-t3735665
I managed to install the temp recovery but I am unable to mount the sd card.
The error seems in the partition structure.
I: Can't partiton unknown volume : /emmc
I Can't patition non-vfat : datamedia
W: failed to mount /dev/block/platform/intel/by-label/ fata ( invalid argument)
Can't partition device : /sdcard
Click to expand...
Click to collapse

Question Every custom ROM I flash is stuck on their bootscreen

Hello.
I have a Redmi Note 10 Pro (8GB RAM Version) with an official unlocked bootloader.
I have managed it to install TWRP, TWRP works, that means, I can boot into it, and use it.
But if I flash a ROM ZIP file over TWRP, every custom ROM gets stuck at its bootscreen. It shows the
bootscreen of the offending custom rom, then nothing happens anymore, its just stuck there.
Does anyone here know, wht I do wrong?
Regards
Try flashing the fastboot firmware using pc so that it may fix corrupt partitions, if any.
or maybe the universe is conspiring against you
Can you tell me how I do that (Flashing over pc?)
ME20001 said:
Hello.
I have a Redmi Note 10 Pro (8GB RAM Version) with an official unlocked bootloader.
I have managed it to install TWRP, TWRP works, that means, I can boot into it, and use it.
But if I flash a ROM ZIP file over TWRP, every custom ROM gets stuck at its bootscreen. It shows the
bootscreen of the offending custom rom, then nothing happens anymore, its just stuck there.
Does anyone here know, wht I do wrong?
Regards
Click to expand...
Click to collapse
Try to format data with yes before and after you flash a ROM via twrp
Tried to format data with yes, shows following errors:
Failed to mount `/system_ext´(Invalid argument)
Failed to mount `/product`(Invalid argument)
Updating partition details...
Failed to mount ´/system_ext`(Invalid argument)
Failed to mount `/product`(Invalid argument)
...done
Full SELinux support is present.
MTP Enabled
Done.
You may need to reboot recovery to be able to use /
data again.
TWRP will not recreate /data/media on an FBE device.
Please reboot into your rom to create /data/media [Note from the narrator: Thats not possible, every ROM stucks on boot]
Formatting Metadata using mke2fs...
Done.
Updating partition details...
Failed to mount ´/system_ext´(Invalid argument)
Failed to mount ´/product´(Invalid argument)
...done
ME20001 said:
Tried to format data with yes, shows following errors:
Failed to mount `/system_ext´(Invalid argument)
Failed to mount `/product`(Invalid argument)
Updating partition details...
Failed to mount ´/system_ext`(Invalid argument)
Failed to mount `/product`(Invalid argument)
...done
Full SELinux support is present.
MTP Enabled
Done.
You may need to reboot recovery to be able to use /
data again.
TWRP will not recreate /data/media on an FBE device.
Please reboot into your rom to create /data/media [Note from the narrator: Thats not possible, every ROM stucks on boot]
Formatting Metadata using mke2fs...
Done.
Updating partition details...
Failed to mount ´/system_ext´(Invalid argument)
Failed to mount ´/product´(Invalid argument)
...done
Click to expand...
Click to collapse
Try to flash stock ROM via PC with mi flash (important don't lock bootloader in miflash)

Categories

Resources