yashsingh1/xdaforums huggingface dataset:
[Google Pixel 5a] nijel8:
Touchscreen wasn't working b/c A11 bootloader reports different bootreason value(guessing...) than A12(on what I test) and the script that loads the appropriate touchscreen drivers for the booted kernel got confused...

Fixed it... Now script reads booted kernel cmdline which has special twrp fastboot portion and should never load wrong drivers.
[Google Pixel 5a] lowridincrew,:
Waiting for a stable version but good job! Well appreciated.
[Google Pixel 5a] izaacze:
My pin worked on Android 11 when loading the twrp image, I was able to install the recovery and do the Direct install with magisk after loading my master_boot.img (magisk patched img from stock barbet).

I haven't done much else yet. But this looks good so far!
[Google Pixel 5a] MrPolite:
Hell ya! Installed while running Lineage and Magisk rooted! Thanks for this!
[Google Pixel 5a] nijel8:
Apart from A12 pin/password/pattern decryption which will take considerable time, this is stable version... or you mean official...
[Google Pixel 5a] nijel8:
Updated... Please redownload from OP

- fixed vibration haptics

- synced with latest TeamWin code

Do not flash twrp-3.6.0_11-0-barbet.img!!! Install it form its Advanced menu ones booted with fastboot...
[Google Pixel 5a] Slim2none4u:
This is awesome!

One question.

If it's for A12, why is it labled twrp-3.6.0_11-0-barbet.img?

I thought _11 indicated android version?

Shouldn't be twrp-3.6.0_12-0-barbet.img?
[Google Pixel 5a] nijel8:
11 indicates TWRP source code branch.
[Google Pixel 5a] TheSayaMan:
Android 12 stock is fine and Android 11 custom firmware fine as well. I'm using it right now on 11 LineageOS and works great.
[Google Pixel 5a] TheSayaMan:
That's because you didn't follow instructions. The post specifically says do not flash twrp, you boot it first then install it in recovery, advanced, and install current twrp there.
[Google Pixel 5a] nijel8:
That actually wasn't in OP yet, added it b/c of his post, so blame me... :)
[Google Pixel 5a] TheSayaMan:
LOL, sorry no hard feelings. My bad!!
[Google Pixel 5a] koreyb:
Do you have any reason to believe there are issues with 11 stock firmware or have you not tried?
[Google Pixel 5a] TheSayaMan:
No reason at all. I haven't tried it on stock 11. I'm using it with custom LineageOS. Update: This does not work with 11 stock. I tried it and there are mounting errors.
[Google Pixel 5a] rspkt:
Installed on LineageOS and I have to admit the touch response is extremely delayed and TWRP as a whole seems "bogged down" or slower to respond than usual. Not sure what the issue is there outside of maybe because it was installed over LineageOS recovery and not stock? Any ideas?

Also, @TheSayaMan how did you re-root after flashing TWRP. Did you patch the LineageOS recovery? Wouldn't that re-install the LineageOS recovery as well? Any info would be appreciated.
[Google Pixel 5a] nijel8:
Does this happens if fastbooted or installed or both?

Looks like vibrator service can't start on your device which causes touchscreen slow responsiveness or rather recovery waits for vibrator service on touch events and eventualy times out. I suppose you don't have the vibrator haptics working, do you?

The only reason I can think of is LineageOS kernel is missing or can't load vibrator related driver.

Boot to recovery, connect USB and run these commands in terminal or command prompt:

adb shell getprop vibrator.haptics.ready

adb shell ls -p1 /sys/class/leds/vibrator

and post the result.

Also logcat might help...
[Google Pixel 5a] TheSayaMan:
I changed magisk.apk to magisk.zip and flashed it in twrp to get root back. Patching is not necessary. Also I have been able to update lineage and keep twrp. This is what I do. I download the new lineage update and place it on my otg cable, you can keep it in your internal storage if you don't have a security lock pin/pattern etc. I use a OTG cable because I have a security pattern set and it won't encrypt internal storage. I also have the gapps on there as well and the twrp.img file. If you update through the built in updater on the phone it will overwrite twrp with lineageos recovery and you will have to boot twrp again in the bootloader. My way, you won't ever have to do that. So what you do next is reboot to twrp and go to install, select the lineage update file and flash it. It will automatically flash it in the opposite slot which is what you want it to do. When it's done, twrp will be overwritten but all you have to do is select install again, and choose install image and select your twrp.img file and install it as recovery ramdisk. This will get twrp back because it was overwritten with LineageOS recovery when you installed update. Now install gapps, it will install them on the current slot which is what you want. After it's done, reboot to system and wait for the update to complete. Then reboot to recovery and flash magisk.zip in recovery again to get rooted again. Reboot to system and your done. If you update this way, don't forget the part to install twrp.img as recovery ramdisk before rebooting the phone otherwise twrp will be gone and you will have to boot it in bootloader again.
[Google Pixel 5a] andybones:
You can actually just flash the Magisk.apk in TWRP now, no need to change to Magisk.zip
[Google Pixel 5a] bobpiesz:
I'm running 11(RD2A 211001.002) and have twrp/magisk successfully installed.

