Database Develop

TWRP - Internal Storage (0 MB)

Hi,
So I unlocked the bootloader on my phone and rooted it successfully (I believe). In the bootloader screen it shows as being unlocked. I am able to use Root Explorer with no problem, as well as Titanium Backup.
I flashed the latest TWRP for this phone (from Original Android Development). It seemed to have flashed fine. The only problem is that I can't really do anything from within recovery. It can't seem to 'see' my internal storage. I don't think mounting it results in anything. It is seeing 0 MB.
Does anyone know what the issue might be? It is TWRP 2.8.2.0 touch recovery.
Thanks in advance for your help.

tonyfiore75 said:
Hi,
So I unlocked the bootloader on my phone and rooted it successfully (I believe). In the bootloader screen it shows as being unlocked. I am able to use Root Explorer with no problem, as well as Titanium Backup.
I flashed the latest TWRP for this phone (from Original Android Development). It seemed to have flashed fine. The only problem is that I can't really do anything from within recovery. It can't seem to 'see' my internal storage. I don't think mounting it results in anything. It is seeing 0 MB.
Does anyone know what the issue might be? It is TWRP 2.8.2.0 touch recovery.
Thanks in advance for your help.
Click to expand...
Click to collapse
If you go into advanced you can manually mount and unmount, give that a try.

Thanks. I had tried that but it still showed 0 mb. It has to be the recovery because I can see all of my files, rooted or otherwise, from Root Explorer.
Sent from my Nexus 6 using XDA Free mobile app

tonyfiore75 said:
Thanks. I had tried that but it still showed 0 mb. It has to be the recovery because I can see all of my files, rooted or otherwise, from Root Explorer.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
maybe this will help you out.
http://forum.xda-developers.com/showthread.php?t=2380913
edit: you're going to want to use the proper system images for this device
https://developers.google.com/android/nexus/images#shamu
Not sure if you'll need the binaries as well
https://developers.google.com/android/nexus/drivers#shamu

Thanks for all that, but I don't understand. It's only twrp recovery that can't see the file system. Root Explorer can see everything. That doesn't sound like the file system is messed up, does it?
Sent from my Nexus 6 using XDA Free mobile app

After reading this thread, I realized I have the same problem as you. What I noticed is that its showing up as 0mb because the device is still encrypted. In order to fix this boot up into the OS. Set a screen lock PIN or password. Make sure you save it as requiring password on startup. Then bootup into TWRP and it should ask you for your password to decrypt. Put in the correct password and your files should show up again...At least that's how it just fixed my problem lol

Man, you are a frigging genius! I was wondering why TWRP was asking me for a password. And I did think to myself for a second, "I wonder if it's not letting me access my files because I didn't provide the correct password". But I never chose a password. I chose a PATTERN. How the hell was I supposed to enter in a pattern? Anyway, I did what you suggested. I entered in a pin, went to recovery, and all was well. Very interesting experience. Thank you SO SO SO much. I was literally pulling my hair out. Oof! What a day!
Sent from my Nexus 6 using XDA Free mobile app

Haha, you're very welcome! Last night I flashed TWRP just for the hell of it in case I ever needed it in the future. I didn't even bother to check out if it worked. Once I saw this thread, I booted up the recovery and noticed the same exact thing as you. I had a pattern as well. Anyway, goodluck!!

If you have a pattern lock, it's currently done by assigning numbers to the 'dots' in a matrix.
Code:
123
456
789
A capital 'L' would be 14789
If you don't set a password, it should decrypt automatically
Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
Click to expand...
Click to collapse

He did set a password. It was a pattern lock and it was set so that it was required at startup. Only problem is, TWRP doesn't have an option to use a pattern to decrypt the device.
---------- Post added at 03:29 AM ---------- Previous post was at 03:23 AM ----------
Zer0_Cool said:
If you have a pattern lock, it's currently done by assigning numbers to the 'dots' in a matrix.
Code:
123
456
789
A capital 'L' would be 14789
If you don't set a password, it should decrypt automatically
Click to expand...
Click to collapse
Cool! Never knew that. So I guess you can use still decrypt it if you have a pattern lol

Holy crap, I didn't even think that the pattern could be entered numerically. What a dope I am. I should have attempted that. Then again, I never thought of it. Oh well. Great to know. Thanks to everyone who helped me out. All of your contributions to the thread are greatly appreciated. I was sweating a bit there. Now I can go to sleep happily instead of angrily confused. I'm sure this will help someone else out down the line. Thanks everyone!

Feedback
Hey guy's,
OK, this samething just thappened to me for the second time since having my N6. The only way I could resolve it was a factory reset. :victory:
Trust me ever since I made the jump from Lollipop to Marshmallow I've had a lot of aggro.
But I'm now rocking Stock Marshmallow with TWRP and Root. Happy Days!! :highfive:

I know that this is an INSANELY old thread, but I just lost about an hour and most of the hair I had left, tearing it out over this issue. And I'd like to suggest -- well, BEG, actually, PLEAD -- for an small UI change that would go a long way to make this problem go away:
The first thing I see in my TWRP (which is 2.0.3-0) is the screen which says:
_______________________________________________________
Mount |
Decrypt Data |
Enter Password |
|
|______________________________________________________ |
....
and so I spend an hour + wrestling with the fact that I **KNOW** I never applied a password to this phone. Now if only the UI said instead:
_______________________________________________________
Mount |
Decrypt Data |
Enter Password |
(this is the PIN you enter to boot your phone and unlock it) |
|
|______________________________________________________ |
....
No normal person who didn't know it in advance would ever imagine that this "password" is just the phone PIN.
Note to dev: you might also include (perhaps as a footnote? lol) the information that 1. a lock pattern represents a PIN as well (and therefore a password); and 2. if no PIN has been set, then the user needs to reboot and set one in order to use TWRP (because, as we all know, one should not engage in unprotected recovery )

@sbpetrack: It's unlikely that the TWRP developers are going to see this thread. You might want to post your change to their Github Issues Log.

Twrp 0mb
I am new to flashing. I just sucessfully flashed twrp on my yureka .I booted into twrp and while taking backup it was showing as internal storage 0mb. What to do next. I donot have any pattern lock but just swipe to unlock.

@prashanth95: You might want to ask that question in the forum for your device. While I commend you for searching for a thread before making a new one, this is the Nexus 6 section. It's unlikely we're going to be of much help because the devices are totally different.

Hi frend
Hi, I also had such a problem. In fact it was very simple. I have Xperia z3 dual. Here's what I did: you need to manually do a form with TWRP:good::good: Wipe / Format data Yes Good Luck

sarkhan88 said:
hi, i also had such a problem. In fact it was very simple. I have xperia z3 dual. Here's what i did: You need to manually do a form with twrp:good::good: Wipe / format data yes good luck
Click to expand...
Click to collapse
format data saved my day
thanks a tom

its not asking for an password for me
---------- Post added at 12:45 PM ---------- Previous post was at 12:43 PM ----------
morphixxp said:
After reading this thread, I realized I have the same problem as you. What I noticed is that its showing up as 0mb because the device is still encrypted. In order to fix this boot up into the OS. Set a screen lock PIN or password. Make sure you save it as requiring password on startup. Then bootup into TWRP and it should ask you for your password to decrypt. Put in the correct password and your files should show up again...At least that's how it just fixed my problem lol
Click to expand...
Click to collapse
I have installed TWRP 3.2.1-1 for the OnePlus 5t, flashed LineageOS 15.1 onto there, February 4th edition.
Now, when i try to update it, it doesnt show any space, and its not asking me for an Password, what now?
please help!

forceartz said:
its not asking for an password for me
---------- Post added at 12:45 PM ---------- Previous post was at 12:43 PM ----------
I have installed TWRP 3.2.1-1 for the OnePlus 5t, flashed LineageOS 15.1 onto there, February 4th edition.
Now, when i try to update it, it doesnt show any space, and its not asking me for an Password, what now?
please help!
Click to expand...
Click to collapse
This is an N6 thread [emoji6]
It's not mounting internal storage, so it shows 0MB. I'm not current in the OP5 + Oreo combination, so you should check the OP5 forum to see if you need to use Codeworkx or maybe Blu Spark TWRP.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

Device Encryption Question/Issue with Unlocking

I have had some issues with my phone since unlocking with sunshine. See separate thread http://forum.xda-developers.com/droid-turbo/help/help-bricked-xt1254-unlocking-to-t3279581 for description. I have a theory about this now and would like some opinions from folks with more experience.
I used device encryption on my Turbo before the OTA update to Lollipop. After encrypting the phone I would be prompted to enter my PIN to decrypt the data partition before the phone would boot, and then I'd have to enter the PIN again after boot to unlock it. After the OTA I no longer had to enter my PIN when booting the phone, but I would still have to enter it after boot to unlock. After the OTA the phone still reported that it was encrypted in the system security settings even though it didn't need a PIN to decrypt at boot time. That makes sense from what little I know because encrypting the device re-writes the data partition, and the OTA didn't touch the data partition and could not un-encrypt it. I was baffled by this, but I didn't want to factory reset and wipe the data partition to let me re-encrypt the phone.
So after the OTA, the data partition of my phone was still encrypted, but magically the phone was able to decrypt data and boot without my PIN. I don't know why. But one clue is that after unlocking and installing TWRP I looked at TWRP log and saw a log message saying something about decrypting with default PIN. Anyway, I never wiped data, but my phone somehow manages to boot. Re-flashing system and recovery caused problems at first, but now it seems to be back to the way it was. I haven't flashed a new ROM yet, but I expect that when I do I'll have to wipe data and that will get everything back to normal.
My question is has anyone else experimented with device encryption and is this behavior expected?
Thanks.

Not having to enter a PIN with the factory image was a bug I initially discovered, and reported, during the *initial* Android L SOAK test. Needless to say, they never fixed the bug (plus one of the Stagefright CVEs) during the second SOAK rollout. I reported it then, too. They did nothing. That second SOAK was the straw that broke the camel's back, for me. I will never participate in another.
As far as this bug goes, what I would do, is an FDR, and re-encrypt your device to wipe the key store and start over.
Sent from my DROID Turbo via Tapatalk. Now with that cyanogenmod goodness.

