Database Info

Cannot mount Data Partition with any recovery

I made a F2FS conversion to Data Partition.When I made a restore the Data Partition cannot be Mount or do a Format.With any recovery(CWM,TWRP,Philz) the Data partition Cannot be mounted or formated.What Can I do?I read threads on the Transformer Forum but nothing of these working for me :crying:

andreas1996 said:
I made a F2FS conversion to Data Partition.When I made a restore the Data Partition cannot be Mount or do a Format.With any recovery(CWM,TWRP,Philz) the Data partition Cannot be mounted or formated.What Can I do?I read threads on the Transformer Forum but nothing of these working for me :crying:
Click to expand...
Click to collapse
Only one that can mount it will be twrp 2.7.1.1 (or the f2fs twrp released in dev)
If it has corrupted just format it back to ext4 and start again.

This is the log when I press wipe or repair partition.in the mount menu i cant select any partition
Sent from my GT-I9505G using XDA Free mobile app

andreas1996 said:
This is the log when I press wipe or repair partition.in the mount menu i cant select any partition
Click to expand...
Click to collapse
That's not a log, it's a screenshot. The log is in /tmp/recovery.log, so you can use adb pull to get it and post it. Or you can probably use the "copy log to SD card" option in the advanced menu.

Here is the log.I compressed the file because the log format is not supported to attachments.

andreas1996 said:
Here is the log.I compressed the file because the log format is not supported to attachments.
Click to expand...
Click to collapse
According to the log, your recovery can't access any partitions on your eMMC. To find out more, reboot to your recovery again and run on the connected PC:
Code:
adb shell dmesg > dmesg.txt
adb shell cat /proc/partitions > partitions.txt
and read/post the resulting files.

Here is the two files your commands gave me

andreas1996 said:
Here is the two files your commands gave me
Click to expand...
Click to collapse
Your tablet's eMMC seems to have no partitions at all:
Code:
<6>[ 4.770320] mmcblk0: unknown partition table
What exactly did you do for "a F2FS conversion to Data Partition"? Did you format mmcblk0 instead of mmcblk0p8?

The only thing I did after f2fs conjversion is in Philz recovery I select wipe to install a new ROM.And the problem began.

andreas1996 said:
The only thing I did after f2fs conjversion
Click to expand...
Click to collapse
If you expect help, you need to answer my question. I did not ask what you did *after* the f2fs conversion - what exactly did you do to convert /data to f2fs?

enter recovery-wipe-advanced-repair or change filesystem-f2fs-reboot

andreas1996 said:
enter recovery-wipe-advanced-repair or change filesystem-f2fs-reboot
Click to expand...
Click to collapse
Friend! You got the attention of one of the few people who may be able to help you get your tab back! Use it!
Post DETAILED steps of what you did or _that is going to ignore you!
Which recovery and version thereof did you use?
What did you do afterwards? You mention 3 recoveries. Did you flash all of them?
What did you do in which order in each of them?
Provide as many details as you can!

First I used the modded twrp recovery from the f2fs thread.I did the f2fs and the chromi-kk work successfull.But because battery drain I wanted to install the last chromi-x version based to stock firmware.Next,I didn't convert f2fs back to ext4,but I made a full wipe with twrp 2.7.1.1.And my problems began.
Also I tried full wipe from the latest CWM and Philz recovery with the same results

andreas1996 said:
First I used the modded twrp recovery from the f2fs thread.I did the f2fs and the chromi-kk work successfull.But because battery drain I wanted to install the last chromi-x version based to stock firmware.Next,I didn't convert f2fs back to ext4,but I made a full wipe with twrp 2.7.1.1.And my problems began.
Also I tried full wipe from the latest CWM and Philz recovery with the same results
Click to expand...
Click to collapse
Define "full wipe".
Which CROMi-X version did you try to flash?
Details, details....

