yashsingh1/xdaforums huggingface dataset:
[Asus Zenfone 9] NisseGurra:
Option 3, install https://xdaforums.com/t/paranoid-android-topaz-alpha-1-asus-zenfone-9.4557631/

Use the suggested image way. It install new recovery, if i rember correct it has adb support

Reboot recovery and use option2

​
[Asus Zenfone 9] lordbit:
@NisseGurra sorry if my question seems dumb. But I have not unlocked my bootloader (when I had the chance). Do these recovery.img methods with adb work for me?
[Asus Zenfone 9] NisseGurra:
If you bootloader is locked so you cant flash anything not signed by Asus, no twrp etc, So strange it got messed up
[Asus Zenfone 9] Darkmasterhk:
Yeah it's weird that you could flash anything at all, that isn't signed

anyway, it seems like you where able to flash the asus recovery?

can you boot it?

If so try booting it and tipe "adb reboot sideload" if everything goes well it should reboot and allow you to sideload unmodified (asus signed) .zips, do this

Also consider data wipe from recovery
[Asus Zenfone 9] lordbit:
1. I pressed power button + vol-up, ended up in "bootloader" menu.

2. Chose "Recovery mode"

3. At this point, on my laptop, I executed "adb reboot sideload" as you suggested.

However, I am prompted with an error that this device is unauthorized.

adb devices
List of devices attached
N...P unauthorized

How can I "authorize" this? When I had access to fully-booted system, I just needed to confirm some dialogue. Here there is no question.
[Asus Zenfone 9] Darkmasterhk:
Aww that's bad, I don't know how to allow a device from recovery, sorry.

Usually, if it worked under Android itself, it works in recovery as well.

Just to make sure, it worked under Android, right?

I assume u use a Linux system and I somehow had trouble under Linux, with adb and authorization
[Asus Zenfone 9] lordbit:
Yes, "adb" did work between my Linux system and phone before it gets stuck in this mode.
[Asus Zenfone 9] lordbit:
I managed to fix the problem by using a RAW image from romdevelopers. Extracted the content of the zip file and executed "flashall_AFT.cmd" on a Windows machine with the right drivers installed.

For the record, these posts [1][2] are pretty close to what I did.

Thank you both for your support.

EDIT:

I converted the "flashall_AFT.cmd' to "flashall_AFT.sh", so I could be able to achieve the same on a Linux system. USE IT AT YOUR OWN RISK.
[Asus Zenfone 9] miki-xda:
I ran into a similar problem I think and I am unable to recover.

When I am in fastboot mode I get:

./flashall_AFT.sh
Looking for fastboot oem...
Try "adb reboot bootloader" if it doesn't work.
Cannot fastboot to the device.

When going to fastboot with power and vol_up keys I get this:

Looking for fastboot oem...
Try "adb reboot bootloader" if it doesn't work.
Project DAVINCI matching success!
/tmp/zenfone/raw/make_f2fs
[OK] Firmware directory: firmware_8475/
[OK] SM ID: 0/
Erasing 'misc' FAILED (remote: 'Erase of misc is not allowed in snapshotted state')
fastboot: error: Command failed

I've also tried the following:

fastboot snapshot-update cancel
Snapshot cancel FAILED (remote: 'Snapshot Cancel is not allowed in Lock State')
fastboot: error: Command failed

fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Device authorized: false
(bootloader) Device authorized2: false
(bootloader) WaterMask unlock: N
(bootloader) XBL:
(bootloader) ABL: 0.0.029.0-WW-user
(bootloader) SSN:
(bootloader) ISN:
(bootloader) IMEI:
(bootloader) IMEI2:
(bootloader) CID: ASUS
(bootloader) COUNTRY: EU
(bootloader) Project: DAVINCI
(bootloader) DT ID: 66
(bootloader) SB: Y
(bootloader) SBNR: Y
(bootloader) DDR Manufacturer ID: 1
(bootloader) DDR Device Type: 8
(bootloader) TotalDMCounter: 0
(bootloader) DMCounter: 0
(bootloader) SlotARetryCounter: 0
(bootloader) SlotAUnbootableCounter: 0
(bootloader) SlotBRetryCounter: 0
(bootloader) SlotBUnbootableCounter: 0
(bootloader) BOOT_COUNT: 0
(bootloader) LOCK_COUNT: 0
(bootloader) Check_APDP: 1
(bootloader) rawdump_en: false
(bootloader) force start logcat-asdf: false
(bootloader) Current Slot: a
(bootloader) Slot_a bootable: Bootable
(bootloader) AVB Verity: Enable
(bootloader) Verify vbmeta ret: 0
(bootloader) ABL_FTM: FALSE
(bootloader) UART-ON Status: false

