Develop Bugs

[Q] Can't mount /data

I have a problem, and I'm dealing with it since this saturday. I really need my phone this evening so I really want help. My phone has since saturday a bootloop with every rom. Today I found out that it could have something in common with a error in the recoveryscreen which says it can't mount /data. CWM and the stock recovery both have this problem. Can please anyone help me? I'm really confused, because I have tried everything.
//I've discovered that the problem is that the /data partition is crashed. Is is possible to recreate the internal partition table?

install a stock rom then re-install cwm 5.0.2.7

Msulviu said:
install a stock rom then re-install cwm 5.0.2.7
Click to expand...
Click to collapse
I have done that already a few times.

Try flashing an ext4 converter, or re dd'ing an empty RFS format partition into place.

Already done. When I try to use ext4formatter in CWM it doesn't give an error, but when I try to do the data reset I will get an error again because it can't mount (and unmount) /data.
//And how do you add a RFS partition on the phone? Or do you mean on the SD?

Factory reset?
Have you tried doing a factory reset with Kies?

be_born said:
Have you tried doing a factory reset with Kies?
Click to expand...
Click to collapse
Thank you for trying to help, but your answer is stupid. It's impossible to go to Kies without a (working) rom...

I think I just found something interesting to know. I tried again to install Cyanogenmod 7.2 (ported by Phiexz) and in the Aroma installer I looked at the System Info. Almost everything looks fine, but this is not good I think:
Data Size : -1MB
Free : -1MB
(/mnt/sdcard) : -1MB
Free : -1MB
Click to expand...
Click to collapse
Are those partitions crashed? And how do I resize or reformat them back?

Which ext4 converter did you use?
Phiexz's if I remember correctly, uses the formatting tools included in the recovery. Mine has its own, separate binaries.
To reflash an RFS partition into place, you could use the dd command (carefully). Here's an empty RFS formated /data partition.
Or reflash back to the stock recovery and use that to format the partitions back to RFS.
Extract to your SD card and use the following command:
dd if=/sdcard/data.rfs of=/dev/block/stl13 bs=4096
Good luck,
Darkshado

Darkshado said:
Which ext4 converter did you use?
Phiexz's if I remember correctly, uses the formatting tools included in the recovery. Mine has its own, separate binaries.
To reflash an RFS partition into place, you could use the dd command (carefully). Here's an empty RFS formated /data partition.
Extract to your SD card and use the following command:
dd if=/sdcard/data.rfs of=/dev/block/stl13 bs=4096
Good luck,
Darkshado
Click to expand...
Click to collapse
I did use Phiexz's first yes. But I can't install yours. And where do I have to use dd commands? :$

What do you mean by "can't install mine"? Is there an error message or you're not sure how to do it?
If so, just apply it from the SD card like any other update.
The dd command has to be input through ADB shell while in recovery. So get ADB working if you haven't already.

Darkshado said:
What do you mean by "can't install mine"? Is there an error message or you're not sure how to do it?
If so, just apply it from the SD card like any other update.
The dd command has to be input through ADB shell while in recovery. So get ADB working if you haven't already.
Click to expand...
Click to collapse
I did know how to install a zip, but I tried 2 times and I think both were a bad download. Now I'm installing your Ext4 Converter.
// YOUR EXT4 CONVERTER WORKED!!! After a week without a phone it finally worked! Thank you so much!

