Unable to Mount Data in TWRP - OnePlus 5T Questions & Answers

I recently flashed OOS 8.0 Beta 1 and now I am no longer able to mount my data partition. I have flashed the official TWRP and Blu_Spark TWRP, but neither is able to mount data. It does not provide any error messages, but when I attempt to mount the data partition it simply will not mount it.
Any suggestions? I am willing to wipe everything if needed, as I performed a back up prior to flashing OOS 8.0.
Thanks in advance!

You are probably encrypted, I think TWRP is not able to decrypt data yet.
Sent from my OnePlus5T using XDA Labs

Unn113 said:
You are probably encrypted, I think TWRP is not able to decrypt data yet.
Sent from my OnePlus5T using XDA Labs
Click to expand...
Click to collapse
Thanks for the response Unn113. Do I simply need to format and start from scratch?

trippmcnealy said:
I recently flashed OOS 8.0 Beta 1 and now I am no longer able to mount my data partition. I have flashed the official TWRP and Blu_Spark TWRP, but neither is able to mount data. It does not provide any error messages, but when I attempt to mount the data partition it simply will not mount it.
Any suggestions? I am willing to wipe everything if needed, as I performed a back up prior to flashing OOS 8.0.
Thanks in advance!
Click to expand...
Click to collapse
Same thing happened to me. I fastboot flashed the recovery.img to get it working again. I flashed the Blue_Spark from this thread
[OFFICIAL] OxygenOS Open Beta 1 (Android O) for the OnePlus 5T
Post#2

Jackson.Armstrong.Blow said:
Same thing happened to me. I fastboot flashed the recovery.img to get it working again. I flashed the Blue_Spark from this thread
[OFFICIAL] OxygenOS Open Beta 1 (Android O) for the OnePlus 5T
Post#2
Click to expand...
Click to collapse
Thanks!

trippmcnealy said:
I recently flashed OOS 8.0 Beta 1 and now I am no longer able to mount my data partition. I have flashed the official TWRP and Blu_Spark TWRP, but neither is able to mount data. It does not provide any error messages, but when I attempt to mount the data partition it simply will not mount it.
Any suggestions? I am willing to wipe everything if needed, as I performed a back up prior to flashing OOS 8.0.
Thanks in advance!
Click to expand...
Click to collapse
Use this Blu_Spark and it should work.
BTW, questions & troubleshooting issues belong in the Help section. A mod will move this thread there shortly.
Unn113 said:
You are probably encrypted, I think TWRP is not able to decrypt data yet.
Click to expand...
Click to collapse
The Blu_Spark above works with encryption for me. Just make sure lockscreen security is set to none or swipe before booting into recovery.

the Doctor said:
Use this Blu_Spark and it should work.
BTW, questions & troubleshooting issues belong in the Help section. A mod will move this thread there shortly.
The Blu_Spark above works with encryption for me. Just make sure lockscreen security is set to none or swipe before booting into recovery.
Click to expand...
Click to collapse
Yes, so it don't work fully, and it's better to either don't use security, (but what's the point of encryption if phone is not secure), or don't mess with risky stuff for now, till twrp bug gonna be fixed.
Sent from my OnePlus5T using XDA Labs

Either blu_spark or ibe recovery work. They also work with lockscreen security setup, no problems over here.

Unn113 said:
Yes, so it don't work fully, and it's better to either don't use security, (but what's the point of encryption if phone is not secure), or don't mess with risky stuff for now, till twrp bug gonna be fixed.
Click to expand...
Click to collapse
How do you figure? I've successfully backed up my previous ROM and flashed another one using that TWRP, my device is encrypted properly, I've reset lockscreen security, and my device passes SafetyNet.

Had the same issue. Flashing Blu_Spark worked perfectly. Thanks @the Doctor

help for twrp
TWrp message
message came to me
say
E: primary block device /dev/block/mmcb1kop8
for mount point /data is not present
failed to mount data
unable to create /data/media folder,
icant install rom and wipe data and now dont have any rom to open my device
please help me

