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.
Related
Hello.
I attempted to flash the Open Beta 7 (OTA_011) zip with TWRP to my OnePlus 3 and it broke everything.
The flash went normally, like with previous updates, but this time, I couldn't flash SuperSU over it. So I rebooted, hoping it worked.
I was presented by a "Decryption failed" screen, with the only option to factory reset.
The problem is, that I don't have any backups of my data, because FolderSyncLite aparently doesn't work at all.
When I got back into TWRP, my /data partition wasn't mounted, with the error
Code:
could not mount /data and unable to find crypto footer
TWRD shows the Data partition as 0MB. I know the data couldn't have just disappeared.
My best guess is that the userdata partition got corrupted somehow, and because it was encrypted, the entire partition is now useless.
TWRP's fsck.f2fs fails with error 255 (glitched error -1?), probably because it's encrypted.
Is there anything I can do to recover my data? Could I copy the raw partition to my computer and process it there?
Could I manually rebuild the broken header/footer? I still know the pattern/PIN and I don't think they're not salted.
I know there's some brilliant people on here. Please help.
Use the mega unbrick guide and everything will be fine
Edit: i didn't read that you're want to recover your data ... Hmm probably you can't recover your data anymore because your partition is currupted.
Look, change the data partition to ext4. It should work because sometimes the partition gets formatted to a corrupted form of f2fs. If it doesn't work, just wipe userdata and try again. It sure should work. Don't be shocked. Happens.
Thanks for the replies.
I tried a few more things, but the partition was beyond help. Full-disk encryption isn't very fault-tolerant.
I'll be using two sync programs from now on, just in case.
franga2000 said:
Thanks for the replies.
I tried a few more things, but the partition was beyond help. Full-disk encryption isn't very fault-tolerant.
I'll be using two sync programs from now on, just in case.
Click to expand...
Click to collapse
I have the same problem. The unbrick guide didn't help. Any ideas anyone?. Please help
I've recently updated my htc 10 to Android 7.0 using the 2.38.617.6 firmware and added twrp to use for backup purposes. I have attempted to root the device with chainfire's supersu, but failed due to data being in the wrong format.
First off, I managed to find out the the system partition is ridiculously large (17,592,186,044,365 MB) leading me to believe that the system partition has been corrupted.
I've checked the format type for each partition (data, system and cache) they check out to be ext4.
As the title of the post states, I've also ran into that problem before the system partition size issue.
Also, when trying to reboot the system through twrp, I get the message, "No OS Installed! Are you sure you..." but the phone boots up just fine.
Any help is appreciated.
ensure you flashed the latest unoffical twrp from the xda twrp thread. not the official one.
j to the 4n said:
ensure you flashed the latest unoffical twrp from the xda twrp thread. not the official one.
Click to expand...
Click to collapse
I have fixed the issue. I had to find and flash the latest ruu because I had restore the /data partition from when I had the phone rooted and downloaded xposed. I ran through the same process after the flash without restoring the data partition and now it work.
Only downside is that I can't restore my data until xposed has a compatible framework. Thanks for replying.
I got a clean backup of the twrp formatted the sd card with external memory I mounted the backup in the external sd and restored the system .... With that I was successful:dedos cruzados::dedos cruzados:
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.
Hello to everyone. I am using Xperia M and can not mount data, system mount via TWRP Recovery. I also can not load the stock version and kernel with Flashtool. The device goes into recovery mode, is charged and is recognized as a nickname when connected to a PC. I will be glad if you help me.
didyou said:
Hello to everyone. I am using Xperia M and can not mount data, system mount via TWRP Recovery. I also can not load the stock version and kernel with Flashtool. The device goes into recovery mode, is charged and is recognized as a nickname when connected to a PC. I will be glad if you help me.
Click to expand...
Click to collapse
Your device got ebola. There is no solution. Sorry mate.
Use internal storage 0 mb problem in TWRP Recovery. No flashing kernel and roms.
didyou said:
Hello to everyone. I am using Xperia M and can not mount data, system mount via TWRP Recovery. I also can not load the stock version and kernel with Flashtool. The device goes into recovery mode, is charged and is recognized as a nickname when connected to a PC. I will be glad if you help me.
Click to expand...
Click to collapse
i am having same problem . but my internal storage is mounted as android os and my actual storage is not visible please help me.
fix for 0MB internal storage problem
Your device is still recoverable if you can boot into twrp successfully
Go to advanced --> terminal
Check your partition table with
fdisk -l /dev/block/mmcblk0
it will print out the partition table, last 3 should be system, cache and data
format system with ext4, for me that was /dev/mmcblk0p25 - YOURS MAY DIFFER
make_ext4fs /dev/block/mmcblk0p25
format data with ext4, for me that was /dev/mmcblk0p27
make_ext4fs /dev/block/mmcblk0p27
For me, this was met with errors, so format it with exfat first, mkfs.exfat /dev/mmcblk0p27, reboot into recovery, then format with make_ext4fs.
You cannot do this through advanced wipe, because twrp tries to guess your partitions AFTER mounting them, then reads /system is mounted on /dev/block/mmdblk0p25, but it's not mounted, so no repairing/formatting through that. Use the terminal instead, then reboot, twrp will find the partitions then.
afterwards reboot again into recovery. I didn't have to reformat cache, but you may have to. try mkfs.ext2 on that. You will always want to go with make_ext4fs though.
internal storage should show up again now, wiping and installing zips will work again.
rak-zero said:
Your device is still recoverable if you can boot into twrp successfully
Go to advanced --> terminal
Check your partition table with
fdisk -l /dev/block/mmcblk0
it will print out the partition table, last 3 should be system, cache and data
format system with ext4, for me that was /dev/mmcblk0p25 - YOURS MAY DIFFER
make_ext4fs /dev/block/mmcblk0p25
format data with ext4, for me that was /dev/mmcblk0p27
make_ext4fs /dev/block/mmcblk0p27
For me, this was met with errors, so format it with exfat first, mkfs.exfat /dev/mmcblk0p27, reboot into recovery, then format with make_ext4fs.
You cannot do this through advanced wipe, because twrp tries to guess your partitions AFTER mounting them, then reads /system is mounted on /dev/block/mmdblk0p25, but it's not mounted, so no repairing/formatting through that. Use the terminal instead, then reboot, twrp will find the partitions then.
afterwards reboot again into recovery. I didn't have to reformat cache, but you may have to. try mkfs.ext2 on that. You will always want to go with make_ext4fs though.
internal storage should show up again now, wiping and installing zips will work again.
Click to expand...
Click to collapse
Thank you for your message I just saw. I tried, but I still see the internal memory of 0MB when I try to Wipe.
https://imgyukle.com/i/Rk24Gt
https://imgyukle.com/i/Rk264c
https://imgyukle.com/i/Rk2fyR
didyou said:
Thank you for your message I just saw. I tried, but I still see the internal memory of 0MB when I try to Wipe.
Did you reboot after? You can try the advanced format in twrp, maybe you need to use exfat for your partition 27 (data) or ext3 not ext4 for system. Try some combinations.
Which twrp version is installed?
I checked mine and partitions 25 to 27 are formatted with ext4. I have latest twrp 3.0.2.0 and use lineage 14.1. from here.
Partition table looks fine, same sizes as me.
Click to expand...
Click to collapse
rak-zero said:
didyou said:
Thank you for your message I just saw. I tried, but I still see the internal memory of 0MB when I try to Wipe.
Did you reboot after? You can try the advanced format in twrp, maybe you need to use exfat for your partition 27 (data) or ext3 not ext4 for system. Try some combinations.
Which twrp version is installed?
I checked mine and partitions 25 to 27 are formatted with ext4. I have latest twrp 3.0.2.0 and use lineage 14.1. from here.
Partition table looks fine, same sizes as me.
Click to expand...
Click to collapse
I am using TWRP version 3.1.1.0. I tried to make Wipe after it restarted after operations but it still seems to be 0MB. I tried to change the file system, but not through the terminal.
Click to expand...
Click to collapse
I was running oos based nougat custom rom with blu spark recovery. Then flashed official ob1, didnt like it, wiped cache/data/system and reinstalled my old oos nougat rom (audax 4.7.6). Now i get the above mentioned message..
Things i tried:
- addionally wipe internal storage and media (installed rom via adb sideload then)
- reformat system/cache/date with ext4
I googled the error and for most people (threads werent particularly concerning the op5t however) it seems that just wiping data and reinstalling the rom did the trick. Not for me though..
What can i do now?
Solution: reformating the data partition with ext4 is not enough. I had to format to FAT and right after that again to ext4, reboot to system and boom, it worked!
PS: i wonder what data is on the internal storage partition that i deleted? I didnt have any data on the phone, i just wonder.. It isnt somehow crucial to the phone?!
I think the decryption key is somehow embedded into the internal storage as wiping /data does not delete the PIN/pattern. Might be a hidden partition or something similar that is not wiped when wiping /data as long as it is ext4.
Your data is gone. It failed to completely encrypt and now there's nothing that can be done. Format /data as ext4 and let it try encrypting again
I have the same problem exactly. Can you explain in steps you have installed then format or how?
I have the same problem exactly. Can you explain in steps you have installed then format or how?
Click to expand...
Click to collapse
I had the exact same problem. But it is an easy fix but does require wiping your internal storage.
So the save way of doing this would be:
1. Backup all your data by going to TWRP or your ROM if that still works. Plug in an USB cable and use MTP or the adb pull command to backup your data
2. Reflash OB1 with no root (like Magisk of SuperSU) if you have TWRP. This will cause you to have the stock recovery again. I also recommend to do a clean flash (Wiping system and data before flashing the rom).
3. Download the rollback build from Oneplus [HERE] and copy this to the internal storage.
4. Boot into the stock recovery flash the rollback build. THIS STEP WILL WIPE YOUR INTERNAL STORAGE.
5. Now you have OxygenOS 4.7.5. Download OxygenOS 4.7.6 Incremental Update [HERE]
6. Go back to the Stock recovery and flash the incremental 4.7.6 zip.
7. You have the latest version now. So boot to fastboot reflash TWRP and flash SuperSU or Magisk in TWRP to regain root
Guys I did a fail, i had OB3 installed, and I wanted to try RR so I wiped system and when I tried to install I have seen error 7 saying its for dumpling not for oenplus5t.
So I restored.... But instead restoring OB3 I have restored stock Nougat rom -.- I have even stock recovery now, what is the best way to fix it?
Can i change to FAT and stay and dont go back to ex4 again?
Hi i don't know if u r reading this but if you are please help me cause I'm so lost and confused over this since yesterday...
so 2 days ago my phone started lagging and hanging and freezing until i realized i have got this issue with data encryption
i have a rooted sony z2 with TWRP Custom recovery
first i didn't know it was with data encryption failure so i literally factory reset and installed all my apps and data again and again!!! after every time my phone started to lag !!
after one whole day of trying everything i finally realized its actually with the data encryption and i should change my ex4 to something else... so here again i wiped the phone and changed to ex3 and installed and all my data and apps all over again
but after a couple hours...same problem again.....
im literally so tired of not knowing what to do ! my head hurts so much due this ugh....
i havent changed to FAT from ex3 so im wondering if it will finally solve my problem permanently if i change to FAT ??
And if it did can i just keep it on FAT forever ?
Please guide me thanks ...!
Lasersdude said:
I was running oos based nougat custom rom with blu spark recovery. Then flashed official ob1, didnt like it, wiped cache/data/system and reinstalled my old oos nougat rom (audax 4.7.6). Now i get the above mentioned message..
Things i tried:
- addionally wipe internal storage and media (installed rom via adb sideload then)
- reformat system/cache/date with ext4
I googled the error and for most people (threads werent particularly concerning the op5t however) it seems that just wiping data and reinstalling the rom did the trick. Not for me though..
What can i do now?
Solution: reformating the data partition with ext4 is not enough. I had to format to FAT and right after that again to ext4, reboot to system and boom, it worked!
PS: i wonder what data is on the internal storage partition that i deleted? I didnt have any data on the phone, i just wonder.. It isnt somehow crucial to the phone?!
Click to expand...
Click to collapse
Finally. Thank you so much!