yashsingh1/xdaforums huggingface dataset:
[ASUS ZenFone 8] bnsmb:
There is only one bootloader on the phone.

AFAIK the phone does not boot automatically into the fastbootd. So you did somethink like "reboot fastboot" instead of "reboot bootloader" I guess.

Reinstall the OmniROM or what do you mean?

If the data decryption works after booting into TWRP you should backup the data to the PC before continueing

So it booted into the original recovery from the OmniROM which did not find a command to execute (the original Recovery from OmniROM is very limited and does not provide a shell)

Did you do something like "reboot recovery"?

If not, the phone booted into the recovery because it did not find a bootable OS.

To find the reason you can boot into the TWRP image file and check the log file of TWRP for the reason for the error -- see https://xdaforums.com/t/how-to-fix-...roid-system-your-data-may-be-corrupt.4534237/

The last time I restored a TWRP backup the data was lost (but that was on another phone ) ...

regards

Bernd
[ASUS ZenFone 8] Yippee38:
It's possible. I don't remember doing that, but it's possible that I did that.

I was thinking that there was a bootloader in each slot. I had already flashed the boot.img to slot_b, but that did make the phone bootable. If I flashed it to slot_a, maybe that would work. But if there's only one bootloader, that won't work.

Yeah. That's my plan. I've been doing research on how to do that. I've got the general stuff, as I said (pictures, music, downloads, etc). I just need to backup the application data. The decryption works fine when booting into TWRP.

No. I did not "reboot recovery".

Yes. It rebooted to recovery because it did not find a bootable OS.

I got the log file onto my PC. There's a lot (almost 45,000 lines). At the end of the file though, there are several lines that say, "No recovery folder found. Using default folder." It also says, "Unable to mount '/usbstorage' a couple of times. In fact, here's the end block of text.

I:No recovery folder found. Using default folder.
I:Attempt to load settings from settings file...
I:InfoManager loading from '/data/recovery/.twrps'.
I:No recovery folder found. Using default folder.
I:Backup folder set to '/data/media/0/TWRP/BACKUPS/M8AIB760J277SLD'
I:Version number saved to '/data/recovery/.version'
I:Unable to mount '/usbstorage'
I:Actual block device: '', current file system: 'vfat'
I:TWFunc::Set_Brightness: Setting brightness control to 420
I:Starting MTP
I:Cannot find file /sys/class/android_usb/android0/idVendor
I:Cannot find file /sys/class/android_usb/android0/idProduct
I:sending message to add 65538 '/data/media/0' 'Internal Storage'
I:Message sent, add storage ID: 65538 '/data/media/0'
MTP Enabled
I:[MTP] Starting MTP
I:Attempt to load settings from settings file...
I:InfoManager loading from '/data/recovery/.twrps'.
I:No recovery folder found. Using default folder.
I:Backup folder set to '/data/media/0/TWRP/BACKUPS/M8AIB760J277SLD'
I:Version number saved to '/data/recovery/.version'
I:Unable to mount '/usbstorage'
I:Actual block device: '', current file system: 'vfat'
I:TWFunc::Set_Brightness: Setting brightness control to 420

Ok. Good to know. I won't do that then.

1. I think my plan of action is to back up all of the app data that I can to my PC.

2. Reflash to TWRP using 'fastboot boot twrp.img'.

3. Once in TWRP, do Advanced, install current TWRP to re-install TWRP in both slots permanently.

4. 'adb push' the OmniROM zip file onto the device.

5. Install OmniROM from TWRP.

6. Cross my fingers.

Does that sound right to you?
[ASUS ZenFone 8] bnsmb:
The bootloader is on one of the partitions that is only available once . The bootloader does not care what is installed in the boot partition -- it just boots the boot partition of the active slot. And that may or may not work depending on the contents of the boot partition.

Then you must only backup the directories in /data/media/0. Doing a backup of only these directories you're missing the internal data of the applications in /data/data/* and probably other directories and the settings of the applications.

Personally, I would back up all files and directories /data in this case - it's better to have more data in the backup than necessary than not enough.

Search for "Android Rescue Party trigger" in the log file

The lines following this line are the important messages

The plan looks fine

The installation of TWRP (point 3) does not make sense.

Installing an operating system image always overwrites the boot partition of the passive slot - so to install TWRP into the boot partition, this must be done after installing the operating system

I would not install TWRP at this time at all: You can always boot into TWRP using "fastboot boot twrp". Installing TWRP at this stage is just another reason that can lead to errors.

Just boot from the TWRP image file , install the OS without doing a factory reset

