yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze General] hellz:
So I guess I'm the only idiot that's dropped his Fuze... Well maybe not the only, but the first that dropped it in such a way to not cause any (visible) physical damage, but enough to make the phone inoperable. Fair enough, I can accept the Dunce cap for this one.

The Phone works, receives calls/messages, even sync's with Activesync. Just one problem, The screen is black. The backlight turns on, but no image is displayed. Not even any of the boot screens. Sounds work, I sync'ed up all my data, everything seems fine, except for the screen.

So here is my Dilemma: Is there anything I can do to fix the phone? Or Am I going to have to re-flash the device to factory settings and try to call att/htc to get a replacement for a device that "just stopped working"?

I'd rather fix it myself just to avoid dealing with the carrier/manufacturer, but if that's my only option than so be it. Please Advise.

Thanks for any advice in advance.
[Touch Pro, Fuze General] CarlCastro:
You can try MyMobiler:

http://www.brothersoft.com/mymobiler-116759.html

But there might be something to accept/allow on the cellphone itself to see the screen. So maybe you can navigate to something on your phone to get it to work. Other than that, I have no idea.

Good luck, maybe reflashing doesn't seem like too bad of an idea.
[Touch Pro, Fuze General] mymimi111:
sell it to me, its broken
[Touch Pro, Fuze General] Scrtcwlvl:
Happened to my Kaiser, screen was white though, rather than black.

Take all the data off you can with MyMobiler and reflash a stock rom. Should still be covered under warranty. I did the exact same thing with my Kaiser.

Flashed the standard ATT upgrade rom, brought it in to warranty replacement and said the screen randomly turned white.

In and out in a few minutes with a new Kaiser. He made me keep my old battery back.

Because it is a problem where no physical damage is apparent, it will be difficult for them to determine if it is simply a manufacture defect where the screen went bad or if it is user accidental.

I actually dropped my Fuze for the first time last night (or this morning, I dont recall). My best friends girlfriend clothelined me while I was texting and the phone went flying, back fell off and battery chucked out. Slid across the ground for a bit. A tiny dent in a corner and some nice scratches on the stock screen protector, other than that A-okay. Invisible shield helped quite a bit ^.^

(I use invis body shield and stock screen protectors, the IS is a strange texture and too grippy for a screen protector)
[Touch Pro, Fuze General] darfri:
I have dropped my Touch PRO about 5 times to tarmac while getting out from the car but nothing happened yet
[Touch Pro, Fuze General] tvos:
do you have insurance on the phone? if you do, then its covered otherwise it is unfortunate.. all new phones, especially ppc's I insure with my local SF insurance.. that is the rule.

tvos
[Touch Pro, Fuze General] hellz:
Same exact thing happened to me minus the clothesline. Landed on the corner, back and battery popped out, powered it back up and black screen of death. Didn't want to wait till tomorrow to get it replaced but oh well, I'll be even more careful than I already am with it. I just need to reflash it to the stock ROM/SPL now. Thankfully I still have my Tilt as a backup.

I do have insurance, when they offered it at the Store I almost said yes before the rep finished explaining it. So I'll just reflash it to a stock ROM/SPL and get it replaced tomorrow.
[Touch Pro, Fuze General] maxh:
If you guys have the fuze through AT&T then you can get warranty replacements quite easily as long as there isn't obvious physical damage suggesting user abuse, ie no crushed screens, liquid damage, etc.

Someone here might suggest that this is unethical abuse of the warranty exchange system, but I will vehemently disagree! Cell phones should absolutely be able to withstand occasional drops from pocket level to concrete, as this is a quite common occurence. Hell, my laptop was designed to be able to take a fall from a table top.

So I would suggest you call AT&T and tell them your screen just stopped working one day. Say you've done a hard reset and everything else they'll suggest you try, and they'll send you a refurb in the mail with a box to send yours back in. I would suggest reflashing the stock rom and spl before returning, though.

