I think I've solved my bootloop issue; stock v30 - G3 Q&A, Help & Troubleshooting

I've used my d855 for years with CM/LOS without any issues. Some day, it randomly started rebooting. It didn't even enter download mode or TWRP correctly, it rebooted just after few seconds later I pressed the power button to turn the phone on.
To cut the story short; it became more stable randomly, so I flashed stock android 4, 5 and 6. The phone bootloops with LOS 14.1, CM 13, v10 and v20 but not with v30.
I think something on the stock partitions of KK and LP makes the devies bootlooop, accidentally or not, but they've removed that in the latest firmware. Now I can't use LOS thus the phone is useless for me.
Does anyone experienced similar issues? Could someone having bootloop issues flash v30 and report back?

Related

LG G3 cyanogenmod 13 update has broken my phone. Stuck on bootloop.

Hello so I flashed cm13 way back in January. Recently the last few nightlies have really messed my phone up. Randomly crashing and got worse before it now bootloops for no reason. I booted up in twrp and read to wipe everything and flash latest nightly again. Did that except now twrp starts the flash before it boots onto the LG screen. It stays like that and I have to remove the battery. Basically it starts to flash before stopping the flash and booting the phone after a few seconds. Phone will only boot into twrp but same thing again. I feel like I have wiped the system so surely flashing the nightly will work. At the moment I have no phone and really not happy. Can someone help? Bit of a noob to this.
Best solution for you is to flash a stock rom using LG Flashtool. You can never go wrong, after that you can root and flash any rom of your choice. Avoid flashing cm nightly, try the stable versions.

D855 keeps rebooting even after rom change and LG Flashtool procedure

Hello,
my phone is stuck in reboot loop since yesterday.
I have this phone since 2 years. It was rooted and on fulmics 5.3. Since few weeks i had random reboots, more and more often, since yesterday when it became unusable because of the reboots.
It wasn't in bootloop, but the phone starts, the rom loads, and after some seconds it reboots.
So i changed rom, went on exodus, but the problem remanins. The rom boots, and after 1 or 2 mins it reboots, go in bootloop, then starts and reboots again.
Today i've made the Flashtool procedure to go back on stock, but the problem still remain. The rom booted, changed the language then rebooted again.
Wad can i do now?
Thanks
perhaps to be hardware problems, there are some parts of poor contact caused by repeatedly reboot
its not the problem of rom . its a battery issue
replace battery
Maybe this ^
I'm using phone connected to power and it seems to works!
Thanks!
Buy a new battery

D855 - Blackscreen / Freeze / Bootloop after flashing Nougat / Only Stock-Roms work?