If everything is OK, the operating system is booting and your data is still there, you can reboot the phone from the TWRP image again and install TWRP in the boot partition.

and fyi

That command boots from the TWRP image file but does not change anything in the boot partition

regards

bernd
[ASUS ZenFone 8] Yippee38:
That worked! I was able to get my phone running again, and get it rooted (by using the OmniROM boot.img this time).

All fixed! Thank you so much for sharing your knowledge and helping me reverse my screw-up.
[Android Q&A, Help & Troubleshooting] QeBurak:
Recently, I tried to install a module on my Redmi S2 device several times due to the problem of banking applications detecting the root. After the modules did not work, I flashed the boot repeatedly while changing the tools I used for rooting. Apart from these, I recently merged my existing SD card with my phone's disk through Android's settings. After these processes and somehow correcting the boot image and solving my problem, I used my device without any problems for a few months. But yesterday my device suddenly froze. He didn't give any reaction. When I switched to recovery, it did not open. It was stuck on a black screen. It would open after waiting for a long time, but when it opened, it would freeze again when I navigated through the functions a few times. I tried to flash my device in fastboot mode. This time, an error like this appeared:

C:\adb>fastboot flash recovery recovery.img
Sending 'recovery' (33664 KB) OKAY [ 1.086s]
Writing 'recovery' FAILED (remote: 'flash write failure')
fastboot: error: Command failed

When I keep trying, sometimes I get an error like this:

target didn't report max-download-size

erasing......

My device has LineageOS 20 and Android 13

3GB ram 32 GB local and 32GB SD memory

While dealing with this problem, I managed to run the update mode in the recovery of Lineage OS. I tried to flash the ROM from here again, but I think after 15 minutes, while the installation was still going on on the phone, my laptop ran out of battery and shut down, then my phone got stuck in -Restoring Google backup- and I turned it off. When I tried again, the recovery was completely dysfunctional.
[Android Q&A, Help & Troubleshooting] QeBurak:
plaese bro
[Xposed Framework Modules] David B.:
CaptureSposed​

With the release of Android 14, Google added an API to enable app developers to detect screenshots. This API has since been adopted by popular apps such as Snapchat.

CaptureSposed is an Xposed module that effectively disables this API to prevent apps that use it from being able to detect when a screenshot was taken.

⚠️ WARNING: CaptureSposed is intended for rooted devices running Android 14 and requires Xposed. The required Xposed variant to use is LSPosed. Other Xposed variants will not work. This module cannot be guaranteed to work on all devices. In the worst case, it can cause a bootloop. Use at your own risk. Additionally, this module does not protect against screenshot detection from apps that use the pre-Android 14 approach of using file system listeners to detect screenshots (ref 1, ref 2).

​

To use CaptureSposed:​

Install LSposed. This requires your device to be rooted with Magisk or KernelSU. Installation instructions for LSPosed are available here.

Install CaptureSposed.

Activate the CaptureSposed module in the LSposed user interface.

Reboot your device and sign in.

Open the CaptureSposed app and take a screenshot of it. If the screenshot is not detected, then the module is working as intended.

CaptureSposed is a collaborative project by Keshav Majeti (@keahav99) and David Berdik.

The official GitHub repository can be found at https://github.com/99keshav99/CaptureSposed.
[Samsung Galaxy S10+ ROMs, Kernels, Recoveries, & O] 7ossam9987:
the software file i ve tried to install EGY-G975FXXSEFUL1-20211221163240.zip

then it gives me this error sw rev check fail bootloader device 16 binary 14
[Samsung Galaxy S10+ ROMs, Kernels, Recoveries, & O] TedFin:
This error is due to Samsung having binary lock, Samsung upgrades the binary on their software every now and then, if you get an update that made it so your binary went higher than the last update, that will make it so you cannot flash binary's lower than the binary you are one
[Poco F5 Pro / Redmi K60 (China)] MangoTCF:
I think i bricked my phone as it shows a different menu from the on that was stock after unlocking the phone. Flashing TWRP doesn't work unless truncated to 100 MB and even then it doesn't want to boot to recovery, not even speaking of the system(lol). I tried to find the bootloader image on the internet but unsuccessfully. What should I do in this situation?

The fastboot menu is completely ASCII and shows some basic info about the phone(?). I am unable to provide the photo for obvious reasons :/
[Poco F5 Pro / Redmi K60 (China)] NOSS8:
Surely in FastbootD, what commands are available in the menu?

What is FastbootD? How to Boot to FastbootD Mode