andreas1996 said:
First I used the modded twrp recovery from the f2fs thread.I did the f2fs and the chromi-kk work successfull.But because battery drain I wanted to install the last chromi-x version based to stock firmware.Next,I didn't convert f2fs back to ext4,but I made a full wipe with twrp 2.7.1.1.And my problems began.
Also I tried full wipe from the latest CWM and Philz recovery with the same results
Click to expand...
Click to collapse
OK So your issue is that you have left your data partition as f2fs and installed a kernel/rom that does not understand f2fs.....
So as I see it - install a recovery that will reformat as EXT4 - format data and start again?

sbdags said:
So as I see it - install a recovery that will reformat as EXT4 - format data and start again?
Click to expand...
Click to collapse
How would you format data without a data partition?

sbdags said:
OK So your issue is that you have left your data partition as f2fs and installed a kernel/rom that does not understand f2fs.....
So as I see it - install a recovery that will reformat as EXT4 - format data and start again?
Click to expand...
Click to collapse
I tried that but the TWRP gave me a ERROR message(cannot mount Data).Tomorrow i will upload screenshots and full logs for that,because my transformer has empty battery because of the attempts

andreas1996 said:
I tried that but the TWRP gave me a ERROR message(cannot mount Data).Tomorrow i will upload screenshots and full logs for that,because my transformer has empty battery because of the attempts
Click to expand...
Click to collapse
So try formatting from adb?
Code:
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot

sbdags said:
So try formatting from adb?
Code:
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
Click to expand...
Click to collapse
When I doing the command (make_ext4fs /dev/block/mmcblk0p8) I receive the message : Need size of file system.

Something seems to be wrong with your GPT. Unfortunately the busybox tools don't support big offsets to read it, so let's first see if the Tegra-specific partition table (which is not used by the kernel) is still there - that won't help you immediately but will show if the eMMC can be read at all and where the partitions are supposed to be. Post the output file of this command:
adb shell hexdump -s 0x300000 -n 2048 -C /dev/block/mmcblk0boot0 > pt.txt

Bootloop + E:unable to mount '/cache'

Hi guys first thread here and i need your help.
i was using my MOTO G XT1033 ( Boot loader unlocked + rooted ) , calling, batt was low and phone goes off, i tried start up and a bootloop appears. So i go to Recovery ( TWRP V2.8.1.0) and i tried to flash a ROM, like always i tried to wipe cache and dalvik bfore flash it but that proces seems to fail, and a couple of messages like unable to mount /data unable to mount /system appears, first time happening,
updating partition details...
E:Unable to stat '/data/data/com.google.android.gms/shared_prefs'
E:Unable to stat '/data/data/com.amazon.kindle/shared_prefs'
E:Unable to stat '/data/data/com.facebook.orca/shared_prefs'
E:Unable to stat '/data/data/com.facebook.katana/shared_prefs'
E:Unable to mount '/cache/
E:Unable to mount '/cache/
Full SELinux support is present
E:Unable to mount '/cache/
E:Unable to mount '/cache/
MTP Enabled
E:Unable to mount '/cache/
E:Failed to wipe dalvik
updating partition details...
E:Unable to stat '/data/data/com.google.android.gms/shared_prefs'
E:Unable to stat '/data/data/com.amazon.kindle/shared_prefs'
E:Unable to stat '/data/data/com.facebook.orca/shared_prefs'
E:Unable to stat '/data/data/com.facebook.katana/shared_prefs'
when I tried to connect it using laptop + fastboot.exe
it always shows waiting for device ( changed many cables + used friends laptops) but always stucked on "waiting for device"
i also tried flashing again a ROM, but only bootloop, tried again to wipe cache and dav but is only unable to mount /data. Any ideas ????
can anyone guide me
what is the possible solution ??
as I was reading here
http://forum.xda-developers.com/showthread.php?t=2683787
that using terminal command we can do something
mke2fs -T ext4 /dev/block/mmcblk0p8
but above was for some tablet
and i do not what has to be written "mmcblk0p8" for MOTO G XT1033 ( dual sim 16 GB india version)
please guide

In TWRP, go to wipe -> advanced wipe and *format* the cache partition.