ONE issue however is in regards to haptic feedback.. If I have any vibrate settings enabled in twrp, the UI is delayed by ~5 seconds each touch/key press. With all haptic vibrate settings set to zero in twrp, it's perfectly fine.

To clarify, haptic vibrate feedback works perfectly fine when not in twrp
[Google Pixel 5a] TheSayaMan:
This twrp works best on Stock 12 or a Custom 11 ROM. I was having issues also along the lines of mounting issues in recovery so I went to a Custom 11 rom and don't have any problems at all.
[Google Pixel 5a] nijel8:
See my answer above...
[Google Pixel 5a] bobpiesz:
Here's my data duuuuuummppp:

Fastbooted ADB output:​

Terminal Log - Fastbooted - ADB Commands

​

**NOTES**

The Following ADB Command Provided Zero Output:

adb shell getprop vibrator.haptics.ready

Terminal Log - Fastbooted - ADB Commands

​

## WHEN FASTBOOTED:

> root in PIXEL/2022_TWRP/TWRP_IMG
✦ ❯ fastboot boot twrp-3.6.0_11-0-barbet.img

Sending 'boot.img' (98304 KB) OKAY [ 3.144s]
Booting (bootloader) boot.img missing cmdline or OS version
OKAY [ 2.269s]
Finished. Total time: 5.468s

> root in PIXEL/2022_TWRP/TWRP_IMG took 5s
✦ ❯ adb shell getprop vibrator.haptics.ready

> root in PIXEL/2022_TWRP/TWRP_IMG
✦ ❯ adb shell ls -p1 /sys/class/leds/vibrator

activate
brightness
device
duration
max_brightness
power/
state
subsystem
trigger
uevent

Flashed TWRP

Terminal Log - ADB Commands

​

Flashed TWRP ADB OUTPUT:

Terminal Log - ADB Commands​

**NOTES**

The Following ADB Command Provided Zero Output, same as when fastbooted:

adb shell getprop vibrator.haptics.ready

Flashed TWRP Recovery - ADB Commands​

## WHEN FASTBOOTED:
root in PIXEL/2022_TWRP/TWRP_IMG
✦ ❯ adb reboot recovery

root in PIXEL/2022_TWRP/TWRP_IMG
✦ ❯ adb shell getprop vibrator.haptics.ready

root in PIXEL/2022_TWRP/TWRP_IMG
✦ ❯ adb shell ls -p1 /sys/class/leds/vibrator
brightness
device
max_brightness
power/
subsystem
trigger
uevent

Various LOGs from logcat/dmesg/recovery are attached as well
[Google Pixel 5a] nijel8:
If you mount system after boot to flashed twrp does haptics start working?

Also does haptics work when twrp is fastbooted?

This is the reason for vibrator not working:

02-18 14:41:00.810 688 688 F linker : CANNOT LINK EXECUTABLE "/system/bin/android.hardware.vibrator-service.barbet": library "android.frameworks.sensorservice@1.0.so" not found: needed by /vendor/lib64/libsensorndkbridge.so in namespace (default)

but library "android.frameworks.sensorservice@1.0.so" is in /vendor/lib64 but linker can't find it on A11 booted twrp and I don't know why...
[Google Pixel 5a] bobpiesz:
Haptics does indeed work when fastbooting i.e.:

fastboot boot twrp-3.6.0_11-0-barbet.img

..but, even after mounting /system the linker error still persists

I can indeed confirm that /vendor/lib64/libsensorndkbridge.so exists when booted to flashed twrp
[Google Pixel 5a] bobpiesz:
But, when booted via the system, I can not see
[Google Pixel 5a] nijel8:
That's really weird...!?

android.frameworks.sensorservice@1.0.so can't just disappear from ramdisk when twrp is flashed...

No idea on a fix...

Just keep haptics disabled then.
[Google Pixel 5a] bobpiesz:
Sadly I think there is way more ot this bug..

