Database Develop

[Q] Screen not responding to touch in TWRP

I was trying to root my one for the first time. I followed someone's tutorial online, and everything was perfect at first, until I got into using TWRP for recovery. I used version 2.5. After I got into it, the touch screen is not working. I stuck in the lock screen now, not able to unlock, not able to restart, not even able to power off. After some digging, I found out that probably I should have used the version 2.6 instead in the first place. Now my question is, do I need to wait until the power drains out before I could do anything else, or if there is anything I could do to restart the phone and do this recovery process again with TWRP v2.6? Thanks.

kevin0634 said:
I was trying to root my one for the first time. I followed someone's tutorial online, and everything was perfect at first, until I got into using TWRP for recovery. I used version 2.5. After I got into it, the touch screen is not working. I stuck in the lock screen now, not able to unlock, not able to restart, not even able to power off. After some digging, I found out that probably I should have used the version 2.6 instead in the first place. Now my question is, do I need to wait until the power drains out before I could do anything else, or if there is anything I could do to restart the phone and do this recovery process again with TWRP v2.6? Thanks.
Click to expand...
Click to collapse
try doing a hard reset and flash the latest TWRP in recovery mode.
hard reset:
hold your phone under bright light ( i personally use a torchlight for this)
press power + vol down button
i had the same panic attack just few days ago

office usirmr
kevin0634 said:
I was trying to root my one for the first time. I followed someone's tutorial online, and everything was perfect at first, until I got into using TWRP for recovery. I used version 2.5. After I got into it, the touch screen is not working. I stuck in the lock screen now, not able to unlock, not able to restart, not even able to power off. After some digging, I found out that probably I should have used the version 2.6 instead in the first place. Now my question is, do I need to wait until the power drains out before I could do anything else, or if there is anything I could do to restart the phone and do this recovery process again with TWRP v2.6? Thanks.
Click to expand...
Click to collapse
It is because your phone has updated firmware with the updated touch drivers. twrp 2.5 does not support the new drivers as 2.6 doesnt support the old drivers either. Download official 2.6.3.0 img file. reboot into boot loader. If you are stuck on twrp hold power button until phone turns off "10-15" sec. Hold vol down and power to get into boot loader. click fastboot. Use your computer in terminal or command
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
obviously you have to be in the directory with the img file. Search twrp in google to get newest img file

an0ther said:
It is because your phone has updated firmware with the updated touch drivers. twrp 2.5 does not support the new drivers as 2.6 doesnt support the old drivers either. Download official 2.6.3.0 img file. reboot into boot loader. If you are stuck on twrp hold power button until phone turns off "10-15" sec. Hold vol down and power to get into boot loader. click fastboot. Use your computer in terminal or command
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
obviously you have to be in the directory with the img file. Search twrp in google to get newest img file
Click to expand...
Click to collapse
I have exactly the same problem.
But I can't hard reset the HTC ONE via volume down + power button...
Can't access the phone via USB attached cable and the common tools... :///
Do I have to wait till the battery is empty or is there a further solution?

Try opening the back cover and removing your battery and connecting again(btw its easy to remove the battery on a non removable battery mobile,unless you have a finger print scanner at the back side)...now switch on the mobile........you cant charge your mobile while it is switched off....so you have to charge your battery in the frozen twrp screen and later you have to remove and connect the battery to operate your mobile(you can charge your phone normally when it is switched on)...i tried this,works fine with my HTC 826..................
BTW if someone found a solution,,please help us to remove the frozen twrp screen....I think this would help

lol same problem, i powered off the phone, then power up it, (redmi 9 lancelot) and its in chinesse lol, hten i forgot to change the leanguege and reboot it, now waiting ;-;

S2 810, unusual boot issue (official firmware)