_that said:
In TWRP, go to wipe -> advanced wipe and *format* the cache partition.
Click to expand...
Click to collapse
tried it already but not working
I have posted error msgs above
this is the falcon partition layout of my device ( http://forum.xda-developers.com/showthread.php?t=2540799)
but i do not know which partion to be used for data ( manual format) ( mke2fs -T ext4 /dev/block/mmcblk0p8)
can you please guide me in this
thanks for ur reply

pulsar180cc said:
tried it already but not working
I have posted error msgs above
Click to expand...
Click to collapse
I can't see anything related to formatting in your log.
Please try formatting again and then run
Code:
adb pull /tmp/recovery.log
and post the full log here or on a paste site.

_that said:
I can't see anything related to formatting in your log.
Please try formatting again and then run
Code:
adb pull /tmp/recovery.log
and post the full log here or on a paste site.
Click to expand...
Click to collapse
I took data through USB OTG
here's pastebin
pastebin+com/iZ55Kx0t

pulsar180cc said:
I took data through USB OTG
here's pastebin
pastebin+com/iZ55Kx0t
Click to expand...
Click to collapse
According to the log it formatted successfully, but maybe there was a problem writing back the changes. Let's look at the kernel log (please reboot and retry formatting again to get a clean log):
Code:
adb shell dmesg > dmesg.txt

_that said:
According to the log it formatted successfully, but maybe there was a problem writing back the changes. Let's look at the kernel log (please reboot and retry formatting again to get a clean log):
Code:
adb shell dmesg > dmesg.txt
Click to expand...
Click to collapse
sry got it now
ran command as admin
here is pastebin
pastebin+com/nUPPUrWH

guys please check kernel log
pastebin+com/nUPPUrWH
and advice what to do now
thanks

pulsar180cc said:
pastebin+com/nUPPUrWH
Click to expand...
Click to collapse
Code:
<3>[ 3.394504,0] mmcblk0: mmc_blk_err_check: general error sending status command, card status 0x80900
This looks like a hardware error. I don't know if it's possible to recover from this, maybe not.

thanks for ur reply and giving your valuable time (@_that)
I went to service centre and they are saying change mother board ( RS 7500 INR )
cant pay this huge amount just for mother board
will buy another phone now =)

How Can I Get Out of This Bootloop on My Moto G

I woke up to find my 1st Generation Moto G battery was depleted and on charging it a bit., I switched it on only to find it optimizing my apps. All these (battery getting depleted, app optimization) happen all the time and I wasn't the least worried.
I picked up my phone later thinking it must have been done with the app optimization only to discover it was totally dead while still connected to a power bank. When I try to switch it on, it is stuck on the "Unlock Bootloader" page. I have tried flashing a new stock rom and it does not work.
I attached the image I see when I try to use recovery to wipe. Basically, nothing works. Can anybody help as I just fixed the screen and also out of warranty?

Fastboot flash the latest Factory Firmware Image for your model.
Factory Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219

lost101 said:
Fastboot flash the latest Factory Firmware Image for your model.
Factory Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Thanks lost101, I do know how to flash perfectly well with fastboot. The problem is it flashes successfully but the phone is still stuck on the Bootloader.
I get this particular message on my recovery when I try to wipe either userdata or cache.
blkdiscard on partition /dev/block/platform/msm_sdcc.1/by-name/userdata failed formatting /userdata failed
formatting cache
and
blkdiscard on partition /dev/block/platform/msm_sdcc.1/by-name/userdata failed formatting /cache
wiping clogo

@NaijaAndroid - Can you try booting into TWRP via: fastboot boot twrp.img

lost101 said:
@NaijaAndroid - Can you try booting into TWRP via: fastboot boot twrp.img
Click to expand...
Click to collapse
I do not have a custom recovery presently but when I try to flash TWRP, it flashes successfully with no error message but the phone is still stuck on the stock recovery.

NaijaAndroid said:
I do not have a custom recovery presently but when I try to flash TWRP, it flashes successfully with no error message but the phone is still stuck on the stock recovery.
Click to expand...
Click to collapse
Read again what I told you to do. I did not say for you to flash anything.

@lost101, I just read your instructions again. I can boot in to TWRP. What else should I do after?
Thanks.