Hey there,
I recently tried to upgrade to Nougat 7.1 by flashing Lineage 14.1 (latest Nightly) or Resurrection Remix 5.8.0 / 5.9.2 via TWRP 3.1.0-2. But somehow I can't get the system to work.
At first I went from Fulmics 6.9 to Lineage. TWRP -> Factory Reset -> Flash ROM -> Flash GAPPS 7.1 Pico -> [1st attempt Reset Cache + Dalvik] / [2nd attempt: Factory Reset] -> Reboot. Same procedure for RR 5.8.
After flashing the boot animation appears for a while and then, finally, the screen turns black, then reboot. When the screen is black I can still push the power button and hear the wakeon sound. But the screen is still empty. At some point I managed to get to the first step of system configuration (language selection) just by waiting one or two minutes. But on the next step the screen tuns black again and eventually freezes. Sometimes I can even see the status bar and change the volume bars for example, but the installation process somehow cannot initialize properly. Most of the time the system just turns black, freezes and then reboots sooner or later. I tried different builds of RR (5.8.0 of 2016 and 2017 as well as the newer 5.8.2) and Lineage (13.0 / 14.1) but the issue is always the same.
On my first attemps - coming from Fumlics 6.9 - I even had problems with the modem. But after switching between 30B and 21C flashing ROMs (7.1 in particular) went mostly fine.
In the meantime I have even performed a full reset via LGUP / LG Flash Tool 2014 to D85521C_00_1204.kdz, Android 5.0 LP with Baseband 13.2-00002 (modem 21c). After rooting with Kingroot, applying TWRP with AutoRec and upgrading to the latest version (3.1.0-2) I tried the whole thing again.
Flashing Nougat RR / Lineage, Gapps, then Factory Reset and Reboot. The issue is still the same... blackscreen, freeze, reboot. Also flashing MR_Bump.zip after the Nougat / Gapps makes no difference. When applying the .zip via TWRP, the system suddenly shuts down and reboots, then the same Nougat bootloop as mentioned before.
Interestingly it isn't even possible to flash back to Fulmics 6.6 after trying a 7.1 Nougat version. When flashing the system just shuts down, then reboots. The ROM won't install. Other MM ROMs have problems after trying to flash Nougat, as well. For most of them I get the same bootloop / freeze phenomenon.
So the only chance is to completely reset back to LP 5.0 via LGUP / Flash Tool 2014 again...
I am not really sure what is going wrong with the system. But generally speaking LP and upgrading to MM and its variants appears to work fine.
Only trying to flash Nougat leads to perpetual bootloops with any ROMs.
Is there any chance to make Nougat run on my D855?
Anything else I could try to fix the issues mentioned above?
Would be grateful for any help!
Edit:
After installing another 6.0 Marshmallow yesterday I oncemore tried flashing two other Nougat ROMs. The first one was AICP, the second crDroid. When flashing in TWRP I noticed that there was a basband incompatibility again. The ROMs required the 21c, which was already installed (by the lastest MM 6.0) but still marked as unsupported. After that I tried flashing Step-hans 21c in the first place and finally got the two ROMs to install. However, after the unconditional flashing procedure I always got two lines of an "Unknown Command [log]" error...
AICP just gave me the black screen after the boot animation again, but suprisingly crDoid booted without any issue. At least I could make it run normally for one or two minutes. Entering the menus, pushing buttons, opening apps just worked fine for that short period. And then the screen finally faded to black again. I could still use the power button and see the display powering on and off. But the screen itself was still black. Maybe my device has problems with running Nougats system UI...?
Any idea? :'(
Did you wipe the system partition before flashing?
Thanks for the response.
Yes, I did
One month has passed and the issue unfortunately still persists.
I have tried to flash an older Lineage version (v13.0 with MM) the other day and realized that even that one had troubles with my phone.
The UI was very slow and finally crashed to a black screen. In some cases only (pices of) the top bar were visible after the UI crashed. So basically the same as with the newer Nougat builds. I also noticed that at some point the screen toggled between full brightness and a yellow mode with lower brightness (reading mode?).
Could those issues be realted to the kernel?
In some rare cases I can get the newer builds to run for maybe 3 or 4 minutes until the UI finally crashes / the screen turns black. I can then push the power button and hear the wake up effect, but the screen remains black. The nougat builds were also running very slow in those few minutes whilst maxing out the temperature of the cpu.
Any further ideas?
Would be glad for any advice!
Edit:
Stock LP and MM with 21C and 30B still work perfectly, and even very smooth.
But as soon as I try to upgrade to another MM such as Mokee or Lineage 13 or the newer Nougat builds, the screen turns black when setting up the device.
It looks like only Stock-based ROMs (Nimax MM or Fulmics MM) appear to work at the moment!

D885P Stuck in Weird Bootloop

Hello guys, my LG G3 fell into a dreaded bootloop suddenly. It started with random reboots while it was on, then it became a bootloop whenever it turned on again and if it somehow managed to turn on, it would reboot soon after that.
I thought it could be related to the ROM I was using (LineageOS 14.1), so I did a clean flash with another ROM (RR Oreo) but it kept bootlooping. Now, after another full wipe, I'm having trouble launching download mode or TWRP unless I plug it in a computer, but it keeps bootlooping even after that.
Can anyone tell me if this is a hardware problem or just a hard brick?

Unusual problem (sort of restarting) on whyred

