/data partition corrupted - Samsung Galaxy Fit GT 5670

Hi guys. To spare you the details and cut to the chase after rebooting the phone in ICS i got a message with "Unsuccessful decryption" and i needed to restore factory to continue. And i got into the CWM5 recovery and tried to wipe data/reset
All partitions were formated but /data:
E:format_volume make_extf4fs failed on /dev/block/stl13
Mounting works expect /data
So i can`t format /data and dalvik cache.
I tried to restore to stock GB with odin and all worked fine until the phone reboots and goes into stock recovery and tries to format data but gives error:
-- Wiping data...
Formatting /data...
E:format_volume: rfs format failed on /dev/stl13
and reboot to bootloader and stuck in bootloop.
I know this looks pretty much like /data partition corruption..
I asked if anyone can help me with this issue :/ I`ve read other forums that this can be fixed but i am afraid to use other phone`s tools not to end up bricking it dead.
I have added recovery report View attachment recovery.txt

I have been googling alot this past time and tried all sorts of binaries and zip trying to repartition slt13 but no luck.
For what i have learn i have one more chance of resurecting the partition with RIFF JTAG Box on low level...
Can anyone answer this question:
If all partitions are working fine exect stl13 (/data) is there any chance the NAND chip is dead/corrupted?!
I don`t alot of physical hardware of my device so is there a separate NAND chip for /data or it is a single chip for all partitions? (I.E: /system/ ; /data/ etc. )