I got notifications that the SU4TL-49 OTA was ready to install on my phone, and I had read that if you try to install it with anything but stock recovery that you get into a boot loop. I figured it was a matter of time before I ended up accidentally installing the OTA upgrade and so decided to wipe my phone and go back to stock, and I would use that opportunity to re-encrypt the phone. It took me a couple of tries before I discovered that factory reset isn't enough to remove the encryption, and that I had to reformat the data partition. This took a few hours of going back and forth between reverting to stock, upgrading, rooting, configuring and starting over before I finally got it right, but eventually the phone said that it wasn't encrypted and gave me the option to encrypt. What a pain. After setting up all my apps for the third or fourth time I thought I was done. Whenever I rebooted I was prompted for my PIN before android booted. I even had to enter my PIN to run TWRP.
At least that's the way it was for a few hours. Now when I reboot it just starts up android with no password again. All the effort to un-encrypt and re-encrypt seems to have been a waste. Oh well, at least I avoided getting into boot loop hell.
Hopefully this unencrypting without requiring password/PIN thing gets fixed when (if) they come out with M for the turbo.

This just keeps getting better and better. I decided to flash the Unofficial CM13 ROM this afternoon just for fun. I got it all set up when I found that the GPS receiver wasn't working. Searching the thread I found a link to a flash-able radio image to fix that, and when I rebooted to TWRP it prompted me for a password to decrypt the data partition! Unfortunately it didn't like my PIN no matter how many times I entered it. I don't know if there's something about entering a numerical PIN on the qwerty keyboard, but it had worked earlier in the day before it stopped prompting for passwords. After a bunch of tries and reboots I gave up and downloaded a fastboot flashable version of the same. I've spent most of the day screwing around with this phone already and I'm not going to reformat the data partition again today for sure! Maybe it just needs a good night's sleep.

Astrobrewer said:
This just keeps getting better and better. I decided to flash the Unofficial CM13 ROM this afternoon just for fun. I got it all set up when I found that the GPS receiver wasn't working. Searching the thread I found a link to a flash-able radio image to fix that, and when I rebooted to TWRP it prompted me for a password to decrypt the data partition! Unfortunately it didn't like my PIN no matter how many times I entered it. I don't know if there's something about entering a numerical PIN on the qwerty keyboard, but it had worked earlier in the day before it stopped prompting for passwords. After a bunch of tries and reboots I gave up and downloaded a fastboot flashable version of the same. I've spent most of the day screwing around with this phone already and I'm not going to reformat the data partition again today for sure! Maybe it just needs a good night's sleep.
Click to expand...
Click to collapse
Encryption is totally broken on CM13. The issue is that our version of TWRP cannot decrypt it. I contacted the maintainer of TWRP for our device about this issue and he said that he tried to fix the issue, but he failed.
Also, official CM13 has been out for a while now for the Turbo. No need to go with the unofficial version.

Thanks for the info @TheSt33v, but I'm not sure that it's totally broken.
The strange thing is that I was using TWRP 3.0.2 just fine after encrypting phone while on stock ROM, and it worked for a while even after flashing CM13. Then it just stopped liking my PIN. But CM13 takes my PIN and decrypts data just fine. So my phone is usable for now, and the problem of it decrypting without asking for a PIN is solved for now. I just went to cyanogenmod and see that there's a CM13 recovery. Based on your post I'm guessing that's what is broken, so no point in flashing that. Oh well, at least my phone is secure.

Astrobrewer said:
Thanks for the info @TheSt33v, but I'm not sure that it's totally broken.
The strange thing is that I was using TWRP 3.0.2 just fine after encrypting phone while on stock ROM, and it worked for a while even after flashing CM13. Then it just stopped liking my PIN. But CM13 takes my PIN and decrypts data just fine. So my phone is usable for now, and the problem of it decrypting without asking for a PIN is solved for now. I just went to cyanogenmod and see that there's a CM13 recovery. Based on your post I'm guessing that's what is broken, so no point in flashing that. Oh well, at least my phone is secure.
Click to expand...
Click to collapse
Just FYI, our TWRP maintainer has fixed decryption. You can get the latest version here: https://www.androidfilehost.com/?w=files&flid=39562 (version 3.0.2-0 mod 02 as of this writing). I still had trouble decrypting a partition that was previously formatted using the stock recovery menu, but once I formatted the data partition using this version of TWRP and re-encrypted, it decrypted fine.

TheSt33v said:
Just FYI, our TWRP maintainer has fixed decryption...
Click to expand...
Click to collapse
Yes they have fixed it! I found TWRP Mod 2 over the weekend and saw from the change log that decryption was fixed. I flashed it and it works great. No problems decrypting my previously encrypted data partition since I flashed mod 2. The funny thing about it is that basic TWRP 3.0.2 (no mod) worked well enough for long enough for me to flash CM13, and it even seemed to work for a little while after that. But then it decided that it didn't know how to decrypt my phone anymore and I was stuck until Mod 2. I can't explain why it worked for a while and then stopped, but I'm very happy that mod 2 fixed it.
Thanks for your help and support. Sometimes I feel like I'm the only user who encrypts his phone. There don't seem to be a lot of threads about encryption/decryption issues.