I had this problem after installing TWRP 3.2.1-1. A new version was released last night (3.2.1-2) which I flashed this morning and seems to solve the problem. You can find the new version here.

Related

HELP: Issues updating rooted device to OOS 3.2.8

hello all,
I have a rooted OP3 running the latest TWRP recovery. Using these instructions I am trying to upgrade to 3.2.8 from 3.2.7. There are no errors displayed during OOS or SuperSU install steps.
But when the phone reboots - it stays stuck at the boot animation. This happens across several attempts. I do not have xposed installed, if it helps. Repeating the above steps with a 3.2.7 image works without issues.
Is there any way I can figure out where the 3.2.8 reboot is getting stuck at? I *do not* want to do a fresh install.
Any thoughts/ Suggestions? I have already posted at the above thread and thought I'd try my luck here too.
EDIT: Can a MOD please move this to Q&A forum. Just realized I posted to Guides, News & Discussion.
backup all your data and install 3.2.8 with the official procedure
Sacob said:
backup all your data and install 3.2.8 with the official procedure
Click to expand...
Click to collapse
That's my last option. But that's as good as starting from scratch. In which case, I might as well postpone until Nougat arrives on the OP3
tropicanapure said:
That's my last option. But that's as good as starting from scratch. In which case, I might as well postpone until Nougat arrives on the OP3
Click to expand...
Click to collapse
and wait without a phone?
Flash the new Beta 10. i'm currently using it with root and it works great
Not sure what you mean - without a phone. I was able to roll back to 3.2.7 with zero issues
I was mulling over installing the Beta - but I understand Nougat is due in Jan? Also, is there a process to move to b10 without losing data?
Sacob said:
and wait without a phone?
Flash the new Beta 10. i'm currently using it with root and it works great
Click to expand...
Click to collapse
tropicanapure said:
Not sure what you mean - without a phone. I was able to roll back to 3.2.7 with zero issues
I was mulling over installing the Beta - but I understand Nougat is due in Jan? Also, is there a process to move to b10 without losing data?
Click to expand...
Click to collapse
i got the impression that your phone wasn't booting xD
well, every time i flash those betas (9 and 10) TWRP asks me for a PIN that doesn't exists and to solve that i need wipe everything... so i wouldn't count on that
tropicanapure said:
hello all,
I have a rooted OP3 running the latest TWRP recovery. Using these instructions I am trying to upgrade to 3.2.8 from 3.2.7. There are no errors displayed during OOS or SuperSU install steps.
But when the phone reboots - it stays stuck at the boot animation. This happens across several attempts. I do not have xposed installed, if it helps. Repeating the above steps with a 3.2.7 image works without issues.
Is there any way I can figure out where the 3.2.8 reboot is getting stuck at? I *do not* want to do a fresh install.
Any thoughts/ Suggestions? I have already posted at the above thread and thought I'd try my luck here too.
EDIT: Can a MOD please move this to Q&A forum. Just realized I posted to Guides, News & Discussion.
Click to expand...
Click to collapse
Did you download the full 3.2.8 zip from http://downloads.oneplus.net? I did. And to my surprise, it erases the whole userdata partition, including TWRP backups and downloaded files (including SuperSU zip). So big warning if you try with that zip. I assume that this zip is intended for those reverting from Nougat Beta, to go back from F2FS to EXT4.
My solution was to restore an old TWRP backup that was saved on my PC and then reflash a modified full 3.2.8 zip where the last line in the update script was removed: the one that erases userdata partition. So before flashing full 3.2.8 zip from http://downloads.oneplus.net I recommend you to remove the last line in the update script.
No, I downloaded the Full ZIP from this official thread on the OP3 forums. I was aware of that line though. And from previous experience - the first thing I do when I make a TWRP backup is to move it off the phone. That and I purchased Titanium Backup long time ago. I use it to back up stuff surgically and sync it up to Dropbox every night. The app also seems to have the ability to make a recovery-flashable "update.zip" - something I have yet to try.
Appreciate the heads-up though.
ptblad said:
Did you download the full 3.2.8 zip from http://downloads.oneplus.net? I did. And to my surprise, it erases the whole userdata partition, including TWRP backups and downloaded files (including SuperSU zip). So big warning if you try with that zip. I assume that this zip is intended for those reverting from Nougat Beta, to go back from F2FS to EXT4.
My solution was to restore an old TWRP backup that was saved on my PC and then reflash a modified full 3.2.8 zip where the last line in the update script was removed: the one that erases userdata partition. So before flashing full 3.2.8 zip from http://downloads.oneplus.net I recommend you to remove the last line in the update script.
Click to expand...
Click to collapse
tropicanapure said:
No, I downloaded the Full ZIP from this official thread on the OP3 forums. I was aware of that line though. And from previous experience - the first thing I do when I make a TWRP backup is to move it off the phone. That and I purchased Titanium Backup long time ago. I use it to back up stuff surgically and sync it up to Dropbox every night. The app also seems to have the ability to make a recovery-flashable "update.zip" - something I have yet to try.
Appreciate the heads-up though.
Click to expand...
Click to collapse
OK. I also use TB, and from now on I use cloud storage :laugh:
After the full modified 3.2.8 zip I successfully flashed official SuperSU 2.79, Xposed v87 and Bluspark r25 kernel. I use F2FS on data partition. It boots and runs fine!
The only thing I'm a bit concerned about is that it stays on the bootlogo (OnePlus logo, Powered by Android) for about 25 secs before the bootanimation begins when booting to system. Much faster before. When booting to recovery (TWRP 28, Bluspark) the time on bootlogo is normal (short). Any thoughts on that?
I wish I had, man. You went a number of steps ahead when your phone went past the boot animation
As a afterthought - try looking through your logs.
ptblad said:
OK. I also use TB, and from now on I use cloud storage :laugh:
After the full modified 3.2.8 zip I successfully flashed official SuperSU 2.79, Xposed v87 and Bluspark r25 kernel. I use F2FS on data partition. It boots and runs fine!
The only thing I'm a bit concerned about is that it stays on the bootlogo (OnePlus logo, Powered by Android) for about 25 secs before the bootanimation begins when booting to system. Much faster before. When booting to recovery (TWRP 28, Bluspark) the time on bootlogo is normal (short). Any thoughts on that?
Click to expand...
Click to collapse

