Related
Dears,
I need to download the lineageos 17.1 source code and build the system then install it into the device Oneplus 7pro to boot success.
I meet some issues that make me can not complete it. If anyone can help me to finish the work, i will pay you dollars.
The system : lineageos 17.1
the device: oneplus 7pro
Thanks very much!
Its really simple actually. What you need is a PC running Ubuntu, Debian Linux or derivate. You will need at least 200-300GB free disk space and you should have 8GB of RAM and a decent CPU.
If you have all of the above you simply follow the build instructions for guacamole (OnePlus 7 Pro) on this link.
https://lineageos.github.io/lineage_wiki/devices/guacamole/build
You will need basic Linux knowledge to have some understanding of what all the commands does on the system.
When done, simply copy the zip to the device, make sure you have correct version of TWRP and follow the installation guide for A/B partition installation, also it's required to do factory reset of device when moving from OxygenOS to LineageOS.
Is this for some school project or something? Else you can find daily builds for guacamole made by my buildbot here (yesterday's build apparently failed for guacamole) - > https://lineageos.wickenberg.nu
pitrus- said:
Its really simple actually. What you need is a PC running Ubuntu, Debian Linux or derivate. You will need at least 200-300GB free disk space and you should have 8GB of RAM and a decent CPU.
If you have all of the above you simply follow the build instructions for guacamole (OnePlus 7 Pro) on this link.
https://lineageos.github.io/lineage_wiki/devices/guacamole/build
You will need basic Linux knowledge to have some understanding of what all the commands does on the system.
When done, simply copy the zip to the device, make sure you have correct version of TWRP and follow the installation guide for A/B partition installation, also it's required to do factory reset of device when moving from OxygenOS to LineageOS.
Is this for some school project or something? Else you can find daily builds for guacamole made by my buildbot here (yesterday's build apparently failed for guacamole) - > https://lineageos.wickenberg
Click to expand...
Click to collapse
You're information is wrong. First off all 8gb ram pc is nowhere near enough. You need at least 16gb with at least a 4gb swapfile to build Android 10. If you don't meet just these requirements your pc will just freeze and shut down when you build. And you don't NEED a pc you can build roms right on your phone with a Google cloud vm. I build with both pc and phone all the time. And according to his op his already started a build but has ran into some build errors. I don't know why people respond to things without fully reading them first.
---------- Post added at 07:28 PM ---------- Previous post was at 07:23 PM ----------
suking89 said:
Dears,
I need to download the lineageos 17.1 source code and build the system then install it into the device Oneplus 7pro to boot success.
I meet some issues that make me can not complete it. If anyone can help me to finish the work, i will pay you dollars.
The system : lineageos 17.1
the device: oneplus 7pro
Thanks very much!
Click to expand...
Click to collapse
{Mod edit}
I really appreciate this other rude person who slams down on us sleep deprevated parents that are just trying to give some advice in the few minutes we have between the rounds of parenting. [emoji12][emoji1787]
Jokes aside, sorry for not reading your entire post, I wasn't 100% attentive at the moment, business as usual with human puppys around [emoji28]
Any rudeness aside, I thing you should really listen to Blackcrane as he can probably teach you a lot about compiling LineageOS 10. One thing I do know is that 48GB and no swap is enough to build both LOS16 and LOS17 at the same time, it never hurts with more RAM. [emoji4]
A couple of weeks ago my phone crashed out of nowhere and QUALCOLM CRASHDUMP MODE was displayed. I got it fixed but since then my wifi isn't turning on. Bluetooth works just fine. Its only the wifi that is causing problem. a few days later it again crashed which forced me to move to a custom ROM; lineage OS. I thought it might fix the issue, but invain. My phone just wont tun on the wifi. The about section says device wifi mac address unavailable. I used busy box and terminal emulator as suggested in one of the post to know the original MAC address but its value tuned out something like this hwdr 00:00:00:00
Any help guys?
.... test MCDKernel.... fixed my WLAN Problem
Release mcd r16 · mcdachpappe/android_kernel_oneplus_sdm845
Two-in-One kernel image installer: The installer detects your current installed OS (OxygenOS / custom ROM) and flashes the correct image file. Prerequisite: An updated firmware isn't needed anymor...
github.com
lamahgra said:
.... test MCDKernel.... fixed my WLAN Problem
Release mcd r16 · mcdachpappe/android_kernel_oneplus_sdm845
Two-in-One kernel image installer: The installer detects your current installed OS (OxygenOS / custom ROM) and flashes the correct image file. Prerequisite: An updated firmware isn't needed anymor...
github.com
Click to expand...
Click to collapse
Can you please tell me step by step process of how to do it. I seem to be messing up somewhere. Pleasseee *_*
flash mcd kernel zip via twrp
mcd-kernel= https://github.com/mcdachpappe/android_kernel_oneplus_sdm845/releases/tag/r17
lamahgra said:
flash mcd kernel zip via twrp
mcd-kernel= https://github.com/mcdachpappe/android_kernel_oneplus_sdm845/releases/tag/r17
Click to expand...
Click to collapse
please can you tell me step by step process. I don't know much about this. I can follow commands tho *_*
OnePlus 6 (enchilada)
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
lamahgra said:
OnePlus 6 (enchilada)
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Click to expand...
Click to collapse
update : didnt work. ANy other thing i could try?
I'm looking for a a way to get two separate display outputs, use eDP to connect 1st monitor(PC monitor), use HDMI to connect 2nd monitor(touch screen monitor).
From https://www.android-x86.org/, there's below descriptions, seems still not supported.
To-Do List
Multiple displays support
Better power management
Miracast
From https://blissos.org/, download below android generic iso image, and after flashed this iso image, we can found which support dual monitors,
display the same content on both monitors.
Android-Generic 11 AOSP (x86_64) Changelog#Kernel5.4 #Mesa20.1 #AOSP
https://sourceforge.net/projects/blissos-dev/files/Android-Generic/PC/aosp/stock/11/AG-11--x86_64-202106131243_k-kernel-5.4_m-x86.iso/download
But after flashed below blissos iso image, android system can boot normally on the 1st monitor(eDP), but only have console on 2nd monitor(HDMI)
Bliss OS 14.3 GMS with Gearlock (x86_64) Changelog#Kernel5.4 #Mesa20.1 #GApps #Gearlock
and we followed "https://docs.blissos.org/development/gui-method-build-bliss-os-14.x", synced the code, then built/flashed, still the same behaviors like blissos iso image.
For above "Android-Generic 11 AOSP" iso image, checked the boot log, there's "HWC=drm_minigbm GARLLOC=minigbm_intel" in the kernel command line,
but for bliss os iso image(download or build locally), there's no "HWC=drm_minigbm GARLLOC=minigbm_intel" in the command line,
only support below options on bliss os, but all are not work for dual monitors, normally on 1st monitor, there's console on 2nd monitor,
----------------------------------------------------------
HWC=drmfb GRALLOC=gbm
HWC=drm GRALLOC=gbm
HWC=drm_minigbm GRALLOC=minigbm
HWC=intel GRALLOC=intel
----------------------------------------------------------
we tried to use https://github.com/intel/minigbm/tree/android10-release to replace external/minigbm, met some build error, from this github, latest minigbm_intel is android 10, minigbm on bliss os 14 is android 11,
and above "Android-Generic 11 AOSP" iso image is actually android 12.
Seems not related with kernel, since we checked 89 kernel patches of android r under vendor_ag, all kernel patches have been merged into blissos 14.
When we tried the "HWC=drm_minigbm GRALLOC=intel", only have console on dual monitors, there's crash for surfaceflinger, sdcard has not been mounted so far, error please refer to attached error.
Why dual monitors supported on "Android-Generic 11 AOSP" iso image?
@electrikjesus could you have a look at this issue? thanks a lot
It will require a number of updates to drm_hwcomposer, gbm_gralloc, libdrm, etc. in order to get second screen activities working properly on AG 11 base. It is working on AG 12, so far, and most of those updates are compatible with AG 11 code base.
Lisbet111111 said:
I'm looking for a a way to get two separate display outputs, use eDP to connect 1st monitor(PC monitor), use HDMI to connect 2nd monitor(touch screen monitor).
From https://www.android-x86.org/, there's below descriptions, seems still not supported.
To-Do List
Multiple displays support
Better power management
Miracast
From https://blissos.org/, download below android generic iso image, and after flashed this iso image, we can found which support dual monitors,
display the same content on both monitors.
Android-Generic 11 AOSP (x86_64) Changelog#Kernel5.4 #Mesa20.1 #AOSP
https://sourceforge.net/projects/blissos-dev/files/Android-Generic/PC/aosp/stock/11/AG-11--x86_64-202106131243_k-kernel-5.4_m-x86.iso/download
But after flashed below blissos iso image, android system can boot normally on the 1st monitor(eDP), but only have console on 2nd monitor(HDMI)
Bliss OS 14.3 GMS with Gearlock (x86_64) Changelog#Kernel5.4 #Mesa20.1 #GApps #Gearlock
and we followed "https://docs.blissos.org/development/gui-method-build-bliss-os-14.x", synced the code, then built/flashed, still the same behaviors like blissos iso image.
For above "Android-Generic 11 AOSP" iso image, checked the boot log, there's "HWC=drm_minigbm GARLLOC=minigbm_intel" in the kernel command line,
but for bliss os iso image(download or build locally), there's no "HWC=drm_minigbm GARLLOC=minigbm_intel" in the command line,
only support below options on bliss os, but all are not work for dual monitors, normally on 1st monitor, there's console on 2nd monitor,
----------------------------------------------------------
HWC=drmfb GRALLOC=gbm
HWC=drm GRALLOC=gbm
HWC=drm_minigbm GRALLOC=minigbm
HWC=intel GRALLOC=intel
----------------------------------------------------------
we tried to use https://github.com/intel/minigbm/tree/android10-release to replace external/minigbm, met some build error, from this github, latest minigbm_intel is android 10, minigbm on bliss os 14 is android 11,
and above "Android-Generic 11 AOSP" iso image is actually android 12.
Seems not related with kernel, since we checked 89 kernel patches of android r under vendor_ag, all kernel patches have been merged into blissos 14.
When we tried the "HWC=drm_minigbm GRALLOC=intel", only have console on dual monitors, there's crash for surfaceflinger, sdcard has not been mounted so far, error please refer to attached error.
Why dual monitors supported on "Android-Generic 11 AOSP" iso image?
Click to expand...
Click to collapse
@electrikjesus Appreciate your quick reply!!
From https://www.android-x86.org/, latest open code base branch is r-86(Android 11), when AG 12 base(Android 12) could be ready and open? Is there any time plan?
From my understanding, updates mentioned below are not included in r-86(Android 11) branch yet, right?
Where can we get these updates so far? we really need these prefect patches,
could these patches can be found by below https://github.com/BlissRoms-x86/manifest/tree/s-x86-r1.1 ?
Just now, I compared r-86 branch and s-x86-r1.1 branch, there are very big change for drm_hwcomposer and libdrm, and grm_gralloc is not existed in s-x86-r1.1 branch.
It will require a number of updates to drm_hwcomposer, gbm_gralloc, libdrm, etc. in order to get second screen activities working properly on AG 11 base. It is working on AG 12, so far, and most of those updates are compatible with AG 11 code base.
Click to expand...
Click to collapse
Lisbet111111 said:
@electrikjesus Appreciate your quick reply!!
From https://www.android-x86.org/, latest open code base branch is r-86(Android 11), when AG 12 base(Android 12) could be ready and open? Is there any time plan?
From my understanding, updates mentioned below are not included in r-86(Android 11) branch yet, right?
Where can we get these updates so far? we really need these prefect patches,
could these patches can be found by below https://github.com/BlissRoms-x86/manifest/tree/s-x86-r1.1 ?
Just now, I compared r-86 branch and s-x86-r1.1 branch, there are very big change for drm_hwcomposer and libdrm, and grm_gralloc is not existed in s-x86-r1.1 branch.
Click to expand...
Click to collapse
Things for that have been made upstream. So gbm_gralloc is now working from mainline repo/Linux.
The recent experiments coming from @HMTheBoy154 also have these included, so you can check his repos for details
electrikjesus said:
Things for that have been made upstream. So gbm_gralloc is now working from mainline repo/Linux.
The recent experiments coming from @HMTheBoy154 also have these included, so you can check his repos for details
Click to expand...
Click to collapse
Thanks again!! It's very helpful.
Hi all,
I'm also trying to get dual monitor to work, with extended Android screen.
It is working on AG 12, so far
Click to expand...
Click to collapse
I tried "Bliss-v15.0-Alpha-android_x86_64-OFFICIAL-foss-202112151838-nb-sd-ksu-gearlock-ex_vt-console_all-mesa-drivers-crocus.iso" and
"android_x86_64-a12.1_r1-03.16.22-01-mesa22-ksu-gapps-libndk-sd.iso", however, I get the same result as the OP - the second display only shows a terminal.
Do I need to use later code and build from source? Or are there any kernel options that needs to be enabled?
Notes:
- Using a AMD Radeon RX 580
- Getting overlay glitches, but the workaround "boot using minigbm_intel" does not work for me (Android doesn't boot then)
Best regards,
Markus
Google posts additional instructions for Pixel 6 owners that flashed Android 13
Can someone explain what the problem is BEFORE people fall prey to it?
Google issued a warning today saying the following:
With Android 13, Google made it so that the Pixel 6, 6 Pro, and 6a cannot reinstall Android 12 in order to address a security issue. In addressing that vulnerability, another problem might arise, and Google has released instructions on how to avoid bricking your device if you flashed Android 13.
A security vulnerability exists with the previous bootloader on the Pixel 6 series, and Android 13 makes it so that the vulnerable version associated with Android 12 cannot be reinstalled.
However, even after flashing an Android 13 factory image - which is different than sideloading an OTA image - on the Pixel 6 series and successfully updating, an Android 12 build remains on your phone. This is due to Android's A/B (seamless) system updates, which are meant to provide redundancy.
Click to expand...
Click to collapse
My question is simply to ask someone who understands this A/B stuff to explain WHERE the specific problem is with the Pixel 6 series but not in any other Pixel? (I have a Samsung which doesn't do the A/B stuff.)
I only know the basics, which is that the newly downloaded OS goes into one partition while the original OS is running in the other partition and somehow they swap when it's time to switch over.
GalaxyA325G said:
Google posts additional instructions for Pixel 6 owners that flashed Android 13
Can someone explain what the problem is BEFORE people fall prey to it?
Click to expand...
Click to collapse
See here
GalaxyA325G said:
My question is simply to ask someone who understands this A/B stuff to explain WHERE the specific problem is with the Pixel 6 series but not in any other Pixel? (I have a Samsung which doesn't do the A/B stuff.)
Click to expand...
Click to collapse
There's two elements in play here. First is the Tensor (Pixel 6 / 6 Pro / 6a) platform bootloader for Android 13, which increments a permanent anti-rollback counter in the device upon successful boot of Android 13. Sort of an e-fuse; it prevents rolling back the bootloader. This does not affect previous Pixels, and was implemented because of a critical security vulnerability in the Android 12 bootloader. This also prevents loading older bootloader images.
Second is the A/B slot system, which is the AOSP recommended format for OEMs to use so as to facilitate seamless updates...
GalaxyA325G said:
I only know the basics, which is that the newly downloaded OS goes into one partition while the original OS is running in the other partition and somehow they swap when it's time to switch over.
Click to expand...
Click to collapse
Sort of.
There's two slots: A and B. Each slot has its own critical partitions: /bootloader_a, /radio_a, /boot_a, /system_a, and so on. The /data partition is shared by both slots.
The way this works is almost exactly as you described. Let's say the system is running on slot A. When an update becomes available, update_engine can download the OTA package, extract the payload, and write the update to slot B - all in the background while the OS is running. This allows user activities to continue and does not prevent critical functions such as phone calls, texts, etc. Once the installation to the other slot is finished, update_engine prompts the user to reboot. It then sets the updated slot, slot B, as "active" so the device will boot from that slot when rebooted. If boot is successful, the system marks that slot as "successful" so the device will always boot from that slot. From the user perspective, their device is only "down" for a couple minutes while it reboots into the updated slot.
If boot fails for whatever reason - bootloop due to corrupt image for example - it will "recycle" to the original slot so the device remains useable instead of being stuck with a corrupted, unbootable update.
The two come together in what is the problem for the Tensor devices: the OTA method only updates one slot, meaning there will now be an Android 13 bootloader on the "new" slot, and Android 12 on the "old" slot. If Android 13 boots far enough to increment the anti-rollback, but later fails and the device recycles to the Android 12 slot, the device will fail to boot because the Android 12 bootloader has now been locked out by the anti-rollback counter.
The reason this doesn't affect Samsung devices is because Samsung has stubbornly resisted the AOSP model and continues to use a standalone /recovery partition instead of the A/B format. The drawback to this is that the system must go "down" for an extended period of time while the update is installed in recovery, preventing use of the device.
Thanks for the clear explanation. From what I've read in other posts, a second fastboot OTA will install Android 13 on the second slot, preventing a potential future brick. Other posts have speculated that Google might create a compliant bootloader for A12L, but there's nothing official, on that. From where I stand, this issue should have been immediately addressed by Google simultaneous with the release of BlueJay. My current choice is to hold-off on A13 until these types of major bugs capable of bricking a device are addressed. Perhaps the Calyx OS folks will tackle this, as well.
Hi, I just registered today to ask this question. Through somewhat simple means using the tools I had available, I was able to readback the stock rom from a TCL 20 XE 5087Z branded under Boost Mobile. I have successfully rooted via magisk and have confirmed that it is indeed the correct stock firmware through a bit of an accident, I forgot to patch vbmeta when flashing magisk_patched_boot.img, so in a panic, I flashed back all the roms I had read back from the device except userdata, and miraculously the device worked! Now the problem I run into is all the bloatware the carrier has installed on the phone. My main reason for rooting my device was I wanted the ability to prevent apps from being killed by the "Smart" manager on the device, because it seems that important apps keep getting killed by the built-in software. I ended up determining that the ram manager on the phone was killing apps based on the amount of ram available. Now that the phone is rooted, you would think I would have no problem getting rid of all the bloatware, except that whenever I forcefully uninstall the ram manager (com.tct.onetouchbooster), the app is still available on my apps menu and clicking on it with pretty much no delay opens the app right up as if the data had just been cleared. Now I have no idea what is causing this, probably another app, but I was wondering if maybe an easier alternative would be to get a generic android image for the device without bloatware that I can install just what I need. Now I say easier, but I find little documentation on how to do this, better yet if it will work. I have limited knowledge of how the android system works, mainly I just understand that /boot contains the bootloader, /system contains the os, and /userdata contains all the extra data apart from the stock image. If someone would enlighten me, would it actually be easier to build a generic image? Are there tools to do this? I understand that firmware is very touchy and that there is no "Generic" image in the sense, but having my stock rom available, would I be able to somehow generate a generic image based on the rom contents? If this would be way harder, how would I go about removing bloatware? I would not want to have to reset my phone each time I uninstall the wrong application, is there a non-data-damaging way to go about removing bloatware? If it ends up not being bloatware that is causing it and some hidden property somewhere in the stock rom config, how hard would it be to find that? Any help would be appreciated, and I am open to any comments and criticism. Please let me know how I might go about this, thanks in advance!
The stock firmware for this device can be found here: https://drive.google.com/file/d/1Q5IDP8V7PvuH2_1z63IFe23O2DF0cXZR/view?usp=sharing
The phone was bought from Walmart with prepaid Boost Mobile and it is a TCL 20 XE 5087Z with a MT6765 processor.
The password for the file is: xda5087Z-MT6765
Is the phone Project Treble enabled? If not don't waste your time.
A GSI is related to Project Treble, which means that the image can be installed on any Project Treble-supported device, regardless of the manufacturer, because it does not contain any hardware-specific components. The advantage is that a GSI can theoretically be used on any Project Treble-supported device.
xXx yYy said:
Is the phone Project Treble enabled? If not don't waste your time.
A GSI is related to Project Treble, which means that the image can be installed on any Project Treble-supported device, regardless of the manufacturer, because it does not contain any hardware-specific components. The advantage is that a GSI can theoretically be used on any Project Treble-supported device.
Click to expand...
Click to collapse
I downloaded the treble info app from the play store and indeed it is available with treble, the system image i need is system-arm64-ab.img.xz, would you mind pointing me in the right direction for how to install this? I'm assuming this just gets installed in the /system partition but let me know if I'm wrong. Thanks!
Can't help you, never did this.
You may look inside here:
[GUIDE] How to build a Project Treble GSI ROM from source? [31/08]
Hello guys, in this guide I'll try to simplify building Treble GSI process. As you read this guide now I'll assume you already have a previous knowledge about How to build android from source, so I won't cover some points with too many basic...
forum.xda-developers.com
Yes, only flash system.img. I recommend Android 10 (Android 11+ introduced restricted permissions)
[DISCONTINUED][GSI][10] LineageOS 17.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 16.0 GSIs I've been making since March 2019. If you clicked in here, I bet you know what LineageOS is already, but just to fill the blank: LineageOS is a free, community built...
forum.xda-developers.com
alecxs said:
Yes, only flash system.img. I recommend Android 10 (Android 11+ introduced restricted permissions)
[DISCONTINUED][GSI][10] LineageOS 17.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 16.0 GSIs I've been making since March 2019. If you clicked in here, I bet you know what LineageOS is already, but just to fill the blank: LineageOS is a free, community built...
forum.xda-developers.com
Click to expand...
Click to collapse
DO NOT DO THIS!!!! The TCL 20 XE is NOT compatible with Android 10 (it only supports something 30, which corresponds to Android 11), and the device will bootloop. I have made this mistake but I can not reach fastboot as the option is not in the recovery, therefore I need to run "adb reboot fastboot" within Android. MTKClient should fix this if you can find a stock super.img file for the 5087z.
note "adb reboot fastboot" is for fastbootd which is in recovery, while "adb reboot bootloader" is for fastboot (you can always enter from Volume button, regardless of destroyed boot/system partition)
boot-loop is probably caused by dm-verity, you forgot vbmeta?
alecxs said:
note "adb reboot fastboot" is for fastbootd which is in recovery, while "adb reboot bootloader" is for fastboot (you can always enter from Volume button, regardless of destroyed boot/system partition)
boot-loop is probably caused by dm-verity, you forgot vbmeta?
Click to expand...
Click to collapse
Fastbootd doesn't have an option in the recovery on my model, I've seen other TCL 20 XE phones have it though (I have the Boost Mobile varient like the thread maker), however Fastbootd let's me boot into recovery. I was only able to flash the stock ROM with MTKClient, which mikedcoombs thankfully provided (I just needed the super partition). For vbmeta, I just have an empty vbmeta that I flashed when I first rooted the phone. I don't think it is dm-verity, because LineageOS 20 as an GSI worked except for the Wi-Fi.