Flashed TWRP will not save it's settings, so each time I load the flashed twrp recovery, it's as if I never used it before, and have to disable vibration settings. It's also having AVC issue as well...I can't really narrow it down :/
[Google Pixel 5a] nijel8:
I can't debug it since I am not running A11 but from your logs posted earlier it looks like twrp is using /data/media/TWRP folder for settings and backup and not /data/media/0/TWRP as it should if internal storage is decrypted... Is it decrypted? Looks like not... Do you see your files in /sdcard? Do you have pin/pattern/password setup in android?

Decryption issues explain twrp settings not saved. TWRP is pretty much useless if internal storage is encrypted....

AVC denials are just reported but not a problem since SELinux is permissive...
[Google Pixel 5a] eriklion:
I must say that this is annoying.

If I attempt to install Lineage it hoses a ton of partitions. Resulting in the need to reflash stock.

I thought I had a screenshot of it in TWRP after attempting the install, but it seems TWRP wont write to my storage(USB Flash).

after that the device is in an unbootable state. defaulting to bootloader.

What am I missing here.

fastboot boot twrp.img

install twrp from booted image, via advanced menu

either sideload or flash lineage rom zip by any means

Expect it to work and not break things like /vendor

Start over and reflash stock because something got broken.

logs soon if I can replicate it without much issue.

I'd almost speculate that it no longer works with Android 11/Lineage. It seems to work after installing lineage, booting it, then going back and applying the image via twrp advanced menu. Also inconsistently leaves me without touch. Not just a delay, but touch, just not working. and yes, vibrator issue, disabling vibration fixes the delay. copying boot_b to boot_a also fixed all of the issues.

Seems to work with Lineage Recovery, no issue.

I'm stuck.
[Google Pixel 5a] bobpiesz:
Migrated to android 12, and that solved many issues.. Is there any eta from teamwin for android 12 decrypt? If I remove pass codes, I can no longer use finger prints to login :/
[Google Pixel 5a] TheSayaMan:
Never ask for eta's. It's against xda rules
[Google Pixel 5a] Zackptg5:
@nijel8 Thanks for this, saved me from a clean flash :)
[Google Pixel 5a] pawlik79:
Can I install Magisk with TWRP to avoid patching boot.img?
[Google Pixel 5a] jimmy16:
Yes you can, the best way is to adb sideload the apk or zip of magisk
[Google Pixel 5a] TheSayaMan:
You can also install it directly from TWRP with a OTG cable with the magisk file on it or by installing it from internal storage of your phone only if you don't have a security, pattern, pin, password set.
[Google Pixel 5a] nohermosa@gmail.com:
@nijel8 Awesome work! Thanks... works great for me!
[Google Pixel 5a] thx1200:
I used it on A11 before upgrading to A12 (Lineage 18.1 to 19) and it worked great. I didn't flash it, I just booted it to run Nandroid.
[Google Pixel 5a] Veraster:
Is there a version of TWRP that works on android 12? This one doesn't work on 12 (it runs but after installing itself, the system and recovery screen don't work). The latest TWRP on twrp.me doesn't work on 12 (freezes on splash screen). Every rom needs firmware 12 to install. It's a catch 22.
[Google Pixel 5a] TheSayaMan:
It works with custom roms, not stock firmware which I assume your using because I have my own ROMs for LineageOS and Pixel Experience and it works fine.
[Google Pixel 5a] Veraster:
What are the actual steps to install one of these custom roms? So far I have tried several different orders of operations to get lineage os installed including:

flash official firmware

fastboot boot twrp

flash rom file