Kinda of a weird thing can't decrypt recovery

Hey guys i flashed twrp-3.0.2-1.28-oneplus3.img and now when i am trying to put in my pattern i doesn't work and it says it can't be decrypted. So what can i do you guys?
Thank you in advance,
Rick
jamesblunt1 said:
Hey guys i flashed twrp-3.0.2-1.28-oneplus3.img and now when i am trying to put in my pattern i doesn't work and it says it can't be decrypted. So what can i do you guys?
Thank you in advance,
Rick
Click to expand...
Click to collapse
It's the problem with nougat update and twrp currently. Look for other threads to see what options you have.
TWRP is in present state is not fully updated to support Nougat on OP3. So if your device is encrypted, it will show you this error. You can try the .19 twrp version as i read somewhere it works fine but i doubt it. Worth giving a shot.
abhibnl said:
TWRP is in present state is not fully updated to support Nougat on OP3. So if your device is encrypted, it will show you this error. You can try the .19 twrp version as i read somewhere it works fine but i doubt it. Worth giving a shot.
Click to expand...
Click to collapse
.19 worked for me.
Wipe the /data partition and it won't ask for the pattern.
dbabaev21 said:
.19 worked for me.
Click to expand...
Click to collapse
To OP, Can you please try .19 version of twrp as suggested and see if it can decrypt your encrypted storage?
abhibnl said:
TWRP is in present state is not fully updated to support Nougat on OP3. So if your device is encrypted, it will show you this error. You can try the .19 twrp version as i read somewhere it works fine but i doubt it. Worth giving a shot.
Click to expand...
Click to collapse
You are wrong. Mine works just fine. To remove encryption, all one needs to do is wipe the data partition and reformat as f2fs. If you are having issues with login (pin/pattern), in TWRP go to data/system and delete two files, gatekeeper.pattern.key and locksettings.db. When you reboot, just swipe and reconfigure your pattern and fingerprint. Done!
jim262 said:
You are wrong. Mine works just fine. To remove encryption, all one needs to do is wipe the data partition and reformat as f2fs. If you are having issues with login (pin/pattern), in TWRP go to data/system and delete two files, gatekeeper.pattern.key and locksettings.db. When you reboot, just swipe and reconfigure your pattern and fingerprint. Done!
Click to expand...
Click to collapse
Please read what i typed, again. Why would i want to remove encryption and wipe my internal storage just because the TWRP is outdated? /data also includes your /data/media which is internal storage. I mentioned that TWRP is not supporting encrypted storage in it's present state. It's working fine for decrypted storage and it won't ask for a password if your storage is decrypted.
jim262 said:
You are wrong. Mine works just fine. To remove encryption, all one needs to do is wipe the data partition and reformat as f2fs. If you are having issues with login (pin/pattern), in TWRP go to data/system and delete two files, gatekeeper.pattern.key and locksettings.db. When you reboot, just swipe and reconfigure your pattern and fingerprint. Done!
Click to expand...
Click to collapse
Even if you use this method, if you flash the official ROM later via TWRP, it won't work right. TWRP will prompt for a password even though you've never set one. So actually he's not really wrong.
I used this "method" just last night on my OP3. Loaded the OS via side load and SU also. I am writing to you on this device right now. I also got an AnTuTu score of over 157,484 running stock OOS 4.0. If you are having issues, they are more than likely user issues.
Please read this install method. It will help with data encryption.
https://forum.xda-developers.com/showthread.php?p=70429702#post70429702

