yashsingh1/xdaforums huggingface dataset:
[Nothing Phone 2] dlads:
Don't need to open your phone buddy, just grab a hydra V2 cable and use the flash tool.

If your screen is totally black then hold vol up and down plus power whilst the phone is connected to a windows computer running win 10 or above.

Wait for the windows ding showing a connection.

You could have the flash tool running there and if it shows connected then you're good to go.

PS: you do not need to open your phone that's mental that's you've done that, a V1 cable does not work on the NP2 V2 is needed, the vol up and down with power does 100% work however it may require a few tries.

Your phone isn't bricked, it's just stuck in a persistent black screen, something I've had myself.
[Nothing Phone 2] Trytoroot00:
I couldn't enter edl mode because I bought a miracle edl cable, even for the NP1. Which works perfectly. https://a.aliexpress.com/_EJnZdZd

But now i ordered the v2 model, And I'm crossing my fingers for a successful flash. Thanks, for the help i thought i totally killed my phone.
[Nothing Phone 2] dlads:
I promise you mate, the V1 doesn't work...has to be V2, I have both...

The persistent black screen is a known issue, you need to force a reboot whilst connected to a windows device with the tool running, you'll eventually see the connection.

@mvikrant97 knows all too well 👍🏼
[Nothing Phone 2] MacTavishFR:
Any updates @Trytoroot00 ?
[Nothing Phone 2] Renate:
I'd be interested to know exactly what the difference between the Hydra v1 and v2 cables is.

I know that the "standard" EDL cable just has a pushbutton that grounds the USB 2 D+ data line.

When the Android wants to show that its USB interface is ready for FS/HS mode it tries to pull up the D+ line with a 1.5 k resistor to 3.3V

If it notices that it's pulling but the level is staying at zero volts it can take discretionary action, including going to EDL mode.

The tests for this may or may not be built into the OEM's abl, so some models don't react.

Moreover, if you broke abl somehow then the tests for the EDL cable may never get executed.

In that case you need either the EDL test points or to defeat the eMMC or UFS.

I built my own "EDL cable" (box) that automatically does this without pressing a button.

Oh, I found my answer already. v2 uses a pullup on a CC line.

https://xdaforums.com/t/hydra-cable-v2-pro-edl-cable-connection.4579275/
[Nothing Phone 2] dlads:
Honestly,

I'm not sure, all I know is I ordered the V1 cable (red and yellow) assuming what could be the difference and that it must work.

Waited for ages to get it then it failed to work, so ordered the V2 (white and black) and that worked immediately, from crash dump and persistent black screen.

@mvikrant97 may know the difference but I'm not sure.

If I had to guess I'd say the button push affects different pins for the NP2 and as such the V1 won't work... But which pins and why I'm not sure, maybe it releases power at a different voltage which has to be within a certain limit in order to force edl mode.

Perhaps they're blocking the use of the V1 cable for third party fixes? Personally I can't see that.

Or they opted for a particular type of port which just requires a different edl type , but not on purpose.

Either way, the V1 100% doesn't work if you're in a persistent crash state.
[Nothing Phone 2] Trytoroot00:
I ordered the V2 cable, which has not yet arrived. @MacTavishFR
[Nothing Phone 2] mvikrant97:
Yes there is a difference between the V1 and V2.

The V1 does not have the Resistor and thus does not support the Nothing 2.

V2 comes with a built in resistor which is between the CC and V+ line.

The picure below is from Hydra V2 cable.
[Nothing Phone 2] Trytoroot00:
I got some updates. The cable has arrived. However, there is a small problem. the phone enters quectel qdloader 9008 mode instead of qualcomm qdloader. Because of this, flash programs do not recognize the phone
[Nothing Phone 2] mvikrant97:
Download this tool here >> here >>

Select Custom Install >> Check the Qualcomm Drivers and then install it.
[Nothing Phone 2] Trytoroot00:
@mvikrant97 You are a life saver man. At this moment, I am flashing the phone, the computer recognized the phone after the drivers
[Nothing Phone 2] mvikrant97:
Let me know if your device boots after flash.
[Nothing Phone 2] Trytoroot00:
Sadly its not. Nothing show up on my screen. Idk what is the problem. I'm using the Nothing for flash 1.4.0.0.
[Nothing Phone 2] mvikrant97:
What is the variant of your device? EU or Global?
[Nothing Phone 2] Trytoroot00:
Honestly? I do not know. What is the difference between the two models? Nothing phone 1 had spacewar and Arceus. But in the case of 2, both were named pong, right? Are there any physical differences between the 2 models? Maybe the back cover?
[Nothing Phone 2] Trytoroot00:
I found, i have the ain065
[Nothing Phone 2] mvikrant97:
Your device is Nothing 2 but what variant is it? Europe or global?
[Nothing Phone 2] dlads:
Think it may be Indian...ain? Mines A065 not AIN065
[Samsung Galaxy A53 5G] soxzko:
if someone contributes, i can be the tester
[Touch HD Themes and Apps] elmarko99:
Hi