Is it bricked or is there any way to rescue the phone?
[Asus Zenfone 9] miki-xda:
I don't know how I fixed it, but seems the phone is back alive with omnirom. I tried

fastboot flash super super.img

on fastboot started with power+vol_up, but it did not help. It worked when I started fastboot in TWRP. Still I see the errors related to partitions in TWRP, but anyway I was able to flash omnirom and it's working.
[Asus Zenfone 9] sendashano:
Wait how ur device suddenly have unlocked state? Without doing any unlock thing? Could you tell me how you do it?
[Asus Zenfone 9] miki-xda:
My device was previously unlocked with the Asus app.
[Asus Zenfone 9] MIhraiz:
Can you give me the RAW image you got from romdevelopers
[Samsung Galaxy S23 Ultra] bathrobehero:
Hey! So yeah, loving the phone but it's giving me a headache; it's not rooted or tampered with. Not even OEM unlocked. Only developer options were unlocked. Apps and settings were migrated from my previous Samsung phone with SmartSwitch.

From the download menu:

All kinds of root and safetynet and whatever apps pass and software and security patches are up to date (Google Play 1 January 2023, Android security patch 1 February 2023, Status: Official)

But Samsung Pass says "Your device has been rooted. Samsung Pass cannot be used on rooted devices for security reasons." Banking apps are obscure but one does give some hints as to the possible causes: modification attempt through hooking, using untrusted screen reader application, root or jailbreak, using untrusted keyboard application.

I use AdGuard and a 3rd party launcher (Flick) instead of OneUI and FlorisBoard keyboard but even if they are uninstalled the issue stays. I don't use any other major apps, just a bunch of regular apps. I don't use "screen reader" as far as I know and TalkBack is disabled.

This is really annoying and I can see dozens of similar cases even for older Sxx generations sometimes after updates and happening out of nowhere and even with new stock phones. People report that sometimes factory reset helps but sometimes doesn't and sometimes it only helps for a while.

I really don't want to factory reset just to try if it works until I exhausted all other options. It took me well over a day to set up everything the way I wanted.

Any help other than reset is very much appreciated!
[Samsung Galaxy S23 Ultra] pjaysnowden:
Find Samsung Pass in apps...and clear data.
[Samsung Galaxy S23 Ultra] bathrobehero:
^Thanks, but it didn't help.
[Samsung Galaxy S23 Ultra] Dummen:
I have the same issue and Im thinking about it is caused by smart switch from my old s21u which was rooted. Did You use smart switch too? Maybe I should do a factory reset, but then I lose all my stuff..
[Samsung Galaxy S23 Ultra] bathrobehero:
^Yep, I also used SmartSwitch with a rooted S9+. And I did find a few posts about SmartSwitch being the issue. But there are also some posts that said that reseting and not using SmartSwitch but manually installing all the apps they used the issue came back later. So far not using SmartSwitch is the only thing that might help but hopefully there's something else I can do to fix this without reseting.
[Samsung Galaxy S23 Ultra] hoss_n2:
My banking apps refused to work until I closed developer mode, it worked normally again, give it a try it may help, otherwise do a hard reset, and don't use smart switch next time
[Samsung Galaxy S23 Ultra] TheNewHEROBRINE:
Install Riru. It will tell you what symptoms of root it detects and could help to understand the cause of this issue.
[Samsung Galaxy S23 Ultra] bathrobehero:
HOLY ****! I could kiss you right now! That tool is awesome!