NaijaAndroid said:
@lost101, I just read your instructions again. I can boot in to TWRP. What else should I do after?
Click to expand...
Click to collapse
Via PC, do the following wipe: (requires working ADB setup)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22​
You could then TWRP > Wipe > Format Data > Yes, and try flashing a custom ROM.
Edit: You should backup photos or important data before hand.

I just downloaded CM 12.1. How can I transfer the ROM to the phone?
Edit: I have done it.

NaijaAndroid said:
I just downloaded CM 12.1. How can I transfer the ROM to the phone?
Click to expand...
Click to collapse
Recovery mode ADB will work with Linux - unsure about Windows. You could boot into an Ubuntu LiveCD (without installing) and transfer the ROM to phone that way. Otherwise, an OTG usb pen would be another option.
adb push rom.zip /sdcard​

@lost101, I tried to send the Rom via ADB and I got : failed to copy 'Rom.zip' to '/sdcard//Rom.zip' : Read-only file system.
Also, TWRP made my phone to load as MTP on my PC but I could not transfer through that method also. The transfer kept on failing. Seems my internal memory (eMMC) is now Read-only.

NaijaAndroid said:
@lost101, I tried to send the Rom via ADB and I got : failed to copy 'Rom.zip' to '/sdcard//Rom.zip' : Read-only file system.
Also, TWRP made my phone to load as MTP on my PC but I could not transfer through that method also. The transfer kept on failing. Seems my internal memory (eMMC) is now Read-only.
Click to expand...
Click to collapse
Try sideloading the ROM.
TWRP > ADB sideload​adb sideload rom.zip​

lost101 said:
Try sideloading the ROM.
TWRP > ADB sideload​adb sideload rom.zip​
Click to expand...
Click to collapse
I got:
Installing zip file '/sideload/package.zip'
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
Can't install this package on top of incompatible data. Please try another package or run a factory reset
Updater process ended with ERROR: 7
I was trying to use CM 12.1.
So sorry for taking your time. Thanks.

NaijaAndroid said:
I got:
Installing zip file '/sideload/package.zip'
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
Can't install this package on top of incompatible data. Please try another package or run a factory reset
Updater process ended with ERROR: 7
I was trying to use CM 12.1.
Click to expand...
Click to collapse
Try a CM13 ROM.

lost101 said:
Try a CM13 ROM.
Click to expand...
Click to collapse
Same problem as above. I got the same message.

On PC:
adb shell​e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata​

lost101 said:
On PC:
adb shell​e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata​
Click to expand...
Click to collapse
I got:
/dev/block/platform/msm_sdcc.1/by-name/userdata is in use.
e2fsck: Cannot continue, aborting.

NaijaAndroid said:
I got:
/dev/block/platform/msm_sdcc.1/by-name/userdata is in use.
e2fsck: Cannot continue, aborting.
Click to expand...
Click to collapse
TWRP > MOUNT > Untick /Data​

lost101 said:
TWRP > MOUNT > Untick /Data​
Click to expand...
Click to collapse
got this after unticking data and trying again:
e2fsck 1.42.9 (28-Dec-2013)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/platform
/msm_sdcc.1/by-name/userdata
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:

NaijaAndroid said:
got this after unticking data and trying again:
e2fsck 1.42.9 (28-Dec-2013)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/platform
/msm_sdcc.1/by-name/userdata
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
Click to expand...
Click to collapse
A certain percentage of phones end up with corrupt emmc (internal storage) over time. This problem is a fairly common thing. I do recall someone managing to boot an use CM13, despite the read-only userdata. I'm guessing they must have flashed it via TWRP, with the ROM.zip on an OTG usb pen. It may have worked because /system was still partially / fully writeable.

Encryption Unsuccesful

Hello!
Recently I recevied "Encryption Unseccesful" message on my phone. I tried to restore backup, but twrp says: "failed to mount /data". So, internal storage is dead. Found this. But cant find "repartition" menu in the cwm.
Questions is:
1. Do I need older versions of cwm to repartition sdcard? (If you have one, please share )
2. Is there any ways of recovering phone?
Thanks in advance!