I just installed Fake Call 1.1 on my HD and it is fully registered so it should be fully operational.

I am having a problem though. When I set a voice clip (tried mp3, wav, and wma) to be played when the call is answered it only plays through the loudspeaker, not the earpiece.

Anyone know what is wrong, or is output through the earpiece not available with this piece of software?

Thanks
[Xiaomi Poco X3 NFC Questions & Answers] samantas5855:
I bought a Poco X3 NFC used some months ago, the phone was listed as working and had pictures with miui too. When the phone arrived it had marks indicative of fall damage and the phone would stay in the Poco logo. I could access fastboot but the bootloader is locked. I can access recovery and after sideloading the stock rom the issue persists. Is this a hardware damage or will EDL fix this?
[Xiaomi Poco X3 NFC Questions & Answers] NOSS8:
Difficult to say, is there a possibility of returning it since it is not functional?

EDL flash is not free and if it is a HW problem the flash will not solve anything.
[Xiaomi Poco X3 NFC Questions & Answers] samantas5855:
Seller vanished

Yeah I know EDL is paid, I figured I'd asked here in case it's a common HW failure of the memory modules or a common situation solvable by fastboot/edl flash
[Xiaomi Poco X3 NFC Questions & Answers] NOSS8:
Have you tried wiping data from recovery?
[Xiaomi Poco X3 NFC Questions & Answers] samantas5855:
Yeah, both data wipe and installing the latest rom from recovery.
[Xiaomi Poco X3 NFC Questions & Answers] NOSS8:
Post the result of this CMD "fastboot getvar all", phone in fastboot mode.
[Xiaomi Poco X3 NFC Questions & Answers] NOSS8:
Nothing to do except an EDL flash without being certain that this will solve the problem if it is at the HW level.

Just in case, it's here:

Xiaomi Auth Flash

Authorised from the site administration. Thanks to @V0latyle @Oswald Boelcke @willverduzco and all other admins. MESSAGE ME on XDA Forums Telegram Support Official MIUI & HyperOS Bootloader Unlock Guide Xiaomi Auth Flash Payments: PLEASE...

xdaforums.com
[Xiaomi Poco X3 NFC Questions & Answers] wilsonhlacerda:
As bootloader is locked (sure?), I would try to:

on fastboot boot recovery newest brigudav's TWRP image file without flashing it itself. If it can boot TWRP, then format data (not wipe, the option with yes/no question).

Maybe also try format system, then flash newest (to avoid rollback problems) stock ROM as zip (for recovery usage).

read this whole thread, maybe it gives you some tips:

https://xdaforums.com/t/poco-x3-ind...oyed-press-power-button-to-shut-down.4675674/

Besides that probably EDL only, if it is not a hardware issue.
[Xiaomi Poco X3 NFC Questions & Answers] NOSS8:
SURE?

(bootloader) secure:yes

Not possible to install twrp with the bootloader locked.
[Xiaomi Poco X3 NFC Questions & Answers] wilsonhlacerda:
Yeap, I saw it just after I've posted.
[Android Head-Units] Francesc9:
Hi,

I have the new Junsun X7 Pro model TS18 that it has 2 usb.

As I wanted to connet more than 2 items in these usb (TPMS, Memory styck, ADAS camera, DAB+ digital radio and Ibus) I would like to know if there any possibilities to connect in one of the USB a USB converter 1 to 4.

Thank you all
[Android Head-Units] Renate:
They're called "hubs". Yup, it should work.
[Android Head-Units] Francesc9:
OK, I will try

Thank you
[Android Head-Units] marchnz:
Not FYT requested moderator move to Android headunits forum
[General Questions and Answers] Woodland586:
(I posted here because I can't find any threads on the E900. Sorry if it's in the wrong place.)

Hello.

A month or two ago, I had bought an old SGH-E900. I plan to use this instead of my current phone (to get away from distractions, you know?)

