Database Users

[GUIDE] TWRP encryption password bypass without format data

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.

Device encryption on rooted G4 Play (XT1604) with TWRP

I have a UK XT1604 Retail device which is running the current TWRP and is rooted with the stock rom.
The device was rooted with the guide from here, but at the time I didn't realise device encryption was not enabled...
Now I'm trying to enable to device encryption, but the process never starts (by the looks of it) the phone reboots to the Moto/Lenovo logo and just sits there. A manual reboot brings back the normal OS with no changes. I've seen some other posts which say I need to un-root, and other which say I just need to re-flash the boot.img file
Can someone tell me the correct process for enabling device encryption and re-rooting the device after.
I was unable to find the stock UK Retail image for this phone, but I have found a o2 version - can I use any .img files I need from that safely ? My other option is - I have an identical none-rooted device, if I fastboot TWRP (rather than install) can I extract and use the .img files from that device on mine? - This has been uploaded this morning - but its not 100% clear is this is UK and for the XT1604
Can anyone confirm the current 3.1.1-0 supports encrypted file systems and can access them?
Very new to all this Android stuff so any help is very welcome.

You should be able to unroot from the SuperSU app (at least that's what I did) and then encryption will work normally.

bsevcenk said:
You should be able to unroot from the SuperSU app (at least that's what I did) and then encryption will work normally.
Click to expand...
Click to collapse
I'd seen the option but wasnt sure if I needed the full un-root, or just 'disable super user' I presume once I've encrypted I just need to re-flash the SuperSU zip file?

iam-q said:
I'd seen the option but wasnt sure if I needed the full un-root, or just 'disable super user' I presume once I've encrypted I just need to re-flash the SuperSU zip file?
Click to expand...
Click to collapse
You'll need to do a full un-root, encrypt, and then you can flash the SuperSU zip again.

So the encryption worked fine & is set with a password. Now I'm unable to access TWRP in recovery mode as it won't accept the known working password.
I Changed the password to a PIN and that allows me to access TWRP - but if I change it back to a password TWRP flat refuses to accept it. I've seen old issues relating to earlier versions to TWRP where people had the same issue, but nothing relating to the current version. Any ideas?

[HOW TO] Root Android 8.1 - DevPreview 1 - OPP5

There are probably already a couple guides up, but I wanted to post about how I went about doing this and have everything working. It may not work for everyone, but for me, it worked the first time.
0: Yep, there is a step zero here. :good: BACKUP YOUR PHONES INTERNAL STORAGE! IT WILL NEED TO BE WIPED FOR THIS TO WORK!
1: Flash factory image of 8.1 WITH the "-w" (wipe) command (LINK HERE)
2: Allow the system to boot. (optional: complete setup wizard and update apps)
3: Connect the phone to a PC and copy the TWRP 3.1.1-1 ZIP installer to internal storage (or download it via browser) (LINK HERE)
4: Download Magisk 14.3 using a PC or the phones browser, to internal storage (LINK HERE)
5: Reboot into bootloader (using the POWER + VOL-DOWN combo)
6: Fastboot BOOT TWRP 3.1.1-1 (LINK HERE)
Code:
fastboot boot twrp-3.1.1-1-fastboot-marlin.img
7: Once TWRP has booted up, flash the TWRP ZIP installer from step 3 (do NOT reboot to the OS yet)
8: Reboot directly to RECOVERY
9: Flash Magisk v14.3 from step 4
10: Reboot to Android and you're done!
Working TWRP and fully working root!
Only issue I'm having so far with TWRP is that MTP doesn't work. I can't transfer files to/from the phone while connected to a PC. That's why the file transfers have to happen while booted into Android. A TWRP update will likely fix this.

Hello, I followed these steps and all is working great, now I have activated fingerprint lock on my device and pin code, TWRP tells me that the pin is wrong when I go in to the recovery ? Any ideas, I did the procedre twice from stock and twrp tells me that the pin is wrong every time

Known issue on 8.1. Twrp is not working properly.
Just don't use pin or pattern at all.

mikaole said:
Known issue on 8.1. Twrp is not working properly.
Just don't use pin or pattern at all.
Click to expand...
Click to collapse
I need security on my phone, I would rather just wait for the TWRP update and/or actual 8.1

kingbri said:
I need security on my phone, I would rather just wait for the TWRP update and/or actual 8.1
Click to expand...
Click to collapse
At the rate TWRP gets updated, you'd have to wait till December for that. And sometime in December, 8.1 Final is supposed to be out.
Not sure if it works, but you could try disabling security, use TWRP for whatever you need, then enable security again when you're done.

So when you say flash with wipe command. You mean flash the flash all with -w tacked on the end?

Mckillagorilla said:
So when you say flash with wipe command. You mean flash the flash all with -w tacked on the end?
Click to expand...
Click to collapse
Yes, in other words: do not edit flash-all.sh.

Mckillagorilla said:
So when you say flash with wipe command. You mean flash the flash all with -w tacked on the end?
Click to expand...
Click to collapse
? No to editing file. The file flash-all.bat already has the -
w command in it. (use Flash-all.sh if you use Apple).
The reason post #1 instructs to wipe with the -w command is because some are used to removing the -w to preserve user data when flashing. For this root solution that won't work.

Born<ICs said:
? No to editing file. The file flash-all.bat already has the -
w command in it. (use Flash-all.sh if you use Apple).
The reason post #1 instructs to wipe with the -w command is because some are used to removing the -w to preserve user data when flashing. For this root solution that won't work.
Click to expand...
Click to collapse
worked perfectly for me ... no errors so far.

Let me rephrase. I wiped the phone, went back to 7.1.2, took 8.1 OTA now I want to root without wiping. Is this possible?
The second try, I hate the scrolling that is within apps. Looks like I might be going back to Nougat.

Scottay5150 said:
Can I root the OTA developer preview after a complete flash/wipe?
Click to expand...
Click to collapse
Yes, I am rooted and on it. Same procedure.

Working for me on Pixel non XL swapped the file for sailfish versions

I forget if I install TWRP to does this wipe the whole device?
TonikJDK said:
Yes, I am rooted and on it. Same procedure.
Click to expand...
Click to collapse
Thanks.

I mention that this method also works on Pixel Sailfish, except that it has to use twrp img and zip for Sailfish.

Any reason why I shouldn't just sideload the zips in TWRP? I did it just to test and things seem to be working so far without wiping the device.

Here's a stupid question- does the bootloader need to be unlocked? I'm carrier locked and want to be rooted with TWRP.

hooks024 said:
Here's a stupid question- does the bootloader need to be unlocked? I'm carrier locked and want to be rooted with TWRP.
Click to expand...
Click to collapse
On the Pixels yes you need to be bootloader unlocked to root.

mikaole said:
Known issue on 8.1. Twrp is not working properly.
Just don't use pin or pattern at all.
Click to expand...
Click to collapse
having same problem (says wrong pin), why do almost all guides that for Pixels you need to set up a pin in order to flash TWRP/root properly? Confused.

eddi0 said:
having same problem (says wrong pin), why do almost all guides that for Pixels you need to set up a pin in order to flash TWRP/root properly? Confused.
Click to expand...
Click to collapse
The phone is encrypted, it needs a PIN to authenticate to the OS to decrypt.

I actually had to factory reset it and NOT use a pin for it to work properly (after factory reset go into settings>security>none for screen lock). I know in the past a pin was required but as the second post states Magisk 14.3 is not playing nice with 8.1 beta.

8.1 Final, updated adb/fastboot, & problems and fixes - update 12/17/2017 TWRP fixed

8.1 Final, updated adb/fastboot, & problems and fixes - update 12/17/2017 TWRP fixed
UPDATE 12/17/2017: @phaino00 and other users have reported that TWRP v3.2.1-0.img take care of the internal storage decryption problem.
https://forum.xda-developers.com/showpost.php?p=74868928&postcount=380
Get it at https://twrp.me/. It has been reported that FLASHing the new TWRP.zip (as opposed to just fastboot boot twrp.img) will make the phone only boot back into recovery every time - never back into Android. I haven't not personally confirmed this, however.
UPDATE 12/9/2017: Word is at https://forum.xda-developers.com/showpost.php?p=74782925&postcount=6238 that Magisk v14.2 (not v14.5 build 1456) both works with Android 8.1 AND with FlashFire - which is an alternative to using TWRP. I used FlashFire 100% from Android 8.0 November for installing complete firmware images and flashing ElementalX and SuperSU, so may work just fine with ElementalX v3.00 and Magisk v14.2.
I have not tested this myself.
UPDATE 12/7/2017: If you had a Contacts Sync issue, the fix was shared by @Jank4AU in this post https://forum.xda-developers.com/showpost.php?p=74767941&postcount=45. Make sure and understand it's the "Contacts Storage" app, not merely the "Contacts" app. THEN Storage section, then Wipe App Data. HEADS UP: Call History will be wiped and it may take a minute or two for Contacts settings to re-sync so your Voicemail tab may disappear and reappear, if applicable.
UPDATE 12/6/2017: ElementalX v3.0.0 has been updated by @flar2 for Android 8.1 Final and the December security patches. IF YOU ROOTED, you MUST flash the stock boot.img before flashing any version of ElementalX.
DO NOT USE FlashFire v0.73 under Android 8.1 Final, at least with Magisk v14.5 build 1456. Just seem to get minutes-long black screen. A long black screen can be normal with FlashFire, but I think that was too long.
Heads up, the standalone platform tools (adb, fastboot...) have changed since the day before Android 8.1 Final was released. Moreover, the zip is now 4.30 MB (14.5 MB uncompressed) vs before and a month ago was 9.31 MB (30.7 MB uncompressed), and was 7.16 MB in July.
Get the latest Platform Tools in preparation for flashing 8.1 final: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
NOTICE: This link doesn't change, but the file it links to does every so often.
Edit: Links up: https://dl.google.com/dl/android/aosp/sailfish-opm1.171019.011-factory-56d15350.zip
SHA-256 56d15350a2c54960b149fc8a080547f17e1c4bba4da89bb03f6c634746ca6318
Used FlashFire to flash entire firmware package including enabling to flash all the dangerous/protected partitions, then had FlashFire flash ElementalX 2.03 (seems to be working fine), then SuperSU 2.82 SR5. DO NOT install ElementalX v2.03 AND/OR SuperSU v2.82 SR5! ElementalX v2.03 caused a system error dialog at least on first boot, caused bootloops like crazy when you go to reboot, and SuperSU v2.82 SR5 just doesn't achieve patching selinux, so no root. SuperSU v2.82 SR5 problem confirmed with others. You should be able to FlashFire ElementalX v3.00 and Magisk v14.5 build 1456 works fine IF you do them in the same chain/after having FlashFire flash the full firmware. FlashFire doesn't seem to work once you're booted into Android 8.1.
The SuperSU installation, I noticed had some failure to patch selinux.
The error on every boot after installing Magisk v14.5 build 1456 is:
Code:
[SIZE="4"][B]Android System[/B][/SIZE]
There's an internal problem with your device. Contact your manufacturer for details.
and an OK button.
I don't think the screen will even sleep with this dialog in front. At least not until my preferred 10-minute delay but I'm told it's harmless otherwise.
KNOWN ISSUES
SuperSU v2.82 SR5 problem confirmed with others.
Both fastboot boot TWRP v3.2.0-0 and 3.1.1-1 don't accept my pin. TWRP problem confirmed with others. No solution other than to use USB-OTG or remove your PIN to install the Magisk v14 build 1456 zip. Hint: A USB 3.0 flash drive via USB-OTG in TWRP is FAST! Too bad we can't backup 8.1 data yet since no decryption (unless you remove PIN).
See the update at the top of the post, the latest version of TWRP is reported to take care of the internal storage decryption problem.
A select very few or individual contact(s) are missing from the Contacts/Phone app. Contacts missing problem confirmed with others. Wiping the Contacts app data didn't help. Turning Contacts/People sync on and off didn't help. Rebooting didn't help. Haven't tried wiping Phone app data but I wouldn't think that would be related since Contacts is a separate app. I've confirmed that my missing contact(s) are still listed in Google Contacts through the web UI on a PC. Exporting via csv/vcf and re-importing/duplicating the contact hasn't helped two of us who have tried that.
Fix shared by @Jank4AU in this post https://forum.xda-developers.com/showpost.php?p=74767941&postcount=45. Make sure and understand it's the "Contacts Storage" app, not merely the "Contacts" app. THEN Storage section, then Wipe App Data. HEADS UP: Call History will be wiped and it may take a minute or two for Contacts settings to re-sync so your Voicemail tab may disappear and reappear, if applicable.
sliding_billy said:
I'm sure that moving the search bar to the bottom works for some folks (AKA increases advertising revenue), but the fact that it cannot be moved or disabled like any other widget is ridiculous. Perhaps someone will write a "fix" for it that doesn't involve installing a custom launcher, or someone already has and I haven't seen it since I was not running the test builds and only installed 8.1 yesterday.
Click to expand...
Click to collapse
There's an error dialog, as noted above, every time you boot into Android after flashing Magisk v14.5 build 1456.
Some users are being offered an OTA from the already flashed Final 8.1 to the DP2 of 8.1. Two users reported. The fix reported by @TonikJDK is to unenroll from the beta program. Thank you!
FlashFire v0.73 doesn't work with Magisk v14.5 build 1456 on Android 8.1. Word is at https://forum.xda-developers.com/showpost.php?p=74782925&postcount=6238 that Magisk v14.2 (not v14.5 build 1456) both works with Android 8.1 AND with FlashFire - which is an alternative to using TWRP. I used FlashFire 100% from Android 8.0 November for installing complete firmware images and flashing ElementalX and SuperSU, so may work just fine with ElementalX v3.00 and Magisk v14.2.
I have not tested this myself.
Let me know if there are any other issues, and links to confirmation posts by others if you have them. I won't post one-off issues here, only those confirmed reported by two or more people. Thanks!
Click to expand...
Click to collapse

Was able to flash-all with -w removed.
Attempted to fastboot boot twrp and adb sideload supersu, but I'm not able to gain root.
Anyone else with any success?

patso23 said:
Was able to flash-all with -w removed.
Attempted to fastboot boot twrp and adb sideload supersu, but I'm not able to gain root.
Anyone else with any success?
Click to expand...
Click to collapse
Fastboot boot TWRP and installed magisk 14.5 via usb-otg and root is successful.

phaino00 said:
Fastboot boot TWRP and installed magisk 14.5 via usb-otg and root is successful.
Click to expand...
Click to collapse
I haven't had any success getting fastboot booted twrp.img to accept my pin. Did you install magisk before setting up Android or after? But I suppose from USB-OTG bypasses that issue, so thanks for reporting.

roirraW "edor" ehT said:
I haven't had any success getting fastboot booted twrp.img to accept my pin. Did you install magisk before setting up Android or after? But I suppose from USB-OTG bypasses that issue, so thanks for reporting.
Click to expand...
Click to collapse
Same here concerning the option to enter pin, pattern, etc. when fastboot booted twrp.img: It does not appear. Given this, I mounted usb-otg partition and flashed Magisk 14.5. Root achieved. I completed this after flashing the Dec factory image. It was a clean flash (i.e., did not remove -w flag)
Have adaway working, removed unwanted system apps and working on getting v4a working.

phaino00 said:
Same here concerning the option to enter pin, pattern, etc. when fastboot booted twrp.img: It does not appear. Given this, I mounted usb-otg partition and flashed Magisk 14.5. Root achieved. I completed this after flashing the Dec factory image. It was a clean flash (i.e., did not remove -w flag)
Have adaway working, removed unwanted system apps and working on getting v4a working.
Click to expand...
Click to collapse
Thanks again, seems to be working 100% with ElementalX v2.03 and Magisk v14.5 (build 1456).

PSA: I recommend avoiding ElementalX 2.03 on 8.1 Final until it's updated. At first, it seems to be working, but boot loops galore when you reboot. No boot loops without it. Also, just because it's related, SuperSU 2.82 SR5 doesn't work for me (repeated tries on fresh installs) on 8.1 Final. Magisk 14.5 build 1456 seems to, though (thanks @phaino00).

phaino00 said:
Same here concerning the option to enter pin, pattern, etc. when fastboot booted twrp.img: It does not appear. Given this, I mounted usb-otg partition and flashed Magisk 14.5. Root achieved. I completed this after flashing the Dec factory image. It was a clean flash (i.e., did not remove -w flag)
Have adaway working, removed unwanted system apps and working on getting v4a working.
Click to expand...
Click to collapse
can you tell me which version of v4a you are working with? I cant seem to find a stand alone version of it but have read several posts whee it's been mentioned. I keep ending back up in the ARISE thread. thanks for the help

Having a major problem with my most important contact not syncing. My wife! I see her in Google in the web ui but she's not on the phone. Tried clearing Contacts app data, turning off sync and back on, rebooting the phone multiple times, I exported her contact info from the web ui and reimported her so there's now two, still no change.

quinejh said:
can you tell me which version of v4a you are working with? I cant seem to find a stand alone version of it but have read several posts whee it's been mentioned. I keep ending back up in the ARISE thread. thanks for the help
Click to expand...
Click to collapse
I have been working with this:
https://forum.xda-developers.com/pixel-2-xl/how-to/viper4android-8-1-0-t3711474/page2
The v4a is 2.5.0.5 app and 2.5.0.4 driver. This seems to be working for some on the pixel 2.
I have not succeeded yet.
---------- Post added at 03:58 AM ---------- Previous post was at 03:32 AM ----------
roirraW "edor" ehT said:
Having a major problem with my most important contact not syncing. My wife! I see her in Google in the web ui but she's not on the phone. Tried clearing Contacts app data, turning off sync and back on, rebooting the phone multiple times, I exported her contact info from the web ui and reimported her so there's now two, still no change.
Click to expand...
Click to collapse
I lost my son and sister....very odd issue
Besides what you did, I exported their contact info as a .vcf and imported to contacts app. Their contact info showed up and within seconds disappeared again.

The latest SuperSU is not working, saying patching sepolicy failed.
A rather strange thing is that the files I have flashed in twrp does not populate after system boots, eg, I placed a file under /system/system/blabla (I have checked mount system read/write in twrp), but after a reboot, I could not find the file under /system

churchmice said:
The latest SuperSU is not working, saying patching sepolicy failed.
A rather strange thing is that the files I have flashed in twrp does not populate after system boots, eg, I placed a file under /system/system/blabla (I have checked mount system read/write in twrp), but after a reboot, I could not find the file under /system
Click to expand...
Click to collapse
I have the same sepolicy crash. Does yours happen on a non-XL Pixel, because that issue only happened to me on the non-XL. My XL rooted fine with the USB install workaround.
https://forum.xda-developers.com/pixel/development/twrp-alpha1-pixel-devices-t3500314/page101

sliding_billy said:
I have the same sepolicy crash. Does yours happen on a non-XL Pixel, because that issue only happened to me on the non-XL. My XL rooted fine with the USB install workaround.
https://forum.xda-developers.com/pixel/development/twrp-alpha1-pixel-devices-t3500314/page101
Click to expand...
Click to collapse
Yes, mine is pixel, generation 1.
I tried to install magisk 14.5 and it works flawlessly.

phaino00 said:
I lost my son and sister....very odd issue
Besides what you did, I exported their contact info as a .vcf and imported to contacts app. Their contact info showed up and within seconds disappeared again.
Click to expand...
Click to collapse
Really odd. That is why they should wait longer than a week after a DP to release a Final. [emoji16]
Guess I'll type her in manually for now, at least basic info. I have her exported and since I can see her in the web UI nothing is really lost.

TWRP v3.2.0.0 is unable to decrypt the data partition. Any solution yet?

m0h1t said:
TWRP v3.2.0.0 is unable to decrypt the data partition. Any solution yet?
Click to expand...
Click to collapse
I removed any screen locking, had a pattern before and tried with pin and password. Removing the screen lock solved the problem.

m0h1t said:
TWRP v3.2.0.0 is unable to decrypt the data partition. Any solution yet?
Click to expand...
Click to collapse
You can also use USB-OTG to install things (like Magisk). I'm sure TWRP will have to be updated before it'll work with decrypting the internal storage on 8.1 Final. Keep an eye on the OP - I'll update there when or if it's fixed.

I'm sure that moving the search bar to the bottom works for some folks (AKA increases advertising revenue), but the fact that it cannot be moved or disabled like any other widget is ridiculous. Perhaps someone will write a "fix" for it that doesn't involve installing a custom launcher, or someone already has and I haven't seen it since I was not running the test builds and only installed 8.1 yesterday.

Has anyone gotten MTP working to access internal storage from a Windows PC from within Android 8.1 Final WITHOUT turning off USB Debugging? Device Manager sees it just fine on Windows 7 but it's not available until I turn off USB Debugging - or is that normal!? Actually, even with it off, Windows Explorer sees the Pixel, but when I enter it, there's no storage listed.
Once again, USB-OTG worked just fine within Android 8.1, at least.
sliding_billy said:
I'm sure that moving the search bar to the bottom works for some folks (AKA increases advertising revenue), but the fact that it cannot be moved or disabled like any other widget is ridiculous. Perhaps someone will write a "fix" for it that doesn't involve installing a custom launcher, or someone already has and I haven't seen it since I was not running the test builds and only installed 8.1 yesterday.
Click to expand...
Click to collapse
I do use a custom launcher (Nova - can never live without it for long), but thanks for noticing since I wouldn't have. I'll add that as a known issue.

Spent hours trying to fix contacts last night, haha.
I got a few that kept disappearing on sync to sync and stay by erasing the anniversary date listed and then manually readding it on my phone after the sync.

I keep loosing root after reboot, Pls help.

Hey guys,
first time posting here so i dont kow how to style the text, so sorry about that.
last time i rooted a phone was on my sony xperia sp , where all i had to do was to go to towelroot .com and click to root.
I tryed to root my OP6T yesterday, after some setbacks i managed to sucessfully do it.
I did it like this:
1. Downloaded full ROM of OOS 10.3.2,
2. copied the payload to a program called payload dumper that extracted the boot image.
3. Copied the boot image to the phone
4. opened Magisk manager and selected install from source where i chose the boot.img
5. it created a copy called magisk_patched.img
6. booted in fastboot
7. on my pc used the command prompt to "fastboot boot magisk_patched.img"
booted normally and i had root.
but then problem appeared
#Problem 1
everytime i rebooted my phone i would loose root and it would say Magisk not installed. To get it back i would need to perform step 7 again and it was not ideal to do that everytime i turned off my phone.
#Problem 2
While tryng to solve problem 1 i read that i needed to open magisk manager and "Install to Inactive Slot (After OTA)."
After doing that it rebooted but now it wont boot at all, even if i try to "fastboot boot magisk_patched.img" the cmd gives me error:
fastboot boot magisk_patched.img
downloading 'boot.img'...
OKAY [ 0.838s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.845s
now my phone is just sitting there i dont want to reset it again. it would be the 4th time that i need to set up my phone in 2 days, so im trying to see if there are alternatives.
If reset is really the only way, i read that with root you can make a full backup of your phone and then restore it. How to do that? can i do it in the situation im in?
How can i root my OP6T running OOS10.3.2, and keep it? Whats the right method bc the one i followed seemed flawed.
I also tried one that had TWRP but maybe i did something wrong bc it didnt work., also there is no official one working for 10.3.2.

What is happening is normal with those instructions (they aren't right).
All you need to do is install TWRP. Do not use the official one, it is out of date. Use TWRP from this thread Link here. The TWRP from that thread is from the official maintainer. It works fine with OOS 10.
- You need to get the phone in fully working order again. Which may mean you need to use the fastboot ROM, as you've probably "goofed" something up at this point. (no offense meant). Make sure your phone boots and such after this.
- For OOS 10 with the phone in fastboot, fastboot boot recoveryimgfilename.img (<-- For OOS 10 you will need TWRP 3.3.1-32 Q Unofficial by mauronofrio from the thread I linked to above) This will boot to TWRP.
- Now run TWRP 3.3.1-32 Unofficial Installer by mauronofrio this will install TWRP. The installer is the same for Android 9 and 10, doesn't matter.
- Once the installer runs, click back, choose reboot to recovery. If you boot to the system, you have to start over. Reboot to recovery!
- Install Magisk 20.3 <-- The current version. The official download page. After that you can reboot to the system. You should now have a rooted, phone with Magisk, and TWRP installed.
Any questions ask.

OhioYJ said:
What is happening is normal with those instructions (they aren't right).
All you need to do is install TWRP. Do not use the official one, it is out of date. Use TWRP from this thread Link here. The TWRP from that thread is from the official maintainer. It works fine with OOS 10.
- You need to get the phone in fully working order again. Which may mean you need to use the fastboot ROM, as you've probably "goofed" something up at this point. (no offense meant). Make sure your phone boots and such after this.
- For OOS 10 with the phone in fastboot, fastboot boot recoveryimgfilename.img (<-- For OOS 10 you will need TWRP 3.3.1-32 Q Unofficial by mauronofrio from the thread I linked to above) This will boot to TWRP.
- Now run TWRP 3.3.1-32 Unofficial Installer by mauronofrio this will install TWRP. The installer is the same for Android 9 and 10, doesn't matter.
- Once the installer runs, click back, choose reboot to recovery. If you boot to the system, you have to start over. Reboot to recovery!
- Install Magisk 20.3 <-- The current version. The official download page. After that you can reboot to the system. You should now have a rooted, phone with Magisk, and TWRP installed.
Any questions ask.
Click to expand...
Click to collapse
So getting it straight, i need to first reset my phone and then do the steps you described.
Can i backup the data first with TWRP to restore it later and avoid setting up everything again?

Davide1713 said:
So getting it straight, i need to first reset my phone and then do the steps you described.
Can i backup the data first with TWRP to restore it later and avoid setting up everything again?
Click to expand...
Click to collapse
Supposedly. I've never used that function of TWRP. Some people have luck with, some people restore things that shouldn't be restored and end up having to wipe the phone again. Personally I just use TitaniumBackup like I always have. I would search for information on that in the TWRP thread if you want to try method. I don't know enough on that to provide solid information.

OhioYJ said:
Supposedly. I've never used that function of TWRP. Some people have luck with, some people restore things that shouldn't be restored and end up having to wipe the phone again. Personally I just use TitaniumBackup like I always have. I would search for information on that in the TWRP thread if you want to try method. I don't know enough on that to provide solid information.
Click to expand...
Click to collapse
Hey man,
Thank you so much. It worked and i stay rooted even after reboot.
May i ask how you use the Titanium Backup, i think back in the days all i used it for was uninstalling system apps. Or if you know some nice guides. If you know other good things to checkout now that i have root i would appreciate it, i have been far away from rooting for too long.
Once again thank you so much

Davide1713 said:
Hey man,
Thank you so much. It worked and i stay rooted even after reboot.
May i ask how you use the Titanium Backup, i think back in the days all i used it for was uninstalling system apps. Or if you know some nice guides. If you know other good things to checkout now that i have root i would appreciate it, i have been far away from rooting for too long.
Click to expand...
Click to collapse
I use it to back up app and app data primarily. It allows me to restore data to apps after a clean install. Since I have the Pro version it's just a batch action (one click essentially). There is also a way to create a flashable .zip you can use in TWRP, although I haven't tried that method, as I'm typically not restoring apps, just data. I also use it remove apps from time to time.

OhioYJ said:
I use it to back up app and app data primarily. It allows me to restore data to apps after a clean install. Since I have the Pro version it's just a batch action (one click essentially). There is also a way to create a flashable .zip you can use in TWRP, although I haven't tried that method, as I'm typically not restoring apps, just data. I also use it remove apps from time to time.
Click to expand...
Click to collapse
Hey man, im sorry i am once again in need.
Idk why but at first i can reboot the system normally without issues. but after a while once i set up everything it just doesnt boot anymore. Am i missing something? do i have to do anything with magisk? download a module or something?
Could it be that google security update is the fault?

Davide1713 said:
Hey man, im sorry i am once again in need.
Idk why but at first i can reboot the system normally without issues. but after a while once i set up everything it just doesnt boot anymore. Am i missing something? do i have to do anything with magisk? download a module or something?
Could it be that google security update is the fault?
Click to expand...
Click to collapse
When you installed everything originally did you fix everything with a clean install? Both slots are the same version of Android? (Like you don't have something weird going on like Android 9 on one and Android 10 on another?)
You definitely have something abnormal going on. There shouldn't be anything in Magisk that you have to do, at least not to prevent crashing. I normally hide it, but that has to do with keeping apps from detecting root.

OhioYJ said:
When you installed everything originally did you fix everything with a clean install? Both slots are the same version of Android? (Like you don't have something weird going on like Android 9 on one and Android 10 on another?)
You definitely have something abnormal going on. There shouldn't be anything in Magisk that you have to do, at least not to prevent crashing. I normally hide it, but that has to do with keeping apps from detecting root.
Click to expand...
Click to collapse
I got it to boot by uninstalling magisk,
I am 100% sure i dont have two different version of android in different slots, bc yesterday i was in big trouble and nothing was working and i flashed on both slots the same version of android 10(dont remember exactly wich one as i tried a couple, but they were the same).
Today when i couldnt boot anymore i went into stock recovery, factory reset -> when it booted i placed the stockOS.zip file in the phone and applied update from local file -> after that i factory reset again from the system settings, so i think the phone should have installed it properly.
Only after that i did what you told me and installed TWRP and Magisk. and as i said it worked and i could restart my device etc..
After a while when i restarted i couldnt boot anymore and went to bootloader. Removing Magisk fixed it,apperantly on install magisk creates a copy of the boot.img that it restores on uninstall, and i booted to system.
Now i can use my phone but dont have root.
Im very thankful for you being there and helping me out trough this, i cant thank you enough

GuestD2272 said:
I got it to boot by uninstalling magisk,
I am 100% sure i dont have two different version of android in different slots, bc yesterday i was in big trouble and nothing was working and i flashed on both slots the same version of android 10(dont remember exactly wich one as i tried a couple, but they were the same).
Today when i couldnt boot anymore i went into stock recovery, factory reset -> when it booted i placed the stockOS.zip file in the phone and applied update from local file -> after that i factory reset again from the system settings, so i think the phone should have installed it properly.
Only after that i did what you told me and installed TWRP and Magisk. and as i said it worked and i could restart my device etc..
After a while when i restarted i couldnt boot anymore and went to bootloader. Removing Magisk fixed it,apperantly on install magisk creates a copy of the boot.img that it restores on uninstall, and i booted to system.
Now i can use my phone but dont have root.
Im very thankful for you being there and helping me out trough this, i cant thank you enough
Click to expand...
Click to collapse
Not sure if you're still having this issue but I'll post the solution just in case anyone gets stumped, does a google search, and comes across this post. You were using the wrong command.
"fastboot boot" just lets you boot with the img so you can verify that root works.
"fastboot FLASH boot" will flash it and root will stick after reboot.
No need to jump through hoops with TWRP and such.