Hey guys. I have a rooted Canvas A1 on CM13 latest nightlies with TWRP recovery installed. It was working fine with the occasional bugs which went away when I reflashed the rom. A few days back I dropped my phone and it rebooted. Now when the phone's battery dies or if I reboot it, the screen brightens up for around 20 seconds and then goes off and this is repeated. Sometimes the Micromax logo comes on but the screen looks yellowish in colour but it boots up. When I press Power button+Vol Up it takes me to all the booting options and I can navigate between them. But if I click Vol Down, the screen freezes and the above brightening of screen problem continues(Basically I can't access recovery). Please help me guys I can't do anything and am currently on a Samsung Core2.
Related
Hello
Have a GS3 running Rootbox 4.2. Was running stable for probably around 6 months, no issues at all except for the occasional random reboot which seems to plague all S3s.
Felt it vibrate in my pocket, assumed I had a message. But when I looked it was restarting. It gets to the rom loading screen then abruptly restarts.
Now it even doesn't get that far. The samsung screen shows up and the phone restarts in a loop.
Cannot stay booted into recovery. CWM recovery screen shows for about 2-3 secs then phone restarts.
Download mode through odin works, but I'd like to avoid wiping everything if at all possible.
thank you for any help.
an easy try to fix is to pull battery , wait a couple minutes and then either just hold power button till vibrate or do button combo to get to recovery.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Try re-flashing an updated version of CWM via Odin and see if you can remain in recovery mode.
Thanks for the replies
Tried pulling battery for few mins (actually a few days since I did not have time to mess with phone) - No good, phone gets partway through the rom load screen then reboots.
Tried the odin suggestion - home +vol. down+ power opens download mode, but download mode stays open for around 10-15 sec before the phone restarts itself.
I have tried swapping back to the oem battery since i have an extended battery and the problem still remains.
Sounds like a hardware problem to me since you can access download and recovery but it turns itself off. You've tried a couple of batteries so that kind of rules out any software issues.
Did you try booting the phone with a de-brick image from XDA?
I recently did a screen & speaker replacement on my oneplus 3.
The device worked for roughly one week with a bit of a touch latency issue. I just assumed the replacement screen was not as good quality as original.
However while downloading an update my screen went black, my battery had sufficient charge i could reboot into recovery but whenever i start up the device the screen would freeze and/ go completely dark immediately or 30 seconds after booting up. The phone does not freeze when in fastboot or recovery mode.
I have tried downgrading my oos version... and also upgrading it to the latest version(currently on latest version) but with each version i encounter the same issue.
The top quarter the screen becomes warm only when the phone boots up and freezes shortly after then.
Phone is is completely stock and has never been rooted/ had bootloader unlocked....
Hi all,
My phone is rooted (still S-ON)(TWRP installed) and running viper's ROM. Last night I forgot to charge the phone when I got home, when I looked it was 1% and shut off. I plugged in the phone and foolishly tried to reboot right away instead of waiting a good ten minutes. Well the phone never got out of the HTC logo screen. I would hold down the power and it would vibrate twice, no clue what that mean't. Anyways I waited for at least 10 minutes to give the battery a chance to chare and see if it rebooted but it didn't. Finally I was able to get into recovery doing the following. Hold down the volume up and power button till the phone reboots (screen will be black) Then quickly hold volume down and power until you see the HTC logo on the black background. Then you should have the options to boot into recovery and into twrp. I had to do a data wipe as something in the OS got hosed. I lost all apps and SMS but at least I was able to boot back into the phone. Hope that helps some out there.
I have encountered this same issue on 2 phones but couldn't recover either without reflashing a stock firmware.
Hi,
a few hours ago I dropped my G4 H815. The back fell off and the battery got out. I put the Battery back in and after a few tries I could load the device. However, I just can`t start the phone now. When I press the power Boutton, nothing happens.
When plugging in the microUSB-Cable the screen turns on and I sometimes see the screen with the LG Logo, but no matter how often I try, it does not boot into recovery (the volume down key was always a bit tricky though). It just goes on to the Screen saying your battery is loading and it´s at 100%.
I can reach Download-Mode, but I do not see any way to force a reboot from there.
My Bootloader is unlocked and the device is rooted. Im running TWRP and LineageOS 14.
Norkzlam said:
Hi,
a few hours ago I dropped my G4 H815. The back fell off and the battery got out. I put the Battery back in and after a few tries I could load the device. However, I just can`t start the phone now. When I press the power Boutton, nothing happens.
When plugging in the microUSB-Cable the screen turns on and I sometimes see the screen with the LG Logo, but no matter how often I try, it does not boot into recovery (the volume down key was always a bit tricky though). It just goes on to the Screen saying your battery is loading and it´s at 100%.
I can reach Download-Mode, but I do not see any way to force a reboot from there.
My Bootloader is unlocked and the device is rooted. Im running TWRP and LineageOS 14.
Click to expand...
Click to collapse
Well it sounds like the infamous Bootloop at least the symptoms are the same. The Bootloop issue is not caused by dropping the phone but while booting Android as this is a very CPU intensive process.
Ilapo or not I would take a backup with SALT before anything else.
You can also boot to fastboot and assuming you haven't installed the nougat v29 bootloader stack you can just boot TWRP temporary by using
fastboot boot twrp.img
(where twrp.img should be my latest TWRP version preview 144 or higher)
Sent from my LG-H815 using XDA Labs
No Bootloop. It seems like the power Button is broken. Using SALT I could reboot the phone and it starts and works normal. The knok-on feature makes this situation, at least temporally, bearable.
I will probably try to fix the Button.
To begin with, the device was rooted with Magisk 18.1 flashed about 2 years ago, running stock OxygenOS Oreo 8.1. Recovery: TWRP-3.2.1-1-cheeseburger. Kernel: RenderZenith OP5T [OOS-O-EAS-V3.7.0]. This was the setup I was satisfied with and running in about a year (a total of 2 years).
However, after the first year, I've tried to update TWRP to version 3.3.1-20190908-0-codeworkx-signed-forcedecrypt-dumpling in order to flash and update to the newer OxygenOS Pie 9.0. Something went wrong after flashing the newer TWRP and I couldn't get into recovery anymore... all I saw was a black screen when trying to get into it. I haven't bothered about this since the system booted and worked fine, so I gave up on the 9.0 update and stayed on 8.1. I was able to use it like normal another year. Everything was running very smoothly until a couple of days ago...
The battery has discharged to 0% and the device shut off by itself. 30 seconds before the shutdown, the UI was much less responsive and a popup about the device turning off popped up. I've put it in charge the whole night and when I woke up in the morning... couldn't boot into the system anymore. Instead, the phone booted into the 'broken' recovery, with constant lit of light blue LED (started to lit a couple of seconds after booting, only in the 'non-visible' recovery), and a black screen. I've looked up the fastboot/bootloader keys combination and went into it, well from there, I've tried the turn-off, start, recovery, and bootloader option. Turn off = Off. Start = Recovery. Recovery = Recovery. Bootloader = Bootloader.
The next step I've done was to connect it through a PC and run ADB on it in order to flash the old TWRP-3.2.1-1-cheeseburger. Re-booted into recovery straight after successfully flash and the recovery started to work again. The light blue LED stopped to lit any longer and I haven't seen it anymore. The first thing I've done in recovery was to clear the cache, dalvik, and do a nandroid backup, then tried to re-boot into the system. Finally, it booted into the system and I was happy like a kid when I saw the OnePlus boot animation again, however after putting my password and SIM pin code, I can enjoy it without any issue for about 30-40 seconds before the UI suddenly starts to be non-response (touch doesn't work), the screen starts to flash, sometimes (looks more like turning the screen on and off), until I see a "Turning off..." popup 20-30 seconds later (the battery is fully charged and disconnected from the power source) and the device is rebooting itself into the 'working' recovery. This is how it works each time I boot up into the system now. However, the power button is working and I can turn the screen off and on while the screen/touch isn't responding, the power menu can be opened by holding it (before it's too late and the "Turning off..." popup appears), from there I can choose to re-boot or power off. Magically the touch is working here. If the phone has been rebooted/turned off manually, by hitting either reboot or power off in the power menu, it reboots into the system instead and the same **** happens - not to recovery like it does when the "Turning off..." popup appears and it's turning off by the system.
I'd like to get everything back if possible, at least for one or two days, to back up all data, do some screenshots, back up browser bookmarks, history, open tabs, sms and calls, then give a fresh custom 11 to it.
Any help I can get from you guys? Is there a solution that I could try? What about flashing the newest Magisk onto it? Might it help or rather corrupt it more? Anything else? I'm out of knowledge in this situation and I'm relying on you.