yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S10+ Accessories] crazzter:
I'm looking for a slim case which has a cutout that allows a wrist-strap to be attached (the kind of strap you'll find on pocket-cameras etc.).

I'm usually using a neoprene pouch for my phone so it should be fairly slim. I'm using a Panzerglass screen protector. The closest that I've come is Otterbox Commuter but I'm not sure if it has the required cutout? Any suggestions?

Purpose of the strap is to minimize the risk of dropping it in concert-crowds, on a boat in rough seas or whatever kind of trouble I might be getting myself into :)
[Samsung Galaxy S10+ Accessories] Jithj45:
Case for s10+

I use the atouchbo case, great protection and has holes for a strap, almost similar to the Spiegen air pocket protection
[Samsung Galaxy S10+ Accessories] moSess:
RhinoShield CrashGuard. Hands down the sexiest as well. Minimal profile with excellent protection. Plus a cutout for a wriststrap. I love it.
[Samsung Galaxy S10+ Accessories] LibertyMonger:
The Ringke Fusion is the best
[Google Pixel 3 XL Questions & Answers] wincaffeine:
Hello guys.

I just bought my Pixel 3 XL phone straight from the Google Store and it just arrived two days ago. After learning about Android Q, I opted-in on the android beta and downloaded the Beta 6 OTA update to my phone. The phone downloaded the OTA and installed it and it seems all is well until the moment it rebooted. It didn't turn on again. It won't turn on. I tried to force restart it by pressing the power button 10 seconds, 30 seconds, or even 1 minute+, won't turn on, no haptic feedback, nothing. I even tried the power button + volume down combo. I also tried plugging it to the original charger it came with for 30 minutes, nothing.

Before this, I have experience with flashing stock and custom roms with pixel devices and other brands (I have owned the OG Pixel until it wont boot due to its motherboard issue), and while normally, I could have just unlocked the bootloader and installed the beta firmware thru fastboot/recovery, or even installed a custom recovery, I didn't and instead tried the OTA update thingy (which claimed that you don't have to unlock your phone or anything). I didn't expect that it will brick this early and unexpectedly.

My suspicion would be that the OTA update broke the bootloader itself, or the firmware that loads the bootloader, thus not responding to the power button correctly. It's also not a power problem, because the phone warms up when plugged to the charger. Also, I download and applied the OTA while the phone is charging (around 70%). Could that also be the culprit?

I'm at my wit's end here. I'm thinking I should RMA this phone, which I haven't done before. Are there any similar issues like this before? Did anyone else had similar issues like this one?
[Google Pixel 3 XL Questions & Answers] boe323:
Plug the charger in and hold all 3 buttons together, not saying it will work but worth a try, it deletes battery stats and cache, if it does boot then keep hold of them for about 40 secs, hold them for over ten seconds even try for a whole minute, this sounds like hardware fault to me though. Also, if youve just bought it, swap it.
[Google Pixel 3 XL Questions & Answers] wincaffeine:
I have tried what you suggested. Still nothing.

If I can I'd try to resolve this without returning the thing but yeah, it may really be a hardware fault. Guess I have to wait for a miracle to happen (like the phone turning on by itself after several hours, like with some posts that I have found around).

If all else fail, maybe I'd just ask Google to replace it.

Thanks anyway :good:
[Google Pixel 3 XL Questions & Answers] kentek:
You may want to try to see if you get a USB notification from your computer on Windows and if it does try to flash it Back to stock. Hope it works
[Google Pixel 3 XL Questions & Answers] wincaffeine:
I also have tried that to no avail. The phone won't just turn on. Anyway I already returned the device. Thanks
[Google Pixel 3 XL Questions & Answers] boe323:
Have you tried making an edl cable, to see if the phone boots to qualcomm flash/diagnostic mode. I dont understand why no one in this thread as mentioned EDL mode, its a life saver for when you brick your device. This allows a full factory image flash through qualcomm flash mode. Plenty of tuturials on internet for EDL. (Emergency Download)
[Google Pixel 3 XL Questions & Answers] ccalixtro:
Because of warranty?
[Moto Z Questions & Answers] juan518:
The phone wouldn't hold a charge so I swapped the battery with a new one and everything seemed ok, but now when I try to take a photo the phone shuts down and won't start until I plug it into the charger, the problem seems to happen with any camera app I tested (stock, gcam & Instagram) and not even flashing a different ROM fixed it (was using lineage and flashed the stock Oreo ROM using RDS lite).

