yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A51 ROMs, Kernels, Recoveries, & Ot] Ibnu pramudya:
Can i get a confirmation of yours if this method works for EUD7 firmware too? Cuz my phone is already EUD7 too. Or i have to change it to DUB1 to use this method?
[Samsung Galaxy A51 ROMs, Kernels, Recoveries, & Ot] m0000:
im on EUD7 and method is working.
[Samsung Galaxy A51 ROMs, Kernels, Recoveries, & Ot] NotleoJ:
my phone just doesn't start twrp, it goes to a black screen and doesn't start twrp, i've tried downgrade to install the old twrp versions and i couldn't. do you have anything in mind of what it might be?

sorry if there is any typo, i'm for the translator
[Samsung Galaxy A51 ROMs, Kernels, Recoveries, & Ot] detrol2k:
Hello! I keep getting the "Only official released binaries" error when trying to flash TWRP in ODIN. I followed the guide and disabled everything step by step, Running at android 11 latest patch.
[Samsung Galaxy A51 ROMs, Kernels, Recoveries, & Ot] sonnenfinder:
Can confirm this on A515F DSN, EUD7, security patch 01.05.2021.

Everthing works as expected. Thank you.
[Samsung Galaxy A51 ROMs, Kernels, Recoveries, & Ot] Gapue:
I TOOK HIGH RISK WITH EUD7 AND IT WORKED!!!!!!!!!! THANKYOU.... IT SEEMS LIKE IT WORKS WITH ALL MODELS ABOVE DUB1
[Samsung Galaxy A51 ROMs, Kernels, Recoveries, & Ot] Gapue:
YEA.. I ROOTED MY EUD7 TODAY , AND IT WORKED PERFECTCTLY
[Samsung Galaxy A51 ROMs, Kernels, Recoveries, & Ot] Jeppa_1:
Is it still compatible with EUI4 ?
[Samsung Galaxy A51 ROMs, Kernels, Recoveries, & Ot] Vanht4:
Как откатить прошивку с загрузчиком U5 до прошивки с загрузчиком U4 (Android 11)

Translated by GT: How to downgrade firmware with U5 bootloader to firmware with U4 bootloader (Android 11)
[Samsung Galaxy A51 ROMs, Kernels, Recoveries, & Ot] roman313:
Никак. Андроид 11 есть и с 5-м ззагрузчиком. К примеру, андроид 11 от декабря 2021 г.

Translated by GT: No way. Android 11 is also available with the 5th bootloader. For example, Android 11 from December 2021.
[Samsung Galaxy A51 ROMs, Kernels, Recoveries, & Ot] Marinada:
Hey, I've got a problem, i was doing it exactly by the guide buut my phone got into twrp bootloop and i can't get out of it. Can you help?
[Samsung Galaxy A51 ROMs, Kernels, Recoveries, & Ot] R.A.D.E.P.A:
Hi i installed the twrp and do step 6 but when the twrp appears it begin to blinking over and over and nothing happens but this.

In addition my phone is A515F and running android 12 oneui 4.0

I didn't find TWRP for Android 12

Please do sth about it and help me out 🥺
[Samsung Galaxy A51 ROMs, Kernels, Recoveries, & Ot] Jeppa_1:
You could also try this version: https://xdaforums.com/t/recovery-unofficial-teamwin-recovery-project-v3-6-2-android-11-12.4400869/
[Samsung Galaxy A51 ROMs, Kernels, Recoveries, & Ot] R.A.D.E.P.A:
It works!!! But when i install latest version of magisk,phone getting reboot rapidly and when install V21 it start up without getting root!

Any advice?
[Samsung Galaxy A51 ROMs, Kernels, Recoveries, & Ot] Jeppa_1:
I had bootloops with latest magisk, too.

