yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4 XL Questions & Answers] Badger50:
You sideloaded the factory image or fastbooted it?

At any rate, you could try fastbooting the factory image again to both slots, one at a time, to see if that works. However, more than likely you'll need to do a factory reset. Going forward, it's always a good idea to remove face ID before doing a monthly update. Haven't had a problem with any update in that regard since I got the device last October :good:
[Google Pixel 4 XL Questions & Answers] neo_lithic3K:
Happened to me too. I fixed it by dirty flashing the march factory image. (I noticed that issue started after I flashed fsociety kernel)

(I was on a clean install of the march factory image; already did a factory reset before flashing and already cleared security/face data/etc beforehand. )
[Google Pixel 4 XL Questions & Answers] ibphantom:
Could you explain your process just a little more. You deleted face data and then how did you dirty flash? Did you just 'adb reboot bootloader' then 'adb flash marchupdate.zip?
[Google Pixel 4 XL Questions & Answers] Badger50:
Dirty flash in essence means removing the -w characters from the flash-all.bat file. This prevents your data from being wiped, when you fastboot the factory image. It's pretty much like taking an OTA :good:
[Google Pixel 4 XL Questions & Answers] neo_lithic3K:
Yup, I can definitely go into more detail., but my situation probably doesn't match yours completely.

As badger50 mentioned, dirty flash is basically removing the -w. In my case, I removed the '-w" from the March factory image's (flash-all.bat) file. Then I cleared the face data from settings-security, removed any pins/pws/patterns, & did a factory reset from settings-system (b/c I read that the titan chip can only be cleared via factory reset). I then booted to bootloader (adb reboot bootloader or use the power-volume down method) and ran the edited flash-all.bat. That basically reinstalls the factory image without erasing my user data.

The reason I dont sideload OTA is because I never had good luck with sideloading. Something comes out wrong or I run into odd issues.
[Google Pixel 4 XL Questions & Answers] ibphantom:
Thank you. You're a wonderful person and I appreciate your time.:fingers-crossed:

Thanks to you as well Badger50:victory:
[Google Pixel 4 XL Questions & Answers] wrecklesswun:
factory reset fixes it all... for some reason using -w may or may not delete something that a factory reset does?
[Google Pixel 4 XL Questions & Answers] lapapunk:
Confirm. Works only factory reset from settings.

Dirty, clean flash, safe mode - doesn't work.
[Google Pixel 4 XL Questions & Answers] krabman:
I've never had a problem on the pixel devices leaving my security in when flashing the full image but it can't hurt to remove it. I agree with others above as regards flashing it BTW, it's easy and works every time without having to research the secret handshake sometimes needed to get the OTA to go. You also don't have to wait for it and you don't have to deal with problems like this that come up here and there when sideloading an OTA.

I'm not really sure why so many are resistant to flashing the full image but you get a lot of push-back on it here which seems misplaced; over time you're ahead of the game.
[Google Pixel 4 XL Questions & Answers] jtwebfusion:
If I install the March 2020 factory image, face unlock works fine. If I install the April 2020 OTA, face unlock breaks. If I install April 2020 or May 2020 factory images, face unlock is broken. SO FRUSTRATING!!!
[Google Pixel 4 XL Questions & Answers] TechOut:
Same it will only work for me on March or DP 3 of the beta. Just RMAd my Pixel
[Google Pixel 4 XL Questions & Answers] jtwebfusion:
I have an RMA in for mine, but Google has nothing in stock. :mad:
[Google Pixel 4 XL Questions & Answers] TechOut:
I'm doing one last full wipe and flash of the may update in hopes it might just work.

---------- Post added at 01:12 AM ---------- Previous post was at 01:10 AM ----------

How long did it take for you to get the email with shipping label? Been waiting about 5 minutes and nothing yet.
[Google Pixel 4 XL Questions & Answers] jtwebfusion:
It took about 5-10 minutes to get it...
[Google Pixel 4 XL Questions & Answers] TechOut:
Yeah just got it and while scheduling the fedex pickup realized I mistyped the address so had to cancel and do it all over...
[Google Pixel 4 XL Questions & Answers] TechOut:
Are they repairing any of these or have they just been replacing them?
[Google Pixel 4 XL Questions & Answers] Mackay53:
You'll get a refurbished one
[ONE Q&A, Help & Troubleshooting] mac89cam:
Hi, I think I have a problem with my OnePlusOne. I have lineage os 16 but I see from BBS that it practically never goes into Deep sleep but there is no app that keeps it awake, it seems to be a kernel problem. Has anyone tried a stable #bacon kernel? I have the 3.4.113! automatic translation
[General Topics] King46:
Can anyone tell me how do I roate the screen when I am playing a video file.