It was Xposed installed automatically with SmartSwitch which I didn't notice or even ever opened on this phone. Uninstalled it and everything works! Thank you!
[Samsung Galaxy S23 Ultra] Dummen:
I had magisk installed lmao.. (cuz of the smart switch)
[Android Head-Units] _sc300:
Recently bought an 8227L headunit running android 11 and randomly after turning on, apple car play has no audio. Restarting the head unit usually resolves this issue but I shouldn’t have to.

Today, the audio wasn’t working so I tried going to the native radio app and it would play sound, but was very low. Going back to apple car play, the audio would play but also sounded very low. Setting the audio to max (40) sounded like it was at 15. Again, restarting resolved the issue.

Is there some setting or workaround for this ? Any help is appreciated. I’ll post the headunit specs below.

2gb ram

Android 11

AC8227L
[Touch Pro, Fuze General] nick87night:
So i got my new phone and it's driving me nuts! Every time i get a phone call it picks up literally after 5 seconds even without touching it. I already checked the phone options and the automatic pickup is not checked. Is there another option that i'm missing?
[Touch Pro, Fuze General] ptyindian:
go to start> settings> personal tab> phone >(scroll over to) more tab> and there u should see a automatic answering check box uncheck it.
[Touch Pro, Fuze General] nick87night:
i already did that. it's unchecked. it seems to only do it when the phone is locked and the screen is off.
[Touch Pro, Fuze General] ptyindian:
hmm i am not really sure i remember seeing another place where it had auto answer option but idk where. Hopefully some one else can help?
[Touch Pro, Fuze General] nick87night:
i really hope someone can. i've tried sensor lock but it doesnt seem to work
[Touch Pro, Fuze General] hotpuck6:
Does this happen if the phone is just sitting there out of your pocket?

I know mine has answered a few phone calls on it's own because the screen turns on and unlocks when a call comes is, so it's possible for the answer button to be pressed while it's still in your pocket.
[Touch Pro, Fuze General] LTxda:
Try PocketShield and let me know if this works for you.
[Touch Pro, Fuze General] at10ti0n:
latest Gyrator has autoanswer if coming from standy on Portrait mode... do you have gyrator installed?
[Touch Pro, Fuze General] stayc29:
how do i turn this off i dont want calls answered unless i click on yes
[General Questions and Answers] Harshith KJ:
So I updated my OnePlus 7t to Oxygen OS 12 and I miss a very important feature. The feature I'm talking about is "Swipe up to search app". This enabled us to search through the app drawer as soon as we swiped up from the home screen. So without any hassle we could search and find the app we were looking for just by swiping up and typing the app name. But unfortunately this feature got removed in Oxygen OS 12. It worked flawlessly on Oxygen OS 10 and 11.

So now we manually gotta swipe up and then tap on the search bar and type. So is there any way to get this feature back on Oxygen OS 12 while using the stock launcher. Like using ADB commands or by using gesture apps or by using automation apps by creating a series of actions.

Any help is welcomed. As I said it used to be a very vital feature for me, I used it very often, so I'm looking for a workaround to get it back. Also I don't wanna rollback to previous version of Oxygen OS.
[General Questions and Answers] alex_whyatt:
+1 Did you ever find an answer??
[Samsung Galaxy Tab A series Questions & Answers] EGY falcon:
I'm just wandering if I could Install either of windows 10 or 11 on Tab A (SM-T585) ? or anything other than the current version of android which support (8.1.0)?
[Samsung Galaxy Tab A series Questions & Answers] V0latyle:
No, you cannot install Windows on an Android device.
[Samsung Galaxy Tab A series Questions & Answers] ipp0:
I’m using LineageOS 19.1 and it is great https://xdaforums.com/t/lineageos-1...anotexlwifi-and-sm-p585-gtanotexllte.4432957/
[Samsung Galaxy Tab A series Questions & Answers] EGY falcon:
Is it compatible with my (Galaxy Tab A 6 , SM-T585) 2016, because I read from the article (Galaxy Tab A 10.1)