Astrobrewer said:
Yes they have fixed it! I found TWRP Mod 2 over the weekend and saw from the change log that decryption was fixed. I flashed it and it works great. No problems decrypting my previously encrypted data partition since I flashed mod 2. The funny thing about it is that basic TWRP 3.0.2 (no mod) worked well enough for long enough for me to flash CM13, and it even seemed to work for a little while after that. But then it decided that it didn't know how to decrypt my phone anymore and I was stuck until Mod 2. I can't explain why it worked for a while and then stopped, but I'm very happy that mod 2 fixed it.
Thanks for your help and support. Sometimes I feel like I'm the only user who encrypts his phone. There don't seem to be a lot of threads about encryption/decryption issues.
Click to expand...
Click to collapse
Most people don't seem to think it's worth the impact that it has on performance.

I was worried about the performance hit too before I tried it. But I don't notice any real difference in performance. Of there is a hit it's too small for me to tell.
Sent from my DROID Turbo using XDA-Developers mobile app

Astrobrewer said:
I was worried about the performance hit too before I tried it. But I don't notice any real difference in performance. Of there is a hit it's too small for me to tell.
Sent from my DROID Turbo using XDA-Developers mobile app
Click to expand...
Click to collapse
This is a very interesting thread. I would like to encrypt so I can setup my work exchange email as its a requirement. Just to clarify what is the order to do this in? Currently I am running RR 6.01 but have run CF's 1.3.6 ROM most of the time as its awesome.
Can I encrypt using RR or do I need to switch back to CFs ROM or to stock Lollipop after installing the upgraded TWRP in place of the standard version I am running now?
thanks for the help and information.

oldidaho said:
This is a very interesting thread. I would like to encrypt so I can setup my work exchange email as its a requirement. Just to clarify what is the order to do this in? Currently I am running RR 6.01 but have run CF's 1.3.6 ROM most of the time as its awesome.
Can I encrypt using RR or do I need to switch back to CFs ROM or to stock Lollipop after installing the upgraded TWRP in place of the standard version I am running now?
thanks for the help and information.
Click to expand...
Click to collapse
You can encrypt on RR. Just make sure you're running TWRP version 3.0.2-0 mod 2: https://www.androidfilehost.com/?w=files&flid=39562
If encryption fails, you'll need to format your data partition (aka do a factory reset) using this version of TWRP. Then it will work.

TheSt33v said:
You can encrypt on RR. Just make sure you're running TWRP version 3.0.2-0 mod 2: https://www.androidfilehost.com/?w=files&flid=39562
If encryption fails, you'll need to format your data partition (aka do a factory reset) using this version of TWRP. Then it will work.
Click to expand...
Click to collapse
thanks so much for the clarification! Being encrypted, how does that affect installing future updates or restores? Can I still flash ROMS and other ZIPS from TWRP the same as now?

oldidaho said:
thanks so much for the clarification! Being encrypted, how does that affect installing future updates or restores? Can I still flash ROMS and other ZIPS from TWRP the same as now?
Click to expand...
Click to collapse
The only difference is that you'll have to enter your password/pin every time you boot twrp. Don't try to use a pattern lock. Everything else will be the same.

TheSt33v said:
The only difference is that you'll have to enter your password/pin every time you boot twrp. Don't try to use a pattern lock. Everything else will be the same.
Click to expand...
Click to collapse
thank you for the help! I was able to encrypt my RR MM install without having to wipe the data partition. It now prompts me to put my PIN in when booting up and when going into the modded version of TWRP. It then is able to decrypt the partition in TWRP so as you said just like before. Only difference is a little longer boot up time. Performance seems the same to me.

oldidaho said:
thank you for the help! I was able to encrypt my RR MM install without having to wipe the data partition. It now prompts me to put my PIN in when booting up and when going into the modded version of TWRP. It then is able to decrypt the partition in TWRP so as you said just like before. Only difference is a little longer boot up time. Performance seems the same to me.
Click to expand...
Click to collapse
Guess I spoke too soon. phone was working fine for a day. Yesterday at work I'm looking at my phone as it reboots on its own (just sitting there). I then get cant decrypt partition message. Cant do anything and it wont boot up into the OS WO giving this error. In TWRP still cant do anything because it cant decript the partition. So I formatted the data partition and started over. I had saved a recent backup to my PC so I was able to get back to that. Now running CFs latest instead of RR. I need my phone, cant take a chance on this happening again as I was instantly dead in the water. Just wont encrypt.

oldidaho said:
This is a very interesting thread. I would like to encrypt so I can setup my work exchange email as its a requirement. Just to clarify what is the order to do this in? Currently I am running RR 6.01 but have run CF's 1.3.6 ROM most of the time as its awesome.
Can I encrypt using RR or do I need to switch back to CFs ROM or to stock Lollipop after installing the upgraded TWRP in place of the standard version I am running now?
thanks for the help and information.
Click to expand...
Click to collapse
oldidaho said:
thank you for the help! I was able to encrypt my RR MM install without having to wipe the data partition. It now prompts me to put my PIN in when booting up and when going into the modded version of TWRP. It then is able to decrypt the partition in TWRP so as you said just like before. Only difference is a little longer boot up time. Performance seems the same to me.
Click to expand...
Click to collapse
oldidaho said:
Guess I spoke too soon. phone was working fine for a day. Yesterday at work I'm looking at my phone as it reboots on its own (just sitting there). I then get cant decrypt partition message. Cant do anything and it wont boot up into the OS WO giving this error. In TWRP still cant do anything because it cant decript the partition. So I formatted the data partition and started over. I had saved a recent backup to my PC so I was able to get back to that. Now running CFs latest instead of RRI need my phone, cant take a chance on this happening again as I was instantly dead in the water. Just wont encrypt.
Click to expand...
Click to collapse
Well, just as you used CM13 Marshmallow and RR Marshmallow just fine without encryption, not sure why you went to CF Lollipop instead of RR just because encryption didn't work. It just seems you were implying it's CM13 or RR at fault when you used them just fine before, and even now on CF you are NOT using encryption.
But it's your phone, so you can run what you want.
I do commend you for having a recent backup on your PC.

