Database Info

[q] no internal storage

I flash with odin and make mistakes.
Flashed:
CSC in PDA
PDA in CSC
Click to expand...
Click to collapse
So everytime I entered recovery I get this kind of messages
E:failed to mount /data (No such file or directory)
E: failed to mount /sdcard (File exists)
E: copy_cache _media: Can't mount /sdcard
your storage not prepared yet,p lese use UI menu for format and reboot actions
E:failed to mount data (Invalid Argument)
Click to expand...
Click to collapse
And I get Bootlop on samsung logo (the second one)
Don't know why, none Roms managed to boot EXCEPT THIS ONE (CM7) http://forum.xda-developers.com/showthread.php?t=1527359
BUT I'm facing this bugs:
#No internal storage at all (It says 0 and can't install google play apps because it says that I have no free space)
#Reboot erase all config and apps installed. It takes the phone like it recently flashed the rom.
#EFS is missing (Have backup, restored, but the problem above makes all difficult)
I'm thinking that the /device files might be corrrupted. But I don't know how to solve this.

try flashing pit file

mehran 92 said:
try flashing pit file
Click to expand...
Click to collapse
Done it 3493493414 times.

jutopa said:
Code:
E:failed to mount /data (No such file or directory)
E: failed to mount /sdcard (File exists)
E: copy_cache _media: Can't mount /sdcard
your storage not prepared yet,p lese use UI menu for format and reboot actions
E:failed to mount data (Invalid Argument)
Click to expand...
Click to collapse
It looks like that the eMMC is not working, /sdcard and /data are on it.
I don't think the problem is due to the fact that you wrongly flashed the files. As long as you don't mess with bootloaders, things can most of the time be fixed.
It looks like an hardware failure, but I could be wrong. I've no ways to determine it.
Anyway, the eMMC is not the most important memory in our device, you can replace it with the external SD. There are several ways to do it, some users posted their solution here in the forum, this for example.

loSconosciuto said:
It looks like that the eMMC is not working, /sdcard and /data are on it.
I don't think the problem is due to the fact that you wrongly flashed the files. As long as you don't mess with bootloaders, things can most of the time be fixed.
It looks like an hardware failure, but I could be wrong. I've no ways to determine it.
Anyway, the eMMC is not the most important memory in our device, you can replace it with the external SD. There are several ways to do it, some users posted their solution here in the forum, this for example.
Click to expand...
Click to collapse
Yeah, I'm starting to think that.
I will try to swap SDs.
But I have a question. My main problem is that most of ROMS don't boot. Don't know why, but the only ROMs I managed to boot are CM7 and MIUI 2.3 also. Why this? If I try a different rom it gets stuck in bootloop or doesn't even install it at all.
If a swap sd would this limitation of roms will be solved? I mean, this swapping is permanent or it goes away every time I flash a new build????

jutopa said:
Yeah, I'm starting to think that.
I will try to swap SDs.
But I have a question. My main problem is that most of ROMS don't boot. Don't know why, but the only ROMs I managed to boot are CM7 and MIUI 2.3 also. Why this? If I try a different rom it gets stuck in bootloop or doesn't even install it at all.
If a swap sd would this limitation of roms will be solved? I mean, this swapping is permanent or it goes away every time I flash a new build????
Click to expand...
Click to collapse
I can't explain why CM7 is working, there could be several reasons (/cache is inside the OneNAND, it's using your SD card for /data etc...).
The changes for the swap are usually in the kernel ramdisk or /system and both of them are entirerly wiped during ROM updates, so you should do them on every ROM update.

Error Mounting XT1032