In this tutorial, we will explain you what is FastbootD Mode in Android, how to boot to FastbootD Mode and how to exit this mode.

droidwin.com
[Nothing Phone 2] 1slotrk:
I don't know what i did wrong but my device is bad off. I tried flashing 2.5.5 inside of orangefox with tool and the device restarted but then bootlooped. So as it sits I cannot boot into anything other than the bootloader no matter what I flash. I have tried using tool but i cannot for the life of me get it past attempting to flash the boot partition. I have tried wiping but with the same error as listed
Flash images on both slots? If unsure, say N. (Y/N) y
fastboot: error: cannot load ' boot.img': No such file or directory
Flashing boot.img failed, Continue? If unsure say N, Pressing Enter key without any input will continue the script. (Y/
N)
I am using linux and have tried 2 different linux systems. I have also tried an older WIN7 and can't even get it to recognize the fastboot device, also using it in a VM. If I need a windows 10 to use the EDL tool then i can try to get a VM spun up for it.

Any help will be greatly appreciated.
[Nothing Phone 2] 1slotrk:
After some beating my head against everything. For some reason i got this tool to work, but it is a fork of the other that is older.
[Nothing Phone 2] yzena:
Please try from nothing archive by arter97.

GitHub - arter97/nothing_archive

Contribute to arter97/nothing_archive development by creating an account on GitHub.

github.com

Using flash_all.bat via fastboot :

GitHub - HELLBOY017/Pong_fastboot_flasher

Contribute to HELLBOY017/Pong_fastboot_flasher development by creating an account on GitHub.

github.com

Worked for me... Good luck :)
[Nothing Phone 2] spike0en:
There was an issue with the script which has been fixed now. Redownload and try again!
[Nothing Phone 2] MacTavishFR:
I had the same fckng issue of 'fastboot: error: cannot load 'someimage.img' when using linux

Had to go on Windows to get it work
[Red Magic 8 pro] viil:
I am having repeated issues with my Red Magic 8 Pro (global rom, no root) following the latest updates in March and April 2024. The issues are narrow and very specific but I am hoping that someone may have a solution for at least one of these:

1. My company requires me to install Intune Company Portal Android app in order to access my email and other work materials. I used the app without any issue till early March 2024 when my phone updated its software to the version REDMAGICOS9.0.10_NX729J_GB (Android version 14). Ever since then, after I complete my registration in Intune Company Portal my device keeps getting unregistered after few hours of use and then it shows Company Access Setup is incomplete. When I try to register the device again it gives me the error and tells me to ‘Try Again’ over and over falling into loop. I only have to uninstall and reinstall the app; or remove the device from the app, clean data and cache, register it again, then the app works for few hours (1-6 hours, no pattern) and then unregisters me again. I have consulted with our company IT dept and we tested the issue. After my device is unregistered in the app, on the server side, it says that my device is registered and should be working. I contacted the developers but to no response.

2. I use Rokid Max AR glasses which are connected via USB-C DP. Normally, the sound was broadcast directly into glasses until the latest software update. Now, the sound comes out of the phone speaker and the glasses simultaneously. Is there any way to block the phone speaker, so I can only hear it in the glasses earphones? For now, I have to connect additionally Bluetooth earphones, but it's not very convenient.
[Red Magic 8 pro] borygo77:
Can't help with issue 1 but issue two is known to me. I've been on support mail for many hours about it and they promised fix for audio routing in next release. 9.0.11 around June.

When you connect your Bluetooth headphones you got no audio from phone speakers but also no from headset I'm guessing? 😉
[Red Magic 8 pro] viil:
Correct. When Bluetooth earphones are on, all other outputs are silent.
[Red Magic 8 pro] borygo77:
Nah. It's different on mine. When I have usb c monitor plugged in there's sound coming from phone speakers and monitor speakers.

When I connect Bluetooth headphones sound from phone speakers disappearing but there's no sound in headphones as well. Only monitor speakers plays sound.

Do you have the same?
[Red Magic 8 pro] viil:
Just tested. You are right. When I connect bluetooth, all audio is rooted to glasses now and doesn't go to bluetooth or phone speaker. This is so weird.
[Red Magic 8 pro] borygo77:
Thanks for confirming 😊 as I said I was told by support fix is coming in June with 9.0.11.

Not sure I can trust them 😉
[Red Magic 8 pro] viil:
Let's wait and see
[Red Magic 8 pro] viil:
FYI, I have following updates from Red Magic support team:

1. As for Intune Company Portal Android app, please kindly advise if you can help us collect log so that our R&D can better analyze the problem you are facing.