ChazzMatt said:
Well, just as you used CM13 and RR just fine without encryption, not sure why you went to CF instead of RR just because encryption didn't work. But it's your phone.
Just not sure why you are implying it's CM13 or RR at fault when you used them just fine before, and even now on CF you are NOT using encryption.
I do commend you for having a recent backup on your PC.
Click to expand...
Click to collapse
I should have clarified, I dont think RR had anything to do with my issue. I actually really liked RR, it has some great features, great performance and good battery life too. I just missed the Moto features in the stock and CFs ROMs.

oldidaho said:
I should have clarified, I dont think RR had anything to do with my issue. I actually really liked RR, it has some great features, great performance and good battery life too. I just missed the Moto features in the stock and CFs ROMs.
Click to expand...
Click to collapse
Strange. I've been using RR M encrypted for several weeks now with no issues. Oh well. If you're happy with modified stock, that's all that matters. You can encrypt that too if you like. I'm a big fan of the Moto features as well, and RR M has basically all of them built in besides Voice (chop chop flashlight was removed for a while, but it has been added back). Although I've never understood what Voice offers that Google Now does not.

Mystery solved!
Astrobrewer said:
... At least that's the way it was for a few hours. Now when I reboot it just starts up android with no password again. All the effort to un-encrypt and re-encrypt seems to have been a waste. Oh well, at least I avoided getting into boot loop hell.
Hopefully this unencrypting without requiring password/PIN thing gets fixed when (if) they come out with M for the turbo.
Click to expand...
Click to collapse
I have been running the CM13 ROM for the past few months and it's been great, but now that Verizon came out with official Marshmallow I decided to go back to a stock-based ROM again because I've been missing VOLTE. So I flashed ComputerFreak274_MM. After flashing and rooting I was back in the stupid state of the phone saying that it was encrypted but booting without a PIN. It seemed unreal that Moto/Verizon would have left this bug in MM too. So I reformatted data, re-flashed and rooted the ROM and tried encrypting. Then I discovered that it won't encrypt if it's rooted. So back to wiping, re-formatting and flashing again, but this time I am able to successfully encrypt before rooting. Success! Now root and start setting up the phone. Now I have to enter my PIN before it will boot into the system or into TWRP. Yay! By now it's 1:00am and I have to be at work early, so I let it sit overnight while my apps download. In the morning I flash SuperSU and notice that I wasn't prompted for a password to decrypt when I booted into TWRP and I wasn't prompted for password when booting system after flashing SuperSU. WTF!!! More time wasted. It seemed that stock ROMs just don't like encryption. :crying:
Anyway, after stewing about it all day I randomly chanced into the solution. In the Security settings menu there's an option under Encryption called "Secure start-up" which only becomes available when phone is encrypted. The Secure start-up options says:
"You can further protect this device by requiring your PIN before it starts up. Until the device starts up, it can't receive calls, messages, or notifications, including alarms. This helps protect data on lost or stolen devices."​Secure start-up defaults to disabled for some reason, and when it's disabled the phone automatically decrypts itself when it boots without requiring PIN entry. So you can encrypt your phone and still be totally unprotected. What a dumb-ass default!
But when I enable Secure start-up then encryption works the way it should -- with phone prompting for PIN before booting. Maybe I just didn't notice it, but I didn't see anything when I encrypted the phone saying to enable Secure start-up to actually protect the phone. I'm guessing that this option was there in Lollipop too; but who knew???

TWRP password???

Running into a weird issue with the bootable TWRP asking for a password that seemingly does not exist. I'm coming from a fresh format and stock reinstall and have not set any password for encryption that I'm aware of. Have tried it several times in many different ways that I've read in other forums: setting an alphanumeric password, a pattern lock with the dots corresponding to numbers on a dial pad, no password at all and using "default-password". Nothing seems to work. Any help/insight would be greatly appreciated and my apologies if this issue was already answered elsewhere.

Reboot to system and remove device protection (remove password, PIN, pattern or fingerprint).
Read more:
https://forum.xda-developers.com/pixel-xl/help/twrp-wont-accept-encryption-password-t3716107

That did the trick! Swear I tried that before and it still prompted me for a password. Must have done something different/wrong. Either way thanks so much!

I am running into this issue again, where TWRP is not accepting my PIN/Password. I am using TWRP 3.2.3-1, and stock retail 9.0 with a fresh install. With no screenlock - no problem with TWRP, but as soon as I add a password or PIN, TWRP asks for, but does not accept password or PIN.
When I ran into this a couple months ago, I could format data, reboot, restore data,, add PIN - and it would work just fine. This time, no matter what I try, TWRP will not allow any PIN or password.
I have not tried reverting to 8.1 to see if this is an issue with 9.0.
Edit: reverted to 8.1 but still can't still can't get the password working.

