Database Users

[Q] Question about unlocking bootloader

So i'm new to android but i continued to root my device. I did it the "legit" way. No tool kit. I installed drivers. ADB and used bootloader. I unlocked the bootloader when the dialog popped on my phone. I navigated and selected "unlock the bootloader" sideloaded clockworkmod touch. Installed supersu from sdcard. Booted up and i still have my pictures and i even found a folder on the phone from the gosms app I had. I know im properly rooted because i was able to flash paranoid rom 3 successfully. Everywhere i've been reading states unlocking the bootloader wipes everything! My question is this normal?

Its standard protocol made by Google. Yes its normal. Just remember if you have stuff on your storage to make sure you back up your storage before unlocking

Jsparta26 said:
Its standard protocol made by Google. Yes its normal. Just remember if you have stuff on your storage to make sure you back up your storage before unlocking
Click to expand...
Click to collapse
standard protocol but it didn't wipe...lol

BugJuice said:
standard protocol but it didn't wipe...lol
Click to expand...
Click to collapse
All you had to do is setup fast boot and use fast boot command fastboot oem unlock to unlock your bootloader. A message always comes up letting you knlw that unlocking bootloader erases your data. You didn't necessarily had to adb not to mention you went and side loaded a custom recovery. Guess you beat the system. Lol

Jsparta26 said:
All you had to do is setup fast boot and use fast boot command fastboot oem unlock to unlock your bootloader. A message always comes up letting you knlw that unlocking bootloader erases your data. You didn't necessarily had to adb not to mention you went and side loaded a custom recovery. Guess you beat the system. Lol
Click to expand...
Click to collapse
I unlocked my bootloader but it didn't wipe my data. But i didn't unlock it correctly and rooted.

BugJuice said:
I unlocked my bootloader but it didn't wipe my data. But i didn't unlock it correctly and rooted.
Click to expand...
Click to collapse
The same thing happened to me. Apparently this happens if you flash the recovery right after unlocking the bootloader. Rather than unlocking, rebooting into android, then flashing the recovery.
Read this for more info.

chromium96 said:
The same thing happened to me. Apparently this happens if you flash the recovery right after unlocking the bootloader. Rather than unlocking, rebooting into android, then flashing the recovery.
Read this for more info.
Click to expand...
Click to collapse
ahhh gotcha! Thats my exact situation. I did not load into android either. Just flashed the recovery immediately afterwards. Is there any negative effects of this?

BugJuice said:
ahhh gotcha! Thats my exact situation. I did not load into android either. Just flashed the recovery immediately afterwards. Is there any negative effects of this?
Click to expand...
Click to collapse
Yep. I was pretty confused too.
So far I havent had any issues and everything seems fine. I flashed superuser on stock rom, flashed CM10.1, and flashed PA and everything has gone smoothly. Its only been about a week though, so im not sure if anything will happen. But i highly doubt that it will cause anything negative to occur.

Nexus 6P stuck in bootloop

128 GB Frost Nexus 6P, just got it today in the mail and decided to restart the phone after a day of installing all my apps and re downloading all my music, and now its stuck in the colorful bootloop and has been for over 2 hours. Not Rooted Not Unlocked, I have no idea how to get it out of this. Any suggestions?

dandpw said:
128 GB Frost Nexus 6P, just got it today in the mail and decided to restart the phone after a day of installing all my apps and re downloading all my music, and now its stuck in the colorful bootloop and has been for over 2 hours. Not Rooted Not Unlocked, I have no idea how to get it out of this. Any suggestions?
Click to expand...
Click to collapse
Same issue here. I booted and setup device just fine over WiFi. I powered down to install SIM. On reboot I get to PIN lock, and then phone is stuck in boot screen.
{Edit} Reset handset and starting over.
{Edit 2} After factory reset, I've restarted handset three times with no problems.
{Edit 3} Factory reset seems to have fixed the problem.

PhiPsi32 said:
Same issue here. I booted and setup device just fine over WiFi. I powered down to install SIM. On reboot I get to PIN lock, and then phone is stuck in boot screen.
{Edit} Reset handset and starting over.
{Edit 2} After factory reset, I've restarted handset three times with no problems.
{Edit 3} Factory reset seems to have fixed the problem.
Click to expand...
Click to collapse
How did you Reset when stuck in the Boot Loop? Thx.
Sent using my Samsung Galaxy Note 4

