Please, I need help. After flashing twrp I boot it and I need a password. I don't have any idea of what password it is. I tried with "default_password", "password" and with my MIUI account password. I also tried the password I have in the lock screen. But nothing seems to work. I tried also RedWolf but it also needs a password.
I have been reading a lot of forums with this topic but no one worked for me. Does somebody have a solution? I will do a fabric reset if necessary, but I want to install a custom rom and with that password it's impossible
pyradke said:
Please, I need help. After flashing twrp I boot it and I need a password. I don't have any idea of what password it is. I tried with "default_password", "password" and with my MIUI account password. I also tried the password I have in the lock screen. But nothing seems to work. I tried also RedWolf but it also needs a password.
I have been reading a lot of forums with this topic but no one worked for me. Does somebody have a solution? I will do a fabric reset if necessary, but I want to install a custom rom and with that password it's impossible
Click to expand...
Click to collapse
press tge back button for twrp u will enter twrp interface now You will have to perform format data(in wipe section) after that your internal storage along with other partitions will be wiped then you mist install orangefox recovery (never choose anyother recovery for whyred only orangefox) then you can install any custom rom your storage will be decrypted.(your os will also b wiped and all your data in internal storage) use sd card or otg to flash a rom.
Use Orange Fox.
The only reason for the encryption of twrp is immediate change of roms from android 10 to android 9 (or) changing the pixel based roms to normal roms to avoid this we can use the lazy flasher zip
Related
Whenever I flash a new rom after a fullwipe, I still have to type in a pin to boot the phone. I think this is called "verified boot". This is also the pin I need in TWRP to decrypt data. So obviously this pin has been stored outside of data or system partitions and is used upon every new install/boot of a new rom to encrypt it immediately upon first boot.
So where is this encryption key stored and how do I delete it?
Lownita said:
Whenever I flash a new rom after a fullwipe, I still have to type in a pin to boot the phone. I think this is called "verified boot". This is also the pin I need in TWRP to decrypt data. So obviously this pin has been stored outside of data or system partitions and is used upon every new install/boot of a new rom to encrypt it immediately upon first boot.
So where is this encryption key stored and how do I delete it?
Click to expand...
Click to collapse
If this link helps you ?
https://source.android.com/security/encryption/index.html
I have this exact problem, not sure how to resolve this issue but it seems my phone needs my pin even after wiping the phone.
I would love to fix this, if anybody has any tips that would be great, I am running a OnePlus 3 with root and twrp.
-thanks.
DonaldKerabatsos said:
I have this exact problem, not sure how to resolve this issue but it seems my phone needs my pin even after wiping the phone.
I would love to fix this, if anybody has any tips that would be great, I am running a OnePlus 3 with root and twrp.
-thanks.
Click to expand...
Click to collapse
Go to fastboot, type fastboot format userdata. Or go to twrp, wipe, wipe data via the button. This should do the same. Beware that data and your internal storage will get wiped.
to disable the pin you have to do this:
setting>security>screen lock> type PIN> PIN
then you will see Secure start-up ( Require PIN to start device/ No Thank you)
Hello,
Whenever i encrypt my phone on DU, when i set the lock screen Password it asks me if i want the phone to ask it to be able to boot, but then, the phone refuses to boot and says that the Password is wrong.
But when i boot into twrp the Password works and i can decrypt the data partition.
I already had the issue but with the phone accepting the boot pin but twrp not.
This is on a fresh DU install with previously formated data partition.
DO NOT encrypt via custom roms: it's cause of troubles and compatibility issues, especially when returning to OxygenOS.
So:
1) Put device in bootloader mode, plug it to computer, type fastboot format userdata via ADB terminal.
2) Go in TWRP and wipe all the partitions (be sure to have /cache formatted in ext4, otherwise change its filesystem):
3) Always from TWRP, flash latest OOS firmware (4.1.6 or OB19);
3) Reboot and configure setup with your PIN required at bootup;
4) After completing wizard, reboot in TWRP;
5) Now you can wipe anything and flash your rom.
Now device should require your PIN even at first boot of DU.
Ps until doing another fastboot format userdata, device will keep encryption.
Simone98RC said:
DO NOT encrypt via custom roms: it's cause of troubles and compatibility issues, especially when returning to OxygenOS.
So:
1) Put device in bootloader mode, plug it to computer, type fastboot format userdata via ADB terminal.
2) Go in TWRP and wipe all the partitions (be sure to have /cache formatted in ext4, otherwise change its filesystem):
3) Always from TWRP, flash latest OOS firmware (4.1.6 or OB19);
3) Reboot and configure setup with your PIN required at bootup;
4) After completing wizard, reboot in TWRP;
5) Now you can wipe anything and flash your rom.
Now device should require your PIN even at first boot of DU.
Ps until doing another fastboot format userdata, device will keep encryption.
Click to expand...
Click to collapse
Thanks for the answer, do you know why custom rom encryption doesnt work ? I used to to this on my old s5 and it worked perfectly
nikexv2 said:
Thanks for the answer, do you know why custom rom encryption doesnt work ? I used to to this on my old s5 and it worked perfectly
Click to expand...
Click to collapse
Maybe if you give his post a thumbs up he might continue helping you out , I mean that's the least you could do ......
Xceeder said:
Maybe if you give his post a thumbs up he might continue helping you out , I mean that's the least you could do ......
Click to expand...
Click to collapse
If members had to wait for thumbs up before they answer to someone's post then they wouldn't answer most of them.
What kind of **** philosophy is this, i hope for you that's not your way of thinking everyday.
And even, that's none of your business, maybe i forgot to like his post ?
Come on, do not vent on XDA, do not make useless quarrels ?
@nikexv2 sorry, but technically speaking, I don't know the reason of problematic encryption on custom roms.
Just enable encryption with official firmware and there's no other compatibility issue.
Encryption still remains when you full wipe device via recovery.
Have a good day.
nikexv2 said:
If members had to wait for thumbs up before they answer to someone's post then they wouldn't answer most of them.
What kind of **** philosophy is this, i hope for you that's not your way of thinking everyday.
And even, that's none of your business, maybe i forgot to like his post ?
Click to expand...
Click to collapse
It works like this - you ask for help and if someone gives you good advice or helps you out in any way then a quick thumbs up is appreciated , it's just courtesy but anyway I hope you get your phone sorted out ...
nikexv2 said:
Hello,
Whenever i encrypt my phone on DU, when i set the lock screen Password it asks me if i want the phone to ask it to be able to boot, but then, the phone refuses to boot and says that the Password is wrong.
But when i boot into twrp the Password works and i can decrypt the data partition.
I already had the issue but with the phone accepting the boot pin but twrp not.
This is on a fresh DU install with previously formated data partition.
Click to expand...
Click to collapse
Not sure what's wrong with your set up but I came from OOS OB19 to DU, wiped userdata to switch data to ext4, flashed DU + beans gapps (recommended for DU) then booted up, encrypted my phone via Settings > Security and set ask pin on booting device, same pin has worked on all ROMs, even tried some OOS based ones like Freedom OS CE, now on Omni + open gapps, I'm using blu spark latest recovery.
I installed RessurectionRemix and i followed the process i will describe now:
I was on 8.7.5 developer.
Flash MIUI from Mi Flash Tool just click on option Clean All, Let it flash and boot up, after it boots reboot to fastboot since you did only clean all it'll not relock BL.
Then flash twrp in fastboot. Go to wipe> advance> select everything (data, system, cache, dalvik, internal, vendor) everything. And swipe right.
Now keep in mind do not touch the format data option at all.
Now go to reboot menu and reboot to recovery after it boots back to recovery transfer the ROM and other files, flash and reboot system and you'll have 100% encrypted device.
Flash the rom
Flash gapps
After that process everything worked fine and the phone was encrypted. Almost instantly (5-10secs) after I power the phone it asked for password.
But i installed magisk through TWRP and since then it asks for password when the phone boots completely and asks the password just to unlock the lockscreen.
Inside settings it says phone is encrypted but my guess is, that it isn't encrypted.
How can i fix that? What is wrong in the process i followed? What is the correct process?
Thank you!
I guess those steps were for lineage os. For others, you've to format data to disable encryption.
i want to have encryption enabled.
I dont want encryption disabled.
What are you asking exactly?
If you go to
Settings - Security & Privacy - Encryption & Credentials - Under Encryption
Are you been offered the choice to encrypt phone? If your not then it is already encrypted.
Is it requesting a password to boot and also to unlock the device?
If you need password to boot, then you selected that as an option when setting up password.
Can be removed by changing your password to swipe/none and setup your password again.
If TWRP, can not decrypt the device, make sure your using the latest.
Why didn't you post your query in RR thread?
corkiejp said:
What are you asking exactly?
If you go to
Settings - Security & Privacy - Encryption & Credentials - Under Encryption
Are you been offered the choice to encrypt phone? If your not then it is already encrypted.
Is it requesting a password to boot and also to unlock the device?
If you need password to boot, then you selected that as an option when setting up password.
Can be removed by changing your password to swipe/none and setup your password again.
If TWRP, can not decrypt the device, make sure your using the latest.
Why didn't you post your query in RR thread?
Click to expand...
Click to collapse
I didnt post in RR because, i tried Aospextended and the same thing happened.
Thank you very much for the solution you gave!! I disabled screen lock,re-enable it with password and now it asks for passwoed on boot and on TWRP.
Thank you again!
Hello from Antwerp.
Can someone help me please? I am contacting you, because my phone does not start anymore. However I can get into TWRP. But TWRP (v. 3.0.2-1) asks a password. In former days I have crypt my phone. But I have done this with a 6-pattern. But now TWRP only accept numbers (or letters). Does someone of you maybe know, how I can enter a 6-pattern code as a numeric code? Or is there a possibility to change the password prompt into a pattern within TWRP? Maybe then I can get further afterwords.
Thanks a lot for your help.
Bergfex
Bergfex2 said:
Hello from Antwerp.
Can someone help me please? I am contacting you, because my phone does not start anymore. However I can get into TWRP. But TWRP (v. 3.0.2-1) asks a password. In former days I have crypt my phone. But I have done this with a 6-pattern. But now TWRP only accept numbers (or letters). Does someone of you maybe know, how I can enter a 6-pattern code as a numeric code? Or is there a possibility to change the password prompt into a pattern within TWRP? Maybe then I can get further afterwords.
Thanks a lot for your help.
Bergfex
Click to expand...
Click to collapse
Hi.
There are a lot of questions open. What firmware are you using? What TWRP version exactly? What do you want to achieve with decrypting /data?
If you just want your phone booting again the easiest way would be skipping the password prompt, wipe /data, /system, caches and reinstall your firmware.
If not:
Pattern-->Numbers works as described here https://twrp.me/faq/openrecoveryscript.html (Scroll down to Specific pattern decrypt note).
The thing now is, that you need to have 2 things:
TWRP capable of decrypt /data
Android version < 8
Decryption in TWRP for Android >= 8 isn't working right now. But you can tell me if you find a version capable of doing so.
If decryption worked that doesn't mean you'll be able to boot again. You can save your data but that's it. Are there known problems with decryption on your firmware?
You can try to backup /data after successful decryption, do a clean install and import backup afterwards.
Hello, I haveNokia 6.1 (2018) and I have just got it into a strange state. It happened during custom rom install, or to be more precise during the set-up (probably). I have finished setting up the Omni ROM from this thread (https://forum.xda-developers.com/nokia-6-2018/development/rom-omnirom-t3945850) and wanted to install magisk to have root.
After downloading the .zip file, I rebooted into TWRP (through the fastboot mode and using the "fastboot boot image.img" command) and TWRP asked for a password to decrypt the storage. I tried password that I am pretty sure is correct, but the TWRP insisted it is incorect. I tried several variations to it in case I made a misclick during a setup but no luck. I wiped everything (system, cache, data, sd) and through a fastboot mode I uploaded stock boot, vendor and system to both slots.
After the reboot, I am stuck on the password (system PIN, to be precise - not the SIM PIN, that is OK) screen. When I enter an incorrect PIN, it will say that the PIN is incorrect, but when I enter the correct one, screen just goes black for a while and I am back at the screen to enter the PIN.
Is there a way to get out of this mess? I am able to get into fastboot mode and boot recovery.
Any help would be much appreciated.
More details about the process as I forgot to include. TWRP used was 3.2.3 from this thread (https://forum.xda-developers.com/no...recovery-twrp-3-2-3-0-touch-recovery-t3825545). Stock FW (Nov 2019 version) used was from this thread (https://forum.xda-developers.com/no...de-how-to-make-backups-restore-stock-t3889815)
Before the OMNI ROM install I have tried stock system with custom vendor (version 2.2 from the thread linked in the OMNI ROM thread) which could also contribute to the failure, but the phone did not even boot (it got stuck on the "android one" logo). I hoped that I could at least get the ability to convert SD to internal storage, as that feature is disabled on stock, but with custom vendor it works (tested on the OMNI rom, which I managed to install correctly before)
I have also found here an OST tool, which could potentially help with the situation (I am not sure) but I am missing the original firmware files to use with this tool.
The problem must be with the internal storage encryption, which got messed up in the process (I am not still sure, what went wrong). Am I correct that now I would need to find the original loadout (is there something as RUU available fror this model?) and basically revert everything including the bootloader unlock and start from the begining? Could someone here point me in the right direction how to fix this issue?
If the only way is to pay someone to fix this issue, I will gladly provide any reasonable amount if it will resolve my problem.
So all I had to do was boot into TWRP and do a factory reset from there. How stupid of me that I did not try this.