Try 24.3 version...
[Samsung Galaxy A51 ROMs, Kernels, Recoveries, & Ot] R.A.D.E.P.A:
Thanks worked. I want to install Xposed framework too can you help me about it?
[Samsung Galaxy A51 ROMs, Kernels, Recoveries, & Ot] Jeppa_1:
Even thow it is "off-topic" again, you could use LSPosed... ;)
[Samsung Galaxy A51 ROMs, Kernels, Recoveries, & Ot] R.A.D.E.P.A:
Thanks i did it already but the app said Xposed framework is not installed
[Samsung Galaxy A51 ROMs, Kernels, Recoveries, & Ot] HuuTan:
I have successfully rooted my A51 Android 11 device, but I do not have TWRP installed. If I do install twrp now just flashing the recovery file???
[Samsung Galaxy A51 ROMs, Kernels, Recoveries, & Ot] helpinghand200:
but is there android 13 twrp for a51?
[Samsung Galaxy A51 ROMs, Kernels, Recoveries, & Ot] goldyit:
i tried this and when the twrp logo appear its just restart over and over again someone help pls
[Samsung Galaxy A51 ROMs, Kernels, Recoveries, & Ot] e347bgb:
Hi all. I just tried this and now stuck in a boot loop with this image. Every time I reboot, it just goes into this image. Flashes to a black screen for 1 second every 5 seconds. Is the phone bricked? Is there anything I can do to sort it out? Thanks.
[Samsung Galaxy A51 ROMs, Kernels, Recoveries, & Ot] mx1212:
Thank you very much for your efforts Please introduce another one for a51 one ui 5.1 android 13
[Samsung Galaxy A51 ROMs, Kernels, Recoveries, & Ot] calypsouh:
my phone is stuck in a bootloop
[Samsung Galaxy A51 ROMs, Kernels, Recoveries, & Ot] HBRyzen:
Is that works?
[Samsung Galaxy A51 ROMs, Kernels, Recoveries, & Ot] eula1977:
Hi everyone my A51 shows the same picture as above. It's stuck in a boot loop. It just shows the picture of Teamwin recovery and restarts again. Had to flash it completely. Reinstalled it. Does anyone have root instructions for 2023 and Android 13? A515FXXU6HWC7
[Samsung Galaxy A51 ROMs, Kernels, Recoveries, & Ot] veekay:
Following in case something is released for A13.
[Samsung Galaxy A51 ROMs, Kernels, Recoveries, & Ot] Dingodile_13:
Good evening everyone, after installing MAGISK the phone goes into bootloop, can you help me? Thank you
[Samsung Galaxy A51 ROMs, Kernels, Recoveries, & Ot] piote:
Hi,

mine same as yours.

Have you eventually found a workaround to this issue?

Thnx.
[Samsung Galaxy A51 ROMs, Kernels, Recoveries, & Ot] eula1977:
Sorry, No! I havent found a fix!
[Oculus Quest] dwkindig:
I was just tooling around in my new Quest 2 and, while my level of technical expertise is sufficient to be dangerous, I don't have any real idea what I'm doing as far as rooting, bootloader mods, etc. However, I seem to have stumbled into the regular Android settings after an app I was trying asked for usage permissions, which it seems Oculus doesn't expect any of its bespoke apps to do.

The Android settings behave oddly, though, but more like there's some kind of watcher app that's preventing access to most of these non-Oculus options. Case-in-point, the app that wants usage access, when I enter the Usage permissions screen and select the app from the menu to be taken to the screen where it displays what the app will do with usage permissions and presents the toggle for it, the screen comes up only briefly before the settings dialogue disappears entirely with an error saying that "System has stopped responding". I'm pretty sure if I were fast enough, I could probably toggle it in time, but I could also try to grant those perms via adb (which I only now remembered I could do and thus haven't done yet).

I also found and enabled the actual Developer Options, not the basic one Oculus gives us if we sign up as a developer organization. I am certain that they have actually been enabled: Even though the "{ } Developer Options" menu item keeps reloading the page that its on, settings that you'd expect to find within now turn up in the settings search dialogue.