BTW, if I were to guess about the cause for the inoperable screen, it would be that the lcd connector came loose in the jolt from the fall. So if for some reason warranty exchange isn't an option, perhaps you could venture into the guts of your device and try firmly reseating the connector...
[General Questions and Answers] Xyberdude:
So guys twrp wasnt able to mount data for me so according to a hovatec guide i tried to edit my fstab to allow data encryption for twrp but upon doing that the fstab became empty and now my phone is in bootloop of the rom im using its stuck there. anyone knows how to fix it and possibly without losing data, thanks.
[General Questions and Answers] xXx yYy:
Reflash stock ROM to get rid off of all changes you applied.
[General Questions and Answers] Xyberdude:
i

will try flashing stock vendor img if that doesnt work then ig i iwll
[General Questions and Answers] Xyberdude:
well i flashed stock rom had no other choice lol
[Redmi Note 8 Questions & Answers] djnfjgsod:
do you know which site/server stored the installation files of Lineage os for Redmi note 8? because their official site already paused the support for this device.

View attachment 6082256
[Android TV General] Atalitee:
I have an x10 max x4 android box device. Unfortunately, I cannot install the ROM. Because the computer sees it as an unknown device.please can you show the pin short in the pictures?Thank you very much.
[Paid Software Announcement and Discussion] motolollipop:
I'm excited to announce the release of my latest game, a thrilling and entertaining platformer game that will keep you hooked for hours! This game is designed to bring joy and excitement to players of all ages.

{Mod edit: Thread closed and link removed. Oswald Boelcke, Senior Moderator}
[Paid Software Announcement and Discussion] Oswald Boelcke:
Thread closed! I'm sorry but you are not qualified (yet) to publish paid applications on XDA.

Regards

Oswald Boelcke

Senior Moderator
[Upgrading, Modifying and Unlocking] sawlwin:
Hi,

Is there any software to unlock HTC G1?
[Upgrading, Modifying and Unlocking] borce_razor:
Still nothing
[Upgrading, Modifying and Unlocking] ICBM:
Hey,

I wanted to take a look at unlocking the Dream (G1), but unfortunately I don't know much about this particular issue (although I'm not bad at other unlock algorithms). Can you point me in the right direction as far as where to get familiar with how unlock codes are constructed (and therefore deconstructed). I saw the thread about the all-in-1 unlocker, but it doesn't cover how they actually got to this point.
[Upgrading, Modifying and Unlocking] ljlam:
Hello there so still no unlock tool for this great G1 until now ?
[Upgrading, Modifying and Unlocking] Neoanderson:
only boxes

for now only tool in commercial boxes for unlocking not free
[General Topics] HippoMan:
Many of us Android modders have been suffering as a result of Google's "improved" (ha ha!) play integrity restrictions that have appeared in recent months.

Given that Google hasn't yet blocked all spoofed fingerprints, there is a lot of wondering going on about what is actually on Google's mind (such as it is) about how spoofed fingerprints are chosen to be blocked.

Perhaps there is a Play Integrity Guy (aka "PIG") who makes the fingerprint blocking decsions, in which case, many people wonder what this PIG's methodologies are for making the blocking decisions.

Or perhaps Google management are out to get modders, but don't know how to properly do so without some fingerprints slipping through the cracks.

Or perhaps Google management are just deliberately toying with modders.

Or perhaps Google wants to help modders, and they deliberately putting out obstacles that will teach us to be better modders once we learn how to overcome these hurdles.

Or perhaps Google management couldn't care less about modders, and it may be that modders' woes are just collateral damage as a result of other, unrelated Google policies.

And there are dozens of other possibilities.

The purpose of this thread is to allow people to post and discuss their ideas, guesses, projections, fantasies, conspiracy theories, delusions, etc. about what are the *real* "how's" and "why's" of Google's Play Integrity restriction policies.

Have at it.
[General Topics] chiteroman:
If you unlock the bootloader of your device and install a custom rom without Google services, nor any bloatware/rootkit, companies would not make as much money as they could, as your metadata could not be sold. I already talked about it in a post on Reddit, it reminds me of 1984....

The answer is money, companies just want money, and to get money, they need your metadata.
[General Topics] sawdoctor:
Tbh i don't think Google want to get rid of modders or they'd just stop us unlocking the bootloader. We actually help them with security and have offered jobs to top modders.

