Hello,
So, I flashed Booroondook's 5.1.1 ROM a few days ago to replace the stock 4.4.4 firmware and all has been fine and dandy except for one thing that didn't happen with the stock firmware.
On a cold boot, the boot logo will show up, load into the home screen, and then go back to the boot logo. The unit boots to the home screen fine after the second time. Also, even though my unit is set to stay on for 30 minutes on ACC OFF, when I turn on my vehicle within the 30 minutes, the home screen shows up for a slight second then goes back to the boot logo before booting back to the home screen. I've changed the timeframe of ACC OFF to other durations, but they all show the boot logo.
Is there a way to fix this, or am I stuck with this issue? Could this be an issue only tied to specific ROMs?
Related
My phone is looping (on and off) during the boot sequence. The boot screen (red green yellow) says code error then goes to the update screen. It starts to flash and then shuts off for a couple of minutes and does the same sequence again. I was running Nedidum v4 and activated the lock screen. Every since then I cant boot to this rom nor can I flash the stock sprint rom. Is my phone bricked? If i take it to sprint can they tell I was running a cooked rom? Note: I reported my touch pro lost through assurion to get this tp2. Can I do it again? Helpppppppppppppp!!!!!
I was trying out using a keyboard with a cheap USB OTG cable, and all was good. Then all of the sudden the screen went buggy, where ever other line of pixels was shifted to the left or the right, almost like some sort of corrupted video file. It started to reboot itself, and it got to the black screen with the Google logo and then the screen fuzzed in the same way as before. It then starts to reboot and does the same thing over and over again. I find that I can get to the recovery screen with the scroll arrows. From there, if I tell it to reboot into recovery it goes back into the same Google logo bootloop. I then went back to the original recovery screen and I decide to try out adb to see if it works. Sure enough it does, and I unwisely start flashing a stock 4.2 bootloader image. However, while it is flashing the screen does the same fuzz thing and and stays fuzzed. Then it doesn't respond to anything. I take out the battery, and try to restart and with will not turn on at all, no vibration, no light from the screen, nothing. I tried a unbricking methods from there, and nothing can make it come back alive. Any ideas?
Additional info:
GSM tajkju
Bootloader unlocked
Running stock unrooted 4.2 that I flashed manually
Stock recovery
Hi,
Today while browsing my stock LG g4 (h815) suddenly rebooted. It showed the LG boot screen for a while but then ended up with a black screen. The power button does nothing. If I remove and insert the battery the power button works again, but I get the same result.
I can boot to (stock) recovery OK and if I connect it to a pc it shows 100% charge. I tried using recovery to reset everything but no change.
I am on holiday so can't easily send it in for repairs. Any ideas? I do have a Windows tablet pc with me with ADB on it.
Search "bootloop" in G4 forum.
Warranty is the only solution.
But this is not a boot loop? It seems to boot normally and then goes to a black screen, it doesn't reboot. I direct about the boot loop but from the videos I could find it looked like it kept booting.
I guess I was wrong trying to start it today it boot looped a few times before the black screen. Guess I will try disabling the big cores so that I will at least have a phone until I get home.
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.
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.