reboot (doesn't boot)

try fastboot boot twrp again. Doesn't work, dead end. The only way to get anywhere at this point is to flash official firmware again.

and

flash official firmware

fastboot boot twrp

flash rom file

flash twrp in advanced options before rebooting. doesn't work, spits out red errors, system doesn't boot. Can't fastboot boot twrp without flashing official firmware, so dead end.

and

flash official firmware

fastboot boot twrp

wipe everything. I no longer have access to sd card

format everything. Still no access to sd card

system no longer boots. Can't flash anything because no sd card

I can still fastboot boot twrp but no sequence of options, data wiping or formatting gets me access to sdcard again.

dead end

and

flash official firmware

fastboot boot twrp

flash twrp in advanced options

try to flash rom (I can't because no sd card or memory access)

try every combination of formatting and data wiping. Nothing regains access to sdcard.

dead end

I have not been successful getting Lineage OS 19 or AICP 16.1 to boot or even flash without spitting out red errors. I am absolutely stumped here. I guess I could try pixel experience and AICP 17 just because I haven't tried those yet..
[Google Pixel 5a] TheSayaMan:
Try factory resetting in the bootloader instead.

fastboot -w

I haven't had a issue with that at all. Also this twrp is unable to decrypt so if you have a password, pin, screen lock set then twrp will be unable to do a proper wipe so you have two options, either remove your security lock then factory reset in twrp after that or you can keep locks but you have to fastboot -w in bootloader instead to do a proper wipe then install rom.
[Google Pixel 5a] Veraster:
I was able to get Lineage OS working by using fastboot to flash the lineage os recovery to vendor_boot, then flashing lineage os and gapps through there. However I can't flash twrp without borking the lineage os installation. Flashing twrp then flashing lineage os again does make lineage os boot but twrp gets replaced.

How are you getting lineage os working through twrp? Are you using firmware 12 and lineage os 19? Do you have magisk functionality at all?

I can rename the magiskapk to magisk.zip and flash it throught the lineage os recovery and that actually works. However it owuld be nice to have twrp for backup and restore.
[Google Pixel 5a] TheSayaMan:
Boot twrp first then sideload ROM and gapps. Reboot to system. Put the twrp.img file on your phone. Do not use a security lock. Reboot to bootloader and boot twrp again. After that, go to install, and select image file and select your twrp.img file that you put on your phone earlier, select install as recovery ramdisk. That will permanently install twrp. Now reboot to system then reboot back to recovery and it will go to twrp. Click install, select your magisk.apk file on your phone and swipe to flash it. Then reboot to system. You now have permanent twrp, and magisk with root. When their is a update though, you can't update through the built in updater on the phone or twrp will be gone. All you have to do is download the update file from the LineageOS site, and transfer it to your phone. Reboot to recovery, select install, then select the new update file and flash it then flash gapps again. Now twrp will be replaced by LineageOS recovery so before you reboot your phone you need to select install again, image and select your twrp.img file again and install it again as recovery ramdisk. Reboot to system, you will be unrooted but simply reboot to twrp and flash magisk as before and you will have twrp, and magisk. Just make sure you don't miss the step about reinstalling twrp in recovery ramdisk, that's why your losing twrp. Here's a link to my ROM if it will help you any further. https://xdaforums.com/t/lineageos-rom-for-pixel-5a-android-12-july-12-2022.4456655/
[Google Pixel 5a] Veraster:
That was the very thing that finally made it work. The trick was to not flash twrp from from from the "advanced" menu of twrp but from the manual flash menu where you install roms and stuff. Selecting the twrp image then flashing it to ramdisk is what made it work.

Thanks a lot for your help!
[Google Pixel 5a] TheSayaMan:
No problem, anytime.
[Google Pixel 5a] rchris494:
really there is no need to flash twrp anymore. i usually just boot it by fastboot boot twrp.img. custom roms are not what they use to be. real custom roms. Project Treble & google ruined that. you only need advanced ==> sideload in twrp. every rom now a days seems to be based off android open source project and include their own generic custom recovery. so you only need to do a factory wipe in the stock recovery or fastboot -w in bootloader mode. just make sure you remove security pins, face locks, swipe locks first. TheSayaMan builds of pe or lineage include the recovery in the zip. so you only need to factory reset and then boot twrp to sideload. it installs everything else needed to work. the generic custom recovery it includes has a sideload mode that you can use to flash OTAs and/or magisk. making twrp more or less not needed. beyond the initial install.or if you want to make a nand backup.
[Google Pixel 5a] TheSayaMan:
I totally agree with you but he wanted to keep twrp permanently so I helped him with it. I don't have it permanently.
[Google Pixel 5a] emonkhan826:
Can i use this TWRP recovery for july security update android 12L? It's work on that?
[Google Pixel 5a] lilovirus:
Not able to flash GApps using this twrp,

get an error message saying insufficient space.

Any help will be helpful and appreciated.

Error is similar to this one

Open GApps for Android 11 installation fails claiming "Insufficient storage space" · Issue #930 · opengapps/opengapps

If Open GApps installation fails: Is the issue reproducible using the latest version of your recovery? Is the issue reproducible with (the latest) TWRP recovery?::: TWRP 3.5.x is not available for ...

github.com
[Google Pixel 5a] emonkhan826:
This recovery support android 13? 🙄
[Google Pixel 5a] andy356:
Hi, has this situation improved any? I would like to keep encryption enabled.
[Google Pixel 5a] rspkt:
Some good news on the TWRP front: https://twrp.me/site/update/2022/10/10/3.7.0-released.html
[Google Pixel 5a] pawlik79:
I don't see listed Pixel 5a on supported devices.
[Google Pixel 5a] rspkt:
It's not but hopefully this official release helps development for our device. Either way it is good news for the TWRP community and fans of it like us.
[Google Pixel 5a] rchris494:
we would need @nijel8 to rebuild the twrp based off the new build for a new twrp to hopefully be more compatible with A12 and possibly A13
[Google Pixel 5a] TheSayaMan:
That new version of twrp and even the previous version was out and device wasn't available. Don't get your hopes up.
[Google Pixel 5a] andy356:
> MTP error handling for FFS devices - nijel8

Since our dev is actively contributing to TWRP, I don't think we have to worry about lack of effort on their part.

> Android 12 Encryption Support - bigbiff

There we go. :D
[Google Pixel 5a] london629:
so followed directions to flash from inside itself when rebooting got error "failed to load/verify boot images".
[Google Pixel 5a] bobpiesz:
Just an FYI...

This build works by booting it (Not gonna try flashing it) via fastboot on Android 13.0.0 (TQ1A.230105.001, Jan 2023)...I tried as a last ditch effort to get in to the system data after an update caused a bootloop by booting it, and worked like a charm.
[Google Pixel 5a] mikhailkurakhtanov:
Hello guys! Before custom ROM installation I flashed TWRP, but after adb sideload mode TWRP was replaced to lineage recovery. Any ideas? 0_o

upd. - can't delete this post, the problem was solved.
[Google Pixel 5a] andy356:
@nijel8 Do you still use this device?
[Google Pixel 5a] mdcghost:
My device booted the recovery once but wasn't working correctly, I think I bricked my device can't get passed the Google logo 😩
[Google Pixel 5a] mdcghost:
Actually I lied I think what's ever rom you installed came with a recovery that it might recommend to use I think
[Google Pixel 5a] Mous3kteer:
Hey y'all, my phone finally hit one of the Black Screen of Death motherboard bugs that 5a's seem to be susceptible to, which means I'm working with a black, unresponsive screen. I'm trying to see if I can get any of my data off it before sending it in for repairs. I've tried running fastboot boot with this image, and it does boot properly. However, twrp decrypt doesn't seem to work, giving a "Failed to decrypt data" message. Should I take it that decrypting doesn't work with this image in Android 13? Or is there a possibility I'm doing something wrong?

ps. If anyone has any other reccomendations for how to get files off a device without a display, that would be much appreciated too!
[Google Pixel 5a] V0latyle:
I don't think TWRP is going to help you recover your data.

Try sideloading the OTA using the stock recovery.
[Google Pixel 5a] Mous3kteer:
I'm not sure how sideloading an OTA would help in my case? I think it's a hardware problem, not a software one. I get a black screen on system, bootloader, and recovery, and I don't think any amount of flashing will fix that. It even boots fine (holding the power button from the lock screen gives the haptic feedback for the power menu), so I would be pulling the data through adb if it would authorize without inputting the unlock pattern. I was just hoping twrp would be able to do the decryption since (afaict) adb is always authorized through recovery.
[Google Pixel 5a] V0latyle:
How do you know TWRP is booting?

Are you saying the screen does not work at all?
[Google Pixel 5a] Mous3kteer:
Correct, the screen does not function whatsoever. I know TWRP is booting because adb recognizes the device in recovery mode and the twrp command functions in an adb shell. But trying to use the command twrp decrypt [pattern code] fails, even though I'm sure I'm using the correct pattern.
[Google Pixel 5a] Kerrylee1738$$$:
only android 12 right?
[Google Pixel 5a] pawlik79:
I'm on Android 14 and side loading monthly updates with it
[Google Pixel 5a] Kerrylee1738$$$:
Nice... hopefully no issues with the Rom crdroid (android 14) I'm using at the moment
[Google Pixel 5a] Kerrylee1738$$$:
It stayed for a little bit but lost it once I rebooted
[Google Pixel 5a] Kerrylee1738$$$:
Pretty sure once I installed magisk it replaced it with the original recovery I previously had which was crdroid
[Google Pixel 5a] pawlik79:
Yes it does that too since is just temporary loaded and not installed.
[Google Pixel 5a] pawlik79:
Yes cdroid rom has it's own recovery.
[Samsung Galaxy Tab A series Questions & Answers] aslan4789:
Hello, the tablet was distributed by the school. Is there a way to cancel the automatic configuration provided by Know?
[Samsung Galaxy A51 Questions & Answers] Ryu945:
Where is a safe location I can download the original firmware for SM-A515F . This is the non 5G model.
[Samsung Galaxy A51 Questions & Answers] SubwayChamp:
In my experience these are two reliable tools to find out and download firmware for Samsung devices https://xdaforums.com/t/tool-frija-samsung-firmware-downloader-checker.3910594/ and https://samfirmtool.com/samfirm-v0-5-0