jhedfors said:
I am running into this issue again, where TWRP is not accepting my PIN/Password. I am using TWRP 3.2.3-1, and stock retail 9.0 with a fresh install. With no screenlock - no problem with TWRP, but as soon as I add a password or PIN, TWRP asks for, but does not accept password or PIN.
When I ran into this a couple months ago, I could format data, reboot, restore data,, add PIN - and it would work just fine. This time, no matter what I try, TWRP will not allow any PIN or password.
I have not tried reverting to 8.1 to see if this is an issue with 9.0.
Click to expand...
Click to collapse
This is an issue with pie. We need an updated TWRP

vidra said:
This is an issue with pie. We need an updated TWRP
Click to expand...
Click to collapse
Yes. Any suggestion on making it work? I want to use lock screen. It is a pain to remove PIN and by extension saved fingerprints every time I want to backup...
Removing lockscreen.db in recovery does not seem to work in Pie as it did in Oreo.

Anyway to enable encryption with miui.eu rom?

Anyway to enable encryption with miui.eu rom?
i tried this method https://xiaomi.eu/community/threads/howto-encryption-on-a-mi-6-with-xiaomi-eu-roms.43286/
But it just gets stuck on boot screen

from here... https://forum.xda-developers.com/mi...-encrytion-t3846726/post77721399#post77721399
t0mas_ said:
hi!
you need to edit ventor/etc/fstab.com
in the file there is "encryptable=ice", you need to change that to "fileencryption=ice"
but you need to format data after that, i dont think it will work if you dont
Click to expand...
Click to collapse
but still untested by myself....

why u need encryption while unlocked, twrp installed?

thanhnvt194 said:
why u need encryption while unlocked, twrp installed?
Click to expand...
Click to collapse
because when encrypted, you can't access data from twrp without a password. all a person without password do is wipe the phone. which is possible even when locked.

t0mas_ said:
because when encrypted, you can't access data from twrp without a password. all a person without password do is wipe the phone. which is possible even when locked.
Click to expand...
Click to collapse
I am waiting for a new update to do the same. You must change a root file, and format the data. Everything will work normal!

gugugrp said:
I am waiting for a new update to do the same. You must change a root file, and format the data. Everything will work normal!
Click to expand...
Click to collapse
I am on global stable with unlocked bootloader (China variant) and haven't flashed TWRP yet. When I enable Fingreprint security, the phone says it's encrypted. In other Android phones (Samsung), we have to manually enable encryption apart from fingerprint security but I couldn't find it in the phone settings in MIUI 10. Any ideas?
So, in EU ROM, when you enable fingerprint security, does it say that the phone is encrypted or not? If no encryption, then flashing the EU ROM is a no go for me as encryption is critical for me

RainGater said:
I am on global stable with unlocked bootloader (China variant) and haven't flashed TWRP yet. When I enable Fingreprint security, the phone says it's encrypted. In other Android phones (Samsung), we have to manually enable encryption apart from fingerprint security but I couldn't find it in the phone settings in MIUI 10. Any ideas?
So, in EU ROM, when you enable fingerprint security, does it say that the phone is encrypted or not? If no encryption, then flashing the EU ROM is a no go for me as encryption is critical for me
Click to expand...
Click to collapse
official miui is encrypted by defaul, i think you can choose not to set pin on first boot (which is required by fingerprint and faceunlock) in which case it doesnt encrypt. not sure what happens if you choose to set pin later.
eu isnt encrypted by default. not sure why they choose to do so. but you cane make it encrypt by modifiying /vendor/etc/fstab.qcom.
oh, and it also runs in selinux permissive. im running magisk module to to make it enforcing on boot.

t0mas_ said:
official miui is encrypted by defaul, i think you can choose not to set pin on first boot (which is required by fingerprint and faceunlock) in which case it doesnt encrypt. not sure what happens if you choose to set pin later.
eu isnt encrypted by default. not sure why they choose to do so. but you cane make it encrypt by modifiying /vendor/etc/fstab.qcom.
oh, and it also runs in selinux permissive. im running magisk module to to make it enforcing on boot.
Click to expand...
Click to collapse
I didn't set the PIN or fingerprint security during the first boot but later added it. When I check the Encryption, it says that the phone is encrypted. Even when I setup the PIN, I didn't see any message indicating that it's encyrpting as it was super quick. Like you said, official MIUI is encrypted by default.
But modifying the fstab.qcom is a pain as I have to keep doing it after every flash of EU ROM? Also, not sure what happens after you make the fstab change, encrypt it, then flash a new version of EU... Does it hang or what happens?
Did you encrypt your device in EU ROM?

RainGater said:
I didn't set the PIN or fingerprint security during the first boot but later added it. When I check the Encryption, it says that the phone is encrypted. Even when I setup the PIN, I didn't see any message indicating that it's encyrpting as it was super quick. Like you said, official MIUI is encrypted by default.
But modifying the fstab.qcom is a pain as I have to keep doing it after every flash of EU ROM? Also, not sure what happens after you make the fstab change, encrypt it, then flash a new version of EU... Does it hang or what happens?
Did you encrypt your device in EU ROM?
Click to expand...
Click to collapse
well not that much of a pain. the file doesn't hang that often so you can have the same file in update zip for quite a while. you do need to flash it every time you flash rom though

