I just spent a few days compiling this kernel. Fixed the paths and whatnot for RNDIS, etc. Its compiling fine but upon packing it with AnyKernel2 and flashing, I get a System Destroyed message, where I have to boot a TWRP img via fastboot and restore a working boot.img. I tried a brand new kernel source with no edits as well, same issue. What am I missing?
I did a make for tissot-perf_defconfig first, then I built it with make -j4 (i have 4 threads). Compiles to a Image.gz-dtb, place it in the AnyKernel2 root and zip it and flash. Flashes fine, boot fails before boot anim.
I tried manually packing the kernel into a boot.img i pulled from a TWRP backup (RR), but fastboot complains its missing DTB no matter which kitchen I use (AIK, Carliv Image Kitchen). Maybe this is the issue?
Thanks!
PS: I'm running it on top of RR 8.1 if that affects anything.
Also is there a Telegram I can join for these questions?
edit: tried pulling the config from a stock boot img using extract-ikconfig. still the same issue booting.
I've wiped the data of my phone. Yes, The os of the phone. I wanted to install the custom lineage os 8.0 rom. I flashed it using twrp and the gapps zip too but at first it was showing that that os was for z010d (which i was using) and not for *dash* *dash*.
So I deleted the 2 lines binary script or what ever it is called inside the meta inf - google - android - binary script. Then it flashed and leaving value 1.00000 something. Then flashed the gapps zip file. Then I rebooted. Everything seemd alright but the boot show just the asus logo powered by android and nothing else. What to do now?
developer.Kabir said:
I've wiped the data of my phone. Yes, The os of the phone. I wanted to install the custom lineage os 8.0 rom. I flashed it using twrp and the gapps zip too but at first it was showing that that os was for z010d (which i was using) and not for *dash* *dash*.
So I deleted the 2 lines binary script or what ever it is called inside the meta inf - google - android - binary script. Then it flashed and leaving value 1.00000 something. Then flashed the gapps zip file. Then I rebooted. Everything seemd alright but the boot show just the asus logo powered by android and nothing else. What to do now?
Click to expand...
Click to collapse
I'll provide any detail you guys need. Please help ?
I've put together a guide for building your own LineageOS 17.1 (android 10) using a docker build environment or on your own system. The guide includes environment setup, and installation instructions as well as some troubleshooting and debugging information.
The easy way is as simple as cloning two git repos, getting the docker image, and running build_sargo.sh
The hard way goes into more detail, requires more previous knowledge, and doesn't use the docker but is useful for getting more familiar with the process.
The docker image is one that already existed for building lineageos 16modified to supports lineagsos 17.
It also includes patches that haven't been merged upstream yet that fix bluetooth, a bootloop, and increase battery life.
With some small modifications, this could also be used for the Pixel 3a XL (bonito)
https://github.com/SolidHal/Build-lineageos-sargo
Thanks for this!
Stealth111
SolidHal said:
I've put together a guide for building your own LineageOS 17.1 (android 10) using a docker build environment or on your own system. The guide includes environment setup, and installation instructions as well as some troubleshooting and debugging information.
The easy way is as simple as cloning two git repos, getting the docker image, and running build_sargo.sh
The hard way goes into more detail, requires more previous knowledge, and doesn't use the docker but is useful for getting more familiar with the process.
The docker image is one that already existed for building lineageos 16modified to supports lineagsos 17.
It also includes patches that haven't been merged upstream yet that fix bluetooth, a bootloop, and increase battery life.
With some small modifications, this could also be used for the Pixel 3a XL (bonito)
https://github.com/SolidHal/Build-lineageos-sargo
Click to expand...
Click to collapse
There should be VERY little modification required from sargo to bonito as one is simply a different size than the other. (I'm actually surprised that nobody ever compared the two in terms of hardware (especially since their simultaneous release).
I have built pure lineageos 17 according to https://forum.xda-developers.com/pixel-3a/how-to/guide-easily-build-install-lineageos-17-t4048063
The esim manager has to be disabled or you have to stop enforcing SELinux.
Download:
https://drive.google.com/drive/folders/19MD_1CZrhejh29ui3Q12Ypqfp-mU3dlt?usp=sharing
anonym12 said:
I have built pure lineageos 17 according to https://forum.xda-developers.com/pixel-3a/how-to/guide-easily-build-install-lineageos-17-t4048063
The esim manager has to be disabled or you have to stop enforcing SELinux.
Download:
https://drive.google.com/drive/folders/19MD_1CZrhejh29ui3Q12Ypqfp-mU3dlt?usp=sharing
Click to expand...
Click to collapse
If you include gapps in your build, the esim manager should stop crashing. If running gappless, I remove esim and hotword enrollment from the proprietary files.
gee one said:
If you include gapps in your build, the esim manager should stop crashing. If running gappless, I remove esim and hotword enrollment from the proprietary files.
Click to expand...
Click to collapse
Hello!
I have also built & installed lineageos 17 according to the guide above, thanks!
Now i like to install Gapps, but how? Booting to linage-recovery and flash from internal storage wont work as it refuse to mount? And adb sideload'ing gapps-nano-zip gives a error message about to little space available? Any ideas?
spinxen said:
Hello!
I have also built & installed lineageos 17 according to the guide above, thanks!
Now i like to install Gapps, but how? Booting to linage-recovery and flash from internal storage wont work as it refuse to mount? And adb sideload'ing gapps-nano-zip gives a error message about to little space available? Any ideas?
Click to expand...
Click to collapse
The issue is the new dynamic partition scheme doesn't leave enough room to install any extra system apps. There is a patch on the Lineage Gerrit, but it hasn't been merged (https://review.lineageos.org/c/LineageOS/android_device_google_bonito/+/261941).
fireclaw722 said:
The issue is the new dynamic partition scheme doesn't leave enough room to install any extra system apps. There is a patch on the Lineage Gerrit, but it hasn't been merged (https://review.lineageos.org/c/LineageOS/android_device_google_bonito/+/261941).
Click to expand...
Click to collapse
Thanks for letting me know, so as of now there is no workaround to get GApps work with this branch after it has been installed?
spinxen said:
Thanks for letting me know, so as of now there is no workaround to get GApps work with this branch after it has been installed?
Click to expand...
Click to collapse
Not that I know of. You either have to create space for G-Apps, or bundle G-Apps with the ROM.
spinxen said:
Hello!
I have also built & installed lineageos 17 according to the guide above, thanks!
Now i like to install Gapps, but how? Booting to linage-recovery and flash from internal storage wont work as it refuse to mount? And adb sideload'ing gapps-nano-zip gives a error message about to little space available? Any ideas?
Click to expand...
Click to collapse
I include gapps when I build the ROM. I have a vendor tree that is based off of opengapps pico. I just unpacked this pico zip and mimic'ed what it installed, plus something like pixel migration tool.
gee one said:
I include gapps when I build the ROM. I have a vendor tree that is based off of opengapps pico. I just unpacked this pico zip and mimic'ed what it installed, plus something like pixel migration tool.
Click to expand...
Click to collapse
Would you mind to share your zip? Thanks!
spinxen said:
Would you mind to share your zip? Thanks!
Click to expand...
Click to collapse
https://opengapps.org/
anonym12 said:
I have built pure lineageos 17 according to https://forum.xda-developers.com/pixel-3a/how-to/guide-easily-build-install-lineageos-17-t4048063
The esim manager has to be disabled or you have to stop enforcing SELinux.
Download:
https://drive.google.com/drive/folders/19MD_1CZrhejh29ui3Q12Ypqfp-mU3dlt?usp=sharing
Click to expand...
Click to collapse
gee one said:
I include gapps when I build the ROM. I have a vendor tree that is based off of opengapps pico. I just unpacked this pico zip and mimic'ed what it installed, plus something like pixel migration tool.
Click to expand...
Click to collapse
This is somewhat above my level of knowledge, if you have a complete build zip with Gapps, do u mind sharing this with me?
How to install?
LioneageOS 17.1 for Poxel 3a: Notes from the front
gee one said:
I include gapps when I build the ROM. I have a vendor tree that is based off of opengapps pico. I just unpacked this pico zip and mimic'ed what it installed, plus something like pixel migration tool.
Click to expand...
Click to collapse
Because of the issues, I have stuck with those versions that include GApps (invisiblek's simple LineageOS 17.1 works a treat, and is cloneable for those looking to build their own). Until beta 3 of Android 11 drops, I'm running this. Still no TWRP, or root, or anything else. Other than Pixel Launcher, I'm basically running stock Lineage.
Hi guys,
Just built my own image according to the 'easy' method (using docker). Took about 5 hours, and seemed to have gone well, almost no errors
I started out by flashing the Pixel 3a with the lastest Android 10 Factory Image from Google (QQ2A.200305.002, Mar 2020) to be sure it's as clean as possible. Booted into Android 10 once, enabled Developer Settings et cetera.
Then followed the 'Install' steps from https://github.com/SolidHal/Build-lineageos-sargo:
- boot into bootloader (fastboot mode)
- run 'fastboot flash boot boot.img'
- reboot into recovery -> Apply update -> Apply from ADB -> run 'adb sideload lineage-17.1-20200404-UNOFFICIAL-sargo.zip' (in my case)
When entering recovery mode I noticed an error at the botton of the screen: 'E:[libfs_mgr]Failed to mount /data: Invalid argument'. Despite that I could continue and sideload/install my self built lineageos zip, which finished without error (status 0). After installation the phone went back to into recovery mode (as described on the Github guide). Unfortunately, when I continued and picked 'Reboot System Now' I got thrown into the bootloader with enter reason: 'error boot prepare'. Every time the phone boots I see this error now.
Does anybody have a clue what I could be doing wrong? Any help is appreciated, thanks!
Edit: Okay, seems my problem is solved. When flashing the self-built boot.img, in my case I also had to specify which boot part to flash to: boot_a or boot_b. After having done that, booting now works.
Thanks SolidHal for providing your docker file and making it easy to built your own LineageOS 17.1 image!
Working and Running Smoothly
Thanks for posting this.
I was also able to build and install this successfully using the easy method. Yes, it takes a long time and requires an ample amount of memory and storage.
The battery life is excellent compared to the other roms/kernels I've tested so far. Started with a factory flash of Android 10.0.0 (QQ2A.200305.002, Mar 2020) (https://developers.google.com/android/ota). Then I followed the instructions here.
I also had the E:[libfs_mgr] error but it still installed correctly after the second try. Specifying boot_a or boot_b may have been what got this to work for me. Thanks to P1x3l3d.
Rooted by patching the boot image with Magisk (https://forum.xda-developers.com/pixel-3a/how-to/how-to-root-pixel-3a-preferred-t3938783).
P1x3l3d said:
Hi guys,
Just built my own image according to the 'easy' method (using docker). Took about 5 hours, and seemed to have gone well, almost no errors
I started out by flashing the Pixel 3a with the lastest Android 10 Factory Image from Google (QQ2A.200305.002, Mar 2020) to be sure it's as clean as possible. Booted into Android 10 once, enabled Developer Settings et cetera.
Then followed the 'Install' steps from https://github.com/SolidHal/Build-lineageos-sargo:
- boot into bootloader (fastboot mode)
- run 'fastboot flash boot boot.img'
- reboot into recovery -> Apply update -> Apply from ADB -> run 'adb sideload lineage-17.1-20200404-UNOFFICIAL-sargo.zip' (in my case)
When entering recovery mode I noticed an error at the botton of the screen: 'E:[libfs_mgr]Failed to mount /data: Invalid argument'. Despite that I could continue and sideload/install my self built lineageos zip, which finished without error (status 0). After installation the phone went back to into recovery mode (as described on the Github guide). Unfortunately, when I continued and picked 'Reboot System Now' I got thrown into the bootloader with enter reason: 'error boot prepare'. Every time the phone boots I see this error now.
Does anybody have a clue what I could be doing wrong? Any help is appreciated, thanks!
Edit: Okay, seems my problem is solved. When flashing the self-built boot.img, in my case I also had to specify which boot part to flash to: boot_a or boot_b. After having done that, booting now works.
Thanks SolidHal for providing your docker file and making it easy to built your own LineageOS 17.1 image!
Click to expand...
Click to collapse
Did you build in Linux? If so, which version? (I'm not used to building Docker - and especially in Linux - and I'd rather do it right; therefore WHICH version of Linux has everything to do it right is critical.)
PGHammer, I don't think it's going to matter too much what distro you use because you're going to have to install the latest platform-tools and install docker from a repo anyways. Just use something recent. Ubuntu comes to mind if you're not a huge GNU/Linux guy.
I built using Debian Stretch and had no issues other than my ram got all used up so I had to create more swap and add
vm.swappiness=60 to /etc/sysctl.conf
You need 100+GB HDD, 16GB+ RAM, and a fat swap space (I used a 20GB Swap file)
Also someone (anon12?) already posted a ~700MB zip of their build in this thread and I can confirm it works.
barqs_root said:
Also someone (anon12?) already posted a ~700MB zip of their build in this thread and I can confirm it works.
Click to expand...
Click to collapse
How did you you get this to install, I get signature verification failed, error:21. Then abd aborts the installation. I confirmed the integrity of the images with the provided checksum files. I even downgraded back to February's update because I was on Aprils update and thought that maybe that was the issues.
The steps I did are as follows:
Unlock bootloader
Enable debugging
Booting into the boot loader- run ./fastboot flash boot_a boot.img( ./ before is required due to being stuck on windows while I work from home.) Successfully installs to boot_a in 2.5sec.
Booting to recovery
Wipe/factory reset
Apply update from ADB- ./adb sideload lineage-17.1-20200222-UNOFFICIAL-sargo.zip
This is the following errors
E: failed to verify whole-file signature
Update package verification took 35.0 s (result 1).
E: Signature verification failed
E: error: 21
Install from ADB completed with status 2.
Installation aborted.
Hi everyone,
I tried searching for a solution, and despite the multiple guides around, I haven't found one for my specific situation.
I have the S6 Lite running Lineage Recovery and Lineage OS 18.1. I have patched the boot.img that was included in the Lineage OS ZIP using Magisk Manager. However, I cannot flash it in any way. I have tried:
flashing using fastboot, however, no matter how I try booting into fastboot, no device is found
flash using heimdall flash --BOOT boot.img, however the error ERROR: Protocol initialisation failed! is shown, despite heimdall print-pit successfully completing
Am I making some silly mistake, or is this not the correct way to root the device? Thank you!
Hi! You shouldn't have to use a patched boot.img unless you're trying to root a stock rom.
With magisk v22 you can just rename the magisk.apk to .zip and flash through lineage recovery adb, this info is in the second paragraph on topjohnwu's magisk github page so please make sure you're not downloading from some shady source (unless you just skimmed straight to the github download then I'd recommend atleast reading the main page so you know what you're doing in the future).
Hopefully this works for you!
Nervusrek said:
Hi! You shouldn't have to use a patched boot.img unless you're trying to root a stock rom.
With magisk v22 you can just rename the magisk.apk to .zip and flash through lineage recovery adb, this info is in the second paragraph on topjohnwu's magisk github page so please make sure you're not downloading from some shady source (unless you just skimmed straight to the github download then I'd recommend atleast reading the main page so you know what you're doing in the future).
Hopefully this works for you!
Click to expand...
Click to collapse
Thank you very much, this worked perfectly! Will read the documentation more carefully next time.
To be fair, the instructions specifically for Samsung are not particularly clear to me either. It jumps from determining the existence of a ramdisk (yes, good), to the SAR=yes section, which goes right into patching the firmware.
Hello, Sorry if this is the wrong place to post this,
I have recently bought an SM-J337U and wanted to root it, I have searched for a TWRP build but there doesn't seem to be one for this phone. I have been able to get magisk working correctly however. I have tried to build TWRP minimal for the device by creating a device tree with the twrpdtgen python script, flashing the resulting image results in a bootloop with only the screen flashing briefly. I have tried for the past few days to change things around in the device tree (boardconfig/fstab) but haven't gotten anything to work. I also tried to build the full omnirom which results in the same bootloop problem (however at one point I was able to get to the recovery screen but there were errors about the cache partition and permission errors). So I'm looking for help in properly building TWRP for this device. If there's any more information that is needed, I am happy to supply it.
Edit: after going back and starting from scratch, it now shows a single line "Unable to normal boot. invalid RAMDISK LENGTH!"