I recently rooted by Galaxy A20 with Magisk and ever since then my touch screen randomly stops working after a reboot but I just normally reboot with ADB (since normal rebooting doesnt work)
I accidentally rebooted and my touchscreen stopped working and ADB just says "Unauthorized Device" I don't know why
and i've tried "force powering it off" and booting to recovery but it just restarts!
What do I do?
Related
I might have bricked my LG G2.
Here is everything I did:
-I rooted the phone with the IO root kit
-wanted to installed a recovery so I installed TWRP manager
-applied SD card patch
-tried to install recovery with TWRP manager several times but app always crashed
-installed SDK on the PC
-started adb and executed "adb reboot bootloader"
the phone got a backlight screen and hasnt been reacting so far.
When I held the power button the screen went black but sometimes the backlight appeard again. I don't know how to reproduce the backlight though.
adb can't detect the phone when connected to the PC.
As soon as I plug it in dozens of Partitions show up. Windows show an error message for each of these partitions. It says I have to format the volumes to use them.
After testing I realized that everytime i long-press the power button for a few seconds the windows errors start popping up.
When i long pressed the power button for 30+ seconds to completely shut it down the notification LED started blinking red 8 times in roughly second intervals. then there was a short break and the 8 blinks repeated.
Thank you for all help, it would suck to have a 1 day old phone broke...
You probably chose the wrong device in TWRP Manager. Choosing the wrong device can easily lead to a brick because TWRP Manager may attempt to flash to the wrong partition. The G2 does not have a TWRP Manager flash available due to loki, so you couldn't have chosen the right device.
Almost have the same problem... the only difference is my black screen is blinking continuously while it is connected to the mac... Seems like it tries to boot but gets blocked and retries in a loop. Tried around now for two evenings without any progress...
Anybody who can help?
Yesterday I've received a notification about the new version of Magisk Manager, clicked "install", the installation process has started, there was a warning "Boot partition space insufficient" (it used to be before I guess). The phone went to reboot, but turned off instead (or just screen off?). I holded the power button, but the phone did not turn on, pressed a combo of buttons, the phone turned on and got into endless boot (got stuck on logo). I rebooted it with buttons again and enter into TWRP, charge level was 68%. So decided to Wipe it, but after a few seconds the touch screen stopped responding so I couldn't. Tried twice, the same issue. Decided to reflash the firmware, turned the phone off via Power Off in TWRP, after that the phone stopped turning on (completely!). Does not react at all. Not charging, no leds, no vibro.. completely nothing. Seem to be hard bricked or even dead, don't understand why.
Update: no drops, no heats, no water.
I guess it's dead on flashing Magisk, not Manager, but I am not 100% sure.
but why touch stopped working? it might be a hardware problem and soft is jist a coincidence
yaro666 said:
but why touch stopped working? it might be a hardware problem and soft is jist a coincidence
Click to expand...
Click to collapse
I really have no clue why. Each time I tried to reboot and enter into TWRP, the touch was working for the first X seconds, 5 maybe... the strange thing is the phone was cold at the time.
Yesterday my phone suddenly froze while using so I forcely shut it down by long pressing the power button but when I restarted it ,it just got stuck at the "powered by Android" logo.
I have tried the following methods and nothing is working:-
1) I tried to enter the Android recovery mode but it didn't work.
2)I tried to forcibly reboot it using my pc through ADB command but my device is not connecting to my pc.
Can anybody help me here...
Do mention if you were using any sort of custom ROM or mods.
I am also facing this issue
When I reboot my phone it sometimes get stuck at Asus logo then I have to long press power button to force reboot the phone .
Using firmware 059 ,unlocked bootloader ,final crDroid Pie ROM because it's very good for gaming
Same here, Asus Zenfone Max Pro M1 no custom firmware etc.
At first the phone seems lagging, then I try to reboot. A moment later, the phone try to reboot, but then it stuck on `Power by Android`.
Unable to go into Recovery Mode, just stuck.
Facing exact same issue, was anyone able to resolve?
Been using the m3 for years.
Just now, i spilled some water into the charging/speaker port on the device..
The device suddenly restarted, and start installing update...
But stuck at 5% and "Software install failed!" with hte only "Reboot System Now" option.
Tried the vol up + power method, and successfully (Once) enter the erecovery mode.
Wipe the cache partition, the upon restart, the screen went to the normal bootscreen (water/bubble graphics) for a few secs, then it restart..
It then stuck at bootloop.
Not sure how, i managed to turn off the device, but later, the device suddenly boot up again and failed at the installing update.
I just want to at least turn off the device for now...
=============================
EDIT: Turned out that the device will shut down after left for a prolonged time...
Suddenly my phone ZBk601 got brick suddenly, first i can open the phone but it goes off after the asus logo then i manage to go to recovery mode and start wiping all the data but its no use, then i retry to install new rom but its hang in installation within 1 hour so i decide to restart the phone and after restart it stuck on recovery logo idk why. i tried to flash using flashboot but
it doesnt detect my device adb devices cuz my enable debugging is not enable.(my bootloader is unlock))