Related
Disclaimer: I have done these steps multiple times and haven't come across any issues
Read All Step carefully. Any issues or damage to your phone that occurs while doing this I am not responsible.
If TWRP asks you for Password to decrypt data & maybe you have important data in you device, So you can't format data.
Follow these steps:
1. Download the OxygenOS full zip file (tested on 4.0.1 & above)
2. Open TWRP.
3. When It asks for password, cancel it.
4. Click "Read Only" button.
5. Install the OxygenOS zip file.
6. Reboot.
7. The OS may misbehave.
8. Open TWRP again. & Boom! No encryption password.
9. Connect to PC and copy the Important data.
10. Flash Any ROM now.
Thanks!
Recently I had to type in the password but I didn't know that it is possible to bypass it with this...
svandasek said:
Thanks!
Recently I had to type in the password but I didn't know that it is possible to bypass it with this...
Click to expand...
Click to collapse
Glad it helped you
ah.... if i only knew :crying:
That's good from a data recovery point of view... but it just sucks from a security point of view.
Not sure if I should be happy or concerned
TWRP Encryption ByPass
maddler said:
That's good from a data recovery point of view... but it just sucks from a security point of view.
Not sure if I should be happy or concerned
Click to expand...
Click to collapse
Agree .... that seems like a gaping security vulnerability. :-/
maddler said:
That's good from a data recovery point of view... but it just sucks from a security point of view.
Not sure if I should be happy or concerned
Click to expand...
Click to collapse
There's no need to be concerned (about this, specifically).
tk8lm6 said:
Agree .... that seems like a gaping security vulnerability. :-/
Click to expand...
Click to collapse
Actually, this is a case where this device is more secure than previous devices. The encryption key for your user data is divided into two parts. First is the part you type in when booting. The other half is stored in the "secure element" (TrustZone) inside the processor, and is unique to your phone. How the OP3 improves this is that it actually stores two versions of the device-specific key. One is used when the system is trusted (the kernel is signed and dm-verity passes), and the other is used when it is untrusted. This is part of what wipes your data when you unlock the bootloader. The security benefit comes from the SoC locking down the encryption keys when verification fails. Going back to the stock ROM causes all of the verification to pass, and the keys stored in the TrustZone are allowed to unlock your data partition.
On the other hand, if this allows you to bypass manually-enabled encryption, that would be a major security problem.
What interests me is that installing OOS should replace TWRP with the stock recovery image, but this appears not to have happened. Or did you have to flash TWRP again from fastboot after booting into OOS?
smaeul said:
There's no need to be concerned (about this, specifically).
Actually, this is a case where this device is more secure than previous devices. The encryption key for your user data is divided into two parts. First is the part you type in when booting. The other half is stored in the "secure element" (TrustZone) inside the processor, and is unique to your phone. How the OP3 improves this is that it actually stores two versions of the device-specific key. One is used when the system is trusted (the kernel is signed and dm-verity passes), and the other is used when it is untrusted. This is part of what wipes your data when you unlock the bootloader. The security benefit comes from the SoC locking down the encryption keys when verification fails. Going back to the stock ROM causes all of the verification to pass, and the keys stored in the TrustZone are allowed to unlock your data partition.
On the other hand, if this allows you to bypass manually-enabled encryption, that would be a major security problem.
What interests me is that installing OOS should replace TWRP with the stock recovery image, but this appears not to have happened. Or did you have to flash TWRP again from fastboot after booting into OOS?
Click to expand...
Click to collapse
No arguing that previous versions were less secure. But, still, as long as there's a way to bypass encryption that's a security failure.
Encrypted data shouldn't be made available unless proper key(s) or passwords have been provided.
If that's the way that's meant to work, then that's flawed by design.
smaeul said:
There's no need to be concerned (about this, specifically).
Actually, this is a case where this device is more secure than previous devices. The encryption key for your user data is divided into two parts. First is the part you type in when booting. The other half is stored in the "secure element" (TrustZone) inside the processor, and is unique to your phone. How the OP3 improves this is that it actually stores two versions of the device-specific key. One is used when the system is trusted (the kernel is signed and dm-verity passes), and the other is used when it is untrusted. This is part of what wipes your data when you unlock the bootloader. The security benefit comes from the SoC locking down the encryption keys when verification fails. Going back to the stock ROM causes all of the verification to pass, and the keys stored in the TrustZone are allowed to unlock your data partition.
On the other hand, if this allows you to bypass manually-enabled encryption, that would be a major security problem.
What interests me is that installing OOS should replace TWRP with the stock recovery image, but this appears not to have happened. Or did you have to flash TWRP again from fastboot after booting into OOS?
Click to expand...
Click to collapse
I've tried many times. OOS replaces TWRP only on CLEAN Instal for me.
hey guys, i tried to flash oos 5.0 zip, before that i was on another rom. wiped data, system, cache and flashed oos 5.0. and now internal storage is encrypted. how do i flash the zip in twrp now?
manchitro said:
hey guys, i tried to flash oos 5.0 zip, before that i was on another rom. wiped data, system, cache and flashed oos 5.0. and now internal storage is encrypted. how do i flash the zip in twrp now?
Click to expand...
Click to collapse
Just flash it.
Wait, are you saying by just installing a zip, the encrypion hardware pass is gone? WTF.. Is such "hack" available on other devices? Xiaomi redmi(s) for example?
hey i am not able to see any of my files or the zip itself within? is there anything to resolve that?
i can boot into os but for whatever reason cant get to twrp. i have the backup .imgs on my pc now too can i sideload a restore?
im stuck not able to get twrp to see any of my storage and i cant get into twrp twice in a row, so if i fastboot and flash twrp thru adb and then boot into twrp, it asks me for the password, if i hit cancel it just shows 0 storage. ive tried to go to adb sideload but it just sits there. I have the backup i made thru twrp before trying to update.
SourPower said:
hey i am not able to see any of my files or the zip itself within? is there anything to resolve that?
i can boot into os but for whatever reason cant get to twrp. i have the backup .imgs on my pc now too can i sideload a restore?
im stuck not able to get twrp to see any of my storage and i cant get into twrp twice in a row, so if i fastboot and flash twrp thru adb and then boot into twrp, it asks me for the password, if i hit cancel it just shows 0 storage. ive tried to go to adb sideload but it just sits there. I have the backup i made thru twrp before trying to update.
Click to expand...
Click to collapse
Yeah same issue here, as soon as I go in twrp and can't type the password, I can't access my files which is expected behavior, so I don't understand how you can access the file to flash from twrp.
Can someone detail please?
---------- Post added at 07:06 PM ---------- Previous post was at 06:40 PM ----------
Actually I just found a way out to get to previous twrp version, and all is back to normal
From your running ROM, you can download the application twrp (root needed oc)
Then you can use it to flash recovery.
I always keep former version file so I could revert to bluspark twrp that was working before. All worked as expected!
Still not solving the encryption password issue when flashing new recent twrp..
Android 10 Encryption / Security Issue - ADB Encryption Bypass?
rahulrs0029 said:
Disclaimer: I have done these steps multiple times and haven't come across any issues
Read All Step carefully. Any issues or damage to your phone that occurs while doing this I am not responsible.
If TWRP asks you for Password to decrypt data & maybe you have important data in you device, So you can't format data.
Follow these steps:
1. Download the OxygenOS full zip file (tested on 4.0.1 & above)
2. Open TWRP.
3. When It asks for password, cancel it.
4. Click "Read Only" button.
5. Install the OxygenOS zip file.
6. Reboot.
7. The OS may misbehave.
8. Open TWRP again. & Boom! No encryption password.
9. Connect to PC and copy the Important data.
10. Flash Any ROM now.
Click to expand...
Click to collapse
Does this only affect the TWRP -encryption, because when you set your lockscreen password (for the auto-encrypted userdata partition in Android 10, for example) the data can't be decrypted without this password..?
I have discovered another security issue however on a rooted device:
On my Magisk-rooted and encrypted Note 10+/Exynos (Android 10) I just found out, that the userdata (data/data ) partition is UNENCRYPTED and fully readable when viewed with an ADB viewer from my PC although the device is in lockscreen mode / locked!
This doesn't happen after reboot before the first unlock! After the device has been unlocked, accessed via ADB and re-locked (but not rebooted) it is (still) unencrypted, even after rebooting the PC!
Here the lockscreen password would not make much sense at every screenlock - it just unlocks the screen which can be bypassed and all data can be read via ADB anyway - it would only make sense once at boot. Is there a way to have two passwords (1 at boot and an easier one at screenlock) for example?
Is this issue related to Magisk? And can it be fixed?
monicaONxda said:
Does this only affect the TWRP -encryption, because when you set your lockscreen password (for the auto-encrypted userdata partition in Android 10, for example) the data can't be decrypted without this password..?
I have discovered another security issue however on a rooted device:
On my Magisk-rooted and encrypted Note 10+/Exynos (Android 10) I just found out, that the userdata (data/data ) partition is UNENCRYPTED and fully readable when viewed with an ADB viewer from my PC although the device is in lockscreen mode / locked!
This doesn't happen after reboot before the first unlock! After the device has been unlocked, accessed via ADB and re-locked (but not rebooted) it is (still) unencrypted, even after rebooting the PC!
Here the lockscreen password would not make much sense at every screenlock - it just unlocks the screen which can be bypassed and all data can be read via ADB anyway - it would only make sense once at boot. Is there a way to have two passwords (1 at boot and an easier one at screenlock) for example?
Is this issue related to Magisk? And can it be fixed?
Click to expand...
Click to collapse
Anyone with thoughts on this...?
monicaONxda said:
Anyone with thoughts on this...?
Click to expand...
Click to collapse
There are two, separate passwords. One for the encryption and one for the lock screen. And they don't have to be the same.
If you remove the encryption by formatting /data and then boot up on stock OOS, it will encrypt /data with a default password. TWRP can decrypt /data because it knows the default password that's used.
When you set the lock screen password you have the option to set the encryption password to be the same or not.
So, you could set the lock screen and encryption password to be something and then change the lock screen password only to be something different.
ADB can only access /data after it has been decrypted, ie the phone has booted up. But only if: 1. ADB is enabled, 2. You have given permission on your phone to trust the PC connecting to the phone.
So, there's no back doors here. If you have set an encryption password, you can't access the data without having entered the password. And you can't access the phone data without entering the lock screen password. And you can't access the data via ADB unless you have given the specific PC permission from your phone.
Of course, if you use the default encryption password and have TWRP installed, you might just as well not have a password at all. But that's up too you.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
When you set the lock screen password you have the option to set the encryption password to be the same or not.
So, you could set the lock screen and encryption password to be something and then change the lock screen password only to be something different.
Click to expand...
Click to collapse
For which roms is this working? I guess this behaviour is rom spefic. E.g. for all lineageos 15.1 and 16.0 roms and all roms based on tje same code base, the above procedure (setting the lockscreen passphrase without the boot passphrase checkbox set) will reset the boot passphrase to "default_password".
The only way I know of to get a seperate passphrase for boot and lockscreen on los15, los16 and roms based on these is this:
https://forum.xda-developers.com/on...eplus-3-3t-t3866517/post80390263#post80390263
nvertigo67 said:
For which roms is this working? I guess this behaviour is rom spefic. E.g. for all lineageos 15.1 and 16.0 roms and all roms based on tje same code base, the above procedure (setting the lockscreen passphrase without the boot passphrase checkbox set) will reset the boot passphrase to "default_password".
The only way I know of to get a seperate passphrase for boot and lockscreen on los15, los16 and roms based on these is this:
https://forum.xda-developers.com/on...eplus-3-3t-t3866517/post80390263#post80390263
Click to expand...
Click to collapse
'setting the lockscreen passphrase without the boot passphrase checkbox set) will reset the boot passphrase to "default_password"' - Ah, sorry, I didn't realise that. I was saying this based on what I had done on another phone.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
'setting the lockscreen passphrase without the boot passphrase checkbox set) will reset the boot passphrase to "default_password"' - Ah, sorry, I didn't realise that. I was saying this based on what I had done on another phone.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
I'm pretty sure this behavior is rom dependent and not device dependent. E.g.: in los14 and early los15 builds the user was able to set lockscreen passphrase and boot passphrase seperately from rom's settings. This has been removed from aosp (officially because of "security concerns"; but I guess these "concerns" has been too many users with too less knowledge have locked up the boot process).
For me the cryptfs cli is perfectly ok, for the average user the behaviour you've expirienced may feel more comfortable. But the longer I think about, the more I like the seperate setting... YMMV.
Just updated with the February full image using fastboot, editing out the -w from flash-all.bat. Fastboot booted TWRP, and then queued up TWRP, Kernel, Magisk and let all 3 rip. No hitches and back up running rooted and everything working normally. Be sure and read the entire Security Bulletin as there were loads of functional updates not always a part of the monthly updates. :good:
Mine wouldn't flash because unlock_critical reset, now my phone is wiped and won't boot the latest update.
Tb0n3 said:
Mine wouldn't flash because unlock_critical reset, now my phone is wiped and won't boot the latest update.
Click to expand...
Click to collapse
Give Deuces script a try. It has helped a lot of people recover their device from similar situations.
I haven't tried it on Feb update though.
You can get it from Development section. Good luck.
Tb0n3 said:
Mine wouldn't flash because unlock_critical reset, now my phone is wiped and won't boot the latest update.
Click to expand...
Click to collapse
what do you mean "because unlock_critical reset?"
Tb0n3 said:
Mine wouldn't flash because unlock_critical reset, now my phone is wiped and won't boot the latest update.
Click to expand...
Click to collapse
Did you ever unlock critical before you tried the update? Or did this happen after the update?
Can someone here confirm the correct way to upgrade from rooted Jan security update without losing data? Would I
reflash stock recovery
fastboot OTA img
fastboot boot twrp.img
flash twrp.zip
flash kernel
flash magisk last?
Or can I use the full image from the dev site, remove the -w and run the flash-all.bat, then use the steps above? Same result, or is one better than the other? Am I missing any steps here?
Is xposed module working on Feb update?
RampageRR said:
Can someone here confirm the correct way to upgrade from rooted Jan security update without losing data? Would I
reflash stock recovery
fastboot OTA img
fastboot boot twrp.img
flash twrp.zip
flash kernel
flash magisk last?
Or can I use the full image from the dev site, remove the -w and run the flash-all.bat, then use the steps above? Same result, or is one better than the other? Am I missing any steps here?
Click to expand...
Click to collapse
See the OP. Use the full image then add back recovery,kernel,magisk in that order. Yes magisk last.
v12xke said:
Just updated with the February full image using fastboot, editing out the -w from flash-all.bat. Fastboot booted TWRP, and then queued up TWRP, Kernel, Magisk and let all 3 rip. No hitches and back up running rooted and everything working normally. Be sure and read the entire Security Bulletin as there were loads of functional updates not always a part of the monthly updates. :good:
Click to expand...
Click to collapse
Quick question - I have performed the flash-all part and at the end it rebooted and everything is fine (except for no root) - it asks for the encryption password and it works with my normal password.
Then I boot TWRP with "fastboot boot twrp-3.2.1-0-taimen.img" and that again works just fine but only to the point where it asks for the password - which here is NOT working? Just a few hours ago the same twrp was working fine with the exact same password (since I did a full backup in advance), and the password is obviously working fine in Android itself, it is only in TWRP where is no longer working???
xclub_101 said:
Quick question - I have performed the flash-all part and at the end it rebooted and everything is fine (except for no root) - it asks for the encryption password and it works with my normal password. Then I boot TWRP with "fastboot boot twrp-3.2.1-0-taimen.img" and that again works just fine but only to the point where it asks for the password - which here is NOT working? Just a few hours ago the same twrp was working fine with the exact same password (since I did a full backup in advance), and the password is obviously working fine in Android itself, it is only in TWRP where is no longer working???
Click to expand...
Click to collapse
I don't really know what went wrong. What do you mean it asks for the encryption password?? If you have some kind of boot encryption set, maybe that is is. My encrypted unit never asks me for a password. I have an unlock screen PIN and that is all. When I flash-all, I wait for the flash to finish (knowing it will reboot) and at the right time hold the volume down button to get me right back into the bootloader. I do not allow it to boot into the OS until I fastboot boot twrp and have never had TWRP refuse my password. Maybe it has something to do with you allowing it to boot into the OS first? Anyway from that "booted" instance of TWRP, I then queue up twrp.zip, kernel.zip, magisk.zip and once they are added, I let TWRP flash all 3. You may want to take this over to the TWRP thread where others have had the PIN issue as well. Some are confirming temporarily removing your PIN/fingerprints fixes it. I have never removed my PIN or fingerprints before or after flashing?
v12xke said:
I don't really know what went wrong. What do you mean it asks for the encryption password?? If you have some kind of boot encryption set, maybe that is is. My encrypted unit never asks me for a password. I have an unlock screen PIN and that is all. When I flash-all, I wait for the flash to finish (knowing it will reboot) and at the right time hold the volume down button to get me right back into the bootloader. I do not allow it to boot into the OS until I fastboot boot twrp and have never had TWRP refuse my password. Maybe it has something to do with you allowing it to boot into the OS first? Anyway from that "booted" instance of TWRP, I then queue up twrp.zip, kernel.zip, magisk.zip and once they are added, I let TWRP flash all 3. You may want to take this over to the TWRP thread where others have had the PIN issue as well. Some are confirming temporarily removing your PIN/fingerprints fixes it. I have never removed my PIN or fingerprints before or after flashing?
Click to expand...
Click to collapse
Yes, it is quite weird.
A few more questions - when you boot your normal Android - do you first get a question about any password there? Since if you don't - your system probably uses the default Android encryption password (which last time when I was looking was literally "default_password" without the quotes).
Why do you still need to flash the kernel - are you using a custom kernel?
xclub_101 said:
Yes, it is quite weird.
A few more questions - when you boot your normal Android - do you first get a question about any password there? Since if you don't - your system probably uses the default Android encryption password (which last time when I was looking was literally "default_password" without the quotes). Why do you still need to flash the kernel - are you using a custom kernel?
Click to expand...
Click to collapse
I never get prompted for a password upon booting, and my phone is encrypted. I think you are probably on to the real reason your twrp is not accepting your PIN. Older Nexus phones had boot encryption with a password but since the Pixel line I thought it was removed? When discussing this further in the TWRP thread I think you should be comparing notes with others on this boot encryption, because I don't have it. I'm reading something now about direct boot and fbe.
Yes I use a custom kernel, always have. I like being able to monitor and control my system and gestures, vibration, etc. I like the kernel monitor (and battery monitor) that goes along with EX Kernel. Highly recommended. Good luck to you.
i sideloaded the update to my verizon version pixel 2 xl, and havent noticed anything, mainly just a run of the mill security update. i read that pixel core has been extended to a few apps.
v12xke said:
I never get prompted for a password upon booting, and my phone is encrypted. I think you are probably on to the real reason your twrp is not accepting your PIN. Older Nexus phones had boot encryption with a password but since the Pixel line I thought it was removed? When discussing this further in the TWRP thread I think you should be comparing notes with others on this boot encryption, because I don't have it. I'm reading something now about direct boot and fbe.
Yes I use a custom kernel, always have. I like being able to monitor and control my system and gestures, vibration, etc. I like the kernel monitor (and battery monitor) that goes along with EX Kernel. Highly recommended. Good luck to you.
Click to expand...
Click to collapse
Thank you for the info!
The encryption is still a weird point - and I believe is still linked by default to the "screen lock password" as described at https://www.xda-developers.com/how-to-manually-change-your-android-encryption-password/ - but I am not yet convinced that I should remove my existing password since the system is telling me that removing it will remove all fingerprints that I have added and mark the system as unsecure for Pay.
What I wonder is if I should go ahead with just writing Magisk without decrypting the user data partition - after all Magisk should not be touching either the system nor the user data partition, so it could work just fine?
Did they remove the setting to turn on Pixel Visua Core in Developer settings?
xclub_101 said:
Thank you for the info!
The encryption is still a weird point - and I believe is still linked by default to the "screen lock password" as described at https://www.xda-developers.com/how-to-manually-change-your-android-encryption-password/ - but I am not yet convinced that I should remove my existing password since the system is telling me that removing it will remove all fingerprints that I have added and mark the system as unsecure for Pay.
What I wonder is if I should go ahead with just writing Magisk without decrypting the user data partition - after all Magisk should not be touching either the system nor the user data partition, so it could work just fine?
Click to expand...
Click to collapse
I guess my question is why do you have an encryption password at boot? My phone boots up to a lockscreen. I enter my PIN and that's it. Maybe I'm misunderstanding and you are calling my PIN your boot encryption password.... do you then have a lockscreen and enter a separate PIN? As for Magisk it doesn't decrypt the data partition or anything else. I always install it by flashing the zip file in TWRP and you have no options there. It just does it's thing and installs Magisk Manager as an app, so when you boot up System, MM is in your app drawer. You can configure it from there. My setup has always passed SafetyNet but I don't use/want Pay.
v12xke said:
I guess my question is why do you have an encryption password at boot? ...
Click to expand...
Click to collapse
Good question - I would normally expect that to be required when Android itself needs to decrypt first time after boot the user data partition? Which up to that point during the boot process is not otherwise needed?
The fact that on some systems is not required suggests to me that Android (like maybe also TWRP) first tries "default_password" and that works?
Mikulec said:
Did they remove the setting to turn on Pixel Visua Core in Developer settings?
Click to expand...
Click to collapse
yes.
djkinetic said:
i sideloaded the update to my verizon version pixel 2 xl, and havent noticed anything, mainly just a run of the mill security update. i read that pixel core has been extended to a few apps.
Click to expand...
Click to collapse
Its quite a bit more than the run of the mill security update.
visual core is now extended to any app, not just a few (so long as they target API level 26, Oreo).
i sideloaded the update like I always do. All updated normally and all functioning as expected. After sideloading the update I booted the twrp-3.2.1-0-taimen.img, it booted and when I entered my pin, which i have been using, in TWRP it would not accept my pin. I rebooted into the boot.img 3 times same issue. I removed my pin and TWRP functioned as expected. I installed TWRP.zip and rebooted recovery. Back in TWRP flashed Kernel, and Magisk and no issues. This was the first time I had issues entering my pin on booting TWRP.img
How to Fix for WIERD LOCKSCREEN BUG on Android 8 and + custom roms
Many of them are facing this Bug after setting up Lockscreen, after few reboots we face System UI FC when entering Unlock code or pattern. This bug is faced when using Oreo, Pie and 10. And this bug is not present on Nougat.
Warning You will loss your all data including your device internal storage and i will be not responsible for any bricks if it happens on your device
Steps :-
Step 1 :- First of all Download MIUI global stable FASTBOOT ROM from the link http://bigota.d.miui.com/V10.2.1.0....XM_20190114.0000.00_6.0_global_8a48e54fe3.tgz
Step 2 :- download mi flashtool and install on your pc and extract fastboot_rom.tgz to a folder.
Step 3 :- Important to have Official Unlock, if you are Unofficially unlocked try this method :- https://forum.xda-developers.com/re...icially-unlock-bootloader-redmi-note-t4009799
Step 4 :- Now copy userdata.img and persist.img from images folder to minimal adb and fastboot folder.
Step 5 :- Now open command window and write following commands -
fastboot erase persist
fastboot erase userdata
fastboot flash persist persist.img
fastboot flash userdata userdata.img
Step 6 :- Now "clean" flash a custom rom 8 or above it. And check whether this bug is still present of not. If you still face the bug then once flash full MIUI through Mi flash tool and repeat Step 5. Note :- After repeating Step 5 don't boot back into MIUI. After performing Step 5 quickly flash twrp and wipe MIUI and flash Custom rom.
Step 7 :- The bug will be gone.
I have made it easy.
If you guys have any Problem regarding this Pm or contact me on telegram my account @sk_ik_27400
Enjoy Flashing:fingers-crossed:
How many days have you checked? Actually after clean flash it happens after roughly one and a half day
One more thing, I am not officially unlocked, I use twrp with locked bootloader, should I try this?
arnabbandopadhyay said:
How many days have you checked? Actually after clean flash it happens after roughly one and a half day
One more thing, I am not officially unlocked, I use twrp with locked bootloader, should I try this?
Click to expand...
Click to collapse
i can 100 percent guarantee it will work i tried about 2 to 3 weeks no issues.
if u are unofficially unlocked then then i would recommend unlock officially using china dev fastboot rom because for many global dev or stable doesnt work
by the way u can if u flash with unofficialy unlocked bootloader then u will be stuck simply do is first of all flash all clean and lock then but remember use that fastboot rom which is recommended for unlocking unofficially rather than latest. then unlock its bootloader then on bootloader flash same image files i have said in above thread simple. also kindly check thread for unnoficial unlocking. http://en.miui.com/thread-345728-1-1.html
tap thanks if helped
Ishaan Kaushal said:
i can 100 percent guarantee it will work i tried about 2 to 3 weeks no issues.
if u are unofficially unlocked then then i would recommend unlock officially using china dev fastboot rom because for many global dev or stable doesnt work
by the way u can if u flash with unofficialy unlocked bootloader then u will be stuck simply do is first of all flash all clean and lock then but remember use that fastboot rom which is recommended for unlocking unofficially rather than latest. then unlock its bootloader then on bootloader flash same image files i have said in above thread simple. also kindly check thread for unnoficial unlocking. http://en.miui.com/thread-345728-1-1.html
tap thanks if helped
Click to expand...
Click to collapse
after doing all, should I wipe all dalvik, system, data, cache, internl before flashing oreo rom?
arnabbandopadhyay said:
after doing all, should I wipe all dalvik, system, data, cache, internl before flashing oreo rom?
Click to expand...
Click to collapse
yes after flashing image files from bootloader simply flash twrp and wipe everything and flash any oreo rom but remember once check in twrp recent screen that there is no warning regarding encrption
It was probably magisk issue
nathanchance said:
also @D-m-x (and everyone else), please try this Magisk build (it can be installed in the modules tab in Magisk Manager)
https://transfer.sh/YVFdi/Magisk-v16.7-1674-.zip
It includes a commit that should fix all of the weird issues with Magisk like the PIN not being accepted after a reboot or the phone getting stuck at the Google logo with the progress bar. The root cause is services crashing during the boot chain and either causing deadlock or lack of functionality. It's entirely possible that a service crashed during boot and started causing issues.
Click to expand...
Click to collapse
Please refer to this post if you have magisk installed. thanks to @nathanchance
Ishaan Kaushal said:
yes after flashing image files from bootloader simply flash twrp and wipe everything and flash any oreo rom but remember once check in twrp recent screen that there is no warning regarding encrption
Click to expand...
Click to collapse
No decryption related message in twrp. I did all qnd will report you back after couple of days, whether is it fixed or not.
arnabbandopadhyay said:
No decryption related message in twrp. I did all qnd will report you back after couple of days, whether is it fixed or not.
Click to expand...
Click to collapse
ok :good:
Dims_Camper said:
Please refer to this post if you have magisk installed. thanks to @nathanchance
Click to expand...
Click to collapse
ok i tried all magisk version but i was fed up with this bug i dont know whether ur method works or not but i know this bug happens due to encryption on userdata. i dont think ur method will because magisk is universal and if problem is related to magisk then it should have happened with many devices not kenzo only
by the way thanks if ever faced again that bug i will try your method:laugh:
Ishaan Kaushal said:
ok :good:
Click to expand...
Click to collapse
On 1st reboot device asking " enter your password to start android", I tried to enter twrp, same thing happens, asking for password.
arnabbandopadhyay said:
On 1st reboot device asking " enter your password to start android", I tried to enter twrp, same thing happens, asking for password.
Click to expand...
Click to collapse
do u use telegram? if yes pm tag mentioned above in thread else send a screenshot of it
Ishaan Kaushal said:
do u use telegram? if yes pm tag mentioned above in thread else send a screenshot of it
Click to expand...
Click to collapse
I use but coudn't start my phone now, I am uploading pic
Ishaan Kaushal said:
ok i tried all magisk version but i was fed up with this bug i dont know whether ur method works or not but i know this bug happens due to encryption on userdata. i dont think ur method will because magisk is universal and if problem is related to magisk then it should have happened with many devices not kenzo only
by the way thanks if ever faced again that bug i will try your method:laugh:
Click to expand...
Click to collapse
i'm referring a post on pixel 2 thread, it's not only kenzo things apparently.
arnabbandopadhyay said:
I use but coudn't start my phone now, I am uploading pic
Click to expand...
Click to collapse
i am not able to see any screenshots attach again
Dims_Camper said:
i'm referring a post on pixel 2 thread, it's not only kenzo things apparently.
Click to expand...
Click to collapse
ok:good:
arnabbandopadhyay said:
I use but coudn't start my phone now, I am uploading pic
Click to expand...
Click to collapse
which rom u flashed?
before doing the method i suggested did u had your set a lockscreen password?
if yes simply enter that password and check else from boot loader enter followimg commands from cmd fastboot erase persist
the again flash persist using fastboot and then reboot to rom
Ishaan Kaushal said:
which rom u flashed?
before doing the method i suggested did u had your set a lockscreen password?
if yes simply enter that password and check else from boot loader enter followimg commands from cmd fastboot erase persist
the again flash persist using fastboot and then reboot to rom
Click to expand...
Click to collapse
I flashed cardinal. I never set any lockscreen password or pin, only a set a pattern.
I couldn't flash persist from fastboot, as I am unofficially unlocked, I need to flash only using mi flash in edl mode.
Unlocking bootloader officially is a harrassment, always getting "couldn't add your account: error 20075" something like that
arnabbandopadhyay said:
I flashed cardinal. I never set any lockscreen password or pin, only a set a pattern.
I couldn't flash persist from fastboot, as I am unofficially unlocked, I need to flash only using mi flash in edl mode.
Unlocking bootloader officially is a harrassment, always getting "couldn't add your account: error 20075" something like that
Click to expand...
Click to collapse
bro its better u contact me on telegram it will better to help Your there
arnabbandopadhyay said:
I use but coudn't start my phone now, I am uploading pic
Click to expand...
Click to collapse
Your device is encrypted!!!
Format data through recovery.
nilesh8343 said:
Your device is encrypted!!!
Format data through recovery.
Click to expand...
Click to collapse
doing this only produces lock screen bug
Ok guys so , I never set-up a password for TWRP , I tried to enter TWRP for installing YouTube VANCED
and I can't because I don't know the password , I tried every password that I can think about , and nothing , I'm sure this is TWRP bug , someone has a clue? Thanks
leftsaray said:
Ok guys so , I never set-up a password for TWRP , I tried to enter TWRP for installing YouTube VANCED
and I can't because I don't know the password , I tried every password that I can think about , and nothing , I'm sure this is TWRP bug , someone has a clue? Thanks
Click to expand...
Click to collapse
Whatever your password is to unlock screen in android
If your phone unlock password doesn't work, it sounds like you have the wrong version of TWRP installed. What ROM and version if TWRP are you running? Easiest work around at the moment will likely to be just temporarily remove your password in Android. That or boot into Fastboot and load a version of TWRP that can decrypt your data.
Newest TWRP
Hi friend , sure password of phone not working ,
TWRP is update . Have other soultion?
leftsaray said:
Hi friend , sure password of phone not working ,
TWRP is update . Have other soultion?
Click to expand...
Click to collapse
Are you using the official one, or the one from this thread? I'm not sure if the official one has patch for latest security patch, but the 3.3.1-6 in that thread should decrypt it. That thread is from the official maintainer too
As stated too, worst case you can remove your password temporarily, which will also delete all your fingerprints. So you'll have to set all that up again if you go that route.
I will try to delete the phone password , should I flash TWRP again? I download from their official site!
leftsaray said:
I will try to delete the phone password , should I flash TWRP again? I download from their official site!
Click to expand...
Click to collapse
I don't believe the one on the official site works with the latest security patch, you need to use the one from the thread above that I linked to. That is from the maintainer of the official version.
Why not just install YouTube vanced thru magisk? Unless you're not rooted.
Hi. My fp stopped working. I need to reconfigure at every reboot. But it doesn't work. I think this is caused because changed SElinux to permissive. Anyone can give me a solution? Now I'm using Pixel Experience last build. Flashed it yesterday in a very strange way: all the apps and datas remained installed (without using migrate for backup).
Flash latest firmware
coremania said:
Flash latest firmware
Click to expand...
Click to collapse
I already flashed the latest firmware but unfortunately it didn't was successful. I need to configure the fingerprint every time I reboot the phone. But it doesn't work.
tudorscutariu said:
I already flashed the latest firmware but unfortunately it didn't was successful. I need to configure the fingerprint every time I reboot the phone. But it doesn't work.
Click to expand...
Click to collapse
Remove your security settings like pin or pattern.
Boot to twrp, mount system, use the twrpfilemanager
and delete locksettings.db under data/system.
Reboot and try to setup your fingerprint again.
coremania said:
Remove your security settings like pin or pattern.
Boot to twrp, mount system, use the twrpfilemanager
and delete locksettings.db under data/system.
Reboot and try to setup your fingerprint again.
Click to expand...
Click to collapse
You probably meant mount DATA, not SYSTEM, right? Mounting system is unnecessary and will just screw up OTA updates.
Edit: ah, guy is on custom rom. So OTA doesn't matter
Btw. it sounds like he installed custom ROM without a data wipe, this might explain the unusual behavior.
_mysiak_ said:
You probably meant mount DATA, not SYSTEM, right? Mounting system is unnecessary and will just screw up OTA updates.
Edit: ah, guy is on custom rom. So OTA doesn't matter
Btw. it sounds like he installed custom ROM without a data wipe, this might explain the unusual behavior.
Click to expand...
Click to collapse
Sounds like same issue as it happens after twrp restore. Deleting the locksettings.db should fix it. I didn't understand his issue in the first place. If he is cross flashing without data wipe he should clean flash anyway, but maybe he's to lazy for it
Edit: of course, you're right, mount data....
First I want to thank you for your helpfulness. I deleted the file but it doesn't work with selinux permissive enabled. Is there a way to make working both permissive and fingerprint? Because I need permissive to make working aiocammodule for gcam
tudorscutariu said:
First I want to thank you for your helpfulness. I deleted the file but it doesn't work with selinux permissive enabled. Is there a way to make working both permissive and fingerprint? Because I need permissive to make working aiocammodule for gcam
Click to expand...
Click to collapse
Not sure what's the purpose of that module, but I'd try setting selinux to enforcing and play with specific selinux policies. With the early Pie releases it was needed to use this to fix lags caused by selinux issues.
Code:
magiskpolicy --live "allow hal_camera_default surfaceflinger_service service_manager find"
Source: https://forum.xda-developers.com/mi-a1/themes/module-long-camera-start-fix-mi-a1-t3745262
You should go for a clean install of pe. What you have written on your first post with your remained data doesn't sound right. If you flash a new rom do it clean or you will constantly run into issues other don't have. Why you want to use an old selinux permissive fix for the tissot cam. Go for gcam it will make better shots anyway.
Made a clean flash of PE. All Is good now, thank you again.