In my opinion it's the banks credit card companies etc and Google have to be seen to be doing something, as osmoSis said with his conversations with Google employees they just want us to be a little quieter to make their life easier. If Google really wanted to stop us they'd just completely ban the fingerprint spoofing by enforcing GPU checks ( there's posts about this in the kernel string banning)and lock bootloader on pixel devices
[General Topics] HippoMan:
But then why are *all* fingerprints not blocked?
[General Topics] 4sz0m:
I have no idea, but might as well be related to US sanctions. They don't want certain functionalities to run on certain Chinese manufacturers' devices. But I have no idea, so I'm talking p**p here.
[General Topics] Skv012a:
Most definitely this, and absolutely what chiteroman said. One thing for sure though, it is NOT to actually protect our banking data demanded by the banks "protecting" our money from a slew of modern viruses that can get into unsecured phones, but that is a very cute cover for it.

Blew my mind that Sony openly allows bootloader unlocks on their phones, except the US market models....
[General Topics] HippoMan:
But then why are some spoofed fingerprints still allowed? It's a small percentage, but it would be easy for the Googlefrinchians to block *all* spoofed FP's.
[General Topics] Zytrel:
Google doesn't care about YOUR security. Lose your physical card, your problem. Get your Wallet hacked, Googles problem. The Bank will blame Google for advertising a service as "safe". Secondly, Googly might appear that they made it their priority to just cause as much hassle for any custom rom users (even unrooted ones) to use their apps. The reality is, they just don't care. The Integrity checkers have DL numbers of like 50k. No major company cares about such a minority.

Now there's two options for the X-print not being banned yet: Either they just want to collect more data, or they're actually kind and keep a (controlled) option open for us (unlikely).

Regards,

Zy.
[Windows 11] aathishiva:
Hi there, please anyone find and tell me a solution for "when i press the brightness button in my hp elitebook 840G5 laptop Hp HotKey Support popup will occurs. How to resolve it? can anyone tell me pls?
[Samsung Galaxy S22 Plus] halit42:
My device has the latest update. When I need to receive notifications from some apps, I don't get notifications on my phone. When I take the phone out of my pocket and turn on the screen, the notification comes.

The following settings are turned off on my device.

-Adaptive Battery

-Sleep unused apps

-Power saving

-Battery use in apps is 'Unrestricted'
[Touch HD General] Wolfenzi:
Hi, I got a problem which drains my batterry life. I am using my touch HD, then I put it on a desk, 10 minutes watching film on PC, then I look on my device again, and the display is still on. Why didnt it turn off ?

In settings, i have "turn off backlight if device is not used for 30 sec.
[Touch HD General] eaglesteve:
You also tick "turn off DEVICE is not used for X min/sec"?
[Touch HD General] Wolfenzi:
Yeah i figured it out already, that was the problem :-) I thought turn off device means it goes completely off like soft restart.
[General Topics] rregn:
Hello,

specifically I have the problem with a galaxy A7 SM-F750, Android 10, but it's probably a general problem.

The A7 comes with some pre-installed apps, including some that I will never need (excel, word, PP )

Nevertheless, I notice via settings / apps that these apps have been updated (I can then run uninstall upgrade)

I don't want this for 2 reasons:

1) the updates are then in the /data area and take away space for other apps

2) if there are apps in the >100MB range every few weeks, this unnecessarily burdens the flash, which has a limited lifetime ( for write operations)

when I google for a solution, I only find hints about the playstore - but I haven't set up a google account and therefore can't do anything in the playstore app, and it's only responsible for the apps that were installed via play!

This is also not about updates to the Android system, which I can manage in Software update. There is also an unclear option in the developer settings "update system automatically", but that is also off

Thank you very much

Translated with DeepL.com (free version)
[Redmi Note 11 (spes/spesn)] Lister Of Smeg:
Hi Sheist!,

This is a brilliant post, and Mods should sticky this to the top section of this forum for easy locating/reading. As this information is useful to all those who are new to this...

I thought it was bad when Samsung introduced Knox, but Xiaomi ARB just seems more worrying.

Why the end user isn't allowed to downgrade firmware easily is beyond me, same as what Apple have done... :(

So if the OEM borks the firmware, and introduces new/fresh bugs, you have to wait for an update to resolve it? No chance to downgrading to an older tried and tested firmware...?? As long as its stock firmware, should be able to go up and down as much as the user wants.

I can understand Xiaomi wanting to protect fraud, with certain firmwares... but surely block unauthorised higher firmwares, than stock lower firmwares.