no, just go to TWRP, Wipe, Format internal sdcard

sandpox said:
no, just go to TWRP, Wipe, Format internal sdcard
Click to expand...
Click to collapse
tried this, but I think internal storage is corrupted. Is there a way to use sdcard as internal storage?

you can use sd card for apps and other stuff, but as I knoe cannot be used for system files

I made 2 partitions on sd:
4gb fat32
4gb ext4
But I cant bind /data to this ext4 partition. Can you help, please?
What i did:
With TWRP's terminal:
Code:
mount -t ext4 /dev/block/mmcblk1p2 /data
- Invalid argument (dunno why)
Code:
ln -s /dev/block/mmcblk1p2 /data
- but on phone boot i receive same "encryption unsuccesful" screen.
Edited /etc/fstab - same result.
Files and mount after reboot turn back to its previous condition.
Also installed stock ROM - same message screen.
[/QUOTE]
I got advice that i must do this things with init.d scripts. How can I do this? Already tried "xda's app2sd scripts" but they works if phone completely boots in OS.

remosam said:
you can use sd card for apps and other stuff, but as I knoe cannot be used for system files
Click to expand...
Click to collapse
Why not? I want only mount /data on sd without booting in OS. Other partitions like /system surprisingly work right, because i can flash ROM (stock, CM), but always receive - "cant mount /data"

blind_aquila said:
Why not? I want only mount /data on sd without booting in OS. Other partitions like /system surprisingly work right, because i can flash ROM (stock, CM), but always receive - "cant mount /data"
Click to expand...
Click to collapse
asked sostk or noname

@blind_aquila
try to flash stock rom with odin

Oneplus One, no storage of TWRP

My Opo disconnected itsself yesterday from its OS while charging, leaving me with the massage "no Os installed" on TWRP.
I tried to reinstall the Os Los16, but not success, it cant "mount the storage". I tried to whipe, but it shows: Failed to mount '/ firmware, system, data, cache.
I can't whipe any data, i can't change any data system (ext4 to ext2 f.e.).
What i can do is install anouther trwp, but none of them succeded to recognize the internal storage. It has the information:
Mount Point: /data
Filesystem: ext/4
Present: No Removable: No
Size: 0MB Used: 0MB
Free: 0MB Backup Size. 0 MB
U think my internal Toshiba 64Gb chip died?
Thanks for any info.

iwishuweredad said:
My Opo disconnected itsself yesterday from its OS while charging, leaving me with the massage "no Os installed" on TWRP.
I tried to reinstall the Os Los16, but not success, it cant "mount the storage". I tried to whipe, but it shows: Failed to mount '/ firmware, system, data, cache.
I can't whipe any data, i can't change any data system (ext4 to ext2 f.e.).
What i can do is install anouther trwp, but none of them succeded to recognize the internal storage. It has the information:
Mount Point: /data
Filesystem: ext/4
Present: No Removable: No
Size: 0MB Used: 0MB
Free: 0MB Backup Size. 0 MB
U think my internal Toshiba 64Gb chip died?
Thanks for any info.
Click to expand...
Click to collapse
Flash the rom using an OTG cable. Cheap and easy!

taunusgta said:
Flash the rom using an OTG cable. Cheap and easy!
Click to expand...
Click to collapse
I tried that, but same reaction.
Error 7, but also unable to wipe cache. That is strange.
All roms i tried worked before.

iwishuweredad said:
I tried that, but same reaction.
Error 7, but also unable to wipe cache. That is strange.
All roms i tried worked before.
Click to expand...
Click to collapse
Very strange. I don't know another solution. Sorry

taunusgta said:
Very strange. I don't know another solution. Sorry
Click to expand...
Click to collapse
No problem, thank you for your replay, i get a new logic board and replace my old one. I think the memory chip is broken. Ciao!

iwishuweredad said:
No problem, thank you for your replay, i get a new logic board and replace my old one. I think the memory chip is broken. Ciao!
Click to expand...
Click to collapse
Yeah it's probably corrupted somehow