Facing the same problem!!
k3eNaNz said:
I have been googling alot this past time and tried all sorts of binaries and zip trying to repartition slt13 but no luck.
For what i have learn i have one more chance of resurecting the partition with RIFF JTAG Box on low level...
Can anyone answer this question:
If all partitions are working fine exect stl13 (/data) is there any chance the NAND chip is dead/corrupted?!
I don`t alot of physical hardware of my device so is there a separate NAND chip for /data or it is a single chip for all partitions? (I.E: /system/ ; /data/ etc. )
Click to expand...
Click to collapse
HAVE YOU FOUND OUT A WAY YET

Related

[Q] Error E:format_Volume: make_extf4fs failed on on dev/block/mmcblk1p2

Im having a trouble reflashing a ROM. During my efforts to fix my horrible battery life problem by doing Odin back to stock and reflashing DK ROM something else has gone wrong.
I go to to Recovery and I tried to wipe data and Reset to Factory
it says
Formatting / data......
Formatting / Cache....
Formatting / sd-ext....
E:format_Volume: make_extf4fs failed on on dev/block/mmcblk1p2
Formatting/sdcard/.android_secure....
Data wipe Complete.
It also says, sd-ext.img not found when I restored my Nandroid backup. Not sure whats going on here...
When it restarts, its still the same old rom with everything still there, just with user data wiped like my google login. How do I fix this? I have already Odin back to stock, rerooted and CWM and am still getting this issue. Could this be contributing to my terrible battery drain?
Nothing wrong, that's normal.
ROMs on phones that didn't have enough local space to install any real number of apps, etc (think Nexus One, or HTC Evo 4G) used to create a second partition on the SD card. This partition was formatted to ext4 and mounted in place of stuff like /system/apps or /data, etc..
Nandroid simply tries to format the partition if it's there, and obviously it isn't. I doubt anyone here has that partition. The sd-ext.img would be the image file nandroid would create if you did have the partition and you backed it up.
But the problem is I cant flash another ROM without doing the factory reset, and when I do factory reset I get that error and the new ROM isnt flashed.... I have never had this error before when I flashed DK originally, or on my last Blaze phone. I need to fix this issue so I can flash a different ROM, or next newest update to this ROM.
You've got some other problems then, because I get that error all the time and have for some time on all sorts of phones.
Once the /data partition is formatted, your wipe is complete. The /cache is good stuff too... once you see those two lines, you are all resetted.
If you nandroid restore, you're going back to what you had.
So why wont it factory reset then? Everytime I do factory reset in recovery, it shows all my files and stuff still on the phone. It never completely wipes my phone. I dont know what to do or what the problem is...
Is there a certain way everything is supposed to look in mounts and storage? Whats supposed to be mounted or unmounted? And what should be formatted?
Factory reset doesn't wipe your sd card. For that you have to format it from the settings menu.
dr4stic said:
Factory reset doesn't wipe your sd card. For that you have to format it from the settings menu.
Click to expand...
Click to collapse
Can you explain how to do that?
I beilive he means in CWM, under mounts and storage, format /sdcard
Sent from my SGH-T769
No, I meant in android. I'm sure a quick Google search would turn it up, but here goes: Settings -> Storage... you'll want to unmount first, then format.
SD card = removable card
USB Storage = internal storage
Just remember, this will destroy ALL your data on whichever you choose to format. Everything, your pictures, music, etc...

Unable to mount /data

I've managed to get that awful Rom (Destroyer) Manager off of my TF101G and have got Rogue on via PERI and now I'm trying to flash the stock ASUS ICS Rom but can't delete the Dalvik Cache because I'm unable to mount /data
Code:
- - Wiping all user data - -
Formatting /data...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure
Cache wipe complete.
Formatting /cache...
Cache wipe complete.
Wiping dalvik-cache...
Error mounting /data!
I'm assuming that /data is stuck on read only?
Manually fixing permissions and then mounting /data also shows the same error.
HELP :crying:
I have the same problem. I know what lead me to it.
Its an Asus SL101
I have cyanogenmod correctly installed. In order to install a megatron rom I downloaded their app called megatron apps. Trying to download a rom from them I got validation error at end of download and I make the stupidity of change the download dir from /mnt/sdcard to /sdcard and then when I restart again it doesn´t load and CWM recovery give me the same errors (unable to mount /data or unable to mount /sdcard when cleaning cache or trying to restore a backup ).
The only thing I have been able to do its to install Rogue XM Recovery 1.5.0 instead of CWM 6.x ) but the problem to apply an update or restore a backup persists.
Any idea ?
Aaargh.
After a year and a half of heavy CWM and TWRP usage, this has suddenly happened to me too, possibly after flashing the updated TWRP blob from Goo Manager (although that's conjecture at best). My ROM (RaymanFX' CM10 v6) is fine in everyday use - no problems whatsoever, but now I want to update, and my recovery won't let me.
In the hope that something simply went wrong during recovery blob flash, I successfully deleted TWRP and flashed a different recovery (latest CWM) from ROM Manager, but the new recovery can't mount anything either - neither sd card, data, or cache. The error messages are more or less identical to TWRP's errors. My system MAY be readable, but I can't backup or restore or flash anything anyway, so I don't dare format it.
I don't have a Windows PC, so I haven't tried Easy Flasher. I could try it on my work computer if there's no way around it and if neither OSX or Ubuntu can help.
Any suggestions?

F2FS on stock

i wanted to know if it is possible to format our system partition as f2fs and have it work our data partition on kitkat is already f2fs so are we able to do it to system? in twrp i attempted this by fro matting to f2fs but when restoring system it reformats system as ext 4 is there away around this? on twrps website there is a command to keep a the file system it is "tw_rm_rf – uses rm –rf instead of formatting system and data partitions, this option is used to prevent changes to the file system settings such as file system type, " i found it here http://www.teamw.in/twrp2-reference-guide would this help to do this? i don't know where to put this command in though
Edit: on a sidenote i formatted cache as f2fs and it booted
Edit 2: i looked at it again and cache was reformatted back to ext4
billycar11 said:
i wanted to know if it is possible to format our system partition as f2fs and have it work our data partition on kitkat is already f2fs so are we able to do it to system? in twrp i attempted this by fro matting to f2fs but when restoring system it reformats system as ext 4 is there away around this? on twrps website there is a command to keep a the file system it is "tw_rm_rf – uses rm –rf instead of formatting system and data partitions, this option is used to prevent changes to the file system settings such as file system type, " i found it here http://www.teamw.in/twrp2-reference-guide would this help to do this? i don't know where to put this command in though
Edit: on a sidenote i formatted cache as f2fs and it booted
Edit 2: i looked at it again and cache was reformatted back to ext4
Click to expand...
Click to collapse
Did you ever succeed in getting stock "DATA" partition to F2FS? I couldn't restore my backup and phone wouldn't boot anymore.. so went back to EXT4..
Maybe @djvita knows something, I think he has been experimenting a bit with F2FS..
StefanGA said:
Did you ever succeed in getting stock "DATA" partition to F2FS? I couldn't restore my backup and phone wouldn't boot anymore.. so went back to EXT4..
Maybe @djvita knows something, I think he has been experimenting a bit with F2FS..
Click to expand...
Click to collapse
yes i was able to get only the data partition to f2fs no other partition will stay another format once it boots it reformats or when restoring system in twrp it will restore the system partition as ext 4
billycar11 said:
yes i was able to get only the data partition to f2fs no other partition will stay another format once it boots it reformats or when restoring system in twrp it will restore the system partition as ext 4
Click to expand...
Click to collapse
interesting.. how did you do it? I did it in TWRP 2.8.1.0 via advanced wipe and after that got stuck on the motorola bootlogo..
That is the same thing I did but after whipeing I restored my data partition. I think the reason you got stuck in a bootloop is because you did not clear dalvic and cache or you do not have the kit Kat boot loader
billycar11 said:
That is the same thing I did but after whipeing I restored my data partition. I think the reason you got stuck in a bootloop is because you did not clear dalvic and cache or you do not have the kit Kat boot loader
Click to expand...
Click to collapse
I tried it again.. this time it worked.. I rebooted after format directly back into recovery and was then able to restore my data from ext4 to f2fs.. not sure, why it didn't work the first time around, but thanks for checking back!

[Q] [BRICK'd?] Can't mount /data /cache /system

One day, about 2-3 weeks ago, on my way to home, I decided to install an other ROM (5.1.1 ivanchi -> CM9). Went straight into recovery (TWRP 2.8.5 or 6) and formatted everything except microsd, everything seemed to go as planned. Then proceeded to install the ROM; it gets stuck, can't get pass the booting screen even after 20-30 minutes. Force-Reboot into recovery and receive "unable to mount /data | /system | /cache error". Tried changing fs-type of /data /cache /system to any other type, no success.
Got back home, tried installing RUU. Got stuck at 39%. every. single. time. !! Tried an older RUU, same response.
Then tried even oem lock + flash recovery_signed.img + boot boot.img with fastboot and then RUU install. Then again with unlocked bootloader. Still no! But, I didn't tried lock + recovery signed + boot + S-On, because I am afraid not to be able to regain S-Off at this state.
Even tried a parted format, implying that one guy managed to make it work in the end. See topic here : link.
Tried doing guy's steps but after parted /dev/block/mmcblk0 I receive Error: Can't have overlapping partitions. Tried then parted /dev/block/mmcblk0p23 (userdata), it works, and if I try mkfs/rm on partition 1, it says it's in use (p23p1 ...).
Output:
~ # parted /dev/block/mmcblk0p23
parted /dev/block/mmcblk0p23
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0p23
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: Unknown (unknown)
Disk /dev/block/mmcblk0p23: 1253MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 1253MB 1253MB ext4
(parted) rm
rm
rm
Partition number? 1
1
1
Error: Partition /dev/block/mmcblk0p23p1 is being used. You must unmount it
before you modify it with Parted.
(parted) mkfs
mkfs
mkfs
Warning: The existing file system will be destroyed and all data on the
partition will be lost. Do you want to continue?
Yes/No? yes
yes
yes
Partition number? 1
1
1
Error: Partition /dev/block/mmcblk0p23p1 is being used. You must unmount it
before you modify it with Parted.
I can format my /data /system /cache one at the time, after doing reboot recovery and that's only in CWM 6.0.1.2. But this CWM isn't able to install ROMs somehow, wether it gets stuck of just plain fails. So, if I want to install a ROM, after the format, I have to install 4Ext (latest) recovery and do it there. Install everything from recovery, boot, sign in for GApps etc etc and while trying to install apps from Google Play, after about 4 to 6 apps, it gives a black screen, leaving no option but remove battery and reboot. Do that and get stuck on bootsplash / bootscreen. Everytime!
If then I try formatting paritions using 4Ext most of the time it fails, making them unmountable again after all.
Tried everything mentioned running PG58IMG with firmware 3.33, Hboot 1.27.1100, worldwide english (.104.). Tried fashing rom.zip as the PG58IMG.zip from fastboot in rebootRUU (gets stuck at [RUU]WP,dzdata,0) and now even from sdCard (gets stuck at [6] USERDATA).
I dug furthermore into bricked Sensation, seeing a QHSUSB brickbug (thread). It is refeered to be a bootloader brickbug; problem which I am not facing right now. Eventho, followed OP's instruction my freshly installed Ubuntu 14.04 can't detect my HTC. Also did some of the YouTube instructions, connecting sdcard's plate with lower pin from the back (trolled?!) (video), yet nothing.
Out of disperation, asked hinxnz and rzr86, and both of you adviced me to try thread 1 or 2 (relying on sdCard as primary/sec partitions). Good advices but I don't consider this be the best solution for this problem; STILL HAVE HOPE MAKING INTERNAL SD TO WORK! :d
ASK ME ANYTHING REGARDING MY PROBLEM! Will post every bit of information you consider relevant.
PLEASE HELP!
u tried ruu, didnt work, tried firmware, didnt work. @rzr86 and @hinxnz gave u those guides coz its the only known way to fix/bypass that problem on xda. maybe there is another way but no one has found it yet. u could take ur phone to a repair shop, pay bout a hundred bucks, connect it to jtag and hope for the best, but that might not even flash partitions back.
personally i dont see how twrp is still allowed to be downloaded on xda in the sensation thread coz it keeps killing peoples phones. that jus my opinion tho.
Atm my phone is literally bricked, QHSUSB brick because of my stupidity... Maybe I will make it to work again; anyways...
For the partition problem, don't the HTC has some kind of .pit files like Samsung does? They should! Also, what if someone with a 'healthy' Pyramid does a dd of the /dev/block/mmcblk* for those with fk'd partitions to use ?
Hi, one more here with wrecked partitions by TWRP factory reset....
Trying to Ruu the Sensation, but RUU has been getting stuck in the process ... I'll edit if I success.
Thanks for all the info out htere!
Edit: no success, even tried at last to fix partitions (parted and fdisk) via ADB, device is now dead. So sad HTC or any ever gave the details for the partition table, a simple script might have solved this.
I'm just catching up on this one.
If I read this right,the information on the partitions was trashed by TWRP recovery?
There was a member that stated the HTC Desire used to be able to have it's partitions reconfigured,IIRC.
Perhaps this is the first step to achieving that with the Sensation?
Sent from my SM-N915W8 using XDA-Developers mobile app
I'm too woried nowadays....i got the error can't mount system,data,cache inmy xolo a600...i can't flash custom rom or can't do factory data reset...but when i try to factory reset using my stock firmware recovery it's done...but in twrp & cwm recoverys say can't mount system,data,cache...i also can't connect my device to pc using usb mode,mtp...my pc said unknown device detected...what to do?...i just really tired & tensed please please please guys give me the solution...please...!!

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

Categories

Resources