If yes, please kindly sign the attached authorization letter and send back to us.

2. The problem of using USB-C DP to connect VR sound output has been fixed and will be optimized and solved in the next version.

The new version is expected to be released at the end of June or early July
[General Topics] knobbs:
I have recently started to have an issue with the bluetooth devices connected to my Android. Everything was working previously no issues at all and about 3 days ago I had a call come through while driving, I picked up with the in-car bluetooth connection and they couldn't hear me. I have tried multiple other times and no one can hear anything, google assistant can't pickup anything if I manually summon it, google keyboard won't type anything when using the mic, whataspp sends blank audio messages. I have tried multiple other bluetooth devices with mics that I have previously connected and worked fine but none of them will bring the microphone through. I have also tested a different phone in the car and it works perfectly so obviously an issue with my phone.

One thing that may lead somewhere is when I turned on google maps and input a destination my microphone will then be picked up through the bluetooth. The car has no android audio though, it is just a bluetooth connection.

What setting where might be the issue?
[Samsung Galaxy M02s] Otaku.xz:
Literally there are all models of samsung but not a single forum on the Galaxy M01s(SM-M017F). Why can't the developers make a 64 bit Custom rom on this device? Aren't there any developers contributed to do something for this model?
[Xiaomi Poco X5 Pro] ajith1809:
Device won't turn on!!
[Xiaomi Poco X5 Pro] IsHacker:
Can you boot to fastboot?
[Xiaomi Poco X5 Pro] rkoopmann:
Can confirm this problem, i flashed lineage 21 from here:

[ROM][14.0][UNOFFICIAL] LineageOS 21 for Poco X5 Pro [redwood][Discontinued]

LineageOS is a free, community built, aftermarket firmware distribution of Android 13 (T), which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with...

xdaforums.com

and used either the newest magisk canary or the kitsune magisk fork, in both cases if i enable the zygisk my phone doesnt boot lineage any longer

could enter to fastboot by key combo though, and use magisk without zygisk, it works.
[OnePlus 12] Lethalben:
Hi,

I don't understand oneplus choice about amoled screen and Grey tint on Black theme.

Why it's not pur Black, amoled screen is do for that.

Pur Black means no consumtion, or less than Grey tint.

Any idea ?

Have a good day !
[Asus ROG Phone 6 / 6 Pro] drvfchtr:
Anybody had the firmware to downgrade android 14 to 13 rog 6

Email: visionisoln@gmail.com
[Xiaomi Mi Pad 5] tom.android:
* Not support with this kernel (linux-6.1.10) , waiting for new compilation.)

* No screen auto-rotation. ( For Manual works)

* Sound from 3 speakers only. (Upper Right corner speaker not works) ( do not open max-volumn- but with headphones its ok. )

* Not worry about activated sleep screen ( not the same bug of Windows11 on nabu -which can damage your device screen. )