sabesh said:
How did you Reset when stuck in the Boot Loop? Thx.
Sent using my Samsung Galaxy Note 4
Click to expand...
Click to collapse
You are going to need to boot into fastboot, unlock the bootloader and flash the stock img file from Google.

sabesh said:
How did you Reset when stuck in the Boot Loop? Thx.
Sent using my Samsung Galaxy Note 4
Click to expand...
Click to collapse
I would think that holding power and volume up will get you to the factory reset screen, even if bootlooping. I don't think you need to unlock the bootloader.

Shockz said:
You are going to need to boot into fastboot, unlock the bootloader and flash the stock img file from Google.
Click to expand...
Click to collapse
You can't unlock the bootloader anyway unless you flip the switch in developer options while the phone is booted. You'd have to go into stock recovery and do a factory reset from there.
Sent from my Nexus 6P using Tapatalk

sabbotage said:
You can't unlock the bootloader anyway unless you flip the switch in developer options while the phone is booted. You'd have to go into stock recovery and do a factory reset from there.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Yeah that's right. Honestly, the first thing you should do when you get your phone is unlock the bootloader since it wipes everything. But yeah, just flash the Google provided images in stock recovery.

Have the exact same problem. However, I've downloaded the MDB08K from the Google site, loaded up the ADB tool, started the flash process but it fails because the device is still unlocked. When I type fastboot oem unlock it fails, presumably because I'm not able to get into the phone to enable debugging. Any ideas?

Shockz said:
Yeah that's right. Honestly, the first thing you should do when you get your phone is unlock the bootloader since it wipes everything. But yeah, just flash the Google provided images in stock recovery.
Click to expand...
Click to collapse
Will the warranty be void if Bootloader is unlocked? Thx.
Sent using my Samsung Galaxy Note 4

sabesh said:
Will the warranty be void if Bootloader is unlocked? Thx.
Sent using my Samsung Galaxy Note 4
Click to expand...
Click to collapse
There is no clear answer here, but I would say the general answer is that no it will not void your warranty. I have never heard of people being rejected by google support if their bootloader was unlocked.

Won't be druv said:
I would think that holding power and volume up will get you to the factory reset screen, even if bootlooping. I don't think you need to unlock the bootloader.
Click to expand...
Click to collapse
I held volume down and power.

diceman725 said:
Have the exact same problem. However, I've downloaded the MDB08K from the Google site, loaded up the ADB tool, started the flash process but it fails because the device is still unlocked. When I type fastboot oem unlock it fails, presumably because I'm not able to get into the phone to enable debugging. Any ideas?
Click to expand...
Click to collapse
try: fastboot flashing unlock

diceman725 said:
Have the exact same problem. However, I've downloaded the MDB08K from the Google site, loaded up the ADB tool, started the flash process but it fails because the device is still unlocked. When I type fastboot oem unlock it fails, presumably because I'm not able to get into the phone to enable debugging. Any ideas?
Click to expand...
Click to collapse
Found a solution. I just wasn't familiar with how to get into the stock recovery menu... Too used to TWRP. Factory reset cleared it up - though who knows for how long.

I have the MDB08L variant and I used the boot image from the stock Google MDB08L and thatvworked and I was able to flash TWRP from CMD but it was when I tried installing SuperSU that I got stuck in the bootnloop. I wiped the whole system from TWRP and I'm wondering what steps I should take next? Should I try flashing Chainfire's modified K variant boot image? Or try again with the L boot image?

PhiPsi32 said:
I held volume down and power.
Click to expand...
Click to collapse
Yes, sorry, my mistake.

This is happening to me. First time restarting since putting the sim card in. I hold the power button and volume down, select "factory" but then it still gets stuck in the boot loop. How do I factory reset with this issue?
Thanks for any help this really sucks.
Edit: I figured out how to factory reset from this site's instructions:
http://www.androidexplained.com/nexus-6p-recovery-mode/
Looks like half of my initial setup was saved with google syncing my settings but I now need to spend a couple hours to get back to where I was today. WHY DO I HAVE TO CUSTOMIZE SO MUCH?!?....OH YEAH BECAUSE IT IS FUN

Shockz said:
Yeah that's right. Honestly, the first thing you should do when you get your phone is unlock the bootloader since it wipes everything. But yeah, just flash the Google provided images in stock recovery.
Click to expand...
Click to collapse
quick question, if i unlock the bootloader and decdie to root the phone later.. does rooting wipe data on the phone?

