Once again I'm back trying to port Lineage 13 to the XT1607 using squid2/moto8916 CM13 device, vendor, and kernel trees. Everything builds successfully, and even flashes to my phone in TWRP just fine. The problem is when I try to boot, my device is stuck on the boot logo. Not the boot animation, the boot LOGO. Normally the device will show the boot logo for 3-5 seconds before vibrating lightly and moving on to the boot animation, but my build doesn't even get to the vibration stage.
Is there any way I can get a logcat or dmesg to diagnose the problem at this very early stage of boot? This is my 3rd attempt at building a ROM (none of which were successful) so I have no idea what I'm doing here...
You should try with nougat. LineageOS 14 will be easier as it is more stable and actively maintained.
tywinlannister7 said:
You should try with nougat. LineageOS 14 will be easier as it is more stable and actively maintained.
Click to expand...
Click to collapse
This is why I want to do it with Lineage 13 though, to give something to the community that they don't have yet
I figured it would be easy enough since Lineage is loosely based on CM, and we already have working CM13 trees. Guess not though...
Related
I have a problem with using LOS: I install the ROM and it boots properly, so I do initial setup (setting name, google account, etc). However, if I reboot the phone, it goes into a bootloop thing where it stays on the boot animation and doesn't show up in ADB. This seems to persist on other ROMs as well. Can anyone help me out? I'm pretty desperate for a solution. I can't provide a logcat, since I can't access adb, but I will say that this issue persists after wiping data, system, cache, and dalvik. I have only installed the rom and SlimGApps 7.1.2. I have not installed any other apps in the recovery or from the Play Store. If it helps, the problem originated when I flashed Quark Kernel. After that, if I reboot, voluntarily or not, I never get to the lock screen. On the very first reboot, It looks as if it might have finished, as I get a black screen, but it just returns to a boot animation and stays there. Finally I noticed that if I touch the fingerprint sensor during this infinite boot, I feel a vibration.
I tried installing Vegito Kernel, and it let me in to the home screen, but the screen went black 10min later and it began bootlooping. Finally, if I try to reinstall LineageOS, the bootlooping still continues. If I install a different ROM such as AOSPExtended or RR, boot into setup, then install lineage again, I can boot.
It seems like your device is actually ducked. Try flashing stock N. goodluck :good:
tywinlannister7 said:
It seems like your device is actually ducked. Try flashing stock N. goodluck :good:
Click to expand...
Click to collapse
I installed RevivorOS and everything works aside from some buggy GApps. Thanks
Covalex said:
I installed RevivorOS and everything works aside from some buggy GApps. Thanks
Click to expand...
Click to collapse
Update them from the PlayStore and everything will work great :good:
tywinlannister7 said:
Update them from the PlayStore and everything will work great :good:
Click to expand...
Click to collapse
That's actually my problem, some apps are refusing to install such as Chrome and the Google App.
Hi, I have a Mi2S with unified partitions. I was using CM12, and MIUI 8.2 without problems for the last years.
Yesterday (with official miui 8.2 developer) the phone turns off. When I switch on, boots the android system, i see the android logo, and all the boot animations but at the end of the boot process, when the lock screen should be viewed, the phone turns off by itself again.
I tried fastboot miui, cyanogenmod, and many different roms installed with many methods with different wipes, and partitions, and the problem persists.
TWRP 3.1 works fine, and I can boot into recovery, and do things there.
No idea what to do....
This propably comes too late, but I had the same problem last new year's eve. I ordered a new battery and now everything has been working like a dream.
So I have researched everywhere I can, watched videos, etc. and I cant figure this out. Wondering if I bricked my phone.
Originally my phone was stuck on the boot animation screen for Essential. For hours. So I factory reset it using the stock recovery. After that phone would boot and either get stuck on the essential Logo, or stuck on the boot animation. I reset the phone a bunch of times, and on 1 of them I was able to get to the phone set up screen which I quickly got through and made sure I was in developer mode, and had OEM unlocked turned on. While I was in the setup screen all kinds of services kept force closing, and about 30 seconds after setting up the developer stuff to unlock the bootloader the phone finally froze and went to the boot animation screen and just stayed there.
Next I unlocked the bootloader following the steps on here, then unlocked critical_processes or whatever it is called.
Next I tried to flash a stock essential rom from the roms dump page. When trying to wipe user date I get "error. Cannot generate image for userdata". I then flashed the stock rom, and restarted and experienced the same exact thing as before. Either stuck on logo screen, or stuck on boot animation....for hours.
Last I tried flashing to the stock rom recommended in the lineage OS thread, and then flashed TWRP again, and flashed Lineage, and once again I am stuck on the essential logo screen. If i go into recovery it now goes to the Lineage recovery so I am assuming the install worked.
I am completely stuck now and can not figure out what to do next, or if I am just stuck with a hard bricked phone. Any help would be appreciated.
Update: So after restarting the phone about 7-8 times I actually got Lineage OS to load up and was able to set the phone up. That lasted about 2-3 minutes before the phone froze, went back to the Lineage startup animation and then restarted. Now it won't go past the Essential logo screen.
I'm new to the PH-1. I went in circles because all I wanted was the AOSiP ROM. Then no touch, tried flashing the September "hyp" and "rpm" partitions. Didn't help... And on it went.
I finally dug out of my hole by sideloading the essential.com OTA in stock recovery.
That's what I would try if I were you. But then, I'm new to the phone [emoji23]
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
ktmom said:
I'm new to the PH-1. I went in circles because all I wanted was the AOSiP ROM. Then no touch, tried flashing the September "hyp" and "rpm" partitions. Didn't help... And on it went.
I finally dug out of my hole by sideloading the essential.com OTA in stock recovery.
That's what I would try if I were you. But then, I'm new to the phone [emoji23]
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
Sideloading it using the factory recovery is the only thing I didn’t do. Everything I flashed through fastboot. Guess I’ll try sideloading it next.
minttoast said:
Sideloading it using the factory recovery is the only thing I didn’t do. Everything I flashed through fastboot. Guess I’ll try sideloading it next.
Click to expand...
Click to collapse
Did that work for you?
I was having these same kind of problems - all guides never said a thing about flashing unlock_critical - after I did that (and all other requirements to unlock and flash roms) then sideloaded I think it was .092 factory zip - I was able to start flashing things like old school android that I am used to. Still need to figure out why they are saying to use magisk on a boot.img and then flash manually but that may just be certain roms.
Hello together,
I'm using official RR ROM 7.0.2 on my G900F, until recently with latest tuned kernel. I suddenly got some random freezes with reboots without knowing the reason. Then after some crashes it resulted in a bootloop, meaning that the RR bootscreen is loading forever (already tested for hours).
Flashing RR ROM again fixed the issue completely, but when I flash tuned kernel again I immediately end in bootloop. Flashing boot.img of RR ROM once again fixes the problem. Then I tried Intelli-Kernel and it boots, however the first unlock screen is very laggy, system ui takes long time to load after unlock (after that it works normal) and I get here and then sudden reboots. After some crashes/reboots I end up with bootloop with Intelli-Kernel.
Once again: flashing boot.img of RR fixes all the problems.
It's unlikely that the kernels itself are at fault, as they are working for many others and also worked for my device until recently.
So why am I unable to use custom kernels suddenly and how can I fix it?
I'm grateful for any hints you can give to pinpoint the reason. I already asked in the kernel Telegram group but sadly they weren't able to help me.
- I'm clearing dalvik/cache every time,
- tried TWRP repair feature for /data partition
- and as far as I can say I removed all remands of boeffla config app, but even if there are some they should load after system boot so obviously kernel settings aren't applied when I stuck on boot screen.
I don't overclock but for the same reason it shouldn't matter even if I do.
If possible, I would like to avoid a full wipe.
Thanks in advance.
Have you tried backing up your entire phone, wiping and installing RR, letting it boot etc before rebooting to recovery and installing a custom kernel again? If that fails, then either the version of RR you are using is incompatible, or you have some sort of hardware failure somewhere.
I've finally decided to install LineageOS on my phone after three years of using stock but when I install 16 it gets stuck on a repeating bootloop when I turn it on where as 15.1 boots correctly. I'll assume this means my bootloader is out of date even though my stock image was fully upto date before I attempted this so to avoid any headaches of myself reading some misinfomation could someone tell me if first I'm correct in thibking this is a bootloader issue and second what I need to flash to get past this problem?
Newer version of stock and a clean install.