t0mas_ said:
official miui is encrypted by defaul, i think you can choose not to set pin on first boot (which is required by fingerprint and faceunlock) in which case it doesnt encrypt. not sure what happens if you choose to set pin later.
eu isnt encrypted by default. not sure why they choose to do so. but you cane make it encrypt by modifiying /vendor/etc/fstab.qcom.
oh, and it also runs in selinux permissive. im running magisk module to to make it enforcing on boot.
Click to expand...
Click to collapse
I try to edit fstab.qcom but even with root it says save failed, tried a couple different editors and the same thing happens. Could you please tell me how to successfully edit fstab.qcom

mikefallen said:
I try to edit fstab.qcom but even with root it says save failed, tried a couple different editors and the same thing happens. Could you please tell me how to successfully edit fstab.qcom
Click to expand...
Click to collapse
you cant doit from running sysetm. i do it from recovery, mount vendor, adb pull. then put it in a flashable zip to have it handy for updates. empty zip is attached, just drop your fstab.qcom inside and flash. if you have vendor allready mounted in recovery it will throw an error about it, but it will flash it. gl

t0mas_ said:
you cant doit from running sysetm. i do it from recovery, mount vendor, adb pull. then put it in a flashable zip to have it handy for updates. empty zip is attached, just drop your fstab.qcom inside and flash. if you have vendor allready mounted in recovery it will throw an error about it, but it will flash it. gl
Click to expand...
Click to collapse
Thanks a lot really appreciate you taking the time to help me out!

Ancient thread
but there's one really important question. why does this method not work with F2FS formatted /data ?

Root [TWRP + Magisk] kills device Security :: Pin/Fingerprints broken

Hello XDA, I'm going to keep this short and sweet - I was able to root my device using the TWRP + Magisk method and some online guides. I believe after experimenting and flashing over the weekend, there is a bug, race condition, or something that prevents bio metrics and security from properly working on the Note 9.
If I set a pin, as it's required for me to add my fingerprints - when I later try to unlock the phone, the device will say the wrong pin. Deleting the cache, reading guides etc will only get you in a bootloop.
I'm in a state right now where I'm rooted with no device security, as adding a pin will effectively brick the device until flashing with Stock Android again.
_______
I was able to root last week Friday. I didn't bother setting a pin as I was happy to have root. Yesterday, I decided to go ahead and set my pin and soon enough, was prompted to use it to disable security.
I really thought I had mistakenly confirmed a stray character in my pin, and after toying, researching, and flashing my device over the weekend, Ive come to a crux where I could use some expert assistance.
Some guides I used had links to an RMM disabled or some ****, another guide had two zips for a different type of disabler. I'm not linking them, because apparently none of them work, but I believe this is where the problem lies. I think one of the zips is to remove the OEM Integrity Check or some **** Samsung wrote to secure the device. One of the packages I flashed took all those packages but nothing has worked.
Setting your pin during setup, or later in settings yields the same results - you will lock yourself out until you flash Stock Android to restart the process.
We're almost there guys, just need to be able to lock my device like a normal cellhpone user - thank you

dekalbcountyman said:
Hello XDA, I'm going to keep this short and sweet - I was able to root my device using the TWRP + Magisk method and some online guides. I believe after experimenting and flashing over the weekend, there is a bug, race condition, or something that prevents bio metrics and security from properly working on the Note 9.
If I set a pin, as it's required for me to add my fingerprints - when I later try to unlock the phone, the device will say the wrong pin. Deleting the cache, reading guides etc will only get you in a bootloop.
I'm in a state right now where I'm rooted with no device security, as adding a pin will effectively brick the device until flashing with Stock Android again.
_______
I was able to root last week Friday. I didn't bother setting a pin as I was happy to have root. Yesterday, I decided to go ahead and set my pin and soon enough, was prompted to use it to disable security.
I really thought I had mistakenly confirmed a stray character in my pin, and after toying, researching, and flashing my device over the weekend, Ive come to a crux where I could use some expert assistance.
Some guides I used had links to an RMM disabled or some ****, another guide had two zips for a different type of disabler. I'm not linking them, because apparently none of them work, but I believe this is where the problem lies. I think one of the zips is to remove the OEM Integrity Check or some **** Samsung wrote to secure the device. One of the packages I flashed took all those packages but nothing has worked.
Setting your pin during setup, or later in settings yields the same results - you will lock yourself out until you flash Stock Android to restart the process.
We're almost there guys, just need to be able to lock my device like a normal cellhpone user - thank you
Click to expand...
Click to collapse
did you encrypt your device? when you reboot, do you see an animation of a pad lock?

bober10113 said:
did you encrypt your device? when you reboot, do you see an animation of a pad lock?
Click to expand...
Click to collapse
Bober, first of all thanks for taking YOUR TIME to respond - as a senior member I feel like we can make progress
No, my phone is not encrypted - there is no lock when booting up, just the Stock Samsung animation
I do not use any system encryption or anything like that. I’m a hardware first guy, and use a suite of my own private encrypted cloud software
I played with my Note 9 before I rotted cow TWRP + Magisk - all tutorials out there mentioned flashing various encryption/security zips which I have - I think those zoos are geared for Knox
After you root the phone, you cannot set any type of biometric security or pin or you will be stuck in a bootloop/lock loop as the device is unable to authenticate your pin