But anyway, great post Sheist!.... as I often wondered about all the ARB info...

Cheers, Lister
[Redmi Note 11 (spes/spesn)] Sheist!:
In terms of firmware (vs ROMs), I too am concerned. I've seen a user brick the phone by installing the wrong firmware. The EDL accounts were "locked down" by the manufacturer to prevent an "easy solution" to this arb brick. To ordinary users, this means finding an authorized account, and of course, paying the fees. Why won't they just turn off arb like Google does when the bootloader is unlocked! o_O

Initial links from 2018 and 2020 suggested this issue ONLY affected a handful (perhaps 4 or 5 models) of older phone models from the China region, UNTIL the statement below was released: "Xiaomi arb has become obligatory on all Xiaomi smartphones starting Android 9." While "obligatory" does not necessarily mean "activated", it does mean any Xiaomi phone could be affected. Even 2018 and 2020 links (you can Google for the 2020 and 2022 links about this) stated their list of models can change at any time!

Xiaomi's Anti-Rollback Protection Explained: How to avoid bricking your phone

All Xiaomi smartphones and tablets will have anti-rollback protection enabled. What is it and how do you avoid bricking your device because of it?

www.xda-developers.com

[Guide] How to check the Anti Value of your Rom or a Rom that you want to install

Hello guys! I know this was much wanted in our community. For some strange reason, the "fastboot getvar Anti" doesnt work on Mi Max 3. it might say "variable not found" or "getvar failed / not found" this leads to people bricking their devices...

xdaforums.com

[Anti-Rollback] All your questions are answered here. - MIUI Feedback - Xiaomi Community - Xiaomi

[Anti-Rollback] All your questions are answered here. - MIUI Feedback - Xiaomi Community - Xiaomi

c.mi.com

Later searching found that list to be "increasing" slightly with no confirmed source about all the other models.

Apparently they discovered fraudsters reflashing some China hardware and selling them off worldwide as local region versions. Perhaps they used lower software versions that were vulnerable to issues. I stick with reliable providers, but it is always a risk to find out what you received. An example is the "selene" Redmi 10 appearance in fastboot when actually being a "selenes" sold in China as a Redmi Note 11: https://xdaforums.com/t/redmi-note-11-selene-help-unbricking.4557817/.

Why would this phone say it was selene in fastboot when it was a selenes release from China? I skip non-region phones and go only with Global versions, but one can never be sure what their provider is shipping until it is in our hands.

Opening the back and disconnecting the battery was an option the user above employed, but I've never opened a phone since we lost the ability to replace batteries ourselves.

It appears we are ROM-safe once we stop using the stock ROM. I am concerned about the firmware. I stick to the recommended version of the custom ROM, or I get the latest release from the xiaomi firmware updater site.
[Redmi Note 11 (spes/spesn)] Elinx:
As long you are on custom rom there shouldn't be a problem. If you are worried, don't flash latest firmware.

With RN8 I had indeed a problem with updating firmware once, that wasn't suitable for the new RN8 batch I had.

This was a mistake of Xiaomi, but a lot of these devices got bricked by updating the firmware to the version adviced for the custom rom.

Also staying with Miui is no guarantee to prevent a brick after updating. A locked bootloader and disabled USB debugmode and you are lost for sure.

All this has nothing to do with ARB. But a brick is a brick.

Imho main problem is what happens if you go from custom back to stock Miui.

You can't go from Global to China phone and vice versa

You can't go to a lower Android version (ARB) than the firmware version you have latest flashed.

So always keep some admistration what you have flashed from Xiaomi.
[Redmi Note 11 (spes/spesn)] Sheist!:
I see customs mention the firmware version to install (i.e. Lineage) or tell you to install the latest yourself, often step 1. (i.e.. "1. Download the latest MIUI 14 firmware for your region")

It has to be related to arb risk.

I remember having to do this:

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

[Guide] Unlocking Bootloader and Disabling VerifiedBoot

/* Your warranty is now void (or isn't ? who am I to judge ?) */ Finally, we got a shiny DeepTesting.apk that compatible with Realme 6 Pro. Thanks to barakcodam for leaking it, and Rizezky for providing a Google Drive mirror of it. Disclaimer...