Has anyone faced this issue?
[OnePlus 7 Pro Questions & Answers] bj8622:
after updating to android q dp3 on my t mobile version of one plus 7 pro to get my bootloader unlocked i restarted into fast boot to install twrp and i followed multiple post of people doing it but i get the error msg below or it says the same thing but it says success. i even tried fastboot flash boot twrp.img. after doing it i restart and it goes right to fastboot and not twrp. Do i have to downgrade out of dp3 first? im stuck any help would be appreciated!

C:\adb>fastboot boot twrp.img

downloading 'boot.img'...

OKAY [ 1.209s]

booting...

FAILED (remote: unknown command)

finished. total time: 1.211s
[OnePlus 7 Pro Questions & Answers] bj8622:
I forgot to mentioned that it worked the very first time and i got into twrp following the video on here xda posted but i failed to flash a custom rom and it was stuck in the splash screen when i installed havoc os rom and i used msm tool to revert back to stock and start over now i cant get twrp re installed
[OnePlus 7 Pro Questions & Answers] zams85:
you need atleast on oos 9.5.7 firmware to able flash twrp again
[OnePlus 7 Pro Questions & Answers] bj8622:
can i instALL TWRP if im on 9.5.11? right now im on the 9.5.1 downgrade from dp3
[OnePlus 7 Pro Questions & Answers] benny3:
Yes, also 9.5.10 works
[OnePlus 7 Pro Questions & Answers] walther1337:
What do you flash to get back to 9.5.10 or 9.5.11? Using the downgrade re-locked my bootloader.
[Android General] neonzz:
Hey guys,

I had an issues yesterday that have forced me to get the original firmware and reinstall it but it won't work end of story phone is in odin mode odin 3.12.3 seems stuck here's my Odin log

<ID:0/004> Added!!

<ID:0/004> Odin engine v(ID:3.1203)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Set PIT file..

<ID:0/004> DO NOT TURN OFF TARGET!!

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> SingleDownload.

<ID:0/004> sboot.bin.lz4

it's been like that since 1am this morning and odin just says "Set Partition" at the top anyone know what's happening?

EDIT: Download mode just came up with VBMETA:ERROR verifing VB META VBMETA: no sign info
[Android General] neonzz:
Fixxed

This was resolved using odin 3.13.1
[Moto E4 Plus Questions & Answers] rozhack:
Hi, I want to ask some questions to you guys. Can somebody help me!

I have exposed in my Moto E4 Plus xt1770 Nicklaus. I trying to mod my battery icon, so I extract the framework.apk file in folder system, I changed the battery icon, and make new framework.apk (my mod), I replace and reboot. After boot I found nothing changed. I really confused from where the device get the default battery icon, because I had replaced that. But some is more interesting is, after that I can mount my data/system partition (I forget about data or system partition) in twrp, so I can't restore that with twrp. My device is work, but I can mount some partition in twrp so I think should be some trouble. Any way I have another case. I get flash my device. After that I rooting with magisk and install Xposed again, now I try changing boot animation. I replace the boot animation.zip in system/media and reboot. But I got the boot animation is not changed, from where the device got the default video, I had replaced . Any way I sure my procedure from all modding I do is right. So I start to thinking. I think Xposed can manipulate the system UI and framework,

so I wanna know are modding framework apk or systemui is have different way for device with Xposed n device without Xposed?

Sorry if my explanation is not clear, but can someone to help me for understanding what going on. Thanks:rolleyes::laugh:
[Moto E4 Plus Questions & Answers] rozhack:
I just flashing my phone, so I don't have XPosed in my phone. After rooting I tried replace bootanimation.zop in "dev/system/media", after reboot I found my boot animation still default. But deferent when XPosed installed in my phone, in case without XPosed, my phone doesn't have any issue like, Bluetooth share stopped, systemui stopped. I got my phone very normal after I'm using for couple hours.

So now I think I do wrong modding procedure,

*Are true if you want to change battery icon, you can do it with modding framework.apk (replace the default icon)?

*Are true you can change boot animation with replace boot animation.zip in "dev/system/media"?

I do that, but all still default. Huft...

I think, I don't wanna modding it any. :rolleyes:

Actually I have made my own battery icon. I really want to use it. You know, I'm newbie. So it's so difficult n much time to made it .But now I give up, I got stuck.
[Android Apps and Games] Noglin:
Hello,