So, I wanted to install a custom ROM, but somewhere along the way something went wrong and I got stuck in a bootloop, I've been reading up on some threads and I followed some steps that were supposed to fix it, but I feel like I'm in even more trouble now (Well, my phone is still alive so I still have hope but yeah..)
Anyways, I'm using Philz custom recovery now, I tried to do a wipe to install a new or stock ROM, at first it said the wipe was succesful, so I tried installing the ROM, but during the install I kept getting:
E: Error mounting /data
It did say the installation was succesful, but after I rebooted it kept trying to wipe eventhough I did not ask for this.
Got another mount error and said Wipe Failed.
Now when I try to sideload stock ROM I get errors like:
Formatting Cache
Formatting /sd-exxt
E: Uknown volume for path /sd-ex
(I also don't know why it's doing that since this phone has no SD card) I got the Falcon edition with the internal storage. Also when my computer recognizes my phone and I want to open the phone folder, there is no longer an Internal Storage folder.
Anyways after those errors it says Data Wipe Complete, Wiping System, Now flash new ROM
But nothing flashes properly it seems due to the mounting error. I've looked for solution, but I can only seem to find threads that involve Samsung
and when I find a solution video it has something to do with either taking your battery out of your phone (which you can't do with this phone) or something
with your SD card (which this phone doesn't have).
So yeah, I'm running out of ideas here and any help would be greatly appreciated!
Cheers.

runittwiice said:
So, I wanted to install a custom ROM, but somewhere along the way something went wrong and I got stuck in a bootloop, I've been reading up on some threads and I followed some steps that were supposed to fix it, but I feel like I'm in even more trouble now (Well, my phone is still alive so I still have hope but yeah..)
Anyways, I'm using Philz custom recovery now, I tried to do a wipe to install a new or stock ROM, at first it said the wipe was succesful, so I tried installing the ROM, but during the install I kept getting:
E: Error mounting /data
It did say the installation was succesful, but after I rebooted it kept trying to wipe eventhough I did not ask for this.
Got another mount error and said Wipe Failed.
Now when I try to sideload stock ROM I get errors like:
Formatting Cache
Formatting /sd-exxt
E: Uknown volume for path /sd-ex
(I also don't know why it's doing that since this phone has no SD card) I got the Falcon edition with the internal storage. Also when my computer recognizes my phone and I want to open the phone folder, there is no longer an Internal Storage folder.
Anyways after those errors it says Data Wipe Complete, Wiping System, Now flash new ROM
But nothing flashes properly it seems due to the mounting error. I've looked for solution, but I can only seem to find threads that involve Samsung
and when I find a solution video it has something to do with either taking your battery out of your phone (which you can't do with this phone) or something
with your SD card (which this phone doesn't have).
So yeah, I'm running out of ideas here and any help would be greatly appreciated!
Cheers.
Click to expand...
Click to collapse
The phone has a virtual SD card.
I had a similar issue. Try flashing TWRP recovery and go to wipe > format data (THIS WILL DELETE ALL DATA) then reboot recovery. Worth a shot if you're not able to use your phone. You can copy over SD card contents to a computer first via TWRP by mounting MTP, or use USB OTG..

Can't flash anything through recovery. (failed to mount "/cpefs" (Invalid Response)

Can't flash anything through recovery. (failed to mount "/cpefs" (Invalid Response)
I recently got this phone and I've been trying to install a custom rom, however, I can't seem to do anything while using TWRP. For some reason the file explorer shows no files and no /storage folder. It also says that the /system partition weights 0MB. I've already tried formatting the /data partition from EXT4 to extFAT, but it won't let me because it cannot mount the "/cpefs" partition, which I've been unable to find any information about.
I can flash the stock firmware trough ODIN, and I can flash the recovery. The internal storage works fine, but nothing shows up when I open TWRP.
I've tried formatting the data partition, repairing it, changing the partition format, wiping, installing a custom rom, installing superSU. But it won't allow me to do any of those things. Either "/data" can't be mounted, or "/cpefs" can't be mounted while formatting /data.

Cepillado said:
I recently got this phone and I've been trying to install a custom rom, however, I can't seem to do anything while using TWRP. For some reason the file explorer shows no files and no /storage folder. It also says that the /system partition weights 0MB. I've already tried formatting the /data partition from EXT4 to extFAT, but it won't let me because it cannot mount the "/cpefs" partition, which I've been unable to find any information about.
I can flash the stock firmware trough ODIN, and I can flash the recovery. The internal storage works fine, but nothing shows up when I open TWRP.
I've tried formatting the data partition, repairing it, changing the partition format, wiping, installing a custom rom, installing superSU. But it won't allow me to do any of those things. Either "/data" can't be mounted, or "/cpefs" can't be mounted while formatting /data.
Click to expand...
Click to collapse
Which phone you're using?
J7 Pro?
Secondly make sure to enable OEM unlock options from the stock ROM's Developer option!
Thirdly check the recovery patches etc of the desired recovery's webiste (you're using) and flash it through the recovery if you're facing the problem!
It'll work, mostly some users said they fixed this by the above mentioned step!
If no luck, maybe someone will sort it out for ya, soon! :laugh:
Good Luck! :good:

sosukeaizen said:
Which phone you're using?
J7 Pro?
Secondly make sure to enable OEM unlock options from the stock ROM's Developer option!
Thirdly check the recovery patches etc of the desired recovery's webiste (you're using) and flash it through the recovery if you're facing the problem!
It'll work, mostly some users said they fixed this by the above mentioned step!
If no luck, maybe someone will sort it out for ya, soon! :laugh:
Good Luck! :good:
Click to expand...
Click to collapse
Thanks for your reply. The model of the phone is SM-J710MN. The OEM unlock option is enabled, otherwise I wouldn't be able to flash the recovery. I am trying to use TWRP. Where would I find a recovery patch for this model?. Everything works fine in the recovery, but it won't let me wipe/format/repair or change ANY partition. It can't mount anything, and the error that I see the most often is that it cannot mount the /cpefs partition.

Cepillado said:
Thanks for your reply. The model of the phone is SM-J710MN. The OEM unlock option is enabled, otherwise I wouldn't be able to flash the recovery. I am trying to use TWRP. Where would I find a recovery patch for this model?. Everything works fine in the recovery, but it won't let me wipe/format/repair or change ANY partition. It can't mount anything, and the error that I see the most often is that it cannot mount the /cpefs partition.
Click to expand...
Click to collapse
try flashing a lower version of the same frimware you've already installed e.g if the latest is nougat 7.1.1 with the recent security update, try flashing with another nougat version that is lower to the recent one's security patch #

I am having trouble rooting Samsung j7 Perx SM-J727P.

I am totally new to rooting, not sure what I've done wrong.
I started trying to root my SM-J727P by installing TWRP with Odin. This works fine, then I added the superSU v2.82 file to the device's microSD card. I went to install tab in TWRP recovery mode->select storage->Micro SD card->superSU.
Then when I try to flash it, a red message appears saying "Could not mount /data and unable to find crypto footer. Failed to mount /data (Invalid Argument). At the bottom it says "Failed to mount /system (Device or Resource Busy). Failed to mount /data (Invalid Argument.)
After this I read that I need to format storage.
I went to wipe->format data->typed yes and the same message appears, "Failed to mount /system (device or resource busy).
I'm extremely new to this so I don't really know what I'm talking about but do I need to disable dm-verity?
Any help would be greatly appreciated.

ColoPhone said:
I am totally new to rooting, not sure what I've done wrong.
I started trying to root my SM-J727P by installing TWRP with Odin. This works fine, then I added the superSU v2.82 file to the device's microSD card. I went to install tab in TWRP recovery mode->select storage->Micro SD card->superSU.
Then when I try to flash it, a red message appears saying "Could not mount /data and unable to find crypto footer. Failed to mount /data (Invalid Argument). At the bottom it says "Failed to mount /system (Device or Resource Busy). Failed to mount /data (Invalid Argument.)
After this I read that I need to format storage.
I went to wipe->format data->typed yes and the same message appears, "Failed to mount /system (device or resource busy).
I'm extremely new to this so I don't really know what I'm talking about but do I need to disable dm-verity?
Any help would be greatly appreciated.
Click to expand...
Click to collapse
I now have manually mounted system and no errors showed, after tapping reboot system, the phone entered a bootloop. Not sure if this is supposed to happen or not and if it is, how long does it take?

ColoPhone said:
I now have manually mounted system and no errors showed, after tapping reboot system, the phone entered a bootloop. Not sure if this is supposed to happen or not and if it is, how long does it take?
Click to expand...
Click to collapse
This happened to me when I was doing my first root with samsung. What I did was completely start over with a new stock ROM and TWRP. Be sure you have all the right things ticked on Odin. What I had to do with my sm-j700p was un-tick auto-restart when done, and when the TWRP was done flashing, I had to remove the battery instead of wait for it to shut down. Then QUICKLY go into recovery mode by pressing the buttons after you turn it back on. Flash ROM. If I remember correctly, I was so good from there, but the timing with samsung when pushing the buttons apparently is EVERYTHING.
And making sure it is the correct TWRP file. I also made the mistake of picking the wrong TWRP file. Same model and carrier...different year of phone. Software version number is where it's at to get the best info.
Good luck!

Is my OP 7Pro permanently broken?

I have an OP 7Pro (GM1917) that was working fine for a long time with OOS 10.3.8.
I hadn't done an upgrade for a long time, and so recently, I did an upgrade to OOS 11.0.5.1.GM21AA. After doing that, my device is unusable, and I fear that there might be something broken or damaged that causes firmware or storage to no longer function properly. All of the explanatory details follow, and please read all of that. What I'm wondering is whether the device is now permanently hosed, or perhaps if there is some way for me to fix it. Here are all of the details:
After the upgrade, my device went into a permanent boot loop when trying to boot to System.
I then did fastboot boot twrp-3.6.0_11-0-guacamole.img, and it indeed put me into TWRP. However, the /data partition is inaccessible. Whenever I try to format /data, I consistently get these messages:
Code:
Failed to mount /data (Invalid argument)
Unable to recreate /data/media folder.
Unable to mount storage
Unable to mount /data/media/TWRP/.twrps
Unable to wipe data
I go back to the bootloader and connect to my PC, and I then run these commands:
Code:
fastboot erase userdata
fastboot format:ext4 userdata
These commands successfully run with no error messages. I then go back into TWRP, but /data is still inaccessible, and I get the same error messages that I listed above when trying to format /data .
I then tried to decrypt /data, but when I do so, it asks for a password, and I have no idea what password to give. I never used any password on the device in the past. I am not allowed to decrypt /data without a password.
So, I decided to use the MsmDownloadTool to reflash my device back to OOS 10.3.8. This works fine with a different GM1917 device that I have (but which I never tried flashing to OOS 11). However, with this particular device, after going into EDL mode, I am told that I am "Connected", but a couple seconds later it gives me the "Sahara Connection Failed" message. I have double-, triple-, and quadruple-checked the device drivers, and it indeed is showing that the "Qualcomm qds 9008" driver is properly installed and active. Furthermore, as I mentioned, I have no problem using MsmDownloadTool on that PC with another GM1917 device.
I went further: I extracted payload.bin from the OOS 11.0.5.1.GM21AA installation bundle, and I extracted all of the *.img files. I flashed boot.img via fastboot and retried everything that I mentioned above, but nothing has changed.
I then went and flashed all of the *.img files. However, still nothing has changed.
When reflashing the set of all *.img files, in some cases, I was told that the file is critical and cannot be reflashed. I then ran these two commands ...
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
... but in both cases, I was told that the device is already unlocked. Trying to reflash all of the *.img files again gave me the same results: i.e., some got flashed, and others were not flashed due to being "Critical".
Also, some of the items I flashed were said to be "sparse" and their flashes were flagged with warnings, but as far as I can tell, they seem to have been flashed anyway.
Do these problems with /data and EDL and everything else mean that my device is somehow permanently damaged? Or are there perhaps one or more additional things that I can try in order to restore it to some sort of working state?
Thank you in advance for any thoughts or ideas.

This has been fixed.
I had forgotten that in the past, I was trying the OrangeFox dual-boot recovery on this device, and it had repartitioned /data.
I fixed this by booting into OrangeFox recovery via fastboot, and then using its adb sideload facility to flash that recovery. OrangeFox's adb sideload mechanism offers options to the user for repartitioning and rebuilding /data. I utilized those options and set /data back to "Stock", and after that, /data was accessible again.
At this point, I flashed OOS 10.3.8, and then flashed the appropriate TWRP and Magisk, now, my device is back up and running in that OOS version.
The EDL problem continues, but given that my device is now usable again, I am not overly concerned about this MsmDownloadTool issue at the moment. In my spare time, I'll continue to look into that.
All's well that ends well!

I think I also have the same issue but the good thing with mine is my device is still working..but every time I access storage via twrp it give me a 0mb or in accessible data no matter if I enter my password to decrypt data. Until now I just leave it as is for I haven't found any solution

I have the same issue but I can't boot at all. I'm only limited to twrp and fastboot. I was previously running 11.0.3 with Magisk and a Magisk module called xXx_nolimit, downloaded the OTA update and went to reboot to recovery before being prompted for a pattern passcode (I hadn't set any fingerprint or password) so I rebooted into twrp and clicked fix bootloader. Now as I reboot it just boots back into twrp.
I'm also getting these same messages:
Failed to mount /data (Invalid argument)
Unable to recreate /data/media folder.
Unable to mount storage
Unable to mount /data/media/TWRP/.twrps
I'm currently running apbf to bruteforce the pattern passcode that I never set in hopes to decrypt my phone. Not even sure it will work though as I don't have FBE user 0 mounted? I have my dad's phone which basically has the exact setup as mine but I didn't update it yet. Anyway to use partition or parts data from his phone to fix mine? I really don't want to wipe my /data or /userdata as it's been a while since I backed anything up.
Edit:
All I have in my /data folder is:
/data/india
/data/recovery
/data/reserve

The edl issue happended to me too and I just needed to use another msmdownloadtool version.