i was using lineageos oreo but the battery was really bad and i tried to install full clean install to marshmallow.
i successfully installed hboot and then tried to flash firmware and phone stopped before this.
now phone is fully black screen. i tried all button combinations for 10 seconds, 30 seconds, 60 seconds.
i tried charging after 2 days and a low-redlight appeared for second and then everything black again.
what can i do for my phone getting back to life..
Related
I recently updated my rom to Gingervillain 2.4 and this morning after the phone had been charging through the night I tried to update some apps from the market when the phone suddently reboots. I gave it a couple of minutes after which I noticed that it was constantly rebooting before getting to the boot screen. It only showed the splash screen and kept on rebooting. I tried pulling the battery after 30 minutes and going to the boot loader (with volume down + power), which worked, but after going to recovery mode the screen just turned black and stayed that way for 10 minutes.
Any clues on what I could do?
Regards,
Me
I would wipe everything in recovery, then either try the flash again or restore nandroid backup and start again with a new download of the rom.
Hello,
I have a xperia zl c6506 and I flashed/ installed candy5 to the device. For like a week and a half, it was working fine. For the first time , it shut down randomly and when you try to turn it on, it keeps rebooting after black screen. I held the reset button for like 20 seconds to shut it down. When I try to turn it on , it keeps rebooting.
What i've tried:
-Reset button
-Going into recovery twrp( tried to flash a different rom , pa 5.1) it turns off as soon as you install in twrp.
-Plugged in while in twrp installing rom( it was successful, as soon as I unplug the phone after like a minute reboot happens again.
I just bought the phone brand new, like 2 weeks ago, so I dont want to assume its the battery. Can it be anything else?
-Reset button
vibrates? how many times?
I just bought the phone brand new, like 2 weeks ago, so I dont want to assume its the battery. Can it be anything else?
Click to expand...
Click to collapse
flash back to stock as best you can assume its the rom.. leave it plugged in and off for at least 12+ hours and then try to start it
try dirty flash the rom and gapps. Worked to me sometimes when I got bootloop. If that doesn't work, you'll have to make a clean install, unfortunately.
Hello there
I own Redmi 1s. I have been using the phone for nearly 2 years now. I currently had Cm 11 installed on my device. Today while using the phone, my phone shut down on its own. A few seconds later the MI logo showed up on the screen. It lasted there for a few seconds and then went off again. The same has been happening for over an hour now. The battery percentage before this happened was over 50 %. I have TWRP installed, i tried to open the recovery. The recovery opens up but the phone shuts down on its own within a second and the MI logo shows up again.
I can't figure out what to do. Please help me. Thanks
I removed the battery when I saw this problem. The moment I put the battery in, the phone starts up on its own. This is pretty different as the phone didn't start on its own when I used to remove the battery in previous cases. In this case it starts on its own and the MI logo keeps of appearing and disappearing.
If you can get into recovery, you might like to try clear cache and data or even a factory reset (means sacrifice all data) and see. If still keep restarting, might be time to flash back the stock ROM...
So i had lineage os 16 until it started to randomly restart multiple times. so i got the newest available Stock rom for the marlin, had some weird trouble flashing it until it finally worked. the phone booted and i set everything up. after a couple of log ins with apps and downloading it just turned off and started boot looping. Now usually you could enter the bootloader but.. it only stays in that for .5 to 4 seconds before restarting. i cant power off because the home button isnt working and i cant flash a clean rom.
Any ideas???
(currently letting my phones battery drain and leaving it for a bit. hopefully that could help but unlikely)
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.