Hello and greetings,
I am looking for some help from the gurus here.
I bought this S2 off of ebay, as broken, no power.
plugged in with adequate power supply, the power button was not responding.
I then tried launch recovery mode, and nothing.
Then I found that this tablet would start with download mode enabled.
naturally the battery was flat, but by cancelling download moded, the tablet booted into the system.
the tablet had 5.1.1 and after allowing the tablet battery to charge up to 100%, I then performed a factory reset from within the tablet, and then restarted the tablet to check for issues.
on reboot, the tablet just went black, and again the power button, nor recovery mode would start the tablet, but here i was again able to start the tablet with download mode (cancelling dl mode when initialized).
(i did manage to enter recovery mode, im not sure, i think i was repeatedly trying the button combos and it worked. the recovery menu is untouched vanilla no twrp was installed. i delete the cache, and again performed a factory reset from the recovery console. still, no change in the power button responsiveness from power off)
the next thing I tried was to update the firmware, by grabbing official firmware from updato, and secondarily from samsung-firmware org as a backup source.
both firmwares are official release, 7.0 nougat.
ran odin, and successfully updated the firmware using the file from updato, and the tablet is now running nougat.
everything works great, except when the unit is shut down the power button alone still will not turn the tablet on. (this was the same issue as before i updated the rom to 7.0)
so the next rabbit hole i dug into was creating a bootloader file to see if that would help this issue (extracted the files and compiled into md5 bootloader using Cygwin), the bootloader flashed fine, but still no change to the power button issue. (the Cygwin method can be used to create samsung 4 files repair, but really doesn't do much if you already have the single fat file (firmware))
a couple other oddities:
occasionally the android system installer will go into erase mode, after performing a firmware install from odin, and not complete or reboot.
the system also for the first few seconds after leaving the download mode has graphical artifacts on the screen, just before the samsung logo appears. usually in the bottom half of the screen which are just random blocky colors.
i am pressed for time, and cannot add any more details at the moment, I'll get back later.
any wisdom or insight would be fantastic,
thank you.

[SOLVED] Redmi 4x cannot enter access recovery

Hello,
I've left my wife phone aside for awhile because I'm stuck for the first time on an android Phone :
RR android N v5.8.5 (7.1.2_r29)
I can't access recovery either through :
magisk > modules > reboot recovery doesnt work
button press combination doesn't work
adb reboot bootloader doesnt work
It seems ADB disable itself phone side after each reboot.
Fastboot through volume down + power does work but the phone is then not recognised through adb
At the time of writing magisk says my version of magisk isn't recognised and I cant therefore use it.
So I cant su root in local terminal.
From MIUI to RR i never had any trouble but it seems at one point in 2017 a firmware or something else broke something.
Any of you could help me ? I read different thread closely related but didn't found the solution yet.
Hope to read from you soon.
Have a nice day.
[UPDATE1]
I installed an old magisk manaer (6.1.0) my magisk version is 17.1
As I havent got recovery I cannot update magisk even through flashify
[UPDATE2]
I was about to install windows in a VM to try smth with MiFlash when suddenly I could finally communicate with the redmi through fastboot.
From the beginning the problem has always been with connector which led to this problem.
The connector constantly connect and disconnects so it's quite hard to maintain or gain connection from adb or fastboot aswell as charging the phone.
I'll look into changing it.

I am quite confused about what is going on with your device and cant understand what exactly going on.
Anyways what is current state of your device? which ROM it has now? is your device able to boot into fastboot mode?(to enter fastboot mode turn off device and then press and hold volume down + power button together) and then flash latest or your choice of recovery.
you can enter into recovery mode by turning on power menu buttons. if you are on RR then it should be in RR settings or somewhere there.
Just look for advance reboot turn that on and then you will see new option available when pressing and holding power button. choose advanced reboot > recovery and your phone will reboot into recovery.
also there is notification toggle is also available if isn't there then add it by using edit icon on notification shade.
if you are on MIUI then go to update and choose reboot to recovery by tapping on three dots on top right corner. if reboot to recovery does not shows then tap MIUI icon several times and then it'll show.

Feb-21 security patch update brick phone

This morning, I saw a notification appear on my phone showing that the Feb-21 security patch is ready to be installed. The size is 41+MB. The description looks nothing unusual as this phone has been getting only security patches for quite some time. However, once it attempt to restart it went dead. I tried numerous times to power up the phone (pressing the power button) but it's not responding. Nothing happen. Does it mean my phone is bricked by the security patch update?

chiwawa10 said:
This morning, I saw a notification appear on my phone showing that the Feb-21 security patch is ready to be installed. The size is 41+MB. The description looks nothing unusual as this phone has been getting only security patches for quite some time. However, once it attempt to restart it went dead. I tried numerous times to power up the phone (pressing the power button) but it's not responding. Nothing happen. Does it mean my phone is bricked by the security patch update?
Click to expand...
Click to collapse
Can you access recovery mode?

chiwawa10 said:
Does it mean my phone is bricked by the security patch update?
Click to expand...
Click to collapse
First of all:
1. Did you had your bootloader unlocked ?
2. Were you rooted when taking the OTA update ?
Your description doesn't quite match the result.
A differential update (like security updates) shouldn't brick the bootloader and from your description the bootloader doesn't (well) load itself.
Worst case with a diff. update is that the bootloader will give you an error message and won't load the OS but the fact that you have a black screen indicates that the bootloader itself isn't able to operate.
I would try two things:
a) Try to access Recovery Mode : Vol Up + Power + Cable connected
b) Try to access Download Mode : Vol Down + Power + Cable connected
Those two will dictate which actions you can take moving forward based on which modes you can still access.
Also:
Does the phone indicate charging when you connect the USB cable ?
Does your PC detect it (shows up in Device Manager) when connected ?
if a) and b) fails but the PC still detects the phone you might be able to reflash using Qualcomm Flash Image Tool (QFLI), I'm pretty sure there was an Oreo firmware in QFIL format available somewhere on the web.
Edit: QFIL, NB0, recovery MR packages firmware available in this thread [OTA] [Fastboot] [QFIL] Nokia 7 Plus OTA and Fastboot Collection