Glad to hear that!
I had a similar problem of being unable to mount /system after installing a CM9 beta (can't remember which) and ended up solving it like that.

Hey guys i have a question relating to this dscussion. I have my gio running CM9 and i recently used BML5 to find my phone's unlock code. I have a nandroid backup of Rooted stock ROM, and when i tried to flash back to it, it said "Could format dev/block/stl13". I have the CWM 5.0.2.7 with RFS and EXT4 support, so it should work. What is the problem?

That's the thing; the exact behavior of those RFS+ext4 CWM builds when changing from one type to the other hasn't been very well documented.
I'm not sure they can format back to RFS properly.
You could always try that empty RFS partition set and attempt a restore afterwards.

What can i do if dd says, that it can't open '/dev/block/stl13': Invalid argument? I placed the data.rfs to the root directory of sdcard. Am I doing something wrong?

Can't mount /data
Hello, I have a bricked phone, and no idea why, and so far I'm unable to fix it. I've been waiting for an RMA so I can send it back to GSM Nation to evaluate and hopefully fix. My problem started when Samsung support told me to do a factory reset of my Samsung Galaxy S3, and it rebooted, then said it could not find or mount /data or anything therein. I have Not, repeat NOT, rooted my phone, it had the stock Android 4.3 OS and updates from T-mobile. The tech at the Samsung Experience Shop in the Best Buy store could not reflash it, when Kies tries to talk to the phone in Side Load mode it freezes or something, nothing happens. I downloaded ODIN 3 on Dad's win XP laptop, and in ODIN download mode the computer sees it as a new device with no driver to make it talk to it, and the drivers I've downloaded simply will not install. The installers die as soon as they run having done nothing. I am using my Samsung Chromebook to write this and have no Linux machine to work with. I am at a loss. Can you help me? Maybe I could re-install android using a microSD card?

I have the solution for data partition crash or any other partition
please do it with your responsibility but your phone is alreay bricked so it doesn't matter
hi every one i 've been through this problem for a long time and just yesterday hamdo lilah i discovered the solution it is by repartitioning your partitions with a pit file . i tried this method with samsung galaxy fit and it works even the pit file is for samsung .all you have to do is open odin included in the package then select pit file included then click start and there you go 'even if it doesn't show PASS ' after that just flash a stock rom ' or maybe any rom ' and that's it you are ready to go . i uploded the package on gulfup cause i have no account in mediafire enjoy if you face any problem just contact me or add a replay
gulfup.com/?rP8hfs

HELP! Verizon GNex stuck in Recovery

My phone is currently not working at all so I would really appreciate some help. I was running MMuzzy's 4.2 JB ROM (Around the 12/16/12 Version) and I decided to update to the 1/11/13 ROM version. So I installed the files onto my phone and rebooted into recovery, wiped cache and dalvik cache, and installed the files form SD Card. After this, I chose reboot system and it just went straight back into recovery. New ROM wouldn't load. I was an idiot and did not do a backup of my previous rom because I thought it would be a flawless process since I was updating to a new version of the same ROM. So I have no backup to access right now. An odd thing I noticed is when I "chose ZIP from SD card" multiple options such as 0/ and obb came up instead of just showing the files in my SD card. Right now to access my files I have to choose ZIP from sd card, choose 0/, 0/ again, 0/again, and then I can see my ROM and gapps zip files. Since the New rom didnt work I did a factory reset and wiped everything and tried to install the Zips again. Still nothing. Also, the phone can't find any of my old backups. I suspect this has something to do with the odd formatting issue and 0/ and obb folders showing up but I have no idea. What should I do? At this point I don't care If I lose everything on my sd card I just want my phone working.
Thanks

in mounts and storage mount /data then
adb push ROM.zip /data/media
then unmount and it should be there on the root of your "sdcard"
Edit- but if you have 3 "0" folders then you will have to change it from data/media to data/media/0/0/0

k786 said:
in mounts and storage mount /data then
adb push ROM.zip /data/media
then unmount and it should be there on the root of your "sdcard"
Edit- but if you have 3 "0" folders then you will have to change it from data/media to data/media/0/0/0
Click to expand...
Click to collapse
Not sure what this would do. Right now I am just stuck unable to run a rom. How do I install one and get it to boot?

schad89 said:
Not sure what this would do. Right now I am just stuck unable to run a rom. How do I install one and get it to boot?
Click to expand...
Click to collapse
Follow the instructions given in the last response

EddyOS said:
Follow the instructions given in the last response
Click to expand...
Click to collapse
Okay. Any way someone can give me a more detailed step by step on how to do these instructions? Sorry I'm pretty much a noob at this and I barely remember the ADP stuff I did on my mac when I first rooted my phone.
Thanks a lot

schad89 said:
Okay. Any way someone can give me a more detailed step by step on how to do these instructions? Sorry I'm pretty much a noob at this and I barely remember the ADP stuff I did on my mac when I first rooted my phone.
Thanks a lot
Click to expand...
Click to collapse
If you're a n00b then flashing a new ROM without knowing how to fix an issue wasn't the best idea was it?
The best solution I can give is to flash back to 100% stock and then start again once you know what you're doing. Use this guide:
http://forum.xda-developers.com/showthread.php?t=1626895

[SOLVED] E: Can't mount /sdcard

Hello dear friends,
I had installed Carbon Kitkat rom on my device then try to undervolt it by Trickester mod but it crashed and phone started on a green screen and didn't boot up at all. I exprienced this green screen before, so I tried to go into recovery and install rom again. But this time when I go to Install Zip -> Choose zip from /sdcard recovery says: E: Can't mount /sdcard
and I can't do anything. Because E975 has insternal SD card I don't know how to fix it
Please help me what should I do?!

Creative9170 said:
Hello dear friends,
I had installed Carbon Kitkat rom on my device then try to undervolt it by Trickester mod but it crashed and phone started on a green screen and didn't boot up at all. I exprienced this green screen before, so I tried to go into recovery and install rom again. But this time when I go to Install Zip -> Choose zip from /sdcard recovery says: E: Can't mount /sdcard
and I can't do anything. Because E975 has insternal SD card I don't know how to fix it
Please help me what should I do?!
Click to expand...
Click to collapse
I think that is because KitKat has different sdcard path. Check if your recovery has the option to change the default path.
If it hasn't this option you have 2 chance: push the ROM using adb command or recover all system using kdz (but after this you need to reunlock the bootloader).
Inviato dal mio LG-E975 utilizzando Tapatalk

[SOLVED]
Thanks for your helps, I could finally solve the issue with another ways.
I was using my camera and taking picture and because of under volting it crashed while saving picture, so this crash make sdcard inaccessible! I try flashing TWRP recovery by ADB, but TWRP also couldn't access sdcard, again I came back to CWM recovery by ADB.
CWM has an erase (format) sdcard function, so I had to format my internal sdcard to make it accessible again. After formatting I lost all of my data but my sdcard works again.
Then I push a zip file rom by ADB with following command: adb push rom.zip /sdcard/
and flash it with by recovery and now my phone is running as well as before
I also should thank @MiZrY for his useful helps :good:

You solved my problem
Creative9170 said:
Thanks for your helps, I could finally solve the issue with another ways.
I was using my camera and taking picture and because of under volting it crashed while saving picture, so this crash make sdcard inaccessible! I try flashing TWRP recovery by ADB, but TWRP also couldn't access sdcard, again I came back to CWM recovery by ADB.
CWM has an erase (format) sdcard function, so I had to format my internal sdcard to make it accessible again. After formatting I lost all of my data but my sdcard works again.
Then I push a zip file rom by ADB with following command: adb push rom.zip /sdcard/
and flash it with by recovery and now my phone is running as well as before
I also should thank @MiZrY for his useful helps :good:
Click to expand...
Click to collapse
Wow... Thank you, You saved my life. :good: :victory:
I had problem in fix permissions fail and forgot to backup before do the fix permissions.
I had tried to find the solution to solve the f***ing problem since I found you topic.
I just format /system, /data and /sdcard all problem were gone.
Thank you again.

Internal storage unavailable after TWRP restore (stock samsung rom, tab 8.4)

FIX: with adb from computer:
adb shell
su
restorecon -v -R /data/media
possible to fix it from android directly with a terminal emulator. Type:
su
restorecon -v -R /data/media
I'll help if I can
Original post:
The restore worked, but the internal storage is unaccessible (stock samsung rom, tab 8.4)
I can access the files in TWRP though. I tried to "fix permissions" in TWRP, didn't help
Any ideas?

I had the same problem twrp, the backups are kinda buggy, somehow it messes up permissions and leaving you unable to write to the internal storage, even when having it connected to the PC it will get permission denied... also even with root you cannot change the permissions to the folder, so it either has to be done through twrp or it's just something really messed up with twrp backups (a broken file that doesn't get restored correctly maybe).
The "fix permissions" setting in TWRP is for something different like messed up app permissions, so it might of messed up your apps if you clicked that...
I'm sure there is a fix maybe even just manually setting the correct permissions in twrp (I didn't try), but in my case I just re-flashed the stock firmware through Odin - everything worked fine again afterwards..
I suggest just using titanium backup to make / restore backups even though its not a one click solution it's reliable, I no longer rely on fixed backups like twrp..

