I had come across this bug in TWRP recovery where the /system partition was unable to mount.
And i wasn't able to flash any new ROM or even backup current ROM.
Hopefully I had another ROM backed up before and I simply formatted the system and VIOLA! the problem was gone.
I posted this for anyone who might get such a problem in the future and doesn't end up cursing themselves.
Its a common bug and very easy to fix. So, Happy Flashing!
This basically work for any partition not mounting error.
Hit thanks if it helped
Help me fix my twrp
Pls, I have been on this platform for some time now. I have a challenge presently with my phone Tecno LB8A. I have been trying to upgrade it to version 10. I have unlocked the bootloader, rooted it and also flash twrp into it. I downloaded Lineage 17 and havoc but I bricked my phone severally. In twrp, I discovered there is no system partition there. Pls I need your guide on how to make the system appear. What I have on the partitions there are: dalvic cache, cache, data,sdcard, otp and internal storage. The second question bis how do I flash Lineage into it without bricking the phone
Related
So tonight I decided to wipe my tab pro 10.1 wifi (SM-T520) and flash the same ROM I've been using for ages (GraveDs 3.0). I just boot into recovery (TWRP 2.7.0.1) like I always have, start wiping everything except extSD. It hangs during wipe and automatically reboots into a bootloop. I get a mild heartattack and now my tab is bricked. I can still get into recovery but can basically do nothing in it because it can't mount data. At first it couldnt mount cache only, but now it can mount cache but not data.
Is there any manners of ways I can unbrick this? I've never really had any issues before
I've read somewhere that you can use the TWRP Terminal to manually format your partitions, but I wouldn't even know where to begin to find the commands that work with my specific tablet. I've been Googleing all day and can't find anything relevant to SM-T520 I also have no nandroid backup because idiocy.
Any help, anything at all, is greatly appreciated.
Fixed it by flashing newest version of TWRP (v2.8.7.0) using Odin 3.07, then I used the new feature under wipe in TWRP to format my data partition into a different file format then back to the original file format and it was finally mountable and flashable again. Thank the lord for that!
Glad to hear you fixed it quickly
HELLO, and thanks for reading me, so today i made the jump and wanted to upgrade stock rom of my xperia S, to the marshmallow rom via rtwp.
so i unlocked the bootloader proprely,but while merging the partitions 14 and 15 to increase the volume, i think something went wrong, after that i managed to continue the process and pushed the rom, i even got the loading screen witch ended ( of course ) by "encryption unsuccessful" and looploading.
inside the twrp i see that the sd card is 0 mb and cannot be accessed or wiped or formatted, i always have lot of errors :
cant't mount /data ( no such device ).
unable to mount storage.
unable to wipe /sdcard.
unable te recreate and sec-folder.
i tried many tricks but nothing is happening, so i flashed again to rtwp and its loopbooting to it, even the rom is lost and adb shell doesnt recognize the device.
fastboot is actually the only thing have access to.
please i need help, i'm desperate !
lotfix said:
HELLO, and thanks for reading me, so today i made the jump and wanted to upgrade stock rom of my xperia S, to the marshmallow rom via rtwp.
so i unlocked the bootloader proprely,but while merging the partitions 14 and 15 to increase the volume, i think something went wrong, after that i managed to continue the process and pushed the rom, i even got the loading screen witch ended ( of course ) by "encryption unsuccessful" and looploading.
inside the twrp i see that the sd card is 0 mb and cannot be accessed or wiped or formatted, i always have lot of errors :
cant't mount /data ( no such device ).
unable to mount storage.
unable to wipe /sdcard.
unable te recreate and sec-folder.
i tried many tricks but nothing is happening, so i flashed again to rtwp and its loopbooting to it, even the rom is lost and adb shell doesnt recognize the device.
fastboot is actually the only thing have access to.
please i need help, i'm desperate !
Click to expand...
Click to collapse
Do you know about adb sideload?it can help you in this case.
Check your partition if you merged p14 n 15 correctly or not.
Convert data and cache to ext4 and again return to f2fs.
without merging p14 and p15 the marshmallow rom can boot but you can only use 2 gb as data.
The MM requires
System as ext4
cache and data as f2fs.
so check if you done this.
ok, just figured out where the error was after merging the 2 partitions i skipped the last step after writing partition
mkfs.f2fs -r 16384 /dev/block/mmcblk0p14
that's because i followed another tutorial rather than xda ! so basically MY FALT !
but to restore my phone the only method that worked is to use flashtool and go back with original tft !!
after following the "right" tutorail everything went fine ! and i have a mooth brand new phone on marshmallow :laugh:
lotfix said:
HELLO, and thanks for reading me, so today i made the jump and wanted to upgrade stock rom of my xperia S, to the marshmallow rom via rtwp.
so i unlocked the bootloader proprely,but while merging the partitions 14 and 15 to increase the volume, i think something went wrong, after that i managed to continue the process and pushed the rom, i even got the loading screen witch ended ( of course ) by "encryption unsuccessful" and looploading.
inside the twrp i see that the sd card is 0 mb and cannot be accessed or wiped or formatted, i always have lot of errors :
cant't mount /data ( no such device ).
unable to mount storage.
unable to wipe /sdcard.
unable te recreate and sec-folder.
i tried many tricks but nothing is happening, so i flashed again to rtwp and its loopbooting to it, even the rom is lost and adb shell doesnt recognize the device.
fastboot is actually the only thing have access to.
please i need help, i'm desperate !
Click to expand...
Click to collapse
I encountered this issue more than once
The 1st time I managed to fix it by Emma the xperia official flashtool and returned to stock
The 2nd time I just flashed doomlord. Kernel with CWM booted to cwm wiped data and internal and then reflashed twrp and all was good with our errors..
I think it's something with twrp having trouble updating to the new partition table. I hope this works for u
I have the same problem, and after recovering to stock with emma I still cant see my SD card, not even on the computer. No internal storage for my Xperia S, it shows its empty.
What to do?
Hello I encounter the same problem while I try to flash to 7.1.2 from 6.0 . Sd card is 0 mb. Is there anyway to fix this ? I cant even flash stock rom any more uploaded some
I've recently updated my htc 10 to Android 7.0 using the 2.38.617.6 firmware and added twrp to use for backup purposes. I have attempted to root the device with chainfire's supersu, but failed due to data being in the wrong format.
First off, I managed to find out the the system partition is ridiculously large (17,592,186,044,365 MB) leading me to believe that the system partition has been corrupted.
I've checked the format type for each partition (data, system and cache) they check out to be ext4.
As the title of the post states, I've also ran into that problem before the system partition size issue.
Also, when trying to reboot the system through twrp, I get the message, "No OS Installed! Are you sure you..." but the phone boots up just fine.
Any help is appreciated.
ensure you flashed the latest unoffical twrp from the xda twrp thread. not the official one.
j to the 4n said:
ensure you flashed the latest unoffical twrp from the xda twrp thread. not the official one.
Click to expand...
Click to collapse
I have fixed the issue. I had to find and flash the latest ruu because I had restore the /data partition from when I had the phone rooted and downloaded xposed. I ran through the same process after the flash without restoring the data partition and now it work.
Only downside is that I can't restore my data until xposed has a compatible framework. Thanks for replying.
I got a clean backup of the twrp formatted the sd card with external memory I mounted the backup in the external sd and restored the system .... With that I was successful:dedos cruzados::dedos cruzados:
I was running oos based nougat custom rom with blu spark recovery. Then flashed official ob1, didnt like it, wiped cache/data/system and reinstalled my old oos nougat rom (audax 4.7.6). Now i get the above mentioned message..
Things i tried:
- addionally wipe internal storage and media (installed rom via adb sideload then)
- reformat system/cache/date with ext4
I googled the error and for most people (threads werent particularly concerning the op5t however) it seems that just wiping data and reinstalling the rom did the trick. Not for me though..
What can i do now?
Solution: reformating the data partition with ext4 is not enough. I had to format to FAT and right after that again to ext4, reboot to system and boom, it worked!
PS: i wonder what data is on the internal storage partition that i deleted? I didnt have any data on the phone, i just wonder.. It isnt somehow crucial to the phone?!
I think the decryption key is somehow embedded into the internal storage as wiping /data does not delete the PIN/pattern. Might be a hidden partition or something similar that is not wiped when wiping /data as long as it is ext4.
Your data is gone. It failed to completely encrypt and now there's nothing that can be done. Format /data as ext4 and let it try encrypting again
I have the same problem exactly. Can you explain in steps you have installed then format or how?
I have the same problem exactly. Can you explain in steps you have installed then format or how?
Click to expand...
Click to collapse
I had the exact same problem. But it is an easy fix but does require wiping your internal storage.
So the save way of doing this would be:
1. Backup all your data by going to TWRP or your ROM if that still works. Plug in an USB cable and use MTP or the adb pull command to backup your data
2. Reflash OB1 with no root (like Magisk of SuperSU) if you have TWRP. This will cause you to have the stock recovery again. I also recommend to do a clean flash (Wiping system and data before flashing the rom).
3. Download the rollback build from Oneplus [HERE] and copy this to the internal storage.
4. Boot into the stock recovery flash the rollback build. THIS STEP WILL WIPE YOUR INTERNAL STORAGE.
5. Now you have OxygenOS 4.7.5. Download OxygenOS 4.7.6 Incremental Update [HERE]
6. Go back to the Stock recovery and flash the incremental 4.7.6 zip.
7. You have the latest version now. So boot to fastboot reflash TWRP and flash SuperSU or Magisk in TWRP to regain root
Guys I did a fail, i had OB3 installed, and I wanted to try RR so I wiped system and when I tried to install I have seen error 7 saying its for dumpling not for oenplus5t.
So I restored.... But instead restoring OB3 I have restored stock Nougat rom -.- I have even stock recovery now, what is the best way to fix it?
Can i change to FAT and stay and dont go back to ex4 again?
Hi i don't know if u r reading this but if you are please help me cause I'm so lost and confused over this since yesterday...
so 2 days ago my phone started lagging and hanging and freezing until i realized i have got this issue with data encryption
i have a rooted sony z2 with TWRP Custom recovery
first i didn't know it was with data encryption failure so i literally factory reset and installed all my apps and data again and again!!! after every time my phone started to lag !!
after one whole day of trying everything i finally realized its actually with the data encryption and i should change my ex4 to something else... so here again i wiped the phone and changed to ex3 and installed and all my data and apps all over again
but after a couple hours...same problem again.....
im literally so tired of not knowing what to do ! my head hurts so much due this ugh....
i havent changed to FAT from ex3 so im wondering if it will finally solve my problem permanently if i change to FAT ??
And if it did can i just keep it on FAT forever ?
Please guide me thanks ...!
Lasersdude said:
I was running oos based nougat custom rom with blu spark recovery. Then flashed official ob1, didnt like it, wiped cache/data/system and reinstalled my old oos nougat rom (audax 4.7.6). Now i get the above mentioned message..
Things i tried:
- addionally wipe internal storage and media (installed rom via adb sideload then)
- reformat system/cache/date with ext4
I googled the error and for most people (threads werent particularly concerning the op5t however) it seems that just wiping data and reinstalling the rom did the trick. Not for me though..
What can i do now?
Solution: reformating the data partition with ext4 is not enough. I had to format to FAT and right after that again to ext4, reboot to system and boom, it worked!
PS: i wonder what data is on the internal storage partition that i deleted? I didnt have any data on the phone, i just wonder.. It isnt somehow crucial to the phone?!
Click to expand...
Click to collapse
Finally. Thank you so much!
Helllo,
I tried to root my Samsung A5 2017 and also too change to LineageOS. I installed TWRP. In TWRP I selected my Lineage-Zip and OpenGApps-Zip. TWRP finished the installation succesfully. When I startet the phone, Lineage said, that it isn`t working. Now i flashed the StockROM with Odin and Android worked again. I flashed TWRP a second time and tried to wipe the Phone. This doesen´t works. Log says: "Unable to mount storage" "Failed to mount ´/data´(Invalide argument)". Then I tried to install Lineage without wiping, but the Log brought the same result.
Thank you for any help.
First of all, I think your thread belongs to the Q&A section.
To answer your question, or try at least, I'm guessing that the storage is encrypted by the Samsung stock ROM. This encryption sadly can't be removed in any other way than completely formatting the data partition.
You can do this in TWRP in the "Wipe" section with "Format data". This will also wipe your internal storage, so you should have all the important zips for installation on a microSD card or your PC, so you can install them after the wipe (I'm guessing you already did that, since you installed without having access to /data).
If you want to keep the data partition unencrypted in the future but still use the stock ROM, you can flash Magisk after removing the encryption.
Hope I could help.