( Did not found "brick by go into EDL State when install linux application- not the same as Win11 on nabu.)

( No GPS on this device , then No acculate location.)

( 2.4 & 5.0 ghz WIFI both works )

View attachment 6104620

Converter USB Type-c to Multiport Docking Station with PD.

* Nabu did not had "Display data transfer ( USB 2.0) " Then only HDMI not works.

View attachment 6104760

View attachment 6107074

Sony WH1000XM4 headphones ( it supports LDAC)

* Press & Hold power button for Bluetooth Setting.

Resources: https://sterba.dev/posts/linux-and-bluetooth/

Test

Share Virtual Extended Screen

https://ubuntuhandbook.org/index.php/2023/07/share-extended-screen-gnome/amp/

Gnome Extension Manager.

Ubuntu 22.04: Install Gnome Extensions Manager (Workaround)

Gnome Shell delivers core user interface functions for Gnome, such as switching windows and launching apps. Some of the interface elements provided by

linuxblog.io

How to remote desktop to Ubuntu

If you need to access your Ubuntu system remotely, you'll have to tweak these few settings.

www.xda-developers.com

Ubuntu’s ‘Media Sharing’

View attachment 6108120

View attachment 6108121

On TV

Media Server

View attachment 6108124
[Xiaomi Mi Pad 5] tom.android:
*update v.3.2

RisingOS Official - Browse /3.x at SourceForge.net

Official builds by RisingOS maintainers.

sourceforge.net

===== 02-06-2024 =====

- Rising v3.2 changes

- Upstreamed BPF Patches (Increased support for legacy (3.14 and below) kernels.)

----------------------​

GSI A14-RisingOS-Vanilla.v3.1 ( Based on LineageOS Android 14 )

(QPR2 based)

(Fixed backward boot on kernel < 4.14)

Download: https://github.com/ItsLynix/RisingTreble/releases

Works

- Bluetooth

- Face unlocked

- DT2W ( Treble for xiaomi )

- Refresh rate. 60,120, Auto adaptive

- Screen Display Auto Brightness.

- Camera

- Flashlight

- USB OTG

- Screen Cast

etc.,

Not work ( uses magisk with AOSP GSIs)

- Xiaomi Keyboard

- Xoaomi Smart pen

View attachment 6108701

View attachment 6108702

●Step by Step●

--> install GSIs-on nabu <--

=========================

S1.Open "cmd admin"

cd "C:\nabu_global_images_OS1.0.1.0.TKXMIXM_13.0"

S2.//Test device online or not?

adb devices

S3.

adb reboot bootloader

S4.

//will found red text on pad screen

//. FASTBOOT

fastboot devices

S5.

//copy vbmeta.img & vbmeta_system.img from Stock Fastboot ROM.

fastboot --disable-verification flash vbmeta vbmeta.img

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

S6. FastbootD good at process "Dynamic System Partition Size" for you.

fastboot reboot fastboot

S7. Check sure //will found blue text on pad screen

//. FASTBOOT

//test you 're on User space ( fastbootd mode)

//is userspace

fastboot getvar is-userspace

S8.//erase system_a. ( not delete physical partition.)

fastboot erase system

S9. Flash new GSI (system)

fastboot flash system LeOS-U-VNDK-arm64-bvN-0606.img

S10.Go to recovery,then perform " Factory reset/Wipe all data

fastboot reboot recovery

Process "FACTORY RESET" with Stock Recovery.

( make from instruction on screen)

---------->

If you encounter issues like invalid partition size then do this:-

Exam:

Spoiler content hidden.

>fastboot erase product

> fastboot resize-logical-partition product 0x0

// test ^Find this if success

// (bootloader) partition-size product:0x0

> fastboot getvar all

Exam:

Spoiler content hidden.

And again start flashing from the fastboot flash system command. Step S9 --->fastboot reboot recovery---->wipe all

------------>

S11.

Reboot system.

============================

----'End Rising OS 3.1

(A14 qpr2)--------​

PONSE'S AOSP A13 FINAL.

Release AOSP 13.0 v2023.09.19 · ponces/treble_aosp

Based on android-13.0.0_r82 Sync with latest sources of TrebleDroid (ci-20230830,ci-20230905)

github.com

View attachment 6109552

View attachment 6109553

View attachment 6109336

YAAP A13

https://github.com/ahnet-69/treble_yaap/releases/download/20230903/YAAP-UNOFFICIAL-20230903-arm64-bgN.img.xz

View attachment 6109737

View attachment 6109738

ARROWOS GSI A13*

Release ArrowOS 13.1 v2023.10.28 · naz664/ArrowOS_gsi

Changelog Synced with September source of Arrow Synced with latest td source

github.com

View attachment 6109898

View attachment 6109899

View attachment 6109912

View attachment 6109917
[Xiaomi Mi Pad 5] tom.android:
Make "RW GSIs & Virtual RW"

Install microG for any GSIs. ( A13 only)

*must increase its additional spaces.

Cont.
[Android Head-Units] TorstenH:
This is a general thread focusing on the

improvement of​

DAB+ signal / receiption quality​

when using USB DAB+ adapters​

For this I will make and describe some experiments.

Baseline

- I'm only focusing on standard (non RTL-SDR) DAB+ USB adapters.

- The used USB adapters have different designs (housings) but finally the circuit inside is always the same. One adapter I use is an exception because the case is made of metal.

- I'm only using the app DABdream and don't do comparisons with other apps.

Environment / testing areas

a) at home I'm using an Android smartphone and a super cheap indoor antenna.

b) in the car I'm using an Android head unit and an active 16V antenna (Calearo 7677840), powered by an separate lead.

Disclaimer

This is not a scientific work and there is no right for completeness and correctness. If you follow any suggestion of this thread, you're responsible for it. If you waste money, destroy the USB adapter, your car or your house catches fire: You're fully accountable and responsible by yourself.

Previous observation / starting point

The receiption quality does not only depend on the antenna position (as it should be). The receiption quality changes massively if the USB lead gets moved or if the USB adapter position gets changed - both without changing the antenna position. I can observe this behavior in both environments (car and home).

This is something you can easily test by yourself. Other users already reported to me that they have observed the same behavior. Youre welcome to let us know if you can reproduce the issue in your environment.