I have copied them as widescreen and they played on my orbit 2 no problem but recently i tried to play a video but it will only play in portrait. Tried rotating screen but didnt change anything.

I dont understand why it would play before in landscape full screen but now only plays in portrait full screen

any ideas

thanks
[OnePlus 7 Questions & Answers] Gaglios:
Hi, does anyone know why after changing the display the fingerprint sensor, the proximity and brightness sensor no longer work?
[OnePlus 7 Questions & Answers] strongst:
In first place it can be a bad connection of the cabling.
[OnePlus 7 Questions & Answers] Gaglios:
already checked :crying:

also done a factory reset
[Samsung Galaxy S20 / S20+ / S20 Ultra Questions & ] finshan:
Been awhile since I used samsung, so I'm just checking.

If I get the verizon model, I understand it will be locked to verizon. But I'd still prefer the clean(er) unlocked firmware. Can I flash that straight away or does it have to be "leaked" or whatever in the coming months?
[Samsung Galaxy S20 / S20+ / S20 Ultra Questions & ] west2cool:
Firmware are already available on Sammobile.com

---------- Post added at 05:36 PM ---------- Previous post was at 05:36 PM ----------
[Samsung Galaxy S20 / S20+ / S20 Ultra Questions & ] XRSTOY1:
Does a Unlocked S20 + have to be rooted to flash let's saw Verizon firmware onto it? Or just Odin and the rom?
[Samsung Galaxy S20 / S20+ / S20 Ultra Questions & ] aroy97:
You don't need to be rooted, just Odin the official ROM.
[Samsung Galaxy S20 / S20+ / S20 Ultra Questions & ] wshader:
Been awhile since played with Samsung but does device need to be unlocked for Odin? I.E Sprint model flashed to generic?
[Android Q&A, Help & Troubleshooting] Tanmay_B:
I am a newbie...

So this question came in my mind when I removed my screen lock using adb by deleting the .key file from the /data/system/ folder....

For removing we delete the .key file, but what if we copy the .key file to our local PC using adb command and then try to brute force the encryption of the .key file using hashcat (like what we do when cracking the .cap file to get the WiFi password). Also we can use a wordlist.

If we can do this then we can easily brute force PIN screen lock because it has the limited range of possible number combinations.

I don't know what kind of encryption method is used for encrypting the plain password/pin for android screen lock so please answer this.

So please let me know if this is possible....

Also I don't if this is discussed before....

:fingers-crossed:
[Redmi Note 8 Questions & Answers] shovan.cc:
Plz help me what can i do? i dont flash properly my system has been destroyed. i did evething for solved this problem . now i have no option to solve this problem . now what can i do? any one Help me?

i am attached some photos

my image file : ginkgo_in_global_images_V11.0.3.0.PCOINXM

[IMG="solved this"]https://i.imgur.com/4cizbpq.jpg[/IMG]_20200214.0000.00_9.0_in_8e42c719e
[Redmi Note 8 Questions & Answers] BusuDD:
Flash vbmeta file or try to move files to root directory.
[Redmi Note 8 Questions & Answers] the_weird_aquarian:
in fastboot rom there must be a file vbmeta.img....

download latest platform tools first.

extract the plaform tools zip...copy vbmeta.img in this folder,open cmd in this folder path and flash vbmeta with phone in fastboot mode by this command

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

after this flash recovery. :)
[Redmi Note 8 Questions & Answers] iaio72:
if you solve the problem, here the vbmeta: https://mega.nz/#!bUwliDDS!PNCWo68avE9GsyK4JeJgV1zoVIiejh0-gIs1X6MCEPk
[Redmi Note 8 Questions & Answers] CommieColin:
Mi Flash should be able to restore your phone to 100% stock, including boot and vbmeta - it could be that the directory is too long. Try placing the fastboot file in your root folder (C:/) and direct Mi Flash Tool towards that.

System has been destroyed should only really show up when you try flashing a ROM without a dummy vbmeta.img
[Redmi Note 8 Questions & Answers] shovan.cc:
Thx.

Thanks For Your Suggestion.. & i Am done This flash Properly.
[Redmi Note 8 Questions & Answers] yazido:
thank you

