[d855] Kernel crash during install - LineageOS Questions & Answers

Hi there,
this morning my LG G3 (running one of the latest LineageOS 14.1 nightlies) crashed and then bootlooped for some reason. Since then I've tried to get my phone running again, sadly to no avail. I've wiped the phone (data, system, cache, dalvik) several times with TWRP and tried to reinstall Lineage. But everytime the phone's in the middle of flashing the zip, suddenly the kernel crashes (or TZ crash).
I've managed to install a stable version of Lineage after the first couple of crashes/wipes, used it your a while and then wiped again to reinstall it with GApps (I forgot the 1st time). After even more crashes/wipes I've managed that aswell, sadly Lineage bootlooped after the first minute of using it.
Am I forgetting something (as I'm typing this: do I need to reroot the phone after wiping?) or is there any way I can start completely anew?

Related

[Q] CM 10.2 bootloop, after successful boot

Hey all,
I've been running CyanogenMod 10.1.3 (Stable) since it came out, and used the Nightlies for many months prior to this.
I recently decided to try the CM 10.2 nightlies, and successfully booted into CM 10.2-20131107. I let Google play restore my apps, and then decided to run "Fix Permissions" and reboot for good measure, however my device was stuck in a boot loop (Google screen with lock) for approximately 10 minutes, before I decided it definitely wasn't going to boot.
This is the second time this hapoened, the first time being with an earlier 10.2 nightly. I assumed it was an issue with that build, but ive found no other reports of my particular issue (I apologise if I am wrong about that, its hard to know exactly what to search for!)
Prior to install, I wiped everything (System, Dalvik Cache, Cache, Data and data/media) for good measure.
I use TWRP.
Does anyone have any idea what the problem might be? I've wiped everything, and gone back to 10.1.3 now with no issues, so at least I have a functioning device.
All I wanted was natively supported TRIM..

D855 - Phone turns off at boot logo

I have been running CM13 for few months now. Yesterday the phone turned off and when I tried to turn it back on, it always kept on turning off once it gets to CM boot logo. Sometimes there might be few background flashes (the white circle that keeps on coming up behind sid, like normal boot) and then it would die.
I have since did a clean install with latest CM13 nightly with opengapps pico without xposed framework just to rule it being the cause of the issue. I am able to boot the first time after clean flash but if I reboot, the issue happens.
Installed fulmics 5.0 ROM for testing and it worked fine If I flash CM13 back again, the issue happens.
Tried to capture logcat by running adb logcat and turn on the phone. It still is stuck at waiting for device.
Does anyone else have issues with latest CM13?
Did you try older builds?
Just ask - Did you made full wipe?
halekhonza said:
Did you try older builds?
Just ask - Did you made full wipe?
Click to expand...
Click to collapse
The oldest build I could find is cm-13.0-20160422-NIGHTLY which I tried and same result.
Yes. wiped system, data, cache, Dalvik Cache & Internal storage partitions.

Boot loop to bootloader after Lineage 14.1 flash

I tried to flash my Wileyfox Swift 1 to Lineage today, from its Android 7.0 rom.
I downloaded twrp-3.1.1-crackling.img and lineage-14.1-20170703-nightly-crackling-signed.zip.
I then followed the instructions on the Lineage OS site for a Wileyfox Swift to the letter to get the Lineage rom flashed (with the one exception being I also "wiped" Internal Storage, along with Cache, System and Data partitions). I didn't try to install, or want to install, the Google Apps.
Everything worked exactly as expected, right down to the absolute final step in the guide. When I chose to Reboot, then System, I just found myself back in the bootloader. No matter what I do, I just keep booting back up to this. I still have full access to recovery mode, but I just can't load an OS or get past the bootloader screen when I restart.
I have an old Cyanogen mod I have been able to revert to in the mean time, but I'm struggling to understand what I did wrong here. Can anyone provide any help/suggestions?
I tried again this afternoon and everything appears to have worked. I've loaded Lineage OS successfully and everything is working well. I'm still not sure what happened the first time, but all is good now.
I had the same issue. After installing an old CM13 release (with TWRP), turning everything off and then start from scratch with LOS 14.1, everything worked. It seems that CM13 does have a side effect that is needed for LOS 14.1.

Bootlooping after clean install of OOS 5.0.8 but can install Lineage OS fine

Hey all,
Bit of a weird one here that has me scratching my head.
I went to do a clean install of Oxygen OS 5.0.8 (the only one I can find on the OP site for the OP3) yesterday coming from rooted LineageOS 15.1 and the phone was stuck in a bootloop for well over an hour. I force rebooted it into recovery (which was still TWRP as opposed to OOS recovery), wiped everything tried installing OOS again (fresh download) and got the same result. Little bit of a panic then began to set in but as I could still boot into Recovery and Bootloader I wasn't too worried.
On a whim I downloaded the latest LineageOS 15.1 nightly and GApps, wiped everything and flashed and lo and behold it worked fine. Happy to have a working phone again I said I'd leave things alone for the rest of the day.
Assuming that it was just weird bug or whatever I tried installing OOS 5.0.8 again this morning (redownloaded again just to be safe) and I'm now 30 minutes into another bootloop.
Anyone have any ideas?
ZeitgeistGlee said:
Hey all,
Bit of a weird one here that has me scratching my head.
I went to do a clean install of Oxygen OS 5.0.8 (the only one I can find on the OP site for the OP3) yesterday coming from rooted LineageOS 15.1 and the phone was stuck in a bootloop for well over an hour. I force rebooted it into recovery (which was still TWRP as opposed to OOS recovery), wiped everything tried installing OOS again (fresh download) and got the same result. Little bit of a panic then began to set in but as I could still boot into Recovery and Bootloader I wasn't too worried.
On a whim I downloaded the latest LineageOS 15.1 nightly and GApps, wiped everything and flashed and lo and behold it worked fine. Happy to have a working phone again I said I'd leave things alone for the rest of the day.
Assuming that it was just weird bug or whatever I tried installing OOS 5.0.8 again this morning (redownloaded again just to be safe) and I'm now 30 minutes into another bootloop.
Anyone have any ideas?
Click to expand...
Click to collapse
Try this:
https://forums.oneplus.com/threads/...-3-3t-and-go-back-completely-to-stock.456232/
ZeitgeistGlee said:
Hey all,
Bit of a weird one here that has me scratching my head.
I went to do a clean install of Oxygen OS 5.0.8 (the only one I can find on the OP site for the OP3) yesterday coming from rooted LineageOS 15.1 and the phone was stuck in a bootloop for well over an hour. I force rebooted it into recovery (which was still TWRP as opposed to OOS recovery), wiped everything tried installing OOS again (fresh download) and got the same result. Little bit of a panic then began to set in but as I could still boot into Recovery and Bootloader I wasn't too worried.
On a whim I downloaded the latest LineageOS 15.1 nightly and GApps, wiped everything and flashed and lo and behold it worked fine. Happy to have a working phone again I said I'd leave things alone for the rest of the day.
Assuming that it was just weird bug or whatever I tried installing OOS 5.0.8 again this morning (redownloaded again just to be safe) and I'm now 30 minutes into another bootloop.
Anyone have any ideas?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Read his second post. Wrong TWRP version may lead to this. 3.2.3.1 encryption issues.
Is had the same issue, i ended up with a fastboot installation. Al is working again.

Stuck at "phone is starting", touchscreen not responding.

Yesterday I did a dirty flash of Oxygen OS 9.0.10 on my OnePlus 5T which was initially running Oxygen OS 5.1.7 with Oreo 8.1.0. After that I flashed latest Magisk zip. After booting into system, then after the final setup of the update, I flashed franco kernel from TWRP.
Everything went smooth. All apps were functioning fine. Today in the evening, while watching YouTube, the touch stopped responding. I restarted my phone, cleared cache, dalvic, still the touch wasn't responding.
I booted in TWRP, the touchscreen wasn't responsive, therefore I used my mouse to decrypt then copied full zip of OOS 9.1.0 zip via adb from my laptop. After clearing cache, dalvic, I flashed the zip file.
After booting into system, my phone is showing the message, "phone is starting" with animated strip below it. This has been since past 45-50 minutes.
The touch is not functioning even now.
What should I do to resolve this trouble?
Has you debloat something from /system/app or priv-app? On my tablet it prevents to boot completely and stucks in this Android update loop.
Also not everytime a good idea to dirty flash to another Android major version (Oreo > Pie)!
Try a fresh install.
OxygenOS 9.0.10
No-Verity v4 (if a decrypted phone)
Boot.
Then back to TWRP
Magisk & Custom Kernel
Boot.
Restore maybe from Titanium user apps only (except Whatsapp/Threema/Telegram.. GCM/FCM notifications problems).
Flash Magisk modules.
Sent with much love and Android.
I have been having persistent problems with the touchscreen on my 5T becoming unresponsive at random times for no apparent reason for a while now (see this This thread for more info there).
I have found that when the touch screen stops responding, the ONLY thing that will get it working again is flashing back to stock firmware - I have been using 9.0.9 (didn't even realise .10 was out). Sometimes it doesn't work the first go, and I have to reflash again over the top (maybe even a couple of times) but I've never failed to get it working after a few goes.
Problem (on my phone at least) is that phone then hangs on the "just a sec" screen at first boot, but once the screen works again I do a clean flash of LineageOS so the setupwizard hanging is not a problem for me per se, except that the touch screen inevitably flakes out again - sometimes it takes a few days, sometimes it happens within minutes, but nothing I have tried has made it go away completely. I'd say it was a hardware problem except that reflashing the stock OOS ROM can bring it back to life... maybe it's some weird hard+firmware combination that is triggering it.
Anyway, reflash stock a few more times and see if that helps.

Categories

Resources