I'm not quite understand
[Samsung Galaxy Tab A series Questions & Answers] ipp0:
Mine is SM-T585, 10.1 inch tab A6 from 2016 with lte networking and it works great. LineageOS 19.1 was first only available for the WiFi version but now both versions are supported.
[BLISS ROMS Q&A] twolittlepennies:
Hi,

I'm using Bliss-v14.10-x86_64-OFFICIAL-opengapps-20230201 on a Dell optiplex 7050 micro with 16gb RAM and a Dell 2418HT touch screen monitor.

Video in apps is corrupted with green and black bars. The video plays smoothly but the entire screen is covered with thin alternating green/black bars.

I can play video fine with firefox/via etc.

I have tried many kernel parameters, such as

video=1920x1080, other valid resolutions

video=HDMI-1:d video=1920x1080, other valid resolutions

video=vga

vga=hex codes/decimal

vga=ask

nomodeset

xforcevesa

nomodeset xforcevesa

uc_mode=vesa (i believe that was it)

i've tried using the vga output instead of hdmi, with all the same parameters

If I choose a valid resolution below 1920x1080, the console seems to change resolution while booting but Bliss never changes, it's always 1920x1080.

The issue seems to persist in Bliss 15.8.4, and across gapps and foss versions. (edited: had Bliss 16 instead of 15)

Here is a screenshot that was taken in an app called Devinfo. Thank you to anyone who can help.
[BLISS ROMS Q&A] HMTheBoy154:
switch gralloc to something else like

GRALLOC=minigbm HWC=drm_minigbm

on kernel parameter.
[BLISS ROMS Q&A] twolittlepennies:
Thank you very much. Everything is working great now.

When I tried both parameters the green and black bars would blink.

When I tried just GRALLOC=minigbm by itself the green/black bars disappeared and everything is fine.
[BLISS ROMS Q&A] HMTheBoy154:
I don't understand, can you explain ?
[BLISS ROMS Q&A] twolittlepennies:
I'm unable to replicate what happened. The green and black bars were no longer static but now flashed on and off like on a switch, which is the first and only time it ever happened.

I'm sure I did something wrong.

Everything works great, and I'm (now) using both of the parameters you provided. Thanks again.

And thanks to everyone who worked so hard to bring Android to PC.
[BLISS ROMS Q&A] Savikate:
Hi, please can You write out the steps, on how to fix that issue. Where do I input aforementioned commands and so on.
[BLISS ROMS Q&A] Savikate:
Please, for the love of god, someone guide me this ****fest. I NEED to fix the exact same issue. Ive been siting here for hours and hours trying to find out how the F* can I modify the system property You guys are talking about. My brain is melting.
[BLISS ROMS Q&A] twolittlepennies:
Boot the device, when you see the boot selection screen hit 'e' to edit the boot parameters.

on the second line after 'quiet' put the following

'GRALLOC=minigbm' 'HWC=drm_minigbm'

then hit f10 to boot and see if it fixed it.

if it did, you can make it permanent by (in my case) doing the following

boot back to the boot selection screen and pick debug to boot

after it boots, type

mkdir /mnt/hd

mount /dev/sda1 /mnt/hd

vi /mnt/hd/EFI/Android/android.cfg

hit 'i' to be able to make changes

go to almost the bottom and look for "Create Main Menu"

on the first entry, after quiet, enter GRALLOC=minigbm HWC=drm_minigbm

hit escape

hold shift and type :

then type wq and hit enter

vi should save and quit

type

umount /dev/sda1

then reboot

this is what I did in my case, there is probably a better way. I'm using Bliss 15.8.4 on bare metal.
[BLISS ROMS Q&A] andrewjonesgw:
This might sound odd. but if your BIOS and uefi and legacy option on I found that some PC with Android do not like it. if your using the uefi boot.