thank you you saved me
[Redmi Note 8 Questions & Answers] Janelas:
I am trying my best to perform this action and i cant
[Redmi Note 8 Questions & Answers] Janelas:
All commands worked but stil stuck on fastboot
[Redmi Note 8 Questions & Answers] the_weird_aquarian:
sorry for the late reply...after vbmeta is successful, did you flash recovery.img?? if after flashing recovery it doesn't enter recovery mode, press vol up + power button then check.
[Xiaomi Poco F1 Questions & Answers] diamoc:
Hey guys i have an issue, i was running Pixel Experience 10 but on MIUI 10, i couldn't update the last one so i thought to get back to stock rom, update to miui 11 and then get back to my Pixel rom. I DID A BIG MISTAKE. I installed the Miui 11 Update through TWRP without restoring the stock miui 10 rom. It worked but i had lost my Pixel rom ( i have a backup), ok then i installed TWRP at the MIUI 11 because recovery mode got me at Xiaomi Recovery for some reason. Inside the TWRP i flashed Disabled forc Encryption, but it didnt flash the Magisk, i reboot to system and after 100 bootloops i tried to go back to recovery mode, it boot at TWRP but since then, the TOUCHSCREEN DOESN'T WORK.. I used xiaomi mi flash tool to return to stock rom, it did, locked the bootloader etc...the touchscreen still doesn't work though... I can connect a mouse with OTG Type-C and i can do anything you tell me in order to fix it.. i have already update to MIUI 11, unlock the bootloader, installed TWRP and have Root. Has anyone any idea or a solution to try? Thanks everyone in advance.
[Xiaomi Poco F1 Questions & Answers] chuckbartowski:
try flashing via fasboot "V10.2.3.0 - Global" - https://c.mi.com/thread-2549712-1-0.html . works for me .............. thanks to zyhpex https://xdaforums.com/poco-f1/help/touchscreen-stopped-twrp-t3979087
[Xiaomi Poco F1 Questions & Answers] dorfohm2:
Worked for me, thanks!
[General Topics] King46:
Can anyone tell me how do I rotate the screen when I am playing a video file.

I have copied them as widescreen and they played on my orbit 2 no problem but recently i tried to play a video but it will only play in portrait. Tried rotating screen but didnt change anything.

I dont understand why it would play before in landscape full screen but now only plays in portrait full screen

any ideas

thanks
[Android Q&A, Help & Troubleshooting] LGZACRO:
Hello, I have Blackview BV9800Pro with MT6771V/CT and Stock Android Pie and Magisk roots + Riru ckre and edXposed. I need TWRP so I could easily backup and restore system at any time. I test EdXposed and Magisk modules and it is PAIN to do factory reset if something fails cause this is my only smartphone. I tried different twrp already, but it didn't worked. Unofficial twrp contact form on website does not work (gives error). Can You help me guys, please? PLEASE!!
[Android Q&A, Help & Troubleshooting] tecs.ottawa:
this one works for me (at mega)

#!GWwXDKjC!vPERdlfIiP-hylz3R7SEcU105PGAP4oi0QC3FtNWsyU

from the hovatek forum (32580)

the only problem is that, like said on that forum, it won't decrypt the user partition. Someone on there says to use the Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip

to disable encryption, but another poster says that it disables the phone, no touch, no mouse, etc. I have the same issue. I'd like to be able to decrypt with TWRP or turn off encryption. Then ill be able to make backups of the user partition. Anyone have any ideas?
[Android Q&A, Help & Troubleshooting] alecxs:
that TWRP looks fine to me, the one who did this was expert. the display driver is hex patched against getbootmode in order to get touch screen working. some user reported that TWRP is asking for password, that indicates to me encryption is supported (/etc/recovery.fstab has entry for full-disk encryption with metadata partition). furthermore this TWRP build is signed with AVBv1 signature that mean it passes Verified Boot and is flashable even on locked bootloader

have you seen Method 3 for disabling dm-verity by disabling AVB with dummy vbmeta?

fastboot --disable-verity -disable-verification flash vbmeta vbmeta.img

also it seems like you can do it with Method 2 patching boot.img with Magisk Manager, the only discrepancy i recommend on step 4. to keep the checkbox for preserve force encryption enabled, then patch it manually in fstab against force encryption by changing the flag from forceencrypt= into encryptable=

if this device has fstab in boot.img then you can use Android.Image.Kitchen.v3.7-Win32.zip for unpack/repack boot.img and do the change in ramdisk/fstab.mt6771 with Notepad++

otherwise fstab is located /system_root/system/vendor/etc/fstab.mt6771 you can use adb pull in TWRP recovery, modify the file, and adb push it back

adb pull /vendor/etc/fstab.mt6771
adb push fstab.mt6771 /tmp
adb shell
cat /tmp/fstab.mt6771 > /vendor/etc/fstab.mt6771

or do it directly with sed

