General [WIP] Porting LineageOS 20 to the Oneplus 11

Search This thread
By:
Advanced…
D

dekefake

Senior Member
Oct 28, 2013
995
1,560
Orleans, France
m_vaisakh said:
I already am helping him, but I'm limited by not having the device :(
Click to expand...
Click to collapse
Yes same. I'll purchase it once we succeed, else I'll go for the S23 Ultra.
ChrisFeiveel84 said:
maybe you should start a survey on xda and tg how many people want a custom rom for the op11 these days
Idk
Click to expand...
Click to collapse
It still looks like a lot of people are interested in custom ROM for the OP11 but the MSM Tools situation is what prevents development and enthusiasts from purchasing it.
 
ChrisFeiveel84

ChrisFeiveel84

Senior Member
Jun 29, 2017
742
253
38
Germany
OnePlus 11
idk because many people have told that they are no longer interested in custom roms or root.


idk if that's true but some also said that they went to the support center in india with their op10p that was bricked and didn't pay anything for the unbricking (we don't even have the support center here)
 
cabagekiller

cabagekiller

Senior Member
Apr 25, 2010
359
68
32
Huber heights
OnePlus 8T
Google Pixel 6 Pro
ChrisFeiveel84 said:
idk because many people have told that they are no longer interested in custom roms or root.


idk if that's true but some also said that they went to the support center in india with their op10p that was bricked and didn't pay anything for the unbricking (we don't even have the support center here)
Click to expand...
Click to collapse
Custom roms are still popular for different reasons. The blocks that have to be overcame for root and custom roms make people less likely to do it.
 
G

Guyinlaca

Senior Member
Sep 13, 2010
580
340
Google Pixel 6 Pro
As someone who created custom themes in the OG Droid days and tried a lot of custom ROM's, the good old days are gone. Even on the "easy" to root phones, there are a lot more hoops to jump through. Especially since the A/B slot partitions were introduced. It used to be you just installed a custom recovery, flashed whatever worked and updated directly from the ROM. The OnePlus 8 Pro was the last great software experience out of the box and didn't need a custom ROM. OxygenOS 13 however is a dumpster fire and I commend everyone who is working to make LineageOS or any AOSP ROM a reality. Thank you for your hard work.


Simple things such as easily swiping the notifications away, having a familiar and labeled settings menu, changing the DPI in Developer Options and having it survive a reboot, and having third party launchers work with gesture navigation are not too much to ask. The hardware is great and love the smaller form factor compared to the S23 Ultra. If only we could get great software too.
 
  • Like
Reactions: ummduh, dekefake and _Johnito_
cavist

cavist

Senior Member
Nov 19, 2010
279
83
Over the years I tried tens of custom roms on OP7 Pro, OP8 and personaly I am sick and tired of them. Always something does not work as intended. Always any of the rom have different bug or sth does not work, no matter how long in development.
And this stupid attitude in the opening thread "Bugs, errors? None are known, you tell me" and literally entire rom thread is filled by people having various bugs and errors.

I gave up on any of the custom roms. For all those years it was a total waste of time for me. I can't recall any fully working rom without issues and going back to stock OOS was always the best choice for me and the best experience overall even when the OOS itself was not perfect.
 
  • Like
  • Sad
Reactions: mxthocc and Patrickzhong
W

wangdaning

Senior Member
Sep 17, 2012
1,477
621
Wuxi
Have you guys already put together the device tree? If you have that up in github I believe that would allow this thread to move back to development tag, but you have to post it. Also, how are you planning to implement kernel? Build with rom or use prebuilt?

I think the proprietary qcomm stuff is in the oneplus git release.
 
Last edited:
  • Like
Reactions: headphones1, ChrisFeiveel84 and w_tapper
H

headphones1

Member
Apr 13, 2015
8
3
cavist said:
Over the years I tried tens of custom roms on OP7 Pro, OP8 and personaly I am sick and tired of them. Always something does not work as intended. Always any of the rom have different bug or sth does not work, no matter how long in development.
And this stupid attitude in the opening thread "Bugs, errors? None are known, you tell me" and literally entire rom thread is filled by people having various bugs and errors.

I gave up on any of the custom roms. For all those years it was a total waste of time for me. I can't recall any fully working rom without issues and going back to stock OOS was always the best choice for me and the best experience overall even when the OOS itself was not perfect.
Click to expand...
Click to collapse
In the interest of showing a bit of encouragement in this thread, I had a lot of issues with an OP7 Pro ROM search until I landed on one I found with absolutely 0 issues I could find, Evolution. Now that is a crazy featured ROM and probably not that easy to implement but if Lineage can happen and be usable, I find that immensely exciting and even defiant to the status quo established by the 10 series. I wish I kept up on programming and understand that it is difficult, but I want to be positive and am willing to test if time allows. The userbase will be larger for the 11 and I am sure some would happily donate a coffee for the trouble. We appreciate it!
 
  • Like
Reactions: suresh007, JPower123 and omgitsMATT
w_tapper

w_tapper

Senior Member
Sep 13, 2022
677
319
Samsung Galaxy Note 10.1
Lenovo K8 Note
headphones1 said:
In the interest of showing a bit of encouragement in this thread, I had a lot of issues with an OP7 Pro ROM search until I landed on one I found with absolutely 0 issues I could find, Evolution. Now that is a crazy featured ROM and probably not that easy to implement but if Lineage can happen and be usable, I find that immensely exciting and even defiant to the status quo established by the 10 series. I wish I kept up on programming and understand that it is difficult, but I want to be positive and am willing to test if time allows. The userbase will be larger for the 11 and I am sure some would happily donate a coffee for the trouble. We appreciate it!
Click to expand...
Click to collapse
evo x is a beautiful rom, no bugs on my pixel 6 pro with it
 
D

dekefake

Senior Member
Oct 28, 2013
995
1,560
Orleans, France
cavist said:
Over the years I tried tens of custom roms on OP7 Pro, OP8 and personaly I am sick and tired of them. Always something does not work as intended. Always any of the rom have different bug or sth does not work, no matter how long in development.
And this stupid attitude in the opening thread "Bugs, errors? None are known, you tell me" and literally entire rom thread is filled by people having various bugs and errors.

I gave up on any of the custom roms. For all those years it was a total waste of time for me. I can't recall any fully working rom without issues and going back to stock OOS was always the best choice for me and the best experience overall even when the OOS itself was not perfect.
Click to expand...
Click to collapse
Lmao that is the very reason I built AOSPA myself for the OnePlus 7 Pro back in the days. Daily driven it until I got the OnePlus 8 Pro, and I'm still using it since then.
wangdaning said:
Have you guys already put together the device tree? If you have that up in github I believe that would allow this thread to move back to development tag, but you have to post it. Also, how are you planning to implement kernel? Build with rom or use prebuilt?

I think the proprietary qcomm stuff is in the oneplus git release.
Click to expand...
Click to collapse
Yes, the device tree is done afaik, and a LineageOS build was completed but it failed to boot and the phone rebooted in fastboot mode. I don't think Chandu is far from booting it, but it still requires some work. As I'm not the one who built the device tree, I won't change the thread tag to development, but Chandu is free to create a new thread to take credit of his own work.
Guyinlaca said:
As someone who created custom themes in the OG Droid days and tried a lot of custom ROM's, the good old days are gone. Even on the "easy" to root phones, there are a lot more hoops to jump through. Especially since the A/B slot partitions were introduced. It used to be you just installed a custom recovery, flashed whatever worked and updated directly from the ROM. The OnePlus 8 Pro was the last great software experience out of the box and didn't need a custom ROM. OxygenOS 13 however is a dumpster fire and I commend everyone who is working to make LineageOS or any AOSP ROM a reality. Thank you for your hard work.


Simple things such as easily swiping the notifications away, having a familiar and labeled settings menu, changing the DPI in Developer Options and having it survive a reboot, and having third party launchers work with gesture navigation are not too much to ask. The hardware is great and love the smaller form factor compared to the S23 Ultra. If only we could get great software too.
Click to expand...
Click to collapse
The OP8 series were the last great we could have fun with because the OP9 had some bugs and noone released anything for the 10 Series. That will change with the OnePlus 11 if we succeed, as it's a great phone hardware-wise. Else, a lot of us including me probably won't purchase any OnePlus devices anymore.
 
  • Like
  • Love
Reactions: qriozum, Ad+1, w_tapper and 5 others
You must log in or register to reply here.

Similar threads

M
General Stock Firmware Collection for OnePlus 11
Replies
363
Views
35K
dmarden
dmarden
zelos156
Question OnePlus 11 Unlock bootloader/msm tool/custom rom
Replies
84
Views
12K
Canuck Knarf
Canuck Knarf
Mobile_Slution
Question OnePlus 11 Convert to OXYGENOS - Fastboot ROM - FLASH_ALL
Replies
59
Views
9K
ThienAn2023
ThienAn2023
G
General Honest opinion of the OnePlus 11
Replies
36
Views
7K
U
ummduh
birdie
General [WARNING] Calling stops working outside of China for the Chinese version
Replies
419
Views
43K
A
alexander宇

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 29
    D
    dekefake
    We all know the path OnePlus/Oppo went with development, MSM Tools and all, and I want to make it clear and short : I'm going to work on this phone no matter what. The OnePlus 10 series were a failure in this regard and I don't want the OnePlus 11 to experience the same.

    I've been in this space for quite some years now, since Xperia X10 times and Android 2.3, and my last device has been a OnePlus 8 Pro that have provided me great service. Sadly, the battery is slowly dying and I can't bring myself to purchasing a phone I cannot tamper with. I've always loved OnePlus and I have hard times considering anything else.

    If you're a developer, just wave at me using this thread. We need to know each other and work together to bring something to this phone. The obvious path would be to at least get a TWRP and a basic kernel built. I absolutely want to get to a LineageOS build.

    If you're not a dev, but you have deep understanding on how fastboot, bootloader, and all else means, you can be a tester. I haven't bought the OnePlus 11 yet but I'm going to work on it and acquire it if some of you follow me.

    If you're nether of these, you can still share the thread to other people to raise awareness.

    I'll likely create a Telegram conversation if we get to a few devs. If you're interested in working on the OnePlus 11, please post a reply
    View
    9
    daxiaamu
    daxiaamu
    oneplus 11 twrp install guide: https://www.bilibili.com/video/BV1Gv4y1r7Gv/
    I develope the app and also update the video above.
    Oneplus roms collection: https://op.daxiaamu.com (yes I maintained it)
    View
    8
    D
    dekefake
    cavist said:
    Over the years I tried tens of custom roms on OP7 Pro, OP8 and personaly I am sick and tired of them. Always something does not work as intended. Always any of the rom have different bug or sth does not work, no matter how long in development.
    And this stupid attitude in the opening thread "Bugs, errors? None are known, you tell me" and literally entire rom thread is filled by people having various bugs and errors.

    I gave up on any of the custom roms. For all those years it was a total waste of time for me. I can't recall any fully working rom without issues and going back to stock OOS was always the best choice for me and the best experience overall even when the OOS itself was not perfect.
    Click to expand...
    Click to collapse
    Lmao that is the very reason I built AOSPA myself for the OnePlus 7 Pro back in the days. Daily driven it until I got the OnePlus 8 Pro, and I'm still using it since then.
    wangdaning said:
    Have you guys already put together the device tree? If you have that up in github I believe that would allow this thread to move back to development tag, but you have to post it. Also, how are you planning to implement kernel? Build with rom or use prebuilt?

    I think the proprietary qcomm stuff is in the oneplus git release.
    Click to expand...
    Click to collapse
    Yes, the device tree is done afaik, and a LineageOS build was completed but it failed to boot and the phone rebooted in fastboot mode. I don't think Chandu is far from booting it, but it still requires some work. As I'm not the one who built the device tree, I won't change the thread tag to development, but Chandu is free to create a new thread to take credit of his own work.
    Guyinlaca said:
    As someone who created custom themes in the OG Droid days and tried a lot of custom ROM's, the good old days are gone. Even on the "easy" to root phones, there are a lot more hoops to jump through. Especially since the A/B slot partitions were introduced. It used to be you just installed a custom recovery, flashed whatever worked and updated directly from the ROM. The OnePlus 8 Pro was the last great software experience out of the box and didn't need a custom ROM. OxygenOS 13 however is a dumpster fire and I commend everyone who is working to make LineageOS or any AOSP ROM a reality. Thank you for your hard work.


    Simple things such as easily swiping the notifications away, having a familiar and labeled settings menu, changing the DPI in Developer Options and having it survive a reboot, and having third party launchers work with gesture navigation are not too much to ask. The hardware is great and love the smaller form factor compared to the S23 Ultra. If only we could get great software too.
    Click to expand...
    Click to collapse
    The OP8 series were the last great we could have fun with because the OP9 had some bugs and noone released anything for the 10 Series. That will change with the OnePlus 11 if we succeed, as it's a great phone hardware-wise. Else, a lot of us including me probably won't purchase any OnePlus devices anymore.
    View
    7
    D
    dekefake
    Guys we all want it to happen but experimenting takes time we don't always have because of real life. Chandu always open-sourced his work here so feel free to contribute to speed up the process
    View
    6
    D
    dekefake
    Quick update on the progress

    Thanks to @qriozum who have provided a full dump to me, I was able to extract a build.prop file from init_boot and a complete fstab.qcom file. Both files will be attached.

    Extracting the super.img reveals quite a few more partitions. Find below a dump of my shell

    Code: 
    MMapped: 0x280000000, imgMeta 0x280001000
liblp dynamic partition (super.img) - Blocksize 0x1000, 3 slots
LP MD Header @0x3000, version 10.2, with 34 logical partitions @0x0 on block device of 16155 GB, at partition super, first sector: 0x800
Partitions @0x3100 in 3 groups:
    Group 0: default
    Group 1: qti_dynamic_partitions_a
        Name: system_a (read-only, Huawei EROFS Filesystem Image, @0x100000 spanning 1 extents of 650 MB) - extracted
        Name: system_ext_a (read-only, Huawei EROFS Filesystem Image, @0x28c00000 spanning 1 extents of 995 MB) - extracted
        Name: vendor_a (read-only, Huawei EROFS Filesystem Image, @0x67000000 spanning 1 extents of 1 GB) - extracted
        Name: product_a (read-only, Linux Ext2/3/4/? Filesystem Image, @0xa7c00000 spanning 1 extents of 6 MB) - extracted
        Name: my_product_a (read-only, Huawei EROFS Filesystem Image, @0xa8300000 spanning 1 extents of 520 MB) - extracted
        Name: odm_a (read-only, Huawei EROFS Filesystem Image, @0xc8c00000 spanning 1 extents of 1 GB) - extracted
        Name: my_engineering_a (read-only, Huawei EROFS Filesystem Image, @0x11fb00000 spanning 1 extents of 328 KB) - extracted
        Name: vendor_dlkm_a (read-only, Linux Ext2/3/4/? Filesystem Image, @0x11fc00000 spanning 1 extents of 126 MB) - extracted
        Name: system_dlkm_a (read-only, Linux Ext2/3/4/? Filesystem Image, @0x127b00000 spanning 1 extents of 340 KB) - extracted
        Name: my_stock_a (read-only, Huawei EROFS Filesystem Image, @0x127c00000 spanning 1 extents of 718 MB) - extracted
        Name: my_heytap_a (read-only, Huawei EROFS Filesystem Image, @0x154b00000 spanning 1 extents of 796 MB) - extracted
        Name: my_carrier_a (read-only, Huawei EROFS Filesystem Image, @0x186800000 spanning 1 extents of 328 KB) - extracted
        Name: my_region_a (read-only, Huawei EROFS Filesystem Image, @0x186900000 spanning 1 extents of 3 MB) - extracted
        Name: my_company_a (read-only, Huawei EROFS Filesystem Image, @0x186d00000 spanning 1 extents of 328 KB) - extracted
        Name: my_preload_a (read-only, Huawei EROFS Filesystem Image, @0x186e00000 spanning 1 extents of 2 MB) - extracted
        Name: my_bigball_a (read-only, Huawei EROFS Filesystem Image, @0x187100000 spanning 1 extents of 746 MB) - extracted
        Name: my_manifest_a (read-only, Huawei EROFS Filesystem Image, @0x1b5c00000 spanning 1 extents of 332 KB) - extracted
    Group 2: qti_dynamic_partitions_b
        Name: system_b (read-only,  empty) - extracted
        Name: system_ext_b (read-only,  empty) - extracted
        Name: vendor_b (read-only,  empty) - extracted
        Name: product_b (read-only,  empty) - extracted
        Name: my_product_b (read-only,  empty) - extracted
        Name: odm_b (read-only,  empty) - extracted
        Name: my_engineering_b (read-only,  empty) - extracted
        Name: vendor_dlkm_b (read-only,  empty) - extracted
        Name: system_dlkm_b (read-only,  empty) - extracted
        Name: my_stock_b (read-only,  empty) - extracted
        Name: my_heytap_b (read-only,  empty) - extracted
        Name: my_carrier_b (read-only,  empty) - extracted
        Name: my_region_b (read-only,  empty) - extracted
        Name: my_company_b (read-only,  empty) - extracted
        Name: my_preload_b (read-only,  empty) - extracted
        Name: my_bigball_b (read-only,  empty) - extracted
        Name: my_manifest_b (read-only,  empty) - extracted

    OnePlus 11 seems to make an extensive use of Huawei's EROFS. I haven't tried to extract any of these images trough, but at least now we know the size of every partition and start creating some device tree.

    Does somebody knows where to find sm8550 CAF code (display, audio, media) to allow for a LineageOS build ? Proprietary files are also a concern I do not really know how to address. Help is appreciated !
    View

New posts