[RECOVERY][TWRP][OFFICIAL] TWRP 3.2.1.0 encrypted /data - cant mount

I searched and didn't found... searched longer than an hour....
nexus 5x, lineageos (not rooted), twrp installed, bootloader open
PROBLEM: when I reboot to recovery twrp asks for lock pattern, so I can't mount /data
Yes I can format data and so on...
But hoe can I flash ROMs (LOS-updates) without loosing the data every time?
Why can't I read the data partition?
First of all, you're posting in the wrong section.
Second, you answered your question yourself when you wrote the title - ENCRYPTED /data. Your /data partition should be decrypted. (read)
Flashing rom updates without losing your data is called dirty flashing - all you need to wipe is /cache and /dalvik(or /art), after that you simply flash the new rom build.
Keep in mind - dirty flashing could: cause new problems; not fix existing ones.
When experiencing issues, go for clean flash.
Thanks.
When Q&A is the right section, then this could be moved, I can't.
But: I did a clean flash, with "advanced data" and factory reset. And I got this encryption problem.
I already made a clean flash again and the pattern comes back.
I don't understand, where is the step I made the mistake.
Also got a g4 h815 here it works....
Again:
shhnedo said:
Your /data partition should be decrypted. (read)
Click to expand...
Click to collapse
Thanks I read it tomorrow, it's 2 aclock in the night in Germany....
By the way , I'm on 14.1 7.2.1 not on 8.1
shhnedo said:
First of all, you're posting in the wrong section.
Second, you answered your question yourself when you wrote the title - ENCRYPTED /data. Your /data partition should be decrypted.
Click to expand...
Click to collapse
Im also facing the same problem... But as you said it has to decrypted that's not correct as far as i know. I flashed many rom in my encrypted Nexus 5X. But never had any problem. Suddenly after flashing crDroid Oreo beta it keep s asking password.
Noob_Master said:
Im also facing the same problem... But as you said it has to decrypted that's not correct as far as i know. I flashed many rom in my encrypted Nexus 5X. But never had any problem. Suddenly after flashing crDroid Oreo beta it keep s asking password.
Click to expand...
Click to collapse
crDroid and many other LOS base ROMs have the "forcefdeorfbe" flag set in the boot.img. (It is the LOS standard to set this). While most don't feel there is a "speed hit" when running encrypted, I don't like the hassle between ROM flashes.