dekalbcountyman said:
Bober, first of all thanks for taking YOUR TIME to respond - as a senior member I feel like we can make progress
No, my phone is not encrypted - there is no lock when booting up, just the Stock Samsung animation
I do not use any system encryption or anything like that. I’m a hardware first guy, and use a suite of my own private encrypted cloud software
I played with my Note 9 before I rotted cow TWRP + Magisk - all tutorials out there mentioned flashing various encryption/security zips which I have - I think those zoos are geared for Knox
After you root the phone, you cannot set any type of biometric security or pin or you will be stuck in a bootloop/lock loop as the device is unable to authenticate your pin
Click to expand...
Click to collapse
Are you using Snapdragon or Exynos?

mmjs14 said:
Are you using Snapdragon or Exynos?
Click to expand...
Click to collapse
Sir, I am using a
Galaxy Note 9
SM-N960F Internationals Unlocked
Alpine White
Exynos
Boot loader is TWRP and OEM Unlock is staying open permanently
I have all the hardware required, just need to overcome this software quirk so I can lock my phone when I’m not using it

dekalbcountyman said:
Bober, first of all thanks for taking YOUR TIME to respond - as a senior member I feel like we can make progress
No, my phone is not encrypted - there is no lock when booting up, just the Stock Samsung animation
I do not use any system encryption or anything like that. I’m a hardware first guy, and use a suite of my own private encrypted cloud software
I played with my Note 9 before I rotted cow TWRP + Magisk - all tutorials out there mentioned flashing various encryption/security zips which I have - I think those zoos are geared for Knox
After you root the phone, you cannot set any type of biometric security or pin or you will be stuck in a bootloop/lock loop as the device is unable to authenticate your pin
Click to expand...
Click to collapse
ive never seen this. what firmware are you on?
have you tried to download the very latest and completely wipe your phone? use samfirm tool 0.3.6 do dl the latest.
fill up all the slots with the md5 files u dled with samfirm and flash using odin( in csc slot use csc.md5 instead of home_csc.md5.)
go dl
magisk zip:
https://github.com/topjohnwu/Magisk/releases/download/v19.2/Magisk-v19.2.zip
and apk:
https://github.com/topjohnwu/Magisk/releases/download/manager-v7.2.0/MagiskManager-v7.2.0.apk
ketan oem fix +root
https://www.androidfilehost.com/?w=files&flid=281291
once back on latest stock firmware root again using twrp 3.2.x.x tar
flash it with odin but go to option and uncheck autoreboot
and flash twrp.tar in the AP slot.
once successful, manualy reboot phone to recovery( dont let it boot to homescreen! so hold vol up + Bixby +power
once in twrp swipe to get in recovery. go to wipe button and Format ( type yes) and go to reboot button and choose reboot to recovery
once back to recovery go again to wipe button and choose factory wipe.
once done flash dr ketan oem and root zip. ( within the aroma setup of that zip choose yes to both option for root and kernel)
once finished you can now flash the latest magisk.zip as dled earlier.
now reboot and setup your device. once done you can install magisk manger .apk that was dled earlier.

Bober, I did your steps exactly as described and used the links you provided and got it working w/ Biometric Security
I've flashed my phone like 20 times so the process took like 15 minutes max - this was also the first time I flashed all the files in the firmware download. Other guides out there tell me I only need to load the AP slot when flashing for this phone.
The "ketan oem fix +root" is the only security/system level zip I flashed using TWRP - besides looking like an early 2000s rootkit, the Terms of Use had an old version listed and said the binary was from 2015
I couldn't take screens, but everything went well when I checked the version
Thank You so much - in the future, will this root method hold for the life of the Note 9? Like when the new Android after Pie is released, will it be as simple as
1. Backing Up Phone
2. Flashing Android 10 Stock via Odin
3. Reflashing TWRP and Rooting
or is there a more streamlined approach to this? Thanks mate

dekalbcountyman said:
Bober, I did your steps exactly as described and used the links you provided and got it working w/ Biometric Security
I've flashed my phone like 20 times so the process took like 15 minutes max - this was also the first time I flashed all the files in the firmware download. Other guides out there tell me I only need to load the AP slot when flashing for this phone.
The "ketan oem fix +root" is the only security/system level zip I flashed using TWRP - besides looking like an early 2000s rootkit, the Terms of Use had an old version listed and said the binary was from 2015
I couldn't take screens, but everything went well when I checked the version
Thank You so much - in the future, will this root method hold for the life of the Note 9? Like when the new Android after Pie is released, will it be as simple as
1. Backing Up Phone
2. Flashing Android 10 Stock via Odin
3. Reflashing TWRP and Rooting
or is there a more streamlined approach to this? Thanks mate
Click to expand...
Click to collapse
actualy the root method that dr ketan created is just a way to bypass an issue that not all phones have(rmm state aka binaries error when booting.
but technically the method should be;
flash twrp, format, reboot again to recovery and flash official magisk .zip
you can also rely on rom developpers to flash their version instead of stock android via odin. this allows you to not always have to go through the twrp/root procedure each time and also rom devs include nice additional features.
anyways glad i could help.