No, rooting does not wipe the device.

sabesh said:
Will the warranty be void if Bootloader is unlocked? Thx.
Sent using my Samsung Galaxy Note 4
Click to expand...
Click to collapse
Shockz said:
There is no clear answer here, but I would say the general answer is that no it will not void your warranty. I have never heard of people being rejected by google support if their bootloader was unlocked.
Click to expand...
Click to collapse
The US, the Magnuson-Moss Warranty Act prevents companies from voiding it if the bootloader is unlocked, provided they explain a way to unlock it. Making it a feature of the device itself. Since Google puts out all of their factory images, and even gives instructions on how to unlock the bootloader , it's very likely that it falls under the terms of this law. I've also never heard of them denying warranty service on a device provided there was no accidental damage. Their support is actually pleasant to speak with (unlike HTC in my experince).

I unlocked my bootloader then install the updated factory image.. which reset everything installed twrp then I rebooted in to android I guess for the last time cause now I'm in the bootloop at the colorful android screen any help would be greatly appreciated if I comeback from this I honestly think ill never root my nexus again please help !!!

Axon 7 Pre-Encrypted Data

Hey guys , Since I upgraded to Nougat, my phone is pre-encrypted and why can't I decrypt it? Why is it like this? I want to decrypt it so that my phone will be a little faster. So how can I decrypt it?

Unlock, install twrp and format data.

lafester said:
Unlock, install twrp and format data.
Click to expand...
Click to collapse
Can't I just do it without unlocking? I can encrypt and unencrypt the phone easily(factory rest) on all my other devices?And any clues why is it pre-encrypted?

I suppose you could try a factory reset in stock recovery.

lafester said:
I suppose you could try a factory reset in stock recovery.
Click to expand...
Click to collapse
I've reset factory a couple times but that option is not choosable and it is written encrypted.

I mean I haven't even encrypted my phone ever , so why is it encrypted?Is it done automatically? What about yours?Is it pre-encrypted too?

It was...

lafester said:
It was...
Click to expand...
Click to collapse
I guess you've got the G or U model?right?(mine is A2017)

Boot into TWRP and change the data partition type from f2s to EXT4.

Double tap screen awake
My phone double tap screen awake doesn't work since these updates what can I do.It's a axon 7 2016 model..

Paulkdixon96 said:
My phone double tap screen awake doesn't work since these updates what can I do.It's a axon 7 2016 model..
Click to expand...
Click to collapse
I think you are in the wrong thread.

Aj-jss said:
I mean I haven't even encrypted my phone ever , so why is it encrypted?Is it done automatically? What about yours?Is it pre-encrypted too?
Click to expand...
Click to collapse
Zte stock rom comes pre-encrypted on every new install. The only way to bypass it is to edl flash a stock rom with twrp. Boot right into twrp after the flash. Find a modded stock boot.img that has a modded fstab, flash it, then boot and your phone will be unencrypted with the stock rom.

Thank you all. I'll do as you said and unencrypt it.

DEAR ZTE CUSTOMER,
Pls describe clearly about the situation of your encrypted phone, because our developer confused about such encrypted issues. BTW, please provide your phone'IMEI.
Thank you!

William Guo said:
DEAR ZTE CUSTOMER,
Pls describe clearly about the situation of your encrypted phone, because our developer confused about such encrypted issues. BTW, please provide your phone'IMEI.
Thank you!
Click to expand...
Click to collapse
No issues. It is encrypted by default in stock ROM.

This guy seems to be spamming and looking for imei info.

Mine is encrypted. Brand new out of box, updated to B10 MM then to B04 Nougat 7.1.1
What are the implications of it being encrypted? Mine is remaining stock, not even TWRP recovery or root. I'm happy if it's secure as I have personal and work SIM in it and will be using a couple of apps that look for root. Kind of tired of modding phones, just want life to be simple and reliable, able to take updates when I like. The work Nexus 5X was a ****ty phone but I got used to it being updated. It's a rare one that doesn't bootloop and is on Oreo but I hate carrying two phones thus the reason for buying the Axon 7 for dual SIM.