Unable to wipe data in TWRP

So, I unlocked my bootloader and wanted to flash Lineage OS, but my phone had a different opinion.
I went into TWRP and tried to format data, but I'm getting
Code:
Formatting Data using mkfs.f2fs...
mkfs.f2fs -t 0 -r 16384 /dev/block/mmcblk0p56
process ended with ERROR: 1
Unable to wipe Data.
Unable to format to remove encryption.
I've tried repairing the data partition, changing the filesystem, nothing works...
Any ideas as to what might be wrong, or how to fix it?
Thanks
todorare said:
So, I unlocked my bootloader and wanted to flash Lineage OS, but my phone had a different opinion.
I went into TWRP and tried to format data, but I'm getting
I've tried repairing the data partition, changing the filesystem, nothing works...
Any ideas as to what might be wrong, or how to fix it?
Thanks
Click to expand...
Click to collapse
Which recovery are u using ?
Armaty said:
Which recovery are u using ?
Click to expand...
Click to collapse
I was using TWRP, but I somehow managed to fix it using Redwolf. Have no idea what happened, but it's ok now.
Hello, I encountered the exact same issue with same origin...
Do you remember what you did to sort this out ?
thanks
(I posted in another thread, before finding yours)
You should check the f2fs kernel workaround guide .
Your problem is due to using incompatible twrp .
Read the guide you'll get around the problem .
0101chaitanya said:
You should check the f2fs kernel workaround guide .
Your problem is due to using incompatible twrp .
Read the guide you'll get around the problem .
Click to expand...
Click to collapse
Thanks... well that's weird, because I downloaded the TWRP recovery linked in LineageOs kuntao install page and I'm coming from stock...
Anyway I just solved my issue by installing Redwolf recovery :
There I could format /data.
I installed crdroid + gapps, but got a "Encryption Unsuccessful" on reboot.
I changed /data from f2fs to ext4 and could reboot properly.
Phone is working good. (I can't get fingerprint reader to unlock my crdroid rom but that's another story and maybe normal limitation, I'll check).
eljuggy said:
Thanks... well that's weird, because I downloaded the TWRP recovery linked in LineageOs kuntao install page and I'm coming from stock...
Anyway I just solved my issue by installing Redwolf recovery :
There I could format /data.
I installed crdroid + gapps, but got a "Encryption Unsuccessful" on reboot.
I changed /data from f2fs to ext4 and could reboot properly.
Phone is working good. (I can't get fingerprint reader to unlock my crdroid rom but that's another story and maybe normal limitation, I'll check).
Click to expand...
Click to collapse
If you ever need to format data just use official build from twrp.me. The one from Lineage wiki has some problems for now. Redwolf is probably based on official one, that's why you succeded.
The thing is that you need to use it ONLY to format /data partition and then switch back to Lineage one before flashing system zip. Known problem, wiki is just a little misguiding here.
Hello. Same problem here, not solved with RedWolf, neither official TWRP.
I've just followed the guide about lineage 15.1 and I really don't know how/if proceed.
Any help would be really appreciated
trespass23 said:
Hello. Same problem here, not solved with RedWolf, neither official TWRP.
I've just followed the guide about lineage 15.1 and I really don't know how/if proceed.
Any help would be really appreciated
Click to expand...
Click to collapse
Update: after closing and run again RedWolf, tap to Format data, magically it worked. I don't know why but thats'it.
Thanks.
this issue seems to pop-up now and then.
just to make it easier for future users coming across this issue. I had explained the issue here in the following post and how to fix it.
just scroll down till it says: "so for those that would like to switch to f2fs but for some reason end up in "black screen with blue led and the phone vibrates".
it applys to the same /data issue.
page 25 off official lineageos 8.1 thread:
https://forum.xda-developers.com/lenovo-p2/development/rom-lineageos-15-1-p2-t3814361/page25

Recovery

What kind of recovery is recovery-oneplus7t-3.4.2-10.0-b26.img? is it the chinese TWRP one?
altojd said:
What kind of recovery is recovery-oneplus7t-3.4.2-10.0-b26.img? is it the chinese TWRP one?
Click to expand...
Click to collapse
Yes
Where did you find it ?
Any idea why after flashing recovery-oneplus7t-3.4.2-10.0-b26.img (chinese twrp) being in recovery mode i don't see ANYTHING in sdcard?
altojd said:
Any idea why after flashing recovery-oneplus7t-3.4.2-10.0-b26.img (chinese twrp) being in recovery mode i don't see ANYTHING in sdcard?
Click to expand...
Click to collapse
Please could you pm the link to this recovery please l think flashing this recovery will format your data because it changes the file system which is why it works
a g bell said:
Please could you pm the link to this recovery please l think flashing this recovery will format your data because it changes the file system which is why it works
Click to expand...
Click to collapse
i found this recovery in msm extended telegram chat.
the installation did not format my data since i have all my apps working and i can see the entire internal storage when i connect the phone to pc.
I have this recovery on my device for a later time in case I decide to move away from OOS so I can't speak to experience...BUT:
My understanding is due to decryption/recovery on this device the chinese recovery will work BUT the limitations are that if you are on OOS currently you cannot decrypt storage, HENCE you will not see anything in TWRP (again that is my understanding). After backing up the device and wiping the data partition at minimum (most custom roms seem to require us to fastboot wipe our partitions from instructions ive read)... then we can use this version of recovery for custom roms.
I think the major difference between this one and the official version here is of course the unofficial nature of this twrp but also the chinese twrp will let you flash (not boot) the recovery image without issue so we can still USE OOS OR flash custom roms without things going...wrong?...I plan to wait until the A11 OOS upgrade before I make a decision. After learning about how 1P botched the recovery keys + partition issues with the A10 launch I think its just better to see how development goes AFTER the new year maybe
Hmm l was of the understanding that if you format using the chinese recovery all will work on oos will see what's what and report back as soon as l find it and flash it
So flashed Chinese twrp couldn't mount data until l formatted data using it then l could see everything in storage but it reverted after a reboot and would need formatting again to see storage also it seems much more functional that the mauronofrio twrp but the decryption issue is still an issue for me at least. It's ashame nobody is working on this to give us a better twrp.
a g bell said:
Hmm l was of the understanding that if you format using the chinese recovery all will work on oos will see what's what and report back as soon as l find it and flash it
So flashed Chinese twrp couldn't mount data until l formatted data using it then l could see everything in storage but it reverted after a reboot and would need formatting again to see storage also it seems much more functional that the mauronofrio twrp but the decryption issue is still an issue for me at least. It's ashame nobody is working on this to give us a better twrp.
Click to expand...
Click to collapse
What's "this"? And what do you mean nobody?
Check twrp gerrit and github and you'll see lots of progress. Fastbootd has been implemented, and dynamic partitions are pretty much handled now. Only significant thing would be decryption, but let's hope Android 11 fixes this as Google once again has changed things regarding to keystore.
Lossyx said:
What's "this"? And what do you mean nobody?
Check twrp gerrit and github and you'll see lots of progress. Fastbootd has been implemented, and dynamic partitions are pretty much handled now. Only significant thing would be decryption, but let's hope Android 11 fixes this as Google once again has changed things regarding to keystore.
Click to expand...
Click to collapse
Ok l stand corrected just wondering why mauronofrio hasn't released an update or updated his thread. So OnePlus have to implement changes to keystore with Android 11 so they might fix it ?

Categories

Resources