I had an issue like the above fixed but setting bios to uefi only. this was on android x86
[BLISS ROMS Q&A] amh-unti:
Hi guys, same problem over here, tried the given solution, didn't work, not resolved yet, on an Asus n61jq 🙄View attachment 5992561View attachment 5992563View attachment 5992565
[BLISS ROMS Q&A] amh-unti:
Bliss 15.8.6 Arcadia
[BLISS ROMS Q&A] DocMAX:
Same issue here, tried all mentioned kernel parameters...

View attachment 6001967
[BLISS ROMS Q&A] DocMAX:
The solution is add CODEC2_LEVEL=0 to the kernel parameters.
[BLISS ROMS Q&A] amh-unti:
Tried it, didn't work, I'm emulating android on Linux distributions now.
[BLISS ROMS Q&A] DocMAX:
ok, then try:

View attachment 6002591

(the 4 after CODEC2_LEVEL=0)
[BLISS ROMS Q&A] amh-unti:
It worked, thanks man.
[OPPO Reno 5 Pro 5G] Brolin Michael:
Has anyone tried installing GSI roms in Oppo Reno 5 Pro?
[General Questions and Answers] clellandm:
I have a Sprint Mogul phone with Windows Mobile 6.1 running.

Hopefully others have had this problem and I just didn't use the right terms in my searches to find the solution.

This started when I clicked on 'live search' in my Start Menu (under Today) - nothing happens. So I went to Settings > Menus and brought up the long list to see what was checked to show up in the today list. I have 2 'live search' items in the list and the first one is checked. I tried unchecking it and a pop-up tells me "cannot move that item". I get the same message when I try checking the 2nd 'live search' item as well.

My guess is the first one is an old version and that's why it doesn't open in the start menu. How do I get that Menu Settings screen cleaned-up?

Thanks!
[General Questions and Answers] clellandm:
Anyone know how to clear-up my menu settings problem?
[Realme 8] kamil.accou:
Hello everyone I have been havinng some issues with my realme 8 RMX 3085. I was planning to install Lineage OS and custom recovery. I followed tutorials on xda. Fortunately i unlocked bootloader with official method - deeptest.apk, to do this firstly I flashed rom with thailand one. Everything seems to be succesfull, in settings bootloader is unlocked.

fastboot flash recovery recovery.img

target reported max download size of 134217728 bytes

sending 'recovery' (131072 KB)...

OKAY [ 5.336s]

writing 'recovery'...

OKAY [ 0.451s]

finished. total time: 5.788s

However after that I am not able to enter recovery (even stock one). I kept flashing recovery image via fastboot. Everything seems to be all right until I try to enter it. Using command fastboot reboot recovery nothing happens. Another one adb reboot recovery tries to enter recovery several times with no success, then reboot to os.

I read couple of threads about that issue, tried using different computers, with different os - still the same. Tried using different cables and usb ports also nothing changed.

Does anyone have any idea what can couse the problem? Appreciate any advices.
[Realme 8] matonka007:
Same here, trying few days but nobody help
[Realme 8] sayanmitra753:
Ok..did you installed magisk by flashing magisk patched boot.img ? If yes..then you need to restore/flash stock boot.img to enter recovery..this problem occurs on android 12 only..
[Realme 8] Chicada:
https://telegra.ph/Flash-LineageOS-on-Realme-8-06-05

try follow this tutorial, worked for me
[Samsung Galaxy A32 5G] plee12:
I need some help.

I'm facing the exact same problem described in this article:

Fix “Can’t Load Android System Your Data May Be Corrupt” Without Reset

Fix "Can't load Android System Your data may be corrupt" without Reset

In this guide, we will show you the steps to fix the "Can't load Android System Your data may be corrupt" error without a factory reset.

www.droidwin.com

I'm able to complete all the steps until the very last step #5.

This is where the adb sideload update.zip command is stuck at Verifying update package (%).

I'm using the latest Google SDK platform tools

I'm using USB A to USB C cable

I wiped the cache partition

I'm using the stock version of Android 13 for update.zip

Any suggestions for how to clear this hurdle?

Thank you
[Samsung Galaxy A32 5G] alecxs:
is there a META-INF/com/google/android/updater-script inside zip?
[Samsung Galaxy A32 5G] plee12:
Alecxs,