RobboW said:
Mine is encrypted. Brand new out of box, updated to B10 MM then to Nougat.
What are the implications of it being encrypted? Mine is remaining stock, not even TWRP recovery or root. I'm happy if it's secure as I have personal and work SIM in it and will be using a couple of apps that look for root.
Click to expand...
Click to collapse
I don't believe you'll get more performance out of an unencrypted phone, or not enough to justify it for that matter. also, on some phones you need it not to be encrypted if you want to see the internal storage in TWRP, but on this phone it doesn't happen.

You can fix it in your settings--hand design(sort of, I guess),or you can update the latest version from ZTE office website. Good luck!

How protect phone data when bootloader unlocked?

Hello,
I doesn't know if this is a real problem in newer Android versions.
I apologize if this problem is already solved; i'm out of Android development since a while...
From me the problem is to protect MY data if I loss the phone...
If my phone is password protected (and bootloader locked), a person that found the device can't use it directly.
It can unlock the bootloader (more or less easily) but the phone data is removed by the unlock process.
My data is sure!
But if the bootloader is unlocked the person that has found my phone can acess to the custom recovery (or load a custom recovery if I'm on stock recovery) then force a wipe of the device.
Due to that, all my security (fingerprint and lock code) was erased and the user can access to my phone and also to all the data stored in /sdcard.
My data isn't sure!
It exists any mode to use a custom ROM but maintaining my data sure?
(I'm not confidence with the Google remote device access)
Thanks in advance!

I think you'll be fine, as the data on your internal memory should be encypted, which is enabled by default!

I'll be honest and I mean no offense but your data is worthless. If someone steals your device the first things done are Sim removed and devices reset or powered off. Data thieves don't get the data from stolen devices. They get it from the places we give it freely. Like shopping stores and on line accounts.

Nobody can access your phone data the way you describe unless you also run your phone decrypted --which is not the default for Android or even for custom ROMs for that matter. When you boot into recovery on a phone that is encrypted TWRP asks for your pin number and without it your data is not accessible. But that doesn't mean a thief couldn't still wipe and use your phone. You need to report it stolen so the IMEI number is blacklisted.

jhs39 said:
Nobody can access your phone data the way you describe unless you also run your phone decrypted --which is not the default for Android or even for custom ROMs for that matter. When you boot into recovery on a phone that is encrypted TWRP asks for your pin number and without it your data is not accessible. But that doesn't mean a thief couldn't still wipe and use your phone. You need to report it stolen so the IMEI number is blacklisted.
Click to expand...
Click to collapse
The /sdcard in phones that doesn't have external sdcard, like O+5, are also protected by the encriptation?
Thanks

bartito said:
The /sdcard in phones that doesn't have external sdcard, like O+5, are also protected by the encriptation?
Thanks
Click to expand...
Click to collapse
Yep, like any other android, the oneplus 5 has full disk encryption enabled by default:
http://www.androidpolice.com/2015/1...ll-disk-encryption-by-default-on-new-devices/

bartito said:
Hello,
I doesn't know if this is a real problem in newer Android versions.
I apologize if this problem is already solved; i'm out of Android development since a while...
...........................................
Click to expand...
Click to collapse
Well, IMO your concern is right to some extent.
With an unlocked bootloader, if there is some version of TWRP (or any other customer recovery for that matter) that can decrypt your data partition automatically or if you have ever formatted your /data partition from TWRP , or even an insecure kernel (most insecure kernels allow USB debugging without asking for authorization keys), all the thief needs is 2 adb commands and your screen lock will be turned off and all your stuff will be exposed 'as is'.
For educational purposes, the commands are:
Code:
adb shell rm /data/system/*.key
adb reboot
Now, for that matter, having a locked bootloader either doesn't ensure that your data is safe. For example, for HTC phones, you don't even need to unlock the bootloader for flashing a custom recovery or kernel. You can turn the phone to S-Off state using some proprietary tools (without losing data) and then flash custom images over a locked bootloader.
In case of Samsung, only FRP lock prevents you from flashing custom images (that too on newer phones) but in that case also, you can turn FRP off using some paid services and then flash any custom images and run the above mentioned commands.
In case of LG, it is even easier. Professional tools exist for communication over download mode protocol and turning off the screen lock doesn't even require a custom image in LG's case. However, most newer models are not supported by those tools yet.
In case of Apple, professional tools existed that used to read screen lock over a time span of 1-4 hours in an older version of iOS. I've heard that a tool is being made available for the current versions also in the coming weeks.
So, if you are conscious about your data, it is safe as far as the you have the phone in your possession. Once you lose it, you can't be sure about what is happening with it.
But then, as said in above posts, why would the thief want to crack open the data of a common man. If you are not a common man, you should worry. Otherwise I personally really don't care.

Hello,
Absolutelly appreciate your anwer.
I'm a common man, but I'm a bit worried due to 2 points:
1) I'm using LastPass and I doesn't would to my passwords to fall into someone's hands if I loss the device,
2) I'm using the app from my bank to pay using NFC and I doesn't would that anyone can use it
EDIT: 3) Of course, I'm using my Google account to store my contacts data. It would be a mess if someone erase my contacts
Thanks!
sikander3786 said:
Well, IMO your concern is right to some extent.
With an unlocked bootloader, if there is some version of TWRP (or any other customer recovery for that matter) that can decrypt your data partition automatically or if you have ever formatted your /data partition from TWRP , or even an insecure kernel (most insecure kernels allow USB debugging without asking for authorization keys), all the thief needs is 2 adb commands and your screen lock will be turned off and all your stuff will be exposed 'as is'.
For educational purposes, the commands are:
Code:
adb shell rm /data/system/*.key
adb reboot
Now, for that matter, having a locked bootloader either doesn't ensure that your data is safe. For example, for HTC phones, you don't even need to unlock the bootloader for flashing a custom recovery or kernel. You can turn the phone to S-Off state using some proprietary tools (without losing data) and then flash custom images over a locked bootloader.
In case of Samsung, only FRP lock prevents you from flashing custom images (that too on newer phones) but in that case also, you can turn FRP off using some paid services and then flash any custom images and run the above mentioned commands.
In case of LG, it is even easier. Professional tools exist for communication over download mode protocol and turning off the screen lock doesn't even require a custom image in LG's case. However, most newer models are not supported by those tools yet.
In case of Apple, professional tools existed that used to read screen lock over a time span of 1-4 hours in an older version of iOS. I've heard that a tool is being made available for the current versions also in the coming weeks.
So, if you are conscious about your data, it is safe as far as the you have the phone in your possession. Once you lose it, you can't be sure about what is happening with it.
But then, as said in above posts, why would the thief want to crack open the data of a common man. If you are not a common man, you should worry. Otherwise I personally really don't care.
Click to expand...
Click to collapse

jhs39 said:
Nobody can access your phone data the way you describe unless you also run your phone decrypted --which is not the default for Android or even for custom ROMs for that matter. When you boot into recovery on a phone that is encrypted TWRP asks for your pin number and without it your data is not accessible. But that doesn't mean a thief couldn't still wipe and use your phone. You need to report it stolen so the IMEI number is blacklisted.
Click to expand...
Click to collapse
Black listing the imei doesn't work everywhere. Plus while banned on xda so I can't say how. But the imei is not that hard to change.

bartito said:
Hello,
Absolutelly appreciate your anwer.
I'm a common man, but I'm a bit worried due to 2 points:
1) I'm using LastPass and I doesn't would to my passwords to fall into someone's hands if I loss the device,
2) I'm using the app from my bank to pay using NFC and I doesn't would that anyone can use it
EDIT: 3) Of course, I'm using my Google account to store my contacts data. It would be a mess if someone erase my contacts
Thanks!
Click to expand...
Click to collapse
Maybe some experts can give their opinion on how to protect your data using some third party apps or by using some other options that I am not aware of. But in my opinion, a phone with an unlocked bootloader is always more vulnerable than a phone with locked bootloader.

Of course, I agree with your affirmation at 100%
The question is: I can improve security if I keep TWRP as a recovery instead of return to the stock recovery and I lock the bootloader?
Thanks
sikander3786 said:
Maybe some experts can give their opinion on how to protect your data using some third party apps or by using some other options that I am not aware of. But in my opinion, a phone with an unlocked bootloader is always more vulnerable than a phone with locked bootloader.
Click to expand...
Click to collapse

bartito said:
Of course, I agree with your affirmation at 100%
The question is: I can improve security if I keep TWRP as a recovery instead of return to the stock recovery and I lock the bootloader?
Thanks
Click to expand...
Click to collapse
I don't think you will be able to boot TWRP after relocking the bootloader. You need to test it yourself. Chances are very few because locked bootloaders prevent from booting un-signed images.
If you do manage to boot TWRP after relocking, make sure your data is encrypted. If it is not, then it doesn't matter if the bootloader is locked or not.
Also, you will need to turn off "oem unlock" option from developer options.

sikander3786 said:
I don't think you will be able to boot TWRP after relocking the bootloader. You need to test it yourself. Chances are very few because locked bootloaders prevent from booting un-signed images.
If you do manage to boot TWRP after relocking, make sure your data is encrypted. If it is not, then it doesn't matter if the bootloader is locked or not.
Also, you will need to turn off "oem unlock" option from developer options.
Click to expand...
Click to collapse
I think in the end I will stay as I am: bootloader unlocked and TWRP instead of the original recovery.
After all... I've never lost a phone...

bartito said:
The /sdcard in phones that doesn't have external sdcard, like O+5, are also protected by the encriptation?
Thanks
Click to expand...
Click to collapse
I haven't checked, but I believe it should.
nxss4 said:
Yep, like any other android, the oneplus 5 has full disk encryption enabled by default:
http://www.androidpolice.com/2015/1...ll-disk-encryption-by-default-on-new-devices/
Click to expand...
Click to collapse
Uh no, OP5 with OOS 4.5.x Nougat uses File-Based Encryption (FBE), not FDE.
I know because I wrote the utility to get back to FDE, which works if you change the/fstab* file:
https://forum.xda-developers.com/showthread.php?t=3672477
sikander3786 said:
Well, IMO your concern is right to some extent.
With an unlocked bootloader, if there is some version of TWRP (or any other customer recovery for that matter) that can decrypt your data partition automatically or if you have ever formatted your /data partition from TWRP , or even an insecure kernel (most insecure kernels allow USB debugging without asking for authorization keys), all the thief needs is 2 adb commands and your screen lock will be turned off and all your stuff will be exposed 'as is'.
Click to expand...
Click to collapse
Do you have a source for the first part of that information? The part where if userdata is formatted with TWRP, it is vulnerable?
I don't see how that can happen unless you run decrypted. TWRP is never involved in the encryption process. When you format userdata, it just runs mkfs. Android upon booting sees the forceencrypt flag in the fstab and then promptly encrypt the device with a default passphrase. When you later set up security, the passphrase is changed to whatever you input.
How can TWRP decrypt the files at this point without your passphrase?
Note that if you are running FBE, and run adb shell on a device that's booted into TWRP while waiting for the password, you will be able to see the file structure under /data, but most of its contents will be garbage (=encrypted).
If you're running FDE, and run adb shell on a device that's booted into TWRP, /data will be completely inaccessible.
sikander3786 said:
For educational purposes, the commands are:
Code:
adb shell rm /data/system/*.key
adb reboot
Click to expand...
Click to collapse
This will remove the PIN/password phrase to get into Android, but won't give access to any encrypted files.
That may mess your phone royally as well.

Hello,
Thanks for your anwer. I appreciate the time that have you spend on my question
I need to go to the FDE thread to learn a bit more about the process and results.
Now, I have 2 more questions...
1) If the phone is encrypted with FBE a user can remove user passwords using "adb shell rm /data/system/*.key
&& adb reboot" commands, like @sikander3786 has explained but, due to the device is encripted, it can't access to my data
and the device will require for the decrypt password when booting in normal mode or recovery. I'm correct?
2) If the device is encrypted with FBE a user can access to /sdcard even without the decrypt password in recovery (TWRP) mode but not if encrypted with FDE?
Thanks again!
Fif_ said:
I haven't checked, but I believe it should.
Uh no, OP5 with OOS 4.5.x Nougat uses File-Based Encryption (FBE), not FDE.
I know because I wrote the utility to get back to FDE, which works if you change the/fstab* file:
https://forum.xda-developers.com/showthread.php?t=3672477
Do you have a source for the first part of that information? The part where if userdata is formatted with TWRP, it is vulnerable?
I don't see how that can happen unless you run decrypted. TWRP is never involved in the encryption process. When you format userdata, it just runs mkfs. Android upon booting sees the forceencrypt flag in the fstab and then promptly encrypt the device with a default passphrase. When you later set up security, the passphrase is changed to whatever you input.
How can TWRP decrypt the files at this point without your passphrase?
Note that if you are running FBE, and run adb shell on a device that's booted into TWRP while waiting for the password, you will be able to see the file structure under /data, but most of its contents will be garbage (=encrypted).
If you're running FDE, and run adb shell on a device that's booted into TWRP, /data will be completely inaccessible.
This will remove the PIN/password phrase to get into Android, but won't give access to any encrypted files.
That may mess your phone royally as well.
Click to expand...
Click to collapse

nxss4 said:
I think you'll be fine, as the data on your internal memory should be encypted, which is enabled by default!
Click to expand...
Click to collapse
Suppose i encrypt my device, i.e., it asks for password everytime before booting...
Q1. Will booting into fastboot or recovery require the password?
Q2. If no, how can i prevent access to fastboot and recovery on an unlocked bootloader?

anuragm13 said:
Suppose i encrypt my device, i.e., it asks for password everytime before booting...
Q1. Will booting into fastboot or recovery require the password?
Q2. If no, how can i prevent access to fastboot and recovery on an unlocked bootloader?
Click to expand...
Click to collapse
You can't, but your data isn't accessible without the password

bartito said:
You can't, but your data isn't accessible without the password
Click to expand...
Click to collapse
But one can flash custom recovery from fastboot and subsequently use it to flash custom roms.
Am i right?

anuragm13 said:
But one can flash custom recovery from fastboot and subsequently use it to flash custom roms.
Am i right?
Click to expand...
Click to collapse
Yes, you can flash any recovery and any rom, but phone data can't be accessible if you don't have the password.
To use the device you need to know the password or do a data format

Isn't your phone technically always safe as long as you keep it encrypt it?
Only thing a thief could do would be a reset in both cases, isn't it?

Bricked?

Hi,
I have the OnePlus 5 8GB.
I unlocked my bootload, rooted my phone, all good.
But then I realized android pay is not working with rooted phones, so i wanted to undo it.
for some reason i ran this because i found it in a guide to lock the bootloader again (yes, it was was stupid):
./fastboot flashing lock
After that i got the message that my device is corrupt and cant boot. So i ran ./fastboot oem unlock and that message disappeard.
I tried booting, but nothing happend for 10 minutes, still boot animation. so i went into fastboot, flashed twrp and tried doing a factory reset, but whatever i do, I get tons of these error messages:
Updating partition details...
Error opening: '/data/misc/[...]
Error opening: '/data/user_de/0/[...['
(No such file or directory)
What can I do?
I can even ADB sideload because of those errors.
edit:
also it shows nothing for bootloader version or baseband version in the fastboot screen.
https://imgur.com/a/z2KN3
doesnt look good. cant copy anything to device or from device

Might have to RMA the phone. I'm not sure I've seen anyone unbrick a phone after locking the bootloader with a custom recovery still installed. I hope someone knows of a way. Good luck bro.
Also, of you get it working, use Magisk, it allows Android pay to work while rooted

Eric214 said:
Might have to RMA the phone. I'm not sure I've seen anyone unbrick a phone after locking the bootloader with a custom recovery still installed. I hope someone knows of a way. Good luck bro.
Also, of you get it working, use Magisk, it allows Android pay to work while rooted
Click to expand...
Click to collapse
Anything I should do to have them not reject the RMA?
thx for the Magisk advice, using it now.

Oh I think i got it.
flashed the OP5_recovery.img from their website via fastboot, android launched again!!!

TheCorax said:
Anything I should do to have them not reject the RMA?
Click to expand...
Click to collapse
Since it's obvious someone tampered with the software, they may reject it.
You don't lose warranty if you root, but they won't cover the cost if anything happens to it due to the user's intervention.
If you manage to get the stock ROM onto the phone, you may be able to flash it from TWRP.

TheCorax said:
Oh I think i got it.
flashed the OP5_recovery.img from their website via fastboot, android launched again!!!
Click to expand...
Click to collapse
So, did it work? Did it boot Android or just recovery? Please let us know so that anyone who comes up with this problem can solve it without suffering as much as you did.
Sent from my OnePlus 5 using XDA Labs

elbuenzurdo said:
So, did it work? Did it boot Android or just recovery? Please let us know so that anyone who comes up with this problem can solve it without suffering as much as you did.
Sent from my OnePlus 5 using XDA Labs
Click to expand...
Click to collapse
Yes it works again. That what I meant by android is launching.

TheCorax said:
Yes it works again. That what I meant by android is launching.
Click to expand...
Click to collapse
How do you do to get your device recognized? I have a similar problem for that command. But muy device just turned off and doesnt do nothing, Im trying flash it but nothing atm.
I have a leeco le s3 x626