xdaforums.com
[Redmi Note 11 (spes/spesn)] Elinx:
No, I mean flash the custom rom without updating firmware.

As said I had

once

a problem with flashing a recommended firmware version that turned out not to be suitable for a certain batch of the phone. As with ARB, Twrp doesn't any compatibility check.

If everything does work as expected you can decide to flash firmware or try another custom rom, which need maybe another version of the firmware.

Disable verified boot has to do with booting a modified or custom kernel. I don't read that much about that anymore.

Maybe A/B partitions have to do with that.
[Redmi Note 11 (spes/spesn)] Sheist!:
It seems to know which partition is active, historically:

platform-tools>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

Rewriting vbmeta struct at offset: 0

Sending 'vbmeta_b' (4 KB) OKAY [ 0.010s]

Writing 'vbmeta_b' OKAY [ 0.002s]

Finished. Total time: 0.053s
[Redmi Note 11 (spes/spesn)] Sheist!:
Some customs omit even basic install steps, which is annoying. But I get your point. We flash our phones and if the firmware borks, for whatever reason, we get the gift of what is left. :cowboy:
[Samsung Galaxy Note 10 Questions & Answers] rregn:
I got an Note10+ , N975F with FW N975FXXS9HWHA and FRP lock.

i could not bypass the frp, and while trying some tools, it happens that the note restarts , shows logo, then restart again, shows logo and now it is in a limited recovery

with shows:

can't load android system your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.

there are only 3 choices, try again , factory data reset, view recovery logs.

I tried reset several times, but this problem remains.

Also i flashed the N975FXXS9HWHA with odin, but it does not help

when google for the error, most posts say, do the reset and then everything is fine.

Can anybody help me to mae the note run again?

thanks
[Samsung Galaxy A8 (2018) Questions & Answers] gildarts1.1:
Hello,

My samsung galaxy A8(2018) suddenly stopped working and stuck on boot loop but not going to samsung logo. Tried volume up and power button it booted to samsung logo then restart again and boot loop. Tried to erase cache then start booting to recovery mode and took almost 30 minutes to get into recovery mode when I tried to go to recovery mode again. Then tried to factory reset took a while to load then took 10 to 15 minutes to "hash tree" command, rebooted again went through to samsung logo then came black screen message "verification invalid try to reset your phone to factory settings". Tried to drain the battery out, still in boot log and pc doesn't recognize the device as well. Tried to reflash the firmware from sammobile full of hope that it will make it work reflash was passed at odin. It reboot itself to recovery mode took a while at "installing new software" then changed to erasing took a while there as well then restart again and received the " encryption failed" black screen message to reset. Reset again then went to recovery mode "erasing", took its time there and recovery boot loop now from erasing screen to running some failed commands. Again volume down and power reset, stuck on erasing recovery screen again then booted and again "encryption failed".

Now I dont know what to do to make it work I tried whatever I knew or found by searching.

Help would be appreciated, thank you in advance.

Two pictures 1 with encryption failed and other recovery boot loop commands
[Samsung Galaxy A8 (2018) Questions & Answers] gildarts1.1:
Sorry if posted in wrong thread
[Samsung Galaxy A8 (2018) Questions & Answers] DaviVole:
have you tried reflashing the stock rom?
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] scamix:
Hi everyone, I have a strange problem with my Poco F5. Basically, sometimes the power button fails to turn off screen.

Currently, I'm running EvoX A14, but I've experienced the same problems on A13, Crdroid, and AOSP-SK.

Changing kernel doesn't resolve anything, tried with Magisk, with KSU, Silvercore, Melt and other (although I can't recall all of them precisely)

Additionally, I've tested different firmware versions including Global, Europe, A13, and HyperOS, yet none have resolved the issue.

It works perfectly on recovery (TWRP and CrDroid recovery), 10/10 tries

It worked perfectly on MIUI

On Rom it's fail every time I try to turn off screen immediately after I turned it on (1-2 seconds).

During usage, it fails 1 on 2, usually it works second times I press it, but sometimes it fails 3 times in a row

Please tell me how to investigate in this issue, tell me if you need LogCat or similar

Thanks.
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] sm00th4f3:
My only guess would be if the finger you used has a fingerprint registerd and that is is having some issue..

Otherwise, it might be your power button. Remember to really press the key and not just press it lightly