Hi,
I am new here, and before you judge me for posting this new thread, I want you to know, I really read A LOT of threads regarding bootloops problem.
But, mine is different.
So, I had LOS 15.1.x (cant remember exact version, at that time, i wasn't really paying attention) installed on my phone. Then, about a week ago I decided to upgrade it to latest LOS 17.1.x.
I flashed it with twrp, and all went well, it fully booted and I managed to fully setup my phone.
But the problem is, when the screen locks (or if I press the power button to lock it), a couple of seconds later phone reboots. Then it boots to Lineage and, again, if no activity, screen locks, and a couple of second later phone reboots. If i leave it, it just goes on and off forever (until battery dies). If i enter screen lock pin, I can normaly use my phone for hours.
It's just that it must not be locked.
Interesting, in twrp, this doesn't happen. I can lock the screen in twrp, and 5 minutes (or a day) later, it is still in twrp. But, than again, twrp is recovery, not full ROM.
So, i tried with different Lineage ROMs, no difference.
Then, I installed latest MIUI 9 (but still ARB3, because phone was ARB3), but, the same problem. Then, I installed MIUI11 (stable, global, ARB4) to update the firmware, and, again: Booted in Miui (let it encrypt my phone), can use the phone normally, as soon as i lock the screen (or leave it to lock itself) a couple of seconds later phone reboots.
I tried Lineage recovery, different twrp versions, Xiaomi recovery, flashed DM-verity zip, nothing helps.
Then, i managed to found one Lineage, it was 15.1.x (I am not at home right now, can tell you exact version as soon as I can), and the phone didn't reboot, BUT, wifi was not working (wifi works normally in LOS 17.x, MIUI 9 and 11), so I gave up.
Yesterday I installed latest LOS ROM, fully booted my phone, pressed power button a couple of times (to check if it is still alive, as it doesn't reboot instantly as the screen locks). Of course it rebooted, but i pressed volume UP and power button, to enter in twrp, where I copied log files to sd card.
In dmesg.log I noticed, it had some problem with i2c bus (as far as I know this is for communication between cpu and external sensors), but dont't know if it is related to my problem. As I am new here, I dont know if I am alowed to post attachments (dmesg.log, recovery.log)?
If this is a hardware problem, why can I use phone normally for hours (assuming i don't lock my screen)?
Also, if it was a hardware problem, why it normaly works in lineage 15.1.x (although, wifi doesn't work there)?
Did any of you had the same problem? I couldn't find any similar problem here, or anywhere else.
Any help would be much appreciated.
OK, here is kernel log. I powered on the device, let it boot to the latest Lineage OS (lineage-17.1-20210201), then entered pin number and waited. Screen turned off, and a couple of second later device restarted (showing "Mi" and at the bottom "unlocked"). Then I imediately pressed "power + volume UP" to boot into recevery, where I copied log file).
I noticed multiple i2c errors, but couldn't find where exactly device initiated reboot.
klepec said:
Hi,
I am new here, and before you judge me for posting this new thread, I want you to know, I really read A LOT of threads regarding bootloops problem.
But, mine is different.
So, I had LOS 15.1.x (cant remember exact version, at that time, i wasn't really paying attention) installed on my phone. Then, about a week ago I decided to upgrade it to latest LOS 17.1.x.
I flashed it with twrp, and all went well, it fully booted and I managed to fully setup my phone.
But the problem is, when the screen locks (or if I press the power button to lock it), a couple of seconds later phone reboots. Then it boots to Lineage and, again, if no activity, screen locks, and a couple of second later phone reboots. If i leave it, it just goes on and off forever (until battery dies). If i enter screen lock pin, I can normaly use my phone for hours.
It's just that it must not be locked.
Interesting, in twrp, this doesn't happen. I can lock the screen in twrp, and 5 minutes (or a day) later, it is still in twrp. But, than again, twrp is recovery, not full ROM.
So, i tried with different Lineage ROMs, no difference.
Then, I installed latest MIUI 9 (but still ARB3, because phone was ARB3), but, the same problem. Then, I installed MIUI11 (stable, global, ARB4) to update the firmware, and, again: Booted in Miui (let it encrypt my phone), can use the phone normally, as soon as i lock the screen (or leave it to lock itself) a couple of seconds later phone reboots.
I tried Lineage recovery, different twrp versions, Xiaomi recovery, flashed DM-verity zip, nothing helps.
Then, i managed to found one Lineage, it was 15.1.x (I am not at home right now, can tell you exact version as soon as I can), and the phone didn't reboot, BUT, wifi was not working (wifi works normally in LOS 17.x, MIUI 9 and 11), so I gave up.
Yesterday I installed latest LOS ROM, fully booted my phone, pressed power button a couple of times (to check if it is still alive, as it doesn't reboot instantly as the screen locks). Of course it rebooted, but i pressed volume UP and power button, to enter in twrp, where I copied log files to sd card.
In dmesg.log I noticed, it had some problem with i2c bus (as far as I know this is for communication between cpu and external sensors), but dont't know if it is related to my problem. As I am new here, I dont know if I am alowed to post attachments (dmesg.log, recovery.log)?
If this is a hardware problem, why can I use phone normally for hours (assuming i don't lock my screen)?
Also, if it was a hardware problem, why it normaly works in lineage 15.1.x (although, wifi doesn't work there)?
Did any of you had the same problem? I couldn't find any similar problem here, or anywhere else.
Any help would be much appreciated.
Click to expand...
Click to collapse
Did you do clean flash? Wipe data, cache, system, on internal storage android directory must be deleted?
What's your firmware? I guess old oreo and not new one - pie, it should be 11.0.3 or newer!
Update Firmware first using MI FLASH TOOL NOT FROM RECOVERY!!!
Than clean flash Official LOS 17.1 again.
If your WiFi won't work after that your persist partition is corrupted.
For extra info search xda forums.
Good luck and stay safe!
Which firmware should I use? I don't want to brick my phone, I am on ARB4 now, and as i was looking for firmware, it didn't specify if it is for ARB4 or ARB3 ...
Is this one ok?
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
klepec said:
Which firmware should I use? I don't want to brick my phone, I am on ARB4 now, and as i was looking for firmware, it didn't specify if it is for ARB4 or ARB3 ...
Is this one ok?
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Click to expand...
Click to collapse
Yap all above 11.0.3 is ok..
Advice: don't rush! Read and take it slow. If you rush you'll probably mess it up... unlock your bootloader first, its easy to bring it back to life if you gonna mess up your phone.
For better overview watch how flash and what options to pick
Good luck and stay safe!

Categories

Resources