Database Develop

[Q] No Hard Reset

My HD7 is stuck on the start-up HTC screen. If left for a few mins. it goes to the screen showing Phone- USB cable -PC and thats it.
I tried hard reset: volume up/down held down + power on/off. No matter how long I hold these buttons down it does not go to the boot loader screen, infact it goes to the same screen as mentioned Phone-USB-PC.
When I hold down volume button + camera +power on/off the tri-colour screen appears for a few seconds but then does to the white screen saying "Enter USB Host Mode"
Zune comes up with error C101002E and trying to flash it with O2 rom the error 260, no comms
Can I do anything to restore this?
I've just found out it has no memory card! Would this stop it from booting past the start-up screen?
Yes I bought it as faulty, so I thought a reset would do it. Its not dead, far from it but I just need pointing in the right direction

Hold volume up + down at the same time and click power once while continuing to hold BOTH volume buttons...
If that doesn't work and u haven't hacked ur fone ibwould call for a replacement .... I'm sending mine back cuz mine is constantly freezing and rebooting by itself
Sent from my HTC Glacier using XDA App

Phone touch screen not working and phone won't turn off

Hi everybody,
So I have an HTC One M7 running Google Play Edition Rom and my touch screen stopped working. Now, this isn't the first time it has happened but it is the first time it's happened on this rom. I was previously running Android Revolution HD and when my touch screen stopped working, I would hard reset by pressing and holding the power and volume down button until the buttons started blinking for around 10 seconds, and then the phone would restart. However, I can't hard reset my phone anymore. I tried holding the power and volume down button down, but after a full minute, the phone still didn't restart; it was just the capacitive buttons flashing. I tried every combination of holding down buttons but it still doesn't work. What should I do? Any help would be appreciated.

use an OTG cable adapter and plug a mouse ;
go to settings backup and reset : reset phone .
if this is what you want to do.
kinda only way to reboot if you stuck .
or download a rebooter apk

XT1096 no longer boots

I accidently removed my OS, and now I cannot boot into my bootloader.
I've tried charging the phone with it's OEM charger, and it stays stuck on the white battery charging screen until it dies again. I've tried doing it via my PC, and it charges, but I cannot do anything but boot onto the Motorola "Powered by Android" where it freezes, until I hold power and volume down, where it black screens, and restarts again. This happened after clearing my data and failing to flash an OS. After rebooting my phone, this happened. My bootloader is unlocked, but the phone isn't rooted. I've got a ROM that works, but adb is useless as my phone doesn't show up.

If you have twrp recovery Press & hold Power key& volumes up/down hold them all together.. Keep holding pressing about 10 sec or until you see little dim red light it's going to be left side upper speaker...once you see it don't let go of buttons for 8 seconds OK this is critical let go of the buttons & hold them again about 5 seconds,
TWRP recovery should show up.. If not repeat steps again. TWRP will show up.

Question Black Screen on Mi 11

Hi everyone,
I really need some help with my Mi 11. I was on FB Messenger when the screen suddenly shut off on its own. I've tried a bunch of stuff already but the screen refuses to turn back on, though I think the phone might still be on: I have Whatsapp Web on my computer and I can still send/receive messages: according to Whatsapp, the application doesn't work if your phone is off or does not have an internet connection. I've tried:
charging the phone
pressing and holding the power button for >30s
pressing and holding the power button and volume up for >30s
pressing and holding the power button and volume down for >30s
pressing and holding all three buttons for >30s
plugging the phone into my computer(computer did not recognize that the device was plugged in)
and after all of these, the phone still hasn't turned back on. Does anyone have any ideas as to how I might be able to fix it?

Do you have CN or global version? Was the device hot?

Stuck in boot loop "KERNEL REV. CHECK FAIL. DEVICE:16, BINARY:9 (OTB)"

I tried to upgrade my device from crDroid 7 to crDroid 9. After flashing crDroid 9 the device didn't want to boot so I reverted back to TWRP to restore a backup. After restoring the backup and rebooting again I ended up in a boot loop. The device is showing the Samsung logo in the middle of the screen and on the top of the screen is a line in red text with light blue background "KERNEL REV. CHECK FAIL. DEVICE:16, BINARY:9 (OTB)". I tried al sorts of key combinations to get into recovery mode (power on + volume up/down + bixby) but it never gets into recovery mode. When I unplug the USB cable the device stops booting and turns of. With the cable unplugged I can power up the device again and the same message appears, after that the device shuts down again. Holding the power button while the device is unplugged doesn't shut down the device, but when the power button is released the device shuts down immediately. This is also happens when holding down the power button + bixby, power button + volume up or power button + volume up + bixby. When pressing the power button + volume down + bixby when the device is unplugged results in the same boot loop as when the device is plugged in.
Any ideas how to get ot of this boot loop and into recovery. Heimdall can't detect the device.

Only the Samsung logo is shown, no Galaxy S10 below that or Secured by Knox or green Android logo

I also tried volume up + volume down and then inserting the USB cable as suggested in some YouTube videos. Still the same effect, the red text on blue background and a boot loop

I tried all other combinations and eventually holding volume down and bixby and inserting the USB cable entered boot mode

Hey,
any news on this Issue? I have the same Problem with my Samsung S10 (SM-G973F)