Thanks for the reply. Finally I managed to boot the phone up by pressing volume up + power button. However, it does not boot into recovery mode. Instead it boots up in normal mode. Since then I did not try reboot or power down my phone. Glad that it's not bricked. And no, I do not have the bootloader unlocked. Though I'm tempted to do so if the updates stop coming. At least I can still breath some life into the phone by installing other flavor of android. Still clinging on to hope that HMD will allow us to officially unlock bootloader. Otherwise, this will be my last Nokia phone from HMD.

chiwawa10 said:
Thanks for the reply. Finally I managed to boot the phone up by pressing volume up + power button. However, it does not boot into recovery mode. Instead it boots up in normal mode. Since then I did not try reboot or power down my phone. Glad that it's not bricked. And no, I do not have the bootloader unlocked. Though I'm tempted to do so if the updates stop coming. At least I can still breath some life into the phone by installing other flavor of android. Still clinging on to hope that HMD will allow us to officially unlock bootloader. Otherwise, this will be my last Nokia phone from HMD.
Click to expand...
Click to collapse
This will be my last one too if nokia won't support the unlock

chiwawa10 said:
This morning, I saw a notification appear on my phone showing that the Feb-21 security patch is ready to be installed. The size is 41+MB. The description looks nothing unusual as this phone has been getting only security patches for quite some time. However, once it attempt to restart it went dead. I tried numerous times to power up the phone (pressing the power button) but it's not responding. Nothing happen. Does it mean my phone is bricked by the security patch update?
Click to expand...
Click to collapse
My phone got bricked after a regular update.no bl unlock or something else weird. I really won't forgive nokia for that.

Question sm-x200 boot loop

Hi All,
I"m reasonably experienced custom flasher but I appear to have stuffed up pretty badly this time. I was attempting to flash a 13 GSI rom and the tablet is in a boot loop. Holding the power button by itself doesn't power it off. The power button with either or both of volume up or down doesn't achieve anything. Any ideas please on how to break the loop?

I solved it so here it is if anyone else falls into the same trap.
I held down volume up & down at the same time and then plugged in the usb cable after the Samsung logo disappeared. I had to try a few times and then I had a landing screen. I then clicked on volume up and the tablet went into download mode. However flashing didn't work both in Odin & Heimdall with no meaningful message. I then noticed o the landing screen on the right side there was "dev_unsupported" and there was an option to long press volume up. This took me to another download screen without the "dev_unsupported". I tried flashing an oem with twrp built in and it failed at recovery.img with a message about not digitally signed. I then download the oem rom and it worked.

Thanks! That was very helpful.
Are you running the new Android 12 firmware (BVI6) on your Tab A8?
Ch42er