adb shell
sed -r ',s,(^/[^[:space:]]+[[:space:]]+/data[[:space:]]+[^[:space:]]+[[:space:]]+[^[:space:]]+[[:space:]]+[^[:space:]]*)force[def]+[cno]+r[befpty]{3}=([^[:space:]]+),\1encryptable=\2,' /vendor/etc/fstab.mt6771 > /tmp/fstab.mt6771
cat /tmp/fstab.mt6771 > /vendor/etc/fstab.mt6771

of course vendor must be mounted. cat is recommended to preserve file permissions

But, before modifying vendor, make sure AVB is disabled (flash empty vbmeta.img)
[Android Q&A, Help & Troubleshooting] tecs.ottawa:
I tried method 1:

it just stalled on the first splash screen when turned on.

for method 3:

i looked in the root and there's no vmbeta folder (vendor is the last one)

for method 2:

i tried it and it has the same issue as when i use the disabler, no touch. i made the boot img in magisk with the force encryption unchecked and the verity checked. i unpacked the boot img but there was no fstab in it. i found the one on the phone but it already had "encryptable=", here is the main section:

/dev/block/platform/bootdevice/by-name/system / ext4 ro wait,recoveryonly

/dev/block/platform/bootdevice/by-name/vendor /vendor ext4 ro wait,recoveryonly

/dev/block/platform/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,errors=panic wait,check,formattable,quota,resize,reservedsize=128m,=/dev/block/platform/bootdevice/by-name/metadata

/dev/block/platform/bootdevice/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,formattable

/dev/block/platform/bootdevice/by-name/protect1 /mnt/vendor/protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,formattable

/dev/block/platform/bootdevice/by-name/protect2 /mnt/vendor/protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,formattable

/dev/block/platform/bootdevice/by-name/nvdata /mnt/vendor/nvdata ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,formattable

/dev/block/platform/bootdevice/by-name/nvcfg /mnt/vendor/nvcfg ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,formattable

/dev/block/platform/bootdevice/by-name/apd /mnt/vendor/apd ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check,formattable

/devices/platform/externdevice* auto auto defaults voldmanaged=sdcard1:auto,encryptable=userdata

when i flashed back the magisk boot img that doesnt have the custom settings, it booted OK, but then twrp cant access the userdata again.
[Android Q&A, Help & Troubleshooting] alecxs:
please read more careful

method 2

force encryption checked and the verity unchecked

