Hey guys, after booting to Havoc OS multiple time successfully, this time I boot into havoc os, it is just a black screen. But I can still hold the power button to power off, restart, and also lockdown. It even can produce sound if it charged. Any help?. I already restarting it and shut down multiple time and the same result. I think its only the display tho
The only way now, is to wipe. But I don't want to start over again
Havoc OS Version : v4.19-20220729-daisy-Official-GApps
nvm, I just boot into another slot and it worked!! the play store keep crashing, and now bootlooped lmao
Related
Hey guys I'm having trouble installing CM-Remix 11. The rom is amazing, I installed an older version and it worked amazingly, but after I turned it off and turned it back on (I simply had it sleep for 3 days, never turned it off) the screen would go black after a couple seconds in the boot screen. The phone is not turned off, 'cause the LED light still flashes when charging and it vibrates when holding the power button.
I tried installing the newer versions, but now the ROM wont even install. It goes black on the boot screen like before. I've tried factory resetting, formatting the entire phone and sideloading the ROM but nothing works. When using the ROM it was super smooth and had awesome features so I'd love to be able to use this ROM. I have been able to install other ROMs, regardless if they are 4.4.x or 4.3.x.
Any suggestions?
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)
Hi everyone,
My parents have a TCL U43P6036 (but hardware says P6046) that keeps shutting down at boot just after the dots animation/before the Android logo.
I don't have a clear backstory of the problems before this but I know the screen started to become darker on a side, there was also a moment when there was no image but the sound was working, and finally this problem of shutting down at boot.
It happens 100% of the time.
I tried a hard reboot but I'm not even sure the buttons under the screen are working for that purpose as there's not clear volume down button (the buttons are like "<", power/menu, ">"). And my attempts at a hard reboot all failed (Android says "error" and just reboots, then the TCL logo shows up and "error" again, etc.)
There's no reset button too, so I can't even try that.
Now I think the next step is trying to flash it but I'm not even sure of the version of Android. The manual says "Android N (7.0), O (8.0) Q3 ‘18 updt" but I don't know what it really says (is the OS Nougat 7 or Oreo 8?). I know some auto updates have been done.
Anyway, I'm stuck and not sure about the real problem here...
Update: tried to flash it but nothing happened at all. The TV starts like usual, then shuts down after the dots animation/before the Android logo... I don't even know if it detected the USB drive...
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.
Hello!
After recently getting my hands on an old Samsung A50, I thought I might as well reflash and do some stuff with it.
After installing Orangefox and Lineage, everything worked fine until the phone eventually ran out of power.
I plugged it in and let it charge for a bit, but it was just constantly showing the gray circle with a charging/power icon in it, but no battery indicator.
This usually means that the phone is completely empty and has to charge a bit before booting.
After letting it sit for a long while and nothing changing, I got a bit worried.
At this point, unplugging the phone does not change anything - it will continue showing the indicator even while unplugged.
Holding power and volume down (or power + both volume) briefly blacks out the screen, but it simply comes back to the indicator a few seconds later.
All of this happened a few days ago - I eventually got it to boot again through some key combination while the screen blacked out, sending me to orangefox or download mode (i dont remember),
from which I was then able to boot into lineage again. In lineage, everything worked fine again, including the battery indicator which showed that the phone was full, and the battery seemed to work completely fine.
After that, I turned from lineage to Fresh, which also ran fine until Fresh wanted to install an update which sent me to TWRP. Not sure what to do, i just booted back into System which worked fine, but the Fresh update hadn't succeeded.
I attempted to update again and this time shut down from TWRP - big mistake. Now i am once again stuck in the low-power indicator.
I believe that last time i escaped by booting into orangefox - but i think fresh replaced orangefox with twrp?
Anyway, i tried holding different button combinations while the screen is briefly blacked out but nothing is happening (also tried getting into download by plugging into pc, holding power+volumedown, then holding volume up+down while screen is black).
I also let the battery empty itself until it went black by itself and then tried again, but no success.
I'm now again unsure what to do. How do i unbrick this to boot into the OS again? How do i prevent this from happening again?
Thank you all.
Same issue with my Redmi 9, it seems a battery issue idk if i had rekt mine after flashing a latest CN rom then after not being satisfied tried to flash thru recovery to its stock rom and it went bootloop. Fixed it by flashing with SP flashtool and some bypass stuff, but damage has been done with my batt. Maxing out the volume when I try to play something video or music would trigger a reboot to my phone.