I had flashed an upgraded firmware (from E900XXFG1 to E900XXFG2 (to remove messages and other data from the device, as the previous owner never wiped the phone)

Yesterday (16/07/24) I got a new SIM Card which the phone accepted just fine. It was able to activate and i was able to make a call. I had also successfully recieved 2 messages too. Around an hour later, the device started acting strange. The phone would freeze and reboot itself whenever it sent/recieved messages or calls. Do you have any ideas on how i can fix this? I believe it may have been linked to the firmware reflashing.

If it helps:

-I had made a dump of the E900XXFG1 firmware before flashing E900XXFG2. I reflashed E900XXFG1, but the issue still persists.

-I have tried the firmwares E900XXFG1, E900XXFG2, E900XXFF2, and E900XXFF3. All of these are UK firmwares, which matches the device.

-I have verified that the SIM is not malfunctioning, as it works just fine in my old android devices, and my T-Mobile Samsung GT-E1190.

-The phone was boxed, and contained an Orange booklet, so it was locked to Orange at some point (Or still is)

However it accepts my new SIM.

Any suggestions?
[General Questions and Answers] Zxalilh:
Maybe the modem was flashed with the wrong firmware it wasn't meant to be flashed with? It might be that the CPU and modem fail to successfully communicate leading to the device rebooting itself.
[General Questions and Answers] Woodland586:
Except for the E908 (Which is the Chinese(?) release of the E900) any firmware should work as long as it's for the E900. I'm specifically trying to flash the UK ones as the phone originally ran on UK firmware (E900XXFG1)

Even flashing the original firmware (Which i dumped myself as it's nowhere online) has the same issue.

Here's specifically what's happening (Apologies for the horrible recording, and the struggle with focus throughout the video)
[General Questions and Answers] Woodland586:
So I figured something out. The E900's fine. Nothing wrong with it.

Turns out there is something in my neighborhood area that's the cause.

I've discovered that once I leave the neighborhood area, the phone works completely fine, until i go back into the area.
[General Questions and Answers] Zxalilh:
Very weird, unless the cell towers in your neighborhood have been changed/upgraded recently.
[General Questions and Answers] Woodland586:
I'm not sure, but the carrier's coverage checker shows that the coverage for the phone should be good. So i'm assuming that someone is unintentionally transmitting an interfering signal. What I find odd is that my Samsung GT-E1190 (Which is less capable then the E900, despite being newer) works completely fine in my neighborhood.
[Fire HD 8 and HD 10 General] ToadCultist:
emmc on my kindle fire hd 8 (5th gen) has decided to flip to a permanent write only state meaning that no changes I make to the device carry across after rebooting the device. I have been informed that this can occur on older devices and is essentially a corruption of the chip which cannot be fixed. Luckily bootloader is unlocked and TWRP recovery is working so I was wondering if it could be possible to completely bypass the emmc and run android directly from the SD card. Would even be willing to open up the device and mess with the internals if necessary. Hopefully someone can help me out here, thanks!
[Fire HD 8 and HD 10 General] ToadCultist:
Upon doing further research something like this has been attempted in the past. See here: https://xdaforums.com/t/how-to-boot...on-qmobile-z8-with-bricked-dead-emmc.3712171/

https://xdaforums.com/t/super-sd-htc-526-vzw-boot-run-android-on-sd-card-pre-rooted.3596497/
[Google Pixel 8a] Barmenchik:
Problems getting Android 15

Registered in the Beta testing program, the Google account says that A15beta2 is available. More than 48 hours have passed and the Beta version has not arrived. Any thoughts or advice?
[LG Optimus L3 II, L5 II, L7 II, L9 II] justajellybeanlover:
So I was trying to mod my L3 when I came across a janky APK to unlock the bootloader. I launched it, then my recovery was gone. Now when I try to boot the phone normally, it doesn't boot. To make it boot, I have hold the power, home and volume up buttons. But when I try to press the buttons for recovery, it doesn't go into recovery but hard resets the phone.
[LG Optimus L3 II, L5 II, L7 II, L9 II] Zxalilh:
I doubt you can revive it without unlocking the bootloader and etc...
[Galaxy Tab S2 Android Development] retiredtab:
Release Notes

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data in TWRP. This is known has a clean install. Backup your data before a clean install.

Jul 19, 2024

1. added sepolicies for apps that target SDK 27 and 29 access to vendor_file:file with rx_file_perms. If you're having problems with some apps showing a black screen after being installed, this might fix the problem. See

https://github.com/retiredtab/msm8976-common/commit/b8bfb8d0e61085d9088c1fb946f329004cfc14c3

Jul 9, 2024

1. Initial 21 ALPHA public release.

2. Incorporates Jul 5th security patches as per https://review.lineageos.org/q/topic:"U_asb_2024-07"

3. If you are coming from stock rom or an older LineageOS version (example, 18.1 or 20), you MUST format your data in TWRP. Remember to backup your data and verify that restore data works before upgrading to 21.
[Galaxy Tab S2 Android Development] retiredtab:
New build called lineage-21.0-20240709-UNOFFICIAL-gts210vewifi.zip

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data in TWRP. This is known has a clean install. Backup your data before a clean install.

Jul 9, 2024

1. Initial 21 ALPHA public release.

2. Incorporates Jul 5th security patches as per https://review.lineageos.org/q/topic:"U_asb_2024-07"

3. If you are coming from stock rom or an older LineageOS version (example, 18.1 or 20), you MUST format your data in TWRP. Remember to backup your data and verify that restore data works before upgrading to 21.
[Galaxy Tab S2 Android Development] cucumbersmell:
Greatly appreciate your work! Have been using your LOS20 builds since they started.

Trying to avoid any discussion about GAPPS, but has anyone who uses GAPPS been able to log in (Playstore, YouTube, etc)?

Let me know if I should start a separate post elsewhere for those of us needing the service.
[Galaxy Tab S2 Android Development] retiredtab:
I started a separate thread for the above. ALL discussion re gapps should be in this thread below.

https://xdaforums.com/t/what-gapps-...os-21-on-samsung-sm-t713-and-sm-t813.4682142/

I've also added this to post #1 and FAQ 12.
[Galaxy Tab S2 Android Development] cucumbersmell:
Much appreciated!
[Galaxy Tab S2 Android Development] Alex7779:
Hello,

just did a clean install.

Boots fine, but termux doesn't seem to work.

I tried both versions (beta 119 and 118.1) from termux github release page.

With termux beta 119 i get a warning that the app is built for an older version. if did "install anyway" and it installs - but when i open the app there is no text and no termux toolbar shown.

Termux 118 installs without warning but has the same problem. just black screen and keyboard is shown. no text.

When I flashed the ROM I also flashed Nikapps and Magisk. Can someone maybe have a look if termux works when flashing just the ROM?

(I also tried the adb-workaround from the gapps thread, but didn't work for termux issue.)

Thanks

EDIT: Just installed Gboard - then restarted Termux. now Termux works!
[Galaxy Tab S2 Android Development] retiredtab:
I get my termux from Aurora Store and it's version 2024.07.07 and I have no problems with it.

I just did add some new sepolicies to address older apps that target SDK 27 and 29 that were having black screen issues. I've made the same changes for SM-T813 in the July 19 build which will be posted shortly. See

https://xdaforums.com/t/unofficial-...or-sm-t713-jul-19-2024.4681952/#post-89618387
[Galaxy Tab S2 Android Development] retiredtab:
New build called lineage-21.0-20240719-UNOFFICIAL-gts210vewifi.zip

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data in TWRP. This is known has a clean install. Backup your data before a clean install.

Jul 19, 2024

1. added sepolicies for apps that target SDK 27 and 29 access to vendor_file:file with rx_file_perms. If you're having problems with some apps showing a black screen after being installed, this might fix the problem. See

https://github.com/retiredtab/msm8976-common/commit/b8bfb8d0e61085d9088c1fb946f329004cfc14c3
[Galaxy Tab S2 Android Development] yoshkapundrick:
Novice question:

You stated "Stock camera doesn't work at all (reason i and ii). Starting with LineageOS 19.1 and higher, camera API functionality (pictures and videos) isn't even recognized by the OS."

I have the T810 and the camera works well with your LineageOS 20.

Are the drivers far different for both cameras?

Thanks.
[Galaxy Tab S2 Android Development] retiredtab:
The 813 and 810 are completely different CPU/SoC architectures with completely different drivers for everything (sound, gps, graphics, camera, etc).
[Galaxy Tab S2 Android Development] FordPrefect:
Did a clean install over the LOS 20 and re-did the setup for my applications. So far it's working nicely! Thank you so much for bringing LOS 21 to our old devices!

I have on question though. Using the osmand maps and navigation. They have a setting to use opengl for the rendering engine. This does not work on the new build. Is opengl supposed to work?
[Galaxy Tab S2 Android Development] retiredtab:
In Android 12, AOSP deprecated the gles render engine in favour of skia.

Unfortunately, Android 14 removed all that gles code in the frameworks/native branch and bringing back gles might be impossible due to the sheer number of changes.

So currently, there is no gles in this build. It's using skia. That's why I wrote in post #1

8. AOSP has been making MASSIVE changes each Android 14 QPR release. Each QPR release breaks something and there's no guarantee that I can make the next monthly security build.
[Galaxy Tab S2 Android Development] FordPrefect:
I see, thanks for the explanation. I didn't connect the dots for that.
[Galaxy Tab S2 Android Development] FordPrefect:
Guess I found a problem ... When I go to Settings -> Display size, and make the display size one tick smaller, it works as expected. If I tune it down one more tick (two ticks as compared to the default), the device reliably is sent to a boot loop. The only way for me to recover was to do factory reset from TWRP:

Just wanted to leave that here for others to see.
[Galaxy Tab S2 Android Development] retiredtab:
Yes, I can reproduce on both T713 and T813. At first glance of the logs, I can't see anything obvious, but this is an area where I usually don't mess around with.

Right now, I've included the above bug in post #1 on the T713 and T813 thread. I can't guarantee that I can fix it.

PS. You don't need to format data in TWRP. I just restored my TWRP backup and it was able to boot fine after. If you don't have a TWRP backup, a wipe data should suffice.

I suspect the wipe data is needed because the OS writes the new display size to the /data partition and then the crash occurs immediately after. Now that the display size is saved to /data, once the OS reboots, it stays at infinite boot animation.

It's strange that moving the setting up notch UP or once notch DOWN works, but not two?

In addition, this bug does NOT happen on my LineageOS 20 build.
[Galaxy Tab S2 Android Development] cucumbersmell:
Will the workaround for the memory leak posted in the N7 (2013) forum work for this ROM?

https://xdaforums.com/t/rom-flo-deb-unofficial-lineageos-20-0.3569067/post-89503721
[Galaxy Tab S2 Android Development] retiredtab:
Most likely, but I'm using DuckDuckGo so I don't have that problem. You can try and report your findings.
[Android Stick & Console AllWinner based Computers] MrLabeeb:
Hello everyone,

I wonder where I can find TX9 Pro Game box firmware/games, as my TF memory card is damaged, and I really appreciate it if I can find an image of it.

I tried to search for it on the internet but no luck, All what I could find is a link with its specs on Alibaba.

Link: https://www.alibaba.com/product-detail/Newest-TX9-Pro-Game-Box-4K_1600819803009.html

Device specs:

Product model	TX9 PRO

Product category	4k Android TV+game
Master frequency	AIIwinner H313 Quadcore cortex-A53 frequency ：1.3G
Memory performance	DDR3 1GB
External TFS are supported	Expandable to 128G
Game content	64GB:10000
128G：15000
Support game	arcade(CPS;FC;GB;GB-A;GBC;MD;SFC,PSP,CPS1,CPS2 )
Function key	Infrared remote control Bt gaming controller
Use interface	HD output, 1080P, 4K60FPS
Voltage input	5V/2A
Packing quantity	40Pcs
Color box size	26*17*7CM
Outer box size	61.5*34.9*38.9CM
Unit weight	About 0.65KG
Gross weight	26kg
Other parameters	Support wireless handle, one drag two handle/support four people online matchmaking

The memory card is 64 GB, so the image should be around that.

If it is hard to find it, then what should I do to get any retro classic games on the box? Will custom firmware work? Any ideas?

Thanks in advance.
[General Questions and Answers] shaneoh:
Hello,

This is my first post on this forum, so please move this if it is needed.

I manage a good amount of mobile device for the company I work for. We have a specific model of Android devices running 9.0 and within this past week they are all being flagged as rooted with Microsoft. (outlook, teams, etc.) These devices have been working for years without issue and I am know wondering what is causing them to be flagged.

There have not been any modifications to any of these devices. If I install TB Checker, Basic Integrity = pass, Device integrity = fail, strong integrity = fail. Root checks all pass. I am assuming this is why the devices are being flagged by MS and reporting as "rooted" and being blocked.

Is there anything simple I can try on these devices? Did Google possible come out with a update to Integrity that these devices just not longer pass now? I am really confused on how all these devices have been flagged within the week.

Thanks in advance for any help and/or advice!
[General Questions and Answers] EllieCat:
is developer options and USB debugging enabled?
[General Questions and Answers] shaneoh:
Developer options are not enabled. If we enable, USB debugging is default off.
[General Questions and Answers] EllieCat:
even a factory reset?
[General Questions and Answers] shaneoh:
Yes we have factory reset a few times, no fix.
[General Questions and Answers] EllieCat:
clear cache and cookies

It's a known problem with Microsoft apps.

Redirecting