i can see your fstab is broken already, there is no forceencrypt= forcefdeorfbe= or encryptable= flag (it's gone) furthermore this is not the only file otherwise it wouldn't encrypt again

method 3

flashing vbmeta is required. please download dummy vbmeta and flash it from fastboot

in TWRP you can list partitions with

ls -d $(find /dev/block -name by-name)/*

don't flash magisk zip this will affect encryption. patch fstab manually in the respective line for /data in the flags in 5th column

/dev/block/platform/bootdevice/by-name/userdata /data ext4
noatime,nosuid,nodev,noauto_da_alloc,errors=panic
wait,check,formattable,quota,resize,reservedsize=128m,encryptable=/dev/block/platform/bootdevice/by-name/metadata

which fstab is it? maybe there is another one in nvdata? at least, it is the only explanation i have why device encryptes anyway..

i am not sure why TWRP does not work for you, please provide recovery.log

edit: btw i wonder why magisk only boot with dm-verity enabled.. are you sure you have unlocked bootloader?
[Android Q&A, Help & Troubleshooting] tecs.ottawa:
sorry about that, i was really tired. that is what i had. under advanced settings in magisk manager: preserve force encryption (checked), preserve AVB 2.0/dm-verity (unchecked), recovery mode (unchecked)

I just typed it wrong in my message :(

I didn't modify that fstab actually. So unless the disabler did it, that is the original one. I tried to unpack the vendor.img from the stock rom to see if that fstab is the same, but that image kitchen .bat threw an error.

i've added "encryptable" after "reservedsize=128m,". i then flashed the magisk boot.img and replaced the fstab using cat with the new one by copying it to /tmp/ and then running cat /tmp/fstab.mt6771 > /vendor/etc/fstab.mt6771

there is also an fstab in nvdata, that one says:

/dev/block/platform/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,errors=panic wait,check,formattable,quota,resize,reservedsize=128m,forcefdeorfbe=/dev/block/platform/bootdevice/by-name/metadata

i edited that one : replaced forcefdeorfbe with encryptable and replaced the file in the same way as the other.

after rebooting with the 2 fstab files with "encryptable" and the custom magisk boot.img (that had no touch before), it works!

i guess that second nvdata fstab was the one we needed to edit or the regular one had been broken somehow and fixing it was the thing. im guessing it was the nvdata one.

now the phone says its unencrypted and twrp can backup the userpartition.

thank you so much
[GiONEE Elife E7] ayhankiraz:
Hello. I own Gionee Elife E7. My phone does not react in any way. There is nothing in the devices section on the computer. I completely disassembled the phone. I removed the battery. There is no sign on the computer when I connect it with usb. The red light of the phone turns on for 30 seconds and then turns off. But it does not connect from usb. That's what happened after he said return the phone to factory settings. The phone never turns on. The computer never sees. What should I do? Please can you help?
[GiONEE Elife E7] ayhankiraz:
Do you know Elife E7 Test points pins? I have tried every possible pin but I could not succeed. If you have information, please write a message. (Note: I try EDL cable but nothing happened)
[GiONEE Elife E7] ayhankiraz:
PLease help me friends. What should I do?
[Thinkpad Tablet Android Development] drizzle123:
hero - thank you
[Thinkpad Tablet Android Development] jcthrower:
Can this be installed on my 8704v?
[Thinkpad Tablet Android Development] highwaystar_ru:
No, it is only for 8504, it has different SOC.

Update here

Fixed graphical issues

Fixed USB modem mode

Selinux now enforcing
[Thinkpad Tablet Android Development] jcthrower:
ok thanks for the response. Are you still planning on updating Lineage 16.1 for the 8704v?
[Thinkpad Tablet Android Development] BigBrother84:
Thank you so much for that rom, I'll be trying to flash it next week!

I have question - is there any possibility to get working stock Dolby atmos which is different from that one we can find in other threads

Or

You prefer Viper4android? ;)

Edit: does Netflix work fluently?
[Thinkpad Tablet Android Development] Lucinde:
Thanks a lot!

Installation went smooth, so far everything seems to be working.

Still need to set up the tab, but I'm glad I finally got rid of the Lenovo bloatware (like kidoz).

Does anybody know perhaps if it is possible to create restricted profiles in LineageOS? Not by default in this ROM, I'm now trying to figure out if it can be enabled.
[Thinkpad Tablet Android Development] highwaystar_ru:
Update:

2020-03-19

Fixed USB flash drives mounting connected by OTG
[Thinkpad Tablet Android Development] Lucinde:
If anyone else would have the same question: I found a workaround. You can create a new user via adb with the command "adb shell pm create-user --restricted <username>".

I didn't find a way to create the restricted profile from the settings menu, but once created, it can be managed via the menu.

In the meantime I installed some apps and so far, so good. From the limited time I worked with it, it seems to run smoother than with the stock ROM :good:
[Thinkpad Tablet Android Development] BigBrother84:
Previously problem with installing process and bricked now fixed using MI lash and successfully installed lineageos see post 18 and later :) how to install:

https://xdaforums.com/showpost.php?p=82142685&postcount=18

And 2088, in second twrp thread, for 100% working restoring stock system solution:

https://xdaforums.com/showpost.php?p=82095401&postcount=2088
[Thinkpad Tablet Android Development] BigBrother84:
Thank you :) [MENTION=9500349]Plant[/MENTION]

I have never been trying to restore using fastboot commands, only by twrp.

The problem is that both twrps aren't working good on my device. Every partition formating and updating, it stucks. Once time I decided to wait and after 2 h 13 min nothing happened. I tried to format data using fastboot

fastboot format data

but error occurred. It said that partition format is " " but twrp said it's ext4 maybe that's why they stuck.

In second twrp 3.2.3 thread, Strephon Alkhalikoi helped me and suggested using MiFlash. It worked and after 4 system updates and personalising I decided not to modify it anymore. The only explanation why it doesn't work may be my first stupid move in twrp - not to modify system - and forced shutdown. Rest should work...

Whole situation It is funny cause I "played" with 5 Sony phones flashing e.g. in two of them, android 9 where stock was 6. Everything was working fluently and fast.

Strange errors surprised me here but I'm really happy that you cared about my situation and try to help :good: thank you!
[Thinkpad Tablet Android Development] richardmc85:
Managed to install Lineage on my TB-8504F, but it doesnt get past the Lineage boot animation, no matter how long I leave it.

Pushed TWRP to Recovery, formatted as required. Had to amend the Lineage image to remove the device checks, as although I definately have TB-8504F, it didnt like that TWRP reported it as TB_8504f - ?

Installed and installed GAPPS, cant get past load screen.

I do have a backup, so not concerned, but frustrated!

Any help appreciated