I have a problem with my phone.
I believe that the internal partitions are messed up.
I have tried a couple of guides to fix this but no luck. I get "error formatting /data!" on recovery. I also tried using the formatting tools from adb shell (e2fsck, gparted).
The main problem is that when i restart my phone the /data partition gets wiped, and the phone reboots in blank, no apps no setting (some of them remain).
I wonder if i can solve this by setting my sd-card to be the new /data. I doesn't matter if i have to leave the sd-card on all the time. i mainly use this phone for developing apps.
Thanks.:good:
Felivel said:
I have a problem with my phone.
I believe that the internal partitions are messed up.
I have tried a couple of guides to fix this but no luck. I get "error formatting /data!" on recovery. I also tried using the formatting tools from adb shell (e2fsck, gparted).
The main problem is that when i restart my phone the /data partition gets wiped, and the phone reboots in blank, no apps no setting (some of them remain).
I wonder if i can solve this by setting my sd-card to be the new /data. I doesn't matter if i have to leave the sd-card on all the time. i mainly use this phone for developing apps.
Thanks.:good:
Click to expand...
Click to collapse
It could probably be done if you could get the sdcard to mount at boot, not sure if thats possible. You would need to create a flashable much like the ext4 mod, that edits the init.inc.rc file to mount the sdcard and /data to it. You would want to partition your sdcard with an ext3 or ext4 partition and use that for data.
Yes it can be done. That's how boot manager works, by modifying the ramdisk to load images from sdcard or emmc instead of the partition. I think I have an idea on how to make your request work.
Edit: If you feel like trying a project, what needs to be done is create a file data.img and mount it as loopback using busybox (ROM needs a working busybox).
Then the boot.img needs to be updated replacing the mount /data entry in init.inc.rc with the location of the loopback device and a loopback setup prior to this. The data.img created needs to be formatted ext3 or ext4. I know it's not too detailed but rather just a summary.
Ok, here is the problem, i woke up today, my phone battery was empty, i connected the phone battery was loading, but i couldn't get to the system, after kernel load it stops, like there was no system installed. Everything worked fine day before,my configuration was: Doomkernel and Existenz_2.0.5 ROM.
So, i got to recovery (recovery works,CWM), and there i saw "can't mount cache" error. I got into shell with adb (this works too), and there is no way i can mount any system partition (/system, /cache, /data), what's more important /sdcard does not mount either. So, i'm in recovery, can't install or restore from sdcard,cause /sdcard does not mount.
I'v tried sideload, no go.
I've tried fastboot flash new kernel, and here's interesing thing, fastboot reported that flashing was ok, but i still have Doomkernel (i was trying to flash 6.0-TUX-Core-HD kernel. So seems like fastboot did not write anything at all.
I've tried flashtool with stock tft. It breaks with "final verification error", when i turn "final verification off" it goes all the way, says everything is installed, but when i restarted, still only Doomkernel.
Any ideas ? I take any advice.
Maybe you have already tried it, but format your phone's data, THEN the cache, and finally the internal storage (SD card). In XS's CWM, there's a bug, which causes sometimes an unformatable and unusable cache parition. But this method can be help on this. Maybe this problem causes those unformatable partitions.
Szatyor said:
Maybe you have already tried it, but format your phone's data, THEN the cache, and finally the internal storage (SD card). In XS's CWM, there's a bug, which causes sometimes an unformatable and unusable cache parition. But this method can be help on this. Maybe this problem causes those unformatable partitions.
Click to expand...
Click to collapse
Thank you for your reply. Haven't tried that but i have now and, unfortunately, no go. With /data and /cache seems like format was success but it didn't ( still can't Mount) and with /sdcard format fails (error mounting /sdcard).
Maybe my sdcard really died ?
qrto said:
Thank you for your reply. Haven't tried that but i have now and, unfortunately, no go. With /data and /cache seems like format was success but it didn't ( still can't Mount) and with /sdcard format fails (error mounting /sdcard).
Maybe my sdcard really died ?
Click to expand...
Click to collapse
Well, I don't think so. The "SD Card" is a part of the memory chip, which includes the system, the data and the cache partitions too. Because you cannot copy anything now to the internal storage, try to install a ROM from ADB Sideload if you can. Once it done, your phone can be boot maybe again. If it happens, try to format the internal storage by the Android. If it fails, connect the phone to your computer, and try to format with Windows or (it can be better) Linux to fat32 filesystem.
Szatyor said:
Well, I don't think so. The "SD Card" is a part of the memory chip, which includes the system, the data and the cache partitions too. Because you cannot copy anything now to the internal storage, try to install a ROM from ADB Sideload if you can. Once it done, your phone can be boot maybe again. If it happens, try to format the internal storage by the Android. If it fails, connect the phone to your computer, and try to format with Windows or (it can be better) Linux to fat32 filesystem.
Click to expand...
Click to collapse
Thank you for your ideas. Thing is, all i can start is cwm recovery. As i wrote, i can't install anything with sideload. And no partition is working. When i start parted /dev/block/mmcblk and try to list partitions, i get unrecognized disk label error, when i try to manually set disk label to msdos, there's I/O Error.
And i can't format sdcard, because when in recovery, phone is not detected by Linux nor Windows. But i tried formatting partitions internally, with mke2fs, and with fastboot command. No go.
I know that /sdcard is just a partition, but what i meant was that probably my phone memory chip died, like hardware died. but i'm still looking for new ideas i want to try everything before giving up.
qrto said:
Thank you for your ideas. Thing is, Alp i can start iż cwm recovery. As i wrote, i can't install anything with sideload. And no partition is working. When i start parted /dev/block/mmcblk and try to list partitions, i get unrecognized disk label error, when i try to manually set disk label to msdos, there's I/O Error.
And i can't format sdcard, because when in recovery, phone is not detected by Linux nor Windows. But i tried formatting partitions internally, with mke2fs, and with fastboot command. No go.
I know that /sdcard is just a partition, but what i meant was that probably my phone memory chip died, like hardware died. but i'm still looking for new ideas i want to try everything before giving up.
Click to expand...
Click to collapse
Then maybe it's a HW error really. But maybe just the partition table is corrupted. At this point, I don't know. I have only one suggestion left: Take the phone to the nearest SONY Center or GSM shop/service to investigation. But I think they will say you'll need to replace the phone's motherboard. Anyway, it's an too expensive solution I think, because this phone is a "retired" modell without any update, but with a "blacksheep (Snapdragon S3) SoC.
Hey guys
So i was trying to flash the new RR remix 7..
I formatted everything and now my TWRP shows 0 MB and i am unable to mount or flash ANYTHING except firmwares and recoveries.
I have NO clue what's going on
Any help will be greatly appreciated.
Thank you!
I was using 7.x the other day and tried to revert back to 6.x. Unfortunately, I couldn't because the data partition was set as f2fs. I tried changing it back to ext4 through twrp and it wouldn't work. It kept saying something about the data partition is busy or in use.
I fixed this by booting into fastboot and reformatting the data partition from there using the command: fastboot format:ext4 data (or maybe it was userdata?) I forgot lol.
Also, which partition did you reformat? I think it's only cache and data that is to be changed to f2fs for that ROM.
Hi,
Hope you guys can help me getting my data back.
I messed around with Substratum in legacy mode on OOS 4.1.0 and ended up with a bootloop (I never saw the boot animation restart, just looping endlessly). To fix, I tried the following things:
Flashed the SubstratumRecovery_legacy.zip in TWRP 3.1.0-0 without any effect.
Dirty-flashed OnePlus3Oxygen_16_OTA_047_all_1703132116_f7372e67 without any effect.
Flashed OnePlus3Oxygen_16_OTA_047_all_1703132116_f7372e67 through ADB sideload without any effect.
Wiped data partition in recovery. System started normally, all data gone (obviously).
Before wiping, I had made a backup of my /data partition (through TWRP backup tool for Mac) and saved the content of /sdcard on the computer as well.
Now when I try to restore the /data backup through the same tool, I get an error:
E:Unable to find file system (first period).
E:Unable to find file system (first period).
E:Unknown restore method for '/data'
ADB Restore failed.
So what can I do to restore my data partition? That's all I care about.
Thanks in advance
Mount data in twrp?..
ASFAIK, /data is mounted rw automatically by TWRP. It also doesn't make a difference.
Moreover, I also cannot restore my boot partition (kernel), same error.
A while ago I changed my filesystem to f2fs. Can that be the culprit?
Nevermind, I've given up and accepted the loss of data. However, it would still be interesting to find out what the problem was
I had the same problem, tried several times. Then I went back and turned of the md5 check and it worked perfect.
Do u still have ur trwp backup or did u delete it
https://forum.xda-developers.com/showpost.php?p=53913623&postcount=22
I still have it on the computer and wouldn't mind making use of it (installed official Resurrection Remix after the data loss but that just wiped my /data partition after backing up kernel in TWRP)
@Bradl79: sounds interesting, will give that a go later when I have some time.
Device storage corrupt
-The data partition has been corrupted. You need to reset your device to factory default settings. This will erase all your data.
I tapped on reset but it just opened twrp and returned to this.
Story - I was trying to back up before a root. It said unable to mount /data so I watched a video that told me to change the file system. Now, this. I changed the system to vfat if it matters.
version - 7 model - SM-A504 build - can't access settings to check.
NVM I FIXED IT
HOW
Giphitt said:
Device storage corrupt
-The data partition has been corrupted. You need to reset your device to factory default settings. This will erase all your data.
I tapped on reset but it just opened twrp and returned to this.
Story - I was trying to back up before a root. It said unable to mount /data so I watched a video that told me to change the file system. Now, this. I changed the system to vfat if it matters.
version - 7 model - SM-A504 build - can't access settings to check.
NVM I FIXED IT
Click to expand...
Click to collapse
How did you fix this issuse? My mother has just had the same problem with her phone, and I'm trying to look for a solution. thx in adv.
MorningGory said:
How did you fix this issuse? My mother has just had the same problem with her phone, and I'm trying to look for a solution. thx in adv.
Click to expand...
Click to collapse
You can fix it by changing the file format of the data partition to EXT2 and EXT4. This will mount the /data to twrp, and you will need to factory reset within twrp since if you reboot to the android, it will encrypt /data again.
what should be partitions format of data,system and cache?