One of these options is to enable OEM bootloader unlock. Selecting that options from the search results screen (or any other search result you'd find within Developer Options) however does like before, drops you at the menu page with the "{ } Developer Options" option.

It would be absurd if it were to be as simple as enabling that option to gain access to the bootloader and do whatever, even moreso if it was me that first wrote about it -- but, since I'm under the impression that the settings aren't actually broken so much as they are being suppressed, is there a way to toggle these various developer options, including the OEM bootloader unlock, via adb?

(Another point in favor of suppression rather than breakage, the Oculus refuses to take a screenshot of anything I'm doing with a message stating that the device is forbidden from doing so, although in less nefarious language.)

tl;dr -- how might I go about programatically toggling developer options on the device to find out what happens? More broadly, what's a good place to start being more dangerous vis-à-vis my Android technical expertise? I find its structure in every way baffling and nightmarish.

And then just for kicks, there's some oddities, like how the machine name in adb shell comes back as "hollywood" (which I found a bit Baader–Meinhof-y, since I was watching a bunch of Modern Vintage Gamer vids including his one on the Wii and its "Hollywood"-benamed graphics coprocessor). Also, fastboot oem unlock returns a curious error directing the user to visit https://oculus.com/unlock, which doesn't exist, and as far as the Wayback Machine is concerned, has basically never existed.
[Oculus Quest] dustojnikhummer:
This settings menu is (or at least it was) fully accessible on my Quest 1 last time I tried it. There does not seem to be an entry point on Quest 2 though.
[Oculus Quest] rickthecabbie:
I am currently enjoying the "Bugjaeger" app from the play store. That is a good ADB solution for the Quest 2. Have fun.
[Oculus Quest] suckerberggth:
Could you please elaborate? Link to any guides or anything?
[Oculus Quest] Honestly Annoying:
Would you mind explaining how you got the settings page to open on the Quest 2? I am an OG root dev and just picked up a Quest 2 myself, would love to crack into this.
[Oculus Quest] dwkindig:
Oh, dang, yeah, sorry things have been mad hectic and I didn't see these responses. I'll provide a write-up tomorrow, ping me again if I don't reply later cause I'm a forgetful idiot.
[Oculus Quest] Honestly Annoying:
All good, I actually figured out how to launch the settings page from this command:

adb shell am start -a android.intent.action.VIEW -d com.oculus.tv -e uri com.android.settings/.DevelopmentSettings com.oculus.vrshell/.MainActivity

Everything works in this page, except for launching the Developer settings option. This crashes the app as you mentioned, even though I can see the OEM Unlock option in the settings search bar.
[Oculus Quest] Honestly Annoying:
This repo is also very helpful, I am getting told to visit the same non-existent page you were as well when running fastboot oem unlock.

GitHub - QuestEscape/research: Sharing our security research on the Oculus Quest

Sharing our security research on the Oculus Quest. Contribute to QuestEscape/research development by creating an account on GitHub.

github.com
[Oculus Quest] dwkindig:
Oh, cool, I spent some time myself looking for a similar command, but I don't know much about the inner workings of Android. Do you know if there's a way to programmatically toggle the OEM Unlock switch?

I'll still post my circuitous method of getting there tonight (US/Central), maybe it will be enlightening in some way. I can't take screenshots or video of the process, cause the security policy configured by Facebook disallows it in those places.
[Oculus Quest] dwkindig:
Okay, things are a bit different since when I first posted -- I can grant packages usage access without crashing back to Android settings (`com.android.settings`). However, I can launch Android settings directly using App Manager (https://muntashirakon.github.io/AppManager/). Still can't screengrab, though, and still can't access the Developer Options, can only search for them. Interestingly, the breadcrumbs in the search results refer to the uppermost level as `null`.
[Oculus Quest] LucasNapik:
So i connected my Quest 2 to Android studio and used the debug and the log tool to see why the settings app crashes when trying to enter the developer settings. I got the exception and maybe i can paste it in here when i get home. Also i managed to sign out of my Facebook account and remove the oculus system administrator but that made the headset useless. I also created an app for the oculus that search for all the installed packages and when you click on one of them it's trying to launch the package in vr shell and found some interesting things such as a oculus assistant and a battery charging mode setting.
[Oculus Quest] misakayuuki:
maybe the page does exist, but you don't have the authority to visit it, so oculus redirect you to somewhere else
[Oculus Quest] raeumler:
maybe its not helpfull, but when you start wireless wifi on the Q via a wired adb host , you can install the app 'remote adb shell' (blue cast icon, pstore) on the quest and connect to localhost. so you have an on device adb shell for pm commands. it has to be this remote app because of lack on adb shell command without magiskmodule (termux crashes to the tv channel). i dont know how the activitys are called in android so maybe you got luck. also are the developer options part of the settings.apk? i think they pulled it out like that so why not making a new settings.apk where the devops are available? on this way there is sure an option to have a lock on the wifi adb too so it doesnt shutdown anytime you reactivate. edit: seems that with the new multitasking feature, its possible to hold up a wifi connection even the hmd was locked, just run the remote shell, connect and dont close it. you can connect via pc too without need to use adb tcpip again. before i setup adb tcpip via ' setprop service.adb.tcp.port 5555 ' again on the remote shell app. i now let it locked, and look how long it can holdup the wifidebug without reactivating via cable.
[Oculus Quest] raeumler:
.

if someone knows a working terminal for the quest (the original crashes the keyboard after a while). to replace the remote adb shell app, we could use an adb binary that holds up the wifi with adb shell to localhost (shell commands), while another terminal (local, pc or smartphone) can connect through the adb binary over wifi to localhost/quest-ip (for adb commands). but setting up an adb server (not the service) via adb binary and on-device terminal (even via adb shell) is not possible without root (but the remote adb shell app starts one or does it somelike different without root and on-device). when we know how we could put that logic together in a script or apk then). but anyways:

so its setted up now on my quest for holding up debug over wifi (sideload connection) and have an ondevice shell. it runs minimum 23 hours without needing to activate it via cable (adb device to check connection)

1. download/sideload remote adb shell app

2. connect quest2 to a host via usb

3. open cmd on host: adb tcpip 5555

4. disconnect usb

5. start remote adb shell on the quest and type quest-ip:5555 OR localhost:5555 and click connect

6. type in remote adb shell: setprop service.adb.tcp.port 5555

7. minimze the remote adb shell app and let it run

(8). to disable wifidebug: setprop service.adb.tcp.port -1

now there is no need for reactivating until reboot. if you want to run a command go to -> apps -> unknown sources -> open remote app (as there is no recent button).

you can connect to any adb host via wifi (local, pc, smartphone) even after lock or a matter of time (min 23 hours)

the remote adb shell app:

Remote ADB Shell – Apps bei Google Play

Eine Verbindung mit ADB auf einem anderen Android-Gerät läuft über das Netzwerk

play.google.com

with terminal shortcut app you can make settings-scripts then and run them via iconlist for textureresolution and gpu level or whatever ....

ps: maybe im in the wrong subforum now. should i make a thread?

pps: the app 'autostart and stay' adds an autostart option to the quest, which allows to run a launcher before original launcher comes up. (buggy)

ppps: the app SSH Server can set up a SFTP connection for wireless filetransfers

edit: could be that it just work to the first whyeverdisconnect then the quests tracking is beside and you have to reboot
[Oculus Quest] espionage724:
This still works today! I have a Quest 2 running V35, and recently un-linked my Facebook and Oculus accounts. After finally getting my Quest 2 back up (still needed to use the old Oculus apk from an Android device and Quest 1 device selection), the timezone was off, so I used the above adb shell command to access settings, and changed the timezone fine.

I also changed the Device Name, although I'm unsure what ramifications that might cause later.

Edit: Don't change your Oculus account password after doing the FB account bypass. You'll break the log-in session, and have to factory-reset and start over.
[Oculus Quest] raeumler:
you can have more settings when you use SetEdit (Settings Database Editor) from pstore. some props are editable, some need root.
[Oculus Quest] BlankEvery:
I wonder if you could use something like a rubber ducky to gain a temp root and have it scripted out to run all your commands after opening a terminal with root privilege like you would on a PC.....just a thought
[Oculus Quest] Wolf_Link115:
I found out in the v47 PTC update, you can actually access developers options through the android settings menu. I decided to try it again for legit no reason and I was surprised. Oddly it seems that the OEM Unlocking option is enabled by default for some reason, which is kinda strange. Might backup my headset and attempt to unlock it when I get home.
[Oculus Quest] dwkindig:
I haven't turned mine on since the last time I posted. (Life happened, long story.) Wanted to keep my revision number low in case anyone figured something out. Definitely let us know if you manage to unlock it; I'll sideload that update and see if it works on mine also.
[Oculus Quest] Wolf_Link115:
Will do, remember the update is a PTC update, meaning it is a Public Test Build. I dunno exactly if people are able to find it online and sideload it but if that is possible then you might be able to install it without issues, dunno how Meta works with those builds tbh. The way you get PTC access is through the Meta app on your phone, go to Menu at the bottom right, your Quest 2, Headset Settings, Advanced Settings, and assuming there are still slots available, enable Public Test Channel.
[Oculus Quest] Wolf_Link115:
Quick update!! I noticed I made a slight typo, I meant to say v57 PTC update! I relooked at my Quest 2 version and then looked at what I wrote because for some reason that didn't sound correct. My apologies!!
[Oculus Quest] jaybird_90:
Hi! I have been following this thread and I was wondering if anyone has had success with the oem unlock since the update. I also found that it was unlocked by default, but when I try to use fastboot I get the error FAILED (remote: 'Unable to open fastboot HAL')
[Oculus Quest] Wolf_Link115:
Were you in fastbootd or normal bootloader fastboot? You need to be in the normal fastboot mode. I still have yet to try it because I don't really want to lose anything and at the moment I use my headset more than my phone.
[Oculus Quest] jaybird_90:
Hey! Thanks for replying. I was in fastbootd...do you know how to reach regular fastboot?

I don't use the headset for too much, I am willing to try anything!

if normal bootloader fastboot is the screen with a few options and "start", then yes I tried that, but i received the message sending me to https://www.oculus.com/unlock. Maybe Meta unlocked the OEM by default but has some sort of wrapper to keep people from using fastboot?
[Oculus Quest] Wolf_Link115:
Seems like that would be the case :/

Knowing that though, I wonder if someone could make a generator using some key or something? That website doesn't actually exist though it used to at some point. Archive.org sadly doesn't help though. If this is the case that would explain how the Oculus Go works then since it was bootloader unlocked through a software update.
[Oculus Quest] jaybird_90:
Hmm...if we can come up with ideas ill happily try out anything. Where would an android developer put a catch to send the oculus.com/unlock error message? Maybe we can start there
[Samsung Galaxy Tab A series Questions & Answers] Lestat5721:
Flashed twrp 3.3.1-1 with Odin. Flashed successfully after literal hours of failure and multiple reflashes of the original ROM. After successful flash, it only boots to the TWRP splash screen. Doesn't progress any further, no matter how long. I can hold the power and volume down buttons, and it'll restart the tablet, but will only reboot into the twrp screen. Wtf can I do now? Wait until it dies, charge it for a bit, and reflash the stock ROM?

Bootloader is unlocked

OEM is unlocked

USB enabled
[Samsung Galaxy Tab A series Questions & Answers] Shrijon:
Maybe wipe cache and retry
[Samsung Galaxy Tab A series Questions & Answers] Lestat5721:
I can't. My PC doesn't recognize it as a device, because it is stuck on that splash screen. Literally the only thing I can do is hold the power+volume down buttons and restart it, but no matter what else I do, it always launches back into the splash screen.
[Samsung Galaxy Tab A series Questions & Answers] rw_on_xda:
here:

https://xdaforums.com/t/rom-sm-t510-unofficial-lineageos-17-1-for-galaxy-tab-a-10-1-2019.4060153/

under the part named "From OEM stock firmware:" is a link names "Unlock bootloader".

cklick on it and read the whole page from comment #1, esp. what is written under section "Buttons" downwards

you'll find the right things need to be done
[Samsung Galaxy Tab A series Questions & Answers] Lestat5721:
So I let it die, and was able to boot back into the Downloader and reflash the Samsung ROM, so it's like it never happened. Still, it's not rooted, and I'm at my wits end.
[Samsung Galaxy Tab A series Questions & Answers] Lestat5721:
Like I said before, my bootloader was unlocked. I even did the little "change the date" hack to get the OEM toggle to appear. The bootloader was definitely unlocked, and still is.
[Samsung Galaxy Tab A series Questions & Answers] Shrijon:
if u want root then install magisk and youre good to go...

if recovery is corrupted then flash it from megadenz's post
[Samsung Galaxy Tab A series Questions & Answers] Lestat5721:
Okay, how? Everywhere I look online, they say to install TWRP first. Is there a way to keep the OEM ROM, and install Magisk?
[Samsung Galaxy Tab A series Questions & Answers] lewmur:
First of all, you have to have the right version of the stock ROM installed. To do what I suggest, you need the BTH4 or BTFN version. Then install the Nexus ROM found here. It includes TWRP . Boot to TWRP and FORMAT the data partition. Notice, that is FORMAT, NOT wipe. Then flash the ROM again to get the correct data partition with gapps. Then flash Magisk to get root.
[Asus Zenfone 5 (2018, ZE620KL) ROMs, Kernels, Reco] roman313:
Where is Gapps ?
[Asus Zenfone 5 (2018, ZE620KL) ROMs, Kernels, Reco] Kaduczi:
This rom working ?
[Asus Zenfone 5 (2018, ZE620KL) ROMs, Kernels, Reco] henricaodopao:
sure lol
[Asus Zenfone 5 (2018, ZE620KL) ROMs, Kernels, Reco] fernando_s97:
Fingerprint is not working for me
[Asus Zenfone 5 (2018, ZE620KL) ROMs, Kernels, Reco] henricaodopao:
download custom firmware that is under the rom link mount vendor in twrp and flash
[Asus Zenfone 5 (2018, ZE620KL) ROMs, Kernels, Reco] fernando_s97:
After I install the Android 10 beta from asus and flashing the dotOS again, it started working
[Asus Zenfone 5 (2018, ZE620KL) ROMs, Kernels, Reco] henricaodopao:
this the alternative way to fix it actually
[Asus Zenfone 5 (2018, ZE620KL) ROMs, Kernels, Reco] lcapone84:
Download link is down.

This rom still available for Zefone 5 (2018)?
[Asus Zenfone 5 (2018, ZE620KL) ROMs, Kernels, Reco] henricaodopao:
fixed, sorry
[Asus Zenfone 5 (2018, ZE620KL) ROMs, Kernels, Reco] PandaXD:
Hey,I've seen my device https://www.gsmarena.com/lenovo_z5-9222.php has very similar specs to the and looks rebranded https://www.gsmarena.com/asus_zenfone_5_ze620kl-9061.php Is that possible I can use roms and such made for the asus?
[Asus Zenfone 5 (2018, ZE620KL) ROMs, Kernels, Reco] Turbo588:
I'm new to this, is there OTA updates or do I need to flash the ROM for every update? Also, how is this different to project sakura?

Thanks!
[Asus Zenfone 5 (2018, ZE620KL) ROMs, Kernels, Reco] BON3YY:
weres the fingerprint option , under security i got nothing plz help
[Asus Zenfone 5 (2018, ZE620KL) ROMs, Kernels, Reco] Pons77:
Hello everybody!

a black circle appeared in the upper left corner of the screen, which remains overlaying everything, even with expanded screen.

any idea what it might be?