Thanks for your question.

After I unzip the file, I get 5 MD5 tar files, BL, AP, CP, CSC or HOME_CSC, and USERDATA.

I think there's a misunderstanding on my part about the file type required by the adb sideload command. I just assumed the file type should be the factory image, so I downloaded that zipped file directly from samfw.com and renamed it update.zip.

I didn't realize there's a difference between a factory image and an OTA image.

Apparently, the adb sideload command requires the file type to be an OTA image, not a factory image.

This Google site provides downloads for both factory and full OTA images: for Pixel and Nexus phones:

Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

However, I don't believe there are any sites that provide downloads for Samsung OTA images.

So, am I using the wrong file type for the adb sideload command? Could this explain why it can't verify the file?

I hope I'm making some sense and not making a total fool of myself.

Thank you,

Peter
[Samsung Galaxy A32 5G] ankkesar:
Plee12

Were you able to resolve this issue?

I also need to flash my phone due to a boot loop issue, but not able to find ROM as OTA image
[Samsung Galaxy A32 5G] plee12:
Sorry to break the news to you, but I couldn't find any way to resolve the boot loop issue. I finally gave up and did a factory reset and lost all my data in the process.
[Nothing Phone 1] Ashiq.makkar:
last time i searched around and got myself in a hard brick situation. please make a guide for this. Noob here
[Nothing Phone 1] ethical_haquer:
If you are rooted using Magisk, look here.

Let me know if you need help.
[Nothing Phone 1] Ashiq.makkar:
thank you but i tried this and got installation problem when trying to update
[Nothing Phone 1] D4yan:
For me it worked to do an OTA update with the same version installed.

For example, my phone was rooted to 1.1.7 and I could not update to 1.1.8. So I downloaded 1.1.7 and updated via OTA. After that I could update to 1.1.8 normally. However, the phone must be rooted again.

For the OTA update you have to download the whole OS (https://xdaforums.com/t/nothing-phone-1-rom-ota-nothing-os-repo-of-nothing-os.4464039/#post-87101175) and then dial *#*#682#*#* in your phone. Now a menu opens in which you can select the OS by browse in the upper right corner. My data has been preserved during the update.
[Nothing Phone 1] Ashiq.makkar:
can you please explain the exact steps?

I'm currently on 1.1.7 rooted with magisk

using some modules and lsposed
[Nothing Phone 1] HermitDash:
Short Guide:

Pretty sure this works across the board with most devices.

If you're doing a OTA and not a manual update:

1. Go into Magisk ~> Uninstall Magisk ~> Restore Images

2. Update via OTA (Do not reboot)

3. Go back into Magisk ~> Install ~> Install to Inactive Slot (After OTA)

4. Reboot
[Nothing Phone 1] Ashiq.makkar:
tried this. after uninstall magisk by restore images, tried to update via OTA and still getting installation problem
[Nothing Phone 1] HermitDash:
How to manually sideload Nothing OS OTA updates on your Nothing Phone 1

To get the latest Nothing OS update onto your Nothing Phone 1 sooner, you can sideload the update manually. Here's how to do it.

www.xda-developers.com

Manually update yourself to the latest and then reroot.
[Nothing Phone 1] Ashiq.makkar:
tried manual update and keeps getting different source build is required
[Nothing Phone 1] mr_viii:
I was on 1.1.8 rooted with magisk.

My knowledge isnt the best but my way to update is:

1. Deinstall Magisk.

2. Flash stock boot.img (my version was 1.1.8 so i flash stock boot.img from 1.1.8)

3. Install Update normal over stystem updater

4. Reinstall magsik, done.
[Nothing Phone 1] paper88:
I tried it also with restoring magisk and update it over OTA. It worked and it installed, but after I installed Magisk to new slot and restart, it bootlooped 3 times and go back to old version. I think the new Android Versions install the update while restarting. So if you install to new slot with magisk you'll reboot with no OS on the Slot installed. I think the best way is just to uninstall magisk, install update and patch boot img