I use an Samsung Galaxy J2 Prime, and i've been trying to connect to the whatsapp web through the Opera browser(also tried with the Edge Browser and Chrome Browser), but i cant the problem is that the cellphone cant read the QR code, i've already tried to restart

my browser, cellphone, clean the lenses,monitor , restart my internet, i've already checked my connection, flip my phone upside down, my whatsapp, browser, android is up to date and it also dosen't work on others computer, but if i try with other phones, it

works

What else could be the problem?
[Xiaomi Mi A1 Questions & Answers] jubayertonu:
I need mi a1 July 2019 letest patch file for root my device
[Xiaomi Mi A1 Questions & Answers] zkoz:
I think this is for you:

https://xdaforums.com/mi-a1/how-to/guide-rooting-mi-a1-twrp-wiping-post-t3824550
[Moto G4 Plus Questions & Answers] Zedlav:
I've had my G4+ rooted for quite a while and i need to format it so my mom can have it since I recently changed to a OnePlus 6T.

I tried to use the factory reset from the settings (seems like it was a big mistake on my part) and it didn't work, so I'm now trying to flash a stock rom through adb (I'd done this before), but I don't know what I need to do at this point, I'm at a loss, I even tried the commands to flash the rom and it seems to copy the system files but some stuff fails in the process.. I don't know what to do, did I just brick my device? please help :(

In case that helps, I have TWRP installed

And I think this might help, I personally don't know what to do with this info but this is what the command prompt throws back at me when trying to flash the custom rom while in bootloader mode:

Also, I tried wiping system, data, cache and dalvik-cache and here's what TWRP says: TWRP Errors

I get similar errors when trying to install my stock zip (from the external sd, I don't have an OTG cable right now so I copied to the sd card)
[Moto G4 Plus Questions & Answers] manjaroid:
Is it possible the bootloader was re-locked with fastboot?

What's the ROM version you're trying to flash? Assuming TWRP hasn't been replaced by stock recovery and you can still load it, it would be interesting to know what kind of errors happen if you tried a TWRP flashable ROM instead of a fastboot ROM. Use the phone's internal storage (/sdcard directory) and avoid using an external SD card. But first see if you can both format and wipe in TWRP without errors.

You don't need an OTG cable for any of this. To simplify trouble shooting, eliminate the external SD card even if temporarily.
[Moto G4 Plus Questions & Answers] Zedlav:
I'm trying to flash a stock ROM from this thread: http://xdaforums.com/moto-x-play/general/official-stock-firmwares-added-xt1562-t3195364.

I'm still using TWRP, it wasn't replaced by stock fortunately. I'll download one or two flashable roms and see if that works.

Also, just tried to go through the process of unlocking the bootloader (in case it was re-locked as you say), and when putting the unique key and all, it says:

(bootloader) invalid boot state

And something I missed to mention now that I think about it, upon booting the phone it doesn't show the usual unlocked bootloader warning, instead its all black and it just says: "N/A" literally.
[Moto G4 Plus Questions & Answers] Zedlav:
Now, upon trying to flash a TWRP flashable ROM, specifically "AFH" from the Nougat 7.0 section of this thread, I got the following:

Image 1

Image 2
[Moto G4 Plus Questions & Answers] manjaroid:
I'm curious why you installed Moto X Play firmware to a G4 Plus. Or was the URL above a mistake and you meant this one?

https://xdaforums.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138

---------- Post added at 10:33 PM ---------- Previous post was at 10:02 PM ----------

That error indicates your bootloader is already unlocked. Flashing errors probably mean you're attempting to flash outdated firmware which sometimes causes problems with Motorola phones, so best to use the same or newer firmware than what was previously installed. See what happens with Oreo.

I suggest starting from scratch as cleanly as possible. I would even re-flash TWRP (official for G4 athene) for extra measure. And note the TWRP instructions about rebooting back into TWRP before flashing your Android ROM to avoid having to repeat installing TWRP. Also, the /system partition needs to be read-only if and when TWRP prompts you about it.

Format and wipe as described here: https://andi34.github.io/faq/faq_twrp.html

Then with the phone in fastboot mode and connected to your PC, flash the latest fastboot 8.1.0 ROM which will replace TWRP with stock recovery. If Android starts and runs normally after that, you should be able to re-lock the bootloader and hand it off to your mom.

You'll see the N/A notice on the boot screen when booting into recovery or a custom ROM is booting. Once stock is running N/A should go away.
[Moto G4 Plus Questions & Answers] Zedlav:
Oh god, I had been using the wrong rom all this time LOL, but it was working, I mean, before all of this I had flashed that x play stock rom on the g4 plus and it was working without a problem for some reason..

Alright, so I reflashed TWRP, did the whole format and wipe thing: Format results Wipe results

I'm downloading the 8.0 image from the stock thread you linked me but its going to take a while, the servers seem to be very slow. In the meantime i tried flashing the twrp-flashable one I downloaded earlier: Image 1 Image 2 Image 3

It would seem it went okay, but I rebooted and nothing changed, so I tried flashing the X Play image i had as I had done before, but I still got errors in the process and it didn't work:

When I'm able to download the stock g4 plus image from the thread i'll try with that one and post my results, but I still don't understand what's going on
[Moto G4 Plus Questions & Answers] manjaroid:
First off, whether you're flashing stock or custom, you need to stick to firmware specifically for Moto G4/G4 Plus athene. Just because firmware from a different Moto booted your phone doesn't mean it's working. Ditto for TWRP so make sure you're using the official release for G4 athene. An unofficial fork of TWRP probably won't do any harm, but for trouble shooting a stock Android install, there's no reason to stray from official TWRP.

Verify that this ROM is version 8.1.0 build OPJ28.111-22 or the more recent build OPJ28.111-22-1. If the ROM is literally version 8.0 that's not right.

Based on your fastboot errors, I'm wondering at this point if partitions have been mangled and even the correct firmware isn't going to flash successfully. Even if the phone boots and everything appears well at first glance, you could find out something is terribly wrong. Like the radio not working because EFS partitions (IMEI) are messed up.

Right now I'm not sure how to advise. I'm tempted to say "blankflash" but I don't think you're there yet because the phone is starting and you can load recovery. Let's hope somebody with more experience chimes in.

For now I suggest disregarding TWRP flashable ROMs and plan on getting through this with adb and fastboot.
[Moto G4 Plus Questions & Answers] Zedlav:
I decided to give it another try, from the start:

Formatted data, then dalvik + system + cache, no problems, no red messages or anything lol

Then, reflashing TWRP:

I guess that's.. not 100% okay but.. alright.

Now, as usual, bunch of errors while flashing:

Now, it says ID: bad key instead of ID: N/A, and there's the android mascot with its belly open saying: No command.

So yeah, didn't work.. I guess I'll look into the blankflash process but I have never done that before

EDIT: weird af thing just happened, I started the blankflash.bat from the guide while I was in fastboot but it was kinda stuck in "waiting for device" so i decided to close and reboot, and now it seems to be loading with the moto and lenovo logos... Now it seems to be working properly lol, this feels weird
[Moto G4 Plus Questions & Answers] manjaroid:
After a clean install like this the first boot-up can take abnormally long. You probably just needed to wait it out. So is the phone starting and running now?

TWRP's output appears scary at first but looks like it flashed normally. All those "not found" messages during the ROM flash were followed by a bunch of "OKAY" messages. And I see that you flashed recovery.img which overwrote TWRP, so you must have seen the Android mascot in bootloader mode at some point during a reboot. All good!

If the phone is booting normally with stock recovery installed, you're ready to re-lock the bootloader if that's what you want. When the bootloader is locked the N/A and/or bad key notice will disappear along with Moto's unlocked bootloader screen. (I had it wrong in my other post; "bad key" is displayed when booting custom ROMs and custom recovery, where "N/A" is a normal part of the unlocked bootloader screen.)

Btw, blankflash is for devices that are hard bricked but you weren't even soft bricked (except for the brief time immediately after format). It's a last resort when phones play dead or partitions are scrambled. I'm glad to hear you stopped it before it did anything.
[Moto G4 Plus Questions & Answers] Zedlav:
It seems to be working fine now, but there's an issue right now that I don't understand.

It only boots into the system if I go into the bootloader and restart from there. I had powered it off to save battery and powered it on right now, it goes straight to the android mascot thing with the belly open along with "No command" text. At that point I go to bootloader, click on "Start", then it boots up with the moto and lenovo logos and sounds.

From what I gather i'd say it isn't getting the command to boot up android when powering on, but no idea how to change that. I need to fix this because I know my mom will not be able to reproduce these steps in the case the phone powers off for whatever reason... Any ideas?

And also, thanks a lot for all of your help!!
[Moto G4 Plus Questions & Answers] manjaroid:
Here in the forums there should be a lot of discussion about all kinds of devices with this same problem. Solutions vary depending on what caused it.

First try a couple of cold restarts. Power off and let the phone sit a few minutes before each start up. If the system still isn't booting try clearing Dalvik cache, power off and start back up. If you're still booting straight into the bootloader try flashing the ROM all over again. You don't need TWRP recovery for this, just flash while the phone is in bootloader mode.

By chance did you flash the 7.0 Nougat ROM? If so try 8.1.0 Oreo. There are bootloop issues with Moto phones that have been downgraded.
[Moto G4 Plus Questions & Answers] Zedlav:
I've been using the 8.1.0 Oreo rom. Before all of this happened it used to have a 7.0.1 rom (which I noticed it was the X Play's rom after all this time lol) and never got updated.

I flashed TWRP to wipe Dalvik, did that and rebooted, it didn't help, and after that I couldn't reach TWRP recovery through bootloader. So then I re-flashed the rom (this time changing the recovery line to flash twrp instead of stock), but nothing changed, I still can't boot the phone without going through the bootloader, not even through TWRP's Reboot > system.

Sorry I took a while to answer back, its been a busy couple of days
[Moto G4 Plus Questions & Answers] manjaroid:
Sorry, but right now I'm stumped on what to try next. You don't want to duplicate this post but you might consider starting a new post on the topic of flashing the wrong firmware. I still wonder how that may have affected your partitions.
[Moto G4 Plus Questions & Answers] manjaroid:
If the fight is still on, maybe this post is pertinent to your problem installing stock Android to your G4 Plus.

https://xdaforums.com/showpost.php?p=80118362&postcount=1442

Fingers crossed.
[Samsung Galaxy S10 5G Accessories] ChrisAC84:
I really enjoy using the 25w charger, but the cable that came with the S10 is just so short. What's the best option for a longer cable, that would still allow for the 25w fast charging?
[OnePlus 6 Questions & Answers] Jaris443:
If I already have a pin and use that primarily, however I want to use the fingerprint scanner to make life easier. Will I have to take off the fingerprint each time I boot into recovery mode and use TWRP? Or can I use the pin and fingerprint together with no problems?

Any feedback would be much appreciated thank you.
[OnePlus 6 Questions & Answers] SimplyMisfit:
You can keep both, however you can unlock TWRP only by PIN.
[OnePlus 6 Questions & Answers] GuestD2559:
You can. You'll still need your PIN to decrypt /data in TWRP. And why are you still running 9.0.5? We're on 9.0.8 now.
[OnePlus 6 Questions & Answers] Jaris443:
Because I dont know how to update my phone once rooted without doing something wrong just didn't want to mess about with something I don't know I've rooted my phone's in the past but never updated my phone after cos people say it messes up.
[Xiaomi Mi 9 SE Questions & Answers] Martinperreault:
I am a big fan of my Mi 9 SE. But there are two things that disapoint me:

1. The MACRO MODE never made it (yet) to my device. I have MIU global stable 10.3.4, and there is no macro mode tk be found... :(

2. The lack of PRO VIDEO MODE in the camera is very puzzling to me. PRO MODE is already present in the camera, why not for VIDEO too? If Xiaomi does not intend on adding pro video, at least they could release the SDK for other devs to have access to all lenses, so we could use alternate Camera Video Apps that have full manual features....
[Xiaomi Mi 9 SE Questions & Answers] elpaablo:
Now that we have optimized kernel for battery, I think the weakness of this phone is video recording which is too unstable.
[Xiaomi Mi 9 SE Questions & Answers] afylioe:
Still no pro mode for video even on the latest MIUI 11
[OPPO Reno 10x Zoom Questions & Answers] n-j-f:
I've just ordered the 256Gb Reno 10X from Amazon Spain which they are shipping internationally to me. The website does not make it clear, and they do not seem to be sure, whether the one they have is the Chinese or International variant. Will it be obvious when I get it which it is - the model number on the box or anything else? How can I tell?
[OPPO Reno 10x Zoom Questions & Answers] Fir3blade:
Amazon Spain will ship the international version usually, of course you will see what version is inside the box once you got it.

Chinese version is PCCMOO, international should be something with CHP1919 or something like this...