otyg said:
I had the same problem twrp, the backups are kinda buggy, somehow it messes up permissions and leaving you unable to write to the internal storage, even when having it connected to the PC it will get permission denied... also even with root you cannot change the permissions to the folder, so it either has to be done through twrp or it's just something really messed up with twrp backups (a broken file that doesn't get restored correctly maybe).
The "fix permissions" setting in TWRP is for something different like messed up app permissions, so it might of messed up your apps if you clicked that...
I'm sure there is a fix maybe even just manually setting the correct permissions in twrp (I didn't try), but in my case I just re-flashed the stock firmware through Odin - everything worked fine again afterwards..
I suggest just using titanium backup to make / restore backups even though its not a one click solution it's reliable, I no longer rely on fixed backups like twrp..
Click to expand...
Click to collapse
well, thanks for your answer. back to reinstalling
it's a pain though, I have to re-enter all my accounts, xposed, and all xprivacy settings
CM is good, but I have too many issues with it (wifi bad connection, or it won't come out of sleep mode)
*sigh*

Found the solution, if you have the same problem read the first post

Problems after Updates and Wipes

Hi,
my G3 and me have a small problem.
I wanted to update from official Cyanogenmod 12.1 to 13.0, backed up my data, etc.
First, there were tno Problems, but very fast battery drainage, and that my mSD card was now not "sdcard1" anymore but some numbers.
I tried fixing permissions in TWRP, had a bootloop. Updated TWRP (now 3.0.0 installed) and it worked somehow.
After one night it said process.acore quit unexpectedly. I had some crashes of the Google Play Services as well.
Then, it would boot, give me like 10 Seconds, and then jump to the boot screen of Cyanogenmod.
I tried to wipe data,system,dalvik. First there were problems with wiping dalvik, then there were problems with wiping system.
It says can't mount system: invalid argument. When looking around with twrp file explorer, the system folder is empty.
I would really appreciate your help!

You must check the partition type. Check if this as Ext4 or f2fs. In any case, try to repair the system of partitions from TWRP.

Okay, so:
Filesystem of /system is ext4
When trying to fix:
Repairing System using ef2fsck....
/sbin/e2fsck -fp /dev/block/mmcblk0p40 process ended with ERROR: 8
Unable to repair file system.
I assume it's because its ext4 and not f2fs?
btw I found something that may be important: when I try to wipe /cache, it takes forever.

Codagon said:
Okay, so:
Filesystem of /system is ext4
When trying to fix:
Repairing System using ef2fsck....
/sbin/e2fsck -fp /dev/block/mmcblk0p40 process ended with ERROR: 8
Unable to repair file system.
I assume it's because its ext4 and not f2fs?
btw I found something that may be important: when I try to wipe /cache, it takes forever.
Click to expand...
Click to collapse
Try to reinstall cyanogedmon 12.1 without wipes. Then, you enter again to the recovery and apply the wipes. I am not sure if for our model, cyanogedmon is compatible with the type of partitions f2fs and if is required a kernel with support for f2fs file system. You could try to changing the partitions (file system to f2fs), installing the rom and see if it starts but could cause a boot loop. Make a nandroid before making any changes.

cesarandres_8911 said:
Try to reinstall cyanogedmon 12.1 without wipes. Then, you enter again to the recovery and apply the wipes. I am not sure if for our model, cyanogedmon is compatible with the type of partitions f2fs and if is required a kernel with support for f2fs file system. You could try to changing the partitions (file system to f2fs), installing the rom and see if it starts but could cause a boot loop. Make a nandroid before making any changes.
Click to expand...
Click to collapse
Okay, i will try this tomorrow and then report back!
Thank you so far

Okay,
when trying to install the latest Snapshot of official CM, it just says ZIP File is corrupt. It said the same about an older build I still had on my PC.
When I try to flash the CM 13.0 build i had previously, TWRP just goes black and reboots (into recovery).
I also have to manually mount /system every time. If I try to mount /system again after dismounting it, it says 'failed to mount /system : Invalid Argument' .
This applies to all other partitions but the external SD Card.
When I try to change the file system to f2fs, it says OPeration successfull, but it didn't change anything, and the file system keeps being displayed as ext4.
Furthermore, i can't just 'Reboot Recovery' with TWRP- I have to take ot the Battery every time.

Codagon said:
Okay,
when trying to install the latest Snapshot of official CM, it just says ZIP File is corrupt. It said the same about an older build I still had on my PC.
When I try to flash the CM 13.0 build i had previously, TWRP just goes black and reboots (into recovery).
I also have to manually mount /system every time. If I try to mount /system again after dismounting it, it says 'failed to mount /system : Invalid Argument' .
This applies to all other partitions but the external SD Card.
When I try to change the file system to f2fs, it says OPeration successfull, but it didn't change anything, and the file system keeps being displayed as ext4.
Furthermore, i can't just 'Reboot Recovery' with TWRP- I have to take ot the Battery every time.
Click to expand...
Click to collapse
Why dont you start from the beginning.flash lp kdz through lg up then try installing cm 13.it might work for you.

jokerpappu said:
Why dont you start from the beginning.flash lp kdz through lg up then try installing cm 13.it might work for you.
Click to expand...
Click to collapse
I didn't want to lose my files
But it seems this is the only way soon- TWRP is giving me Error 7 when trying to flash CM 13.0. ....
:crying:

Codagon said:
I didn't want to lose my files
But it seems this is the only way soon- TWRP is giving me Error 7 when trying to flash CM 13.0. ....
:crying:
Click to expand...
Click to collapse
Which is your recovery version? If your recovery version is 3.0, you could try performing a downgrade of your recovery. If the errors persist, make an clean installation of the rom from LG Flash Tool (KDZ).

cesarandres_8911 said:
Which is your recovery version? If your recovery version is 3.0, you could try performing a downgrade of your recovery. If the errors persist, make an clean installation of the rom from LG Flash Tool (KDZ).
Click to expand...
Click to collapse
My Version is indeed 3.0. I had 2.8 before. Should I downgrade even further?
What would you recommend?
Besides:
I tried saving my files with the Terminal and [cp * /data/data/media/ /external_sd/Backup -r] and others, but it keeps giving me Zero-Byte Files.
Is this due to the Recovery version too?
You guys really are a big help! Thanks!

Codagon said:
My Version is indeed 3.0. I had 2.8 before. Should I downgrade even further?
What would you recommend?
Besides:
I tried saving my files with the Terminal and [cp * /data/data/media/ /external_sd/Backup -r] and others, but it keeps giving me Zero-Byte Files.
Is this due to the Recovery version too?
You guys really are a big help! Thanks!
Click to expand...
Click to collapse
I think that you try to save an empty folder. Use any backup applications to accomplish this. I have installed recovery twrp version 3 and I have no problem.

cesarandres_8911 said:
I think that you try to save an empty folder. Use any backup applications to accomplish this. I have installed recovery twrp version 3 and I have no problem.
Click to expand...
Click to collapse
Ok but doing it woth cp * /sdcard/WhatsApp it keeps doing the same.
The only thing that matters to me now are my WhatsApp Images
I was able to grab the chatlogs but not more.
Sometimes it even copies all pictures (Like 8.000 files) but all of them are 0-Bytes.
I will try the downgrade tomorrow.
Thank you so far!

Were you able to resolve this? I have an identical issue. I was playing CoC on my LS990 with CM13 before it went black and now it always boots in to twrp recovery 3.0. The only thing that mounts is the external sd card.
I've tried the following and all fail:
adb push cm13 and then install from recovery
adb sideload cm13
lg flash tool via firmware upgrade, roms:ZV4, ZV6, ZV8
Is the internal sd damaged? Please help XDA gods. Thanks