Hello everyone!
About three weeks ago I built first LineageOS zip. Since that time I trying to boot it, but unsuccessful.
I think, here exists someone, who knows how to launch it.
By the way, here is my works:
https://github.com/RunningMango/adroid_device_on5xelte_lineage
https://github.com/RunningMango/adroid_device_7570-common_lineage
Problem is in kernel sources. IDK what patches should I apply to boot it up.
Last kernel log: https://pastebin.com/FYY9KYLq
Related
Hello fellow devs & modding enthusiasts,
I know that the Note 3 version of the CM is still unofficial, but I decided to give it a go and build it for myself.
However, I bumped into a few strange issues and seeing the number of people who have succeeded in producing a working rom it seemed like the right place to look for some advice.
First of all, my environment setup has been done correctly (as per the instructions on the CM site) and my repo is always synced before each build.
I am planning on installing the rom on my Qualcomm SM-N9005, so I thought that the hltexx version is what I need. I "breakfasted" it, then extracted all prebuilts from the phone. "Brunch" came next, along with the first problem:
The build started normally, but after 30-40 seconds I got a missing library (libtime_genoff.so) error message which aborted the build. After looking in the CM directories and not being able to locate it, I decided to get it from the phone itself, just like the prebuilts. So, I did "make clean" and started the build once again, but this time copied the missing library manually to "out/target/product/hltexx/obj/lib" right after the output directories were created in the beginning of the build.
At this point I was very skeptical for the result, but for my surprise after about 1 hour the build was completed without any errors and I was on my way to Flashingtown.
Yes... But no. After selecting the .zip from CWM, I got a incorrect version error from the first assert line of the updater script. It said "this version is for hltexx only, your version is hlte". Now this is just plain weird to me...
I always thought that the SM-N9005 is actually "hltexx". Am I wrong?
As there is no "hlte" only project in the CM repo and having in mind that everyone is building mainly for the 9005 model, I decided to modify the first line of the updater script so to recognize the "hlte" device.
And so I did, then flashed and... well that's it. The device could not boot beyond the "Galaxy Note 3" logo. I immediately flashed one of the unofficial builds from XDA and everything suddenly worked smoothly and I was rocking a nice clean CM on my Note 3.
What am I missing? Is there anything more to building the CM repo for the Note 3?
Any ideas / suggestions will be immensely appreciated!
Cheers,
Vlad
Hey,
I was looking for another kernel for my pretty new nexus 10 and i wanted to try franko kernel, i knew it already from other devices.
Well, I flashed the zip, no problem, and rebooted the tablet.
Even before I was able to unlock the screen, the first message appeared which told me that "com.android.phone" crashed.
It kept showing up, so that i had problems to reboot or shutdown my tablet properly.
I already tried to disable xposed framework, with no effect.
I chose to create a new thread, because i'm not (yet) allowed to post into this one
Repack the kernel with the ramdisk of your rom. I think it should do it
EDIT: THIS WAS RESOLVED IN THE NEW 20171231 NIGHTLY, EVERYTHING WORKS PERFECTLY NOW!
So I have this problem with Lineage OS 13 on my N10, so I flash the following packages:
Super SU 2.78
Busy-box
Open Gapps 6.0 nano
Lineage 13 10/14/17 nightly
The first boot is successful, I install some apps, watch some videos, normal tablet stuff. The problem is when I reboot, every time I reboot it ends in a boot loop. The tablet just won't boot up after I reboot it. The first boot works great, but nothing works after-wards.
Doesn't work on mine either, with CM13 20171017 build. I also made comment on the CM14 build thread here on XDA. I couldn't complete the initial setup using the CM14 build. I'm going back to stock.
I have the same problem with 20171021
I was able to reproduce the Error and attatched a logcat.
The bootloop always started while installing the App "immobilienscout24".
Hope someone can examine my logcat. I attached 2 (split) files, because I don't know, what is relevant.
Best regards
In my case the "BlueMail"-App cause the bootloops. After a factory reset LOS13 works fine, at the end of the install process of BlueMail Android restarts and bootloops. Deleting the bluemail-folder via TWRP solves the problem.
Frank
BerlinOtto said:
In my case the "BlueMail"-App cause the bootloops. After a factory reset LOS13 works fine, at the end of the install process of BlueMail Android restarts and bootloops. Deleting the bluemail-folder via TWRP solves the problem.
Frank
Click to expand...
Click to collapse
So basically I have to pick my apps wisely or lineage will reboot? **** that noise I'd rather run stock lollipop, lineage on my N10 is awful.
Again bootloop at the current nightly version. Official Lineageops version is slowly evolving to crap. I switch to the unofficial nougat version!
I have the same issue of constant boot loops. I tried several LOS nighly build w/o any success.
Funny thing is, after i rolled back to an old CynogenMod backup (v13.0 snapshot from 21.12.2016) it started to boot loop too, after I started updating my apps with Playstore.
So the bug must be very old, and it must be in CM/LOS, not in some specifiy app...
Folks, there is a defect open in the official lineage bug tracking system. please add your comments there - maybe this needs some more support to get looked at:
https://jira.lineageos.org/browse/BUGBASH-1075
Marktplaats causes boot loop
In my case, 'marktplaats', a dutch app, caused the boot loop. At some point I decided to upgrade to Lineage. I never had any issues on Cyanogenmod 13.
There seems to be a solution for this Problem in the newest nightly, See
https://jira.lineageos.org/browse/BUGBASH-1052
I've done a test Installation with my two Problem apps and it works fine for me.
I0tacle said:
Again bootloop at the current nightly version. Official Lineageops version is slowly evolving to crap. I switch to the unofficial nougat version!
Click to expand...
Click to collapse
All the problems were fixed in the in 20171231 nightly, running it without hitch no, stable and fast MM with CM theme support, finally
I am running LineageOS 17.1 (ver. 0.2.11.202414 ) with microg on my oneplus 6T.
I am totally happy with it except that sometimes my nfc is not working on my yubikey but with this i can life.
My main problem i have with updates to newer builds. They are released every week and under settings->system->advanced->updater I can see the builds that i could download and install. Also the OS is reminding me that i should update to newer versions.
I did it once and I softbricked my phone and i dont understand why...
On the LOS guide the steps mentioned are these:
Open Settings, navigate to “System”, then “Updater”.
Click the Refresh Icon in the top right corner.
Choose which update you’d like and press “Download”.
When the download completes, click “Install”. Once the update process has finished, the device will display a “Reboot” button, you may need to go into the Updater menu in Settings, “System” to see it. This will reboot you into the updated system
This is for shore not working with my version and microg variant.
How should i proper update my OS to a newer build version?
Does nobody have a hint for me?
marsxxl said:
Does nobody have a hint for me?
Click to expand...
Click to collapse
Maybe try asking in the Lineage thread.
marsxxl said:
I am running LineageOS 17.1 (ver. 0.2.11.202414 ) with microg on my oneplus 6T.
Click to expand...
Click to collapse
The updater had issues originally. Although since you are using microg, you might have issues anyways. Now it would probably work if you were using a stock version of Lineage. Personally I still just use TWRP to update.
I have a guide here: Installing Lineage, it covers updating.
The only time I ran MicroG for any length of time was Omni, but it was still updated the same way.
You should be able to just flash the new build in recovery, flash the TWRP installer, reboot to recovery, flash Magisk if you use it, reboot to system. Since at this point, most modules will cause problems if flashed in TWRP.
I don't know how old your phone's firmware is, but there was a point in there LOS started checking for the updated firmware, so you maybe forced to update too. It should check before it flashes anyways. So just know if it errors out, you'll be updating everything. Be prepared to backup and clean install if you have to.
Thank you a lot @OhioYJ !
I was able to do the Update
If someone is interested in the NFC problem that I have, i will post it here:
https://forum.xda-developers.com/t/nfc-not-working.3945659/#post-84280433
Hi, after attempting to enable encryption I get an infinite boot loop animation, and after I force a hard reset (keeping the power button pressed) the phone boots back to normal as if nothing happened. This means that encryption was not even started (otherwise it would be needed to format partition again if the process was interrupted).
What are my options here? On previous Android versions, whenever I came across a Rom that didn't support encryption, I would just flash a stock recovery image alongside the custom rom and try encrypting again, successfully. However, there are no Android 11 stock recovery images for this device (it got abandoned in Android 8.1 I believe), so this isn't an option anymore.
Unfortunately this ROM doesn't seem to have a dedicated thread here on XDA and people on their Telegram channel have not been able to provide guidance so far...
Any tips are appreciated!
ROM: PixelExperience Plus 11 (Android 11) version 2021.05.14
Device: Moto G5 Plus (potter, XT1685)
Recovery image: TWRP 3.5.2_9-0-potter
I have found no v11 or v10 roms which work with encryption (even when they say they do). I have not tried many v9; Your answer is to go back to stock 8.1 and everything will work again (but you'll be on v8):
[Oreo][Stock][Rom] TWRP Flashable Stock Builds
About this project This project provides repackaged Stock Oreo roms that can be flashed by TWRP. Modifications from stock are listed below. As we are now moving into the Oreo world, I've decided that now is a good time to make a few changes...
forum.xda-developers.com
edit: note that i'm on xt1687 (usa) model of potter
edit2: I just tried Arrow v10(official) and it encrypts (after a number of reboots; give it time)
bravo97 said:
edit2: I just tried Arrow v10(official) and it encrypts (after a number of reboots; give it time)
Click to expand...
Click to collapse
hi, in the case of PE+ 11, it just goes to reboot the first time and stays in loading android screen forever (waited a couple hours last time), so I think "giving it more time" wouldn't solve it.
Good to know there's some Rom compatible with encryption though, although it's android 10... I also got a hint that crDroid 11 may be compatible with encryption on potter.