This is an adaptation of @ottmi's work to OmniROM (64bit). Feature-wise it is not as rich as LineageOS, but it is an open source friendly project.
Credits go to @ottmi (obviously!), @arvinquilao (for the omnirom seed device tree, my starting point), @lolmaxlik_ru (for the 32bit device tree I used when trying 32bit) and @dev_harsh1998 (Bluetooth loop fix).
The kernel is based on CAF kernel, with changes for the Trunk from @ottmi's kernel. Kernel source is here:
https://github.com/omnirom/android_kernel_elephone_msm8916
I think it's usable: essential features seem to work. A minor issue is long press for home button, which does not work as expected.
I managed to upload on xda the build now. Bluetooth has been fixed.
The OmniROM team has accepted trunk as an official device. So, you can download the ROM directly from OmniROM website:
http://dl.omnirom.org/trunk/
If you do so, you will be able to receive ROM updates (weekly).
You are welcome to report any problem!
XDA:DevDB Information
OmniROM 7.1.2 for Elephone Trunk, ROM for all devices (see above for details)
Contributors
siljaer, ottmi, arvinquilao, lolmaxlik_ru, dev_harsh1998
Source Code: https://github.com/omnirom/android_device_elephone_trunk
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: OmniROM
Version Information
Status: Snapshot
Created 2017-05-25
Last Updated 2017-12-14
Reserved
Reserved
Changelog
20171021: update kernel to LA.BR.1.2.9-03710-8x16.0. Security fixes (Blueborne and KRACK).
20170820: New GPS blobs from crackling. In my case, it resulted in improved GPS precision. People with overheating problem, please let me know if it improves the issue.
20170730: New Thermal blobs from crackling. New thermal engine configuration. Hopefully, that should prevent overheating.
20170709: New GPU blobs from crackling. Because of a case of reported overheating, several drivers were added in kernel config. Some related SELinux denials were addressed. Something strange was also found in Trunk's DTs: GPIO pins for the tps65132 were wrong, leading to failed driver probe (however, that happens in stock rom too). Correct values for them was added. However, real effectiveness for those changes in preventing overheating is to be proved.
20170618: Fixed reboot to recovery (and automatic updates). Using again Trunk's Camera HAL.
20170603: now compatible with 64bit opengapps, fixed start recording sound at beginning of video recordings, SELinux fixes (by @ottmi), long press of home key now shows recent apps.
20170529: update kernel to LA.BR.1.2.9-02910-8x16.0
20170526: first build
@siljaer
Happy for your new job I'll let you know my impression after installing and testing it. I am currently using the "aicp_peach_n-12.1-NIGHTLY-20170526.zip" rom with great efficiency with up-to-date OTA updates at the same time as the Open Gapps update. It's just 32bit and has been made for "ARK Benefit A3" and not for our Elephone Trunk. It would be interesting, for the many extra functions of this rom, its fluency, the OTA updates, to recover all that has good and transfer it to your rom, even that I saw that something you used as a contribution from "lolmaxlik_ru". In any case thank you for your work and I apologize if I have been able to give you that imput.
Hi siljaer, I would like to test your ROM. I'm using ottmi's ROM but I have some problems: i.e. focus problem on the camera, camera works only for photo and non for videos, sometimes I have random reboots.... So I would like to try: which TWRP should I use? may I use gapps? what are the wipes that I need: can you describe me a sequence? TKS
ve66 said:
Hi siljaer, I would like to test your ROM. I'm using ottmi's ROM but I have some problems: i.e. focus problem on the camera, camera works only for photo and non for videos, sometimes I have random reboots.... So I would like to try: which TWRP should I use? may I use gapps? what are the wipes that I need: can you describe me a sequence? TKS
Click to expand...
Click to collapse
Sorry for the delay. You can use the same TWRP you're using now. The sequence is exactly the same one described by @ottmi for his rom. And you can use gapps, 64bit. Your feedback will be very appreciated!
As for the wipes, I am afraid that you have to wipe everything except internal sd card For later flashings, you don't have to wipe anything.
First time boot takes several minutes, wait some time.
Thanks!
opengapps 64/32 bit!
siljaer said:
And you can use gapps, 64bit. Your feedback will be very appreciated!
Click to expand...
Click to collapse
Actually there's a problem and you can only flash 32 bit gapps. I have fixed this and I am uploading the build later.
siljaer said:
Actually there's a problem and you can only flash 32 bit gapps. I have fixed this and I am uploading the build later.
Click to expand...
Click to collapse
I uploaded the fixed build. Now you can install 64bit opengapps. Since the previous builds were 64bit but they used zygote32 (a mistake) I deleted them.
siljaer said:
I uploaded the fixed build. Now you can install 64bit opengapps. Since the previous builds were 64bit but they used zygote32 (a mistake) I deleted them.
Click to expand...
Click to collapse
Ok, now I will download this new build. Tomorrow I think to install and then I'll send U my feedback
Inviato dal mio trunk utilizzando Tapatalk
OMS/Substratum working
BTW, for those interested in theme engines, I have tested Substratum and it works without root.
ve66 said:
Ok, now I will download this new build. Tomorrow I think to install and then I'll send U my feedback
Inviato dal mio trunk utilizzando Tapatalk
Click to expand...
Click to collapse
Thanks!
siljaer said:
Thanks!
Click to expand...
Click to collapse
Ok, my feedback:
I wiped cache, dalvik, data and system, then I flashed the ROM and after I flashed the gapps. After reboot I didn't reach to configure the telephone: it appeared me this message "L'app Configurazione guidata si è interrotta" and there isn't a way to configure the telephone. I'm writing from the PC 'cause the phone is out of service. I see the BT icon opened on the right-top of the screen, I don't know if this can help (you told you had problems with BT....). What do you suggest me to do?
EDIT: I flashed the ROM once again without Gapps, I did it two times but without any success, I also had a couple of random reboots
ve66 said:
Ok, my feedback:
I wiped cache, dalvik, data and system, then I flashed the ROM and after I flashed the gapps. After reboot I didn't reach to configure the telephone: it appeared me this message "L'app Configurazione guidata si è interrotta" and there isn't a way to configure the telephone. I'm writing from the PC 'cause the phone is out of service. I see the BT icon opened on the right-top of the screen, I don't know if this can help (you told you had problems with BT....). What do you suggest me to do?
EDIT: I flashed the ROM once again without Gapps, I did it two times but without any success, I also had a couple of random reboots
Click to expand...
Click to collapse
What do you mean with "without any success?"
siljaer said:
What do you mean with "without any success?"
Click to expand...
Click to collapse
I had to power off. I want to say that to make my telephone works I had to reinstall otttmi's ROM. In fact, also if i did a backup just after flashing your ROM, it was impossible to reload the backup. I think it's because - wiping all cache, dalvik, data and system - I deleted also parts that could contain parts of the backup. I reached to have some screenshot, tomorrow I'll post here
This is what happened
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Inviato dal mio trunk utilizzando Tapatalk
ve66 said:
I had to power off. I want to say that to make my telephone works I had to reinstall otttmi's ROM. In fact, also if i did a backup just after flashing your ROM, it was impossible to reload the backup. I think it's because - wiping all cache, dalvik, data and system - I deleted also parts that could contain parts of the backup. I reached to have some screenshot, tomorrow I'll post here
Click to expand...
Click to collapse
When did you do a backup? Did you backup your data online? From the screenshot, it looks like the restore application failed.
Hi,
With the last ROM i have a message "Encryption Unsuccessful" after the first boot, i can't do anything.
Thank you
---------- Post added at 10:59 PM ---------- Previous post was at 10:46 PM ----------
Bizen-Ya said:
Hi,
With the last ROM i have a message "Encryption Unsuccessful" after the first boot, i can't do anything.
Thank you
Click to expand...
Click to collapse
Ok i have reformated my /data from f2fs to ext4, it's ok now.
Bizen-Ya said:
Hi,
With the last ROM i have a message "Encryption Unsuccessful" after the first boot, i can't do anything.
Thank you
---------- Post added at 10:59 PM ---------- Previous post was at 10:46 PM ----------
Ok i have reformated my /data from f2fs to ext4, it's ok now.
Click to expand...
Click to collapse
Yes, f2fs is not enabled. I don't know enough about its reliability with CAF kernel.
gapps and camera
siljaer said:
Yes, f2fs is not enabled. I don't know enough about its reliability with CAF kernel.
Click to expand...
Click to collapse
BTW, if you're installing gapps I would suggest a flavour that does not replace default applications. Otherwise you will lose Snapdragon Camera that in my opinion is much better than google (legacy, as we use an old HAL) camera.
@ siljaer
Tried the ROM using TWRP-3.0.2-20161108-trunk.img, without installing gapps as recommended. Pretty fluid without breaks and quite complete without so many customizations. Problems with Smart Launcher does not activate the home key for shutdown or recovery commands. Weekly update to switch to version 20170611 all OK download but failed restart for flash with recovery. Tried several times but nothing to do. Obviously using either Launcher 3 or OmniSwitch. Installed TWRP manual and all OK. By the way, with the first installation I installed Supersu, which I did not find after updating. This is my first impression.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Resurrection Remix the ROM has been based on CM,slim.omni and original Remix ROM builds, this creates an awesome combination of performance, customization, power and the most new features, brought directly to your Device
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Resurrection Remix
Special thanks to, the CM team,OMNI team ,SLIMROMS and of course to all the supporters
New download: https://www.mediafire.com/folder/5a97vbv93k24n/tate
Old download: https://www.mediafire.com/folder/w9nh7oyabwvww/tate
(backup before flash, gapps need for upgrade, don`t flash SuperSU)
http://opengapps.org/ (arm, 6.0)
Kernel auditor - Low memory killer - Very aggressive
If you install Gapps after the ROM has been booted for the first time you either need to wipe data and reboot. Without this Gapps will crash constantly. This is due to the new permissions-system in M.
CURRENT KNOWN ISSUES:
Bootloop with app optimize
Thank you so much!!! Downloading and flashing this now!! I'll report any bugs I find, if any.
So far it flashed ok, (Clean) and flashed Open Gapps (Pico), booted thru the animation, set up all 87 apps, and now it's been sitting on "Starting apps" for about 10 minutes or so... I'm thinking about powering it down and trying to reboot.
Update2: Tried reboot- stuck at Starting apps
Tried reflash w/o gapps- Still stuck at Starting apps.
Anyone else get past this point?
Wait... Marshmallow? For the Tate? What!!!!
vasolini said:
Thank you so much!!! Downloading and flashing this now!! I'll report any bugs I find, if any.
So far it flashed ok, (Clean) and flashed Open Gapps (Pico), booted thru the animation, set up all 87 apps, and now it's been sitting on "Starting apps" for about 10 minutes or so... I'm thinking about powering it down and trying to reboot.
Update2: Tried reboot- stuck at Starting apps
Tried reflash w/o gapps- Still stuck at Starting apps.
Anyone else get past this point?
Click to expand...
Click to collapse
Are you able to pull a log?
xWolf13 said:
Are you able to pull a log?
Click to expand...
Click to collapse
I would love to. Is there an easy way to do it? (sorry, noob here!)
vasolini said:
I would love to. Is there an easy way to do it? (sorry, noob here!)
Click to expand...
Click to collapse
i`ll checking on jem this trouble, maybe RR-team updated this trouble
transi1 said:
i`ll checking on jem this trouble, maybe RR-team updated this trouble
Click to expand...
Click to collapse
Sounds good. Just so they know, I have the latest TWRP installed, and did a full wipe except internal sd. Looking forward to getting this going! :good:
Update: turns out I didn't have the latest TWRP. I had 2.8.3.0! Just updated it to 2.8.7.0 and tried again..... still stuck at "Starting apps".
vasolini said:
Sounds good. Just so they know, I have the latest TWRP installed, and did a full wipe except internal sd. Looking forward to getting this going! :good:
Update: turns out I didn't have the latest TWRP. I had 2.8.3.0! Just updated it to 2.8.7.0 and tried again..... still stuck at "Starting apps".
Click to expand...
Click to collapse
Hmm... are you flashing a compatible build? Make sure the gapps package is built for arm (not arm64), and the chosen android version is 6.0. If if still happens, try flashing Open Gapps, available here (again, make sure you pick those options correctly).
monster1612 said:
Hmm... are you flashing a compatible build? Make sure the gapps package is built for arm (not arm64), and the chosen android version is 6.0. If if still happens, try flashing Open Gapps, available here (again, make sure you pick those options correctly).
Click to expand...
Click to collapse
Thanks. I picked the correct gapps. I even tried without gapps just to see what would happen and got the same results. I will try to get a log somehow tomorrow.
monster1612 said:
Hmm... are you flashing a compatible build? Make sure the gapps package is built for arm (not arm64), and the chosen android version is 6.0. If if still happens, try flashing Open Gapps, available here (again, make sure you pick those options correctly).
Click to expand...
Click to collapse
I would love to contribute to the kernel. Can you link me to the source of your kernel? Vanilla CM13 is on my list for this device. As I have yet to flash this, has anyone bypassed the Starting Apps screen?
vasolini said:
Thanks. I picked the correct gapps. I even tried without gapps just to see what would happen and got the same results. I will try to get a log somehow tomorrow.
Click to expand...
Click to collapse
If it still doesn't work, then try clearing your dalvik and cache partitions from TWRP (under Wipe -> Advanced Wipe) and rebooting.
---------- Post added at 04:56 AM ---------- Previous post was at 04:51 AM ----------
xWolf13 said:
I would love to contribute to the kernel. Can you link me to the source of your kernel? Vanilla CM13 is on my list for this device. As I have yet to flash this, has anyone bypassed the Starting Apps screen?
Click to expand...
Click to collapse
I'm using the jem version to type this response right now, and I got past the Starting Apps screen.
Also, I'm fairly certain the sources would be on his github, which I've linked here. I plan on forking it and hoping to have a modded boot splash merged into this project.
monster1612 said:
If it still doesn't work, then try clearing your dalvik and cache partitions from TWRP (under Wipe -> Advanced Wipe) and rebooting.
---------- Post added at 04:56 AM ---------- Previous post was at 04:51 AM ----------
I'm using the jem version to type this response right now, and I got past the Starting Apps screen.
Also, I'm fairly certain the sources would be on his github, which I've linked here. I plan on forking it and hoping to have a modded boot splash merged into this project.
Click to expand...
Click to collapse
Any problems that have come up on the jem? I don't own the device, but I reckon that whatever the bugs are in jems may come up on the tate.
xWolf13 said:
Any problems that have come up on the jem? I don't own the device, but I reckon that whatever the bugs are in jems may come up on the tate.
Click to expand...
Click to collapse
So far, there are some issues. Among these:
1) the AOSP camera app doesn't work; however, accessing the camera through another app such as Snapchat works fine. [SIDE NOTE: this is listed as a known issue in the jem port's thread.]
2) the camera has a yellow tint. I'm guessing it's a driver issue.
3) when I watch Snapchat stories with video, the audio is really choppy about half the time.
These are some of the major bugs I felt were worth listing. Also, I'm not sure if RRO/layers works, as I haven't been able to thoroughly test it.
vasolini said:
Thanks. I picked the correct gapps. I even tried without gapps just to see what would happen and got the same results. I will try to get a log somehow tomorrow.
Click to expand...
Click to collapse
today i`ll uploading new build, trouble fixed in RR
monster1612 said:
If it still doesn't work, then try clearing your dalvik and cache partitions from TWRP (under Wipe -> Advanced Wipe) and rebooting.
I did do an advanced wipe. The only thing I didn't wipe was the internal SD card since that's where the image is. I always do a clean flash, especially when I am going to a different version of Android.
Click to expand...
Click to collapse
monster1612 said:
If it still doesn't work, then try clearing your dalvik and cache partitions from TWRP (under Wipe -> Advanced Wipe) and rebooting.
---------- Post added at 04:56 AM ---------- Previous post was at 04:51 AM ----------
I'm using the jem version to type this response right now, and I got past the Starting Apps screen.
Also, I'm fairly certain the sources would be on his github, which I've linked here. I plan on forking it and hoping to have a modded boot splash merged into this project.
Click to expand...
Click to collapse
I also have the 8.9 (jem) and that one is working great! Now if I can get the 7 (tate) to be like it's big brother, we'd be set!
new test build 20150121: https://www.dropbox.com/s/mirvtf17a666j87/ResurrectionRemix-M-v5.6.1-20160121-tate.zip?dl=0
jem works on same source buid
transi1 said:
new test build 20150121: https://www.dropbox.com/s/mirvtf17a666j87/ResurrectionRemix-M-v5.6.1-20160121-tate.zip?dl=0
jem works on same source buid
Click to expand...
Click to collapse
(that was fast!) Downloading it now...
transi1 said:
new test build 20150121: https://www.dropbox.com/s/mirvtf17a666j87/ResurrectionRemix-M-v5.6.1-20160121-tate.zip?dl=0
jem works on same source buid
Click to expand...
Click to collapse
Any chance you could compose another build for jem? I would, but I'm not too certain as to how to obtain and build the RR sources.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
* Your warranty is now void. Knox 0x1.
*
* We are not responsible for bricked devices, dead SD cards,
* lost data due to failed backups, etc, etc.
* flash at your own risk
*/
How to flash this ROM:
Download the zip file. (Make sure to download the file for your specific device)
Make sure this zip file is saved to your device (I prefer transferring to sd card to allow for full wipe of data on phone).
If you want Google Play functionality, download OpenGApps (link below). (optional)
Reboot into TWRP (Volume Up + Home + Power or Advanced Restart).
Make a backup (optional).
Wipe System, Data, Cache, and Dalvik Cache partitions with Advanced Wipe. (I like wiping internal data too, do NOT wipe SD Card!)
Flash the ROM you just downloaded.
Flash OpenGApps for Android 8.1 if you want Google services (optional).
If you want root, flash Magisk.
Reboot and proceed normally with installation.
Download links:
HLTE : HLTE
HLTECHN : HLTECHN
HLTEKOR : HLTEKOR
HLTETMO : HLTETMO
OpenGApps 8.1 (I use pico): http://opengapps.org
Source code:
LineageOS on GitHub
jfuginay (forked from LineageOS, and rest of the developers mentioned in the following Credits) on Github
Credits:
The LineageOS Team
haggertk
Trader418
andr01dfr3ak
temasek
TheMuppets
Version Information:
ROM OS Version: Android 8.1.0 Oreo
Kernel Version: Linux 3.4.113
Android security patch level: November 5, 2018
Known Bugs: bluetooth calls may not be working
All other functions seem to be working fine. Please report bugs with logcat
Screenshots
Hola, buenos días, gracias por compartir tu trabajo,¿Funciona para n900v?
Hello, good morning, thanks for sharing your work, does it work for n900v?
Yes, the n900v shares the hltetmo code name in LineageOS so it should work.
Try it and let me know ?
Perfect
I just installed it on my N900V and excellent works: Automatic rotation to ?, Bluetooth very well, is not cut, only calls with Bluetooth do not work, but otherwise very well, thank you very much, very well work, congratulations ?
franciscojarobles said:
I just installed it on my N900V and excellent works: Automatic rotation to ?, Bluetooth very well, is not cut, only calls with Bluetooth do not work, but otherwise very well, thank you very much, very well work, congratulations ?
Click to expand...
Click to collapse
Thanks. I just noticed now that Bluetooth calls aren't working for me either, but Bluetooth music playback is smooth without cutting in and out, so that's a plus.
I'll be working on getting Bluetooth calls fixed, hopefully by next weekly build which I'll probably do on the weekend.
Working well here. It appears that using the speakerphone during a call mutes the microphone. Only thing I've noticed so far. Thanks for this!
patrioticparadox said:
Working well here. It appears that using the speakerphone during a call mutes the microphone. Only thing I've noticed so far. Thanks for this!
Click to expand...
Click to collapse
What version of note 3 are you running? I use speakerphone on my TMobile note 3 for all my calls and haven't had an issue with the mic being muted yet.
Are you rooted? If so, how?
Using Xposed?
I am rooted (Magisk v16.0), no Xposed yet. Pretty sure my modem and whatnot are out if date but hadn't updated them yet as they were working with Lineage 14.1. Made the mistake of encrypting and now can't get into TWRP. I'll try to check logs later and see if I can get anymore info. Sounds like it's gonna be on my end.
I haven't updated my twrp in a while, its still 2.7, still should work right?
alexishaze said:
I haven't updated my twrp in a while, its still 2.7, still should work right?
Click to expand...
Click to collapse
It's possible, but most devs recommend using TWRP 3.0.2+ for any Android version 6.0 or higher. We're doing 8.1 with this ROM so I'd definitely upgrade TWRP first.
alexishaze said:
I haven't updated my twrp in a while, its still 2.7, still should work right?
Click to expand...
Click to collapse
https://dl.twrp.me/hltetmo/twrp-3.2.3-0-hltetmo.img
Link to latest TWRP for note 3
Jfuginay said:
Link to latest TWRP for note 3
Click to expand...
Click to collapse
Is there a difference between the twrp you linked above and the ones found at this link:xxxxxxxxxxxxxx ??? (I'm not allowed to post links yet, but google "twrp hltetmo" and you'll see what I'm talking about)
I found that part of TWRP's site with google - and couldn't figure out how to actually navigate to that page from within their site...
Also, I have two questions, you mention in OP that you are not having radio power issues - what you listed as (3) describes a bug I have been seeing frequently running RR - is this still the case a week later? And, how is the phone working with regards to incoming/outgoing calls?
damnZSquirrels said:
Is there a difference between the twrp you linked above and the ones found at this link:xxxxxxxxxxxxxx ??? (I'm not allowed to post links yet, but google "twrp hltetmo" and you'll see what I'm talking about)
I found that part of TWRP's site with google - and couldn't figure out how to actually navigate to that page from within their site...
Also, I have two questions, you mention in OP that you are not having radio power issues - what you listed as (3) describes a bug I have been seeing frequently running RR - is this still the case a week later? And, how is the phone working with regards to incoming/outgoing calls?
Click to expand...
Click to collapse
Updated my link, I accidentally put link to hlte twrp instead of hltetmo specific one.
As for #3 on the problems list of OP, I'm still running the same build and the network is still working well. Incoming and out going calls working just fine. I have bad cell reception at work, on previous ROMs I would leave work and still have no signal until I reboot my phone. On my current ROM I can just step outside and the network kicks on again.
I get my larger hard drive from Amazon tomorrow so I plan on releasing a new build tomorrow night if all goes well.
(Wed night, Aug 22nd, or Thurs night at the latest)
@Jfuginay are you using the FPL1 firmware. It's been a while so I was thinking about fully flashing the latest Stock firmware and then ROMing from there. That way I can rule out any firmware issues and start completely fresh. Piece of mind, ya know?
Edited for the nightlies to start rolling :victory:
patrioticparadox said:
@Jfuginay are you using the FPL1 firmware. It's been a while so I was thinking about fully flashing the latest Stock firmware and then ROMing from there. That way I can rule out any firmware issues and start completely fresh. Piece of mind, ya know?
Edited for the nightlies to start rolling :victory:
Click to expand...
Click to collapse
No, I'm on a different one. Screenshot attached. Will be doing a clean install of latest build once it finishes compiling before uploading.
Coming from latest Stock N900TUVUFQD2 I am unable to boot into any version of twrp over 2.8.7.0. Will this rom boot with this version of twrp?
Any help booting into the latest version of twrp is also appreciated.
New 8/24/2018 build is up, follow original download link to locate and download file.
Built on my Toshiba Tecra z40a running Lubuntu (first build was on an old HP pavillion laptop)
Build took only 3 hours and 40 minutes, my first build on older laptop took over 11 hours!
Visit LineageOS 15.1 for changelog. Most changes are to lineage apps and small kernel tweaks.
I gave the original build a try after posting earlier. The radio definitely works better than with RR - while I have had a few instances where it seems the signal gets "stuck" on GMS or EDGE, a quick toggle of airplane mode quickly clears things up. Also, the built in dialer in the DIGITS app works much better - texting & calling over wifi both work (sometimes I have to toggle wifi to get it to connect, but I think that might be an issue on t-mobile's end).
I'll be trying your latest build just after I post this reply.
---------- Post added at 04:55 PM ---------- Previous post was at 04:32 PM ----------
iPack said:
Coming from latest Stock N900TUVUFQD2 I am unable to boot into any version of twrp over 2.8.7.0. Will this rom boot with this version of twrp?
Any help booting into the latest version of twrp is also appreciated.
Click to expand...
Click to collapse
I am using Twrp3.2.3. I believe you can upgrade by installing from within TWRP or flashing with ODIN.
https://twrp.me/samsung/samsunggalaxynote3qualcomm.html -->read the install instructions here
https://dl.twrp.me/hltetmo/ -->download the file for your chosen method here
Last time I went back to stock, I flashed the FQD2 firmware with ODIN 3.12, CF-AutoRoot (odin again), then twrp3.2.3(also with odin).
Cant upgrade to any twrp higher than 2.8. and no rom not even one boots on my note 3
i even flashed this N900TUVUFQD2 stock rom in hopes that maybe my bootloader was outdated but it did not help., I still cant boot any rom . they either bootloop or dont get past flashing also my phone says qulcom secure boot enabled (CSB) in odin is that normal... note 3 tmobile
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at Github and at Gerrit.
Disclaimer
Flash and use with your own risk.
Please read whole this thread for minimize FAQ
Notice
Before you flash, backup everything important of your device, then flash the ROM in TWRP.
Bugs
You tell me (with logs please)
Download and Installing
Carbon Pie ROM at here
Latest arm64GAPPs (Optional, Pico recommended)
Wipe system, dalvik/art cache, cache, data partition
Flash Carbon Rom and GAPPs throught TWRP.
Wipe dalvik/art and cache partition
Reboot your device and Enjoy Carbon Rom.
Source tree
Device
Vendor
Sensors
Kernel
Special thanks
CarbonROM Team
Alberto97 for his repos
Me
XDA:DevDB Information
CarbonROM for Moto Z Play, ROM for the Moto Z Play
Contributors
Stayn
Source Code: https://github.com/CarbonROM
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Unlocked Bootloader and TWRP Recovery
Version Information
Status: Stable
Created 2019-05-23
Last Updated 2019-08-10
Features added to this ROM:
Powered by ArtxPlay Kernel
Boosted Headphones volume
Optimized Shutdown and Restart time (now its 1s - 2s always)
Optimizations from Android GO
Enabled touch optimizations
Enabled PinnerService to keep loaded critical apps into memory
(framework, default launcher, default camera, SystemUI...)
SystemUI Pre-Optimized
And more...
Changelog:
* 8/10/2019
Fixed reboot, sim and other issues
Now using ArtxKernel 3.0 (Simplified, clean)
Added some settings at boot
* 5/23/2019
Initial Release
Omg, A new rom!! This morning I flashed AOSP (Xperience was giving me a poor battery life) but I don't care, I must try this one asap!
Thanks for this man. I'll report if anything happens.
Dovahkiin1290 said:
Omg, A new rom!! This morning I flashed AOSP (Xperience was giving me a poor battery life) but I don't care, I must try this one asap!
Thanks for this man. I'll report if anything happens.
Click to expand...
Click to collapse
Sure, feedback will be appreciated!
Another rom hurray! after so many become closed something new. Could you maybe pick up some Lineage rom and keep going 16 is pretty good?
Good to see new rom - only disadvantage for me that it is arm - 32bit :/ . I prefer arm64 roms since I don't have problems with them .
Hey,
long time custom rom user but lurking here. It's great that you bring a new ROM for this phone. Everything works great as far as I can tell. No magisk boot or battery problems.
2 very minor things I would like to see fixed/added: 1) Status bar icons don't fit inside the box. Wi-Fi and Auto-Rotate flood and get out of border. Also I remember a settings button being present there without the need to expand the menu. 2) Add touch fingerprint for lock option.
EDIT: Mobile network seems to not work (no access point names?)
EDIT2: Added them manually and everything is fine
Always great to have a new ROM, thanks!! Unfortunately it's always rebooting into recovery after some few minutes, even without gapps. It even showed the "Shutting Down" system message . Also the ROM didn't find my SIM and I didn't have any mobile network, i would have tried adding access point names if it wasn't for the constant reboots. I have copied logs from recovery, if that is what you wanted I can share with you.
all good until now only difficulty in the optimization in the camera! presents delays. I can not find the option to wake up and sleep the phone with the fingerprint reader
FelTell13 said:
Always great to have a new ROM, thanks!! Unfortunately it's always rebooting into recovery after some few minutes, even without gapps. It even showed the "Shutting Down" system message . Also the ROM didn't find my SIM and I didn't have any mobile network, i would have tried adding access point names if it wasn't for the constant reboots. I have copied logs from recovery, if that is what you wanted I can share with you.
Click to expand...
Click to collapse
Always provide logs, also, whats your flashing procedure?
Stayn said:
Always provide logs, also, whats your flashing procedure?
Click to expand...
Click to collapse
Wipe Dalvik,System,data and cache
Install ROM and Gapps
wipe cache and dalvik
reboot
I even tried without gapps and it still turned off.
Here is the logs
Thank you for new rom! Will try it
Edit: Ok, it reboots to recovery after few minutes. Can't use it by now.
Very good ROM, no problem so far. Just note that the navbar at times is half, you can not see the complete drawing. The icons in the status bar solve them by shrinking the screen, sorry for my English and thanks
manfred18 said:
Thank you for new rom! Will try it
Edit: Ok, it reboots to recovery after few minutes. Can't use it by now.
Click to expand...
Click to collapse
Are you using some Magisk module? Because for me that was the issue while using other two roms. The only solution was to avoid flashing any module and the phone worked just fine, no reboots or data corruption.
Dovahkiin1290 said:
Are you using some Magisk module? Because for me that was the issue while using other two roms. The only solution was to avoid flashing any module and the phone worked just fine, no reboots or data corruption.
Click to expand...
Click to collapse
I had the same problem as him, and no, even without flashing Magisk I still had the reboot...
sebx_g1 said:
Good to see new rom - only disadvantage for me that it is arm - 32bit :/ . I prefer arm64 roms since I don't have problems with them .
Click to expand...
Click to collapse
+1
bootloop..
FelTell13 said:
Always great to have a new ROM, thanks!! Unfortunately it's always rebooting into recovery after some few minutes, even without gapps. It even showed the "Shutting Down" system message . Also the ROM didn't find my SIM and I didn't have any mobile network, i would have tried adding access point names if it wasn't for the constant reboots. I have copied logs from recovery, if that is what you wanted I can share with you.
Click to expand...
Click to collapse
FelTell13 said:
Wipe Dalvik,System,data and cache
Install ROM and Gapps
wipe cache and dalvik
reboot
I even tried without gapps and it still turned off.
Here is the logs
Click to expand...
Click to collapse
manfred18 said:
Thank you for new rom! Will try it
Edit: Ok, it reboots to recovery after few minutes. Can't use it by now.
Click to expand...
Click to collapse
FelTell13 said:
I had the same problem as him, and no, even without flashing Magisk I still had the reboot...
Click to expand...
Click to collapse
New update
For you guys and others with sim card problems download the ROM from here or the OP
This build most likely fixes that problem, if not, I'll prepare another solution, thanks
Stayn said:
New update
For you guys and others with sim card problems download the ROM from here or the OP
This build most likely fixes that problem, if not, I'll prepare another solution, thanks
Click to expand...
Click to collapse
Lets see how it works - I am a bit tired with all GSIs ...:silly:
--- Rom boots to desktop then do auto shutdown and return to recovery --- interesting never seen that before ?! (with Magisk 19.2 + gapps nano) .
Clean rom flashed again - it lasted longer before reboot to recovery on desktop - so I manage to see that no sim problem is still there :/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions :
Download the latest build and gapps
Boot to recovery
Flash the latest build
Boot to recovery again
Flash gapps
Reboot
Downloads :
Builds : http://download.lineageos.org/mermaid
SemcCamera addon : https://androidfilehost.com/?w=files&flid=305730
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
[ROM][OFFICIAL][mermaid][10] LineageOS 17.1, ROM for the Sony Xperia X10 Plus
Contributors
LuK1337
Source Code: https://github.com/LineageOS
ROM OS Version: Windows 8 Mobile
Version Information
Status: Testing
Created 2020-02-16
Last Updated 2020-04-01
oh btw you might want to use this TWRP for flashing my builds.
Just bootlop
Great performance and smoothness.
reintal said:
Just bootlop
Click to expand...
Click to collapse
Did you format data? If that didn't help, mind sending me a msg on irc?
https://kiwiirc.com/nextclient/irc.freenode.net?channel=#titandev
NFC does not work
reintal said:
NFC does not work
Click to expand...
Click to collapse
Works here? I just tried Android Beam.
LuK1337 said:
Works here? I just tried Android Beam.
Click to expand...
Click to collapse
He works with some issues, sometimes i can't read nfc cards and use android beam. I assume this is an application problem.
LuK1337 said:
oh btw you might want to use this TWRP for flashing my builds.
Click to expand...
Click to collapse
X10 plus I4293, use this TWRP 3.3.1-1,
if use fastboot boot twrp.img, the touch is right,
if install Recovery ramdisk, then use Vol- and Power into twrp, the Touch is unavailable！
easyt said:
X10 plus I4293, use this TWRP 3.3.1-1,
if use fastboot boot twrp.img, the touch is right,
if install Recovery ramdisk, then use Vol- and Power into twrp, the Touch is unavailable！
Click to expand...
Click to collapse
Oh. I kinda understand why something like this would happen...
Can you come irc? I don't want to reflash stock just to debug this.
EDIT: Maybe fixed in twrp-3.3.1-2-mermaid.img.
LuK1337 said:
Oh. I kinda understand why something like this would happen...
Can you come irc? I don't want to reflash stock just to debug this.
EDIT: Maybe fixed in twrp-3.3.1-2-mermaid.img.
Click to expand...
Click to collapse
I re-flashed the official firmware, and then flash twrp again, it's right!
thank you
Two sim
LuK1337 said:
Oh. I kinda understand why something like this would happen...
Can you come irc? I don't want to reflash stock just to debug this.
EDIT: Maybe fixed in twrp-3.3.1-2-mermaid.img.
Click to expand...
Click to collapse
Two sim does not work when an SD card is inserted
Stezko said:
Two sim does not work when an SD card is inserted
Click to expand...
Click to collapse
Hmm...I would need you to test something for me in that case. Mind sending me a msg on irc/hangouts/discord?
LuK1337 said:
Hmm...I would need you to test something for me in that case. Mind sending me a msg on irc/hangouts/discord?
Click to expand...
Click to collapse
my english level is zero)
The second question is, is it possible to install Magisk on this rom?
I install Magisk-v20.3.zip via twrp and get a bootloop
Stezko said:
my english level is zero)
The second question is, is it possible to install Magisk on this rom?
I install Magisk-v20.3.zip via twrp and get a bootloop
Click to expand...
Click to collapse
I don't really care whether your english is perfect or not. I just need you to test that for me...
I can't say much about magisk tho, I don't use it.
EDIT: I guess that was too much to ask for... If there's anyone with dsds device who wants to be helpful, please msg me. I would prefer to release something tested rather than hope for the best.
Stezko said:
my english level is zero)
The second question is, is it possible to install Magisk on this rom?
I install Magisk-v20.3.zip via twrp and get a bootloop
Click to expand...
Click to collapse
Everything works without problems https://imgur.com/a/ij094yH
Camera2api
Hello!
I'm using this build for daily use! I can say it's really smooth and, no issues at all!
My only question is if enabling camera2api is possible, and then install a working version of gcam...
Any help will be appreciated!
I'm also willing to provide feedback and make my mobile a Guinea pig to make this work!:fingers-crossed:
Lineage is running stable with semc addons, Gapps, tai chi, and root with magisk 20.3.
fastboot boot boot.img and reboot to recovery ramdisk worked best.
After failing to successfully root flashing magisk.zip, I got a boot image
from a twrp backup. I renamed boot.emmc.win to boot.img and patched
with Magisk. Flashed the new boot.img, magisk.zip, and had root on startup.
Any recommended gapps? Tried both open gapps nano and micro and both force close on account setup
aeppacher said:
Any recommended gapps? Tried both open gapps nano and micro and both force close on account setup
Click to expand...
Click to collapse
Did you even format data?
LuK1337 said:
Did you even format data?
Click to expand...
Click to collapse
Did a full format before installation and then after lineage install. Tried factory reset after gapps installation and tried 3 different dates for gapps in case it was a new bug. Are you suggesting to do an installation, gapps, then full format?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
Unlock your bootloader
Backup strongly advised, including the "persist" partition
Download the latest build
Reboot bootloader
$ fastboot -w (This wipes your data!)
Download and boot TWRP for instantnoodle Important: Do not flash anything using the built-in recovery for now, it will severely brick your device.
Flash LOS zip
Reboot
Downloads:
https://drive.google.com/drive/folders/1BGTV9LD_PLAR5p0o3fUdKqR3IWxUGJPV
Known issues:
Weak vibrator
Displays "Charging slowly" when it's actually not
Flashing anything using built-in recovery bricks the device, factory reset and wipe should be safe though
Probably loads of untested things
Build signed with public keys for now
GApps not flashable yet
Reporting Bugs:
Make sure the bug you want to report isn't already known
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
[ROM][UNOFFICIAL][instantnoodle][10] LineageOS 17.1, ROM for the OnePlus 8
Contributors
KennyG9, LuK1337
Source Code:
Device Tree: https://gitlab.com/nlr/android_device_oneplus_instantnoodle + https://github.com/luk1337/android_device_oneplus_sm8250-common
Kernel: https://github.com/luk1337/android_kernel_oneplus_sm8250
Most of the work just consisted in adapting LuK1337's fantastic work on the OP8 Pro (instantnoodlep), all credits should actually go to him.
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Created 2020-07-11
Last Updated 2020-07-11
Noice! ?
Awesome, so glad to see ROMs development starting up for this phone!
I retract my post. Thank you.
---------- Post added at 08:22 PM ---------- Previous post was at 07:40 PM ----------
I can't flash any custom rom. For some reason it just won't flash it. Always get a generic error code. Tis frustrating. I'm not sure what to do about it. I really wanted to try this too.
same. got it to flash via the fastboot method from Luks post in the 8 pro but it reboots as soon as it boots.
gerguter said:
I retract my post. Thank you.
---------- Post added at 08:22 PM ---------- Previous post was at 07:40 PM ----------
I can't flash any custom rom. For some reason it just won't flash it. Always get a generic error code. Tis frustrating. I'm not sure what to do about it. I really wanted to try this too.
Click to expand...
Click to collapse
What error code? Can you try "Wipe" + "Format Data" in TWRP instead of just wiping in fastboot? If you are able to flash in TWRP at some point and Lineage Recovery asks you to factory reset, do it. Also, sideloading doesn't work in TWRP at the moment. You have to install from sdcard or USB stick.
But yeah, A/B partitions + Android 10's super partition makes it quite hard to work with this device at the moment unfortunately. I went through serious complications and weird issues while porting the ROM.
joemossjr said:
same. got it to flash via the fastboot method from Luks post in the 8 pro but it reboots as soon as it boots.
Click to expand...
Click to collapse
What do you mean by "reboots as soon as it boots"? Do you reach the boot animation and then it reboots? Did you extract the content of the payload.bin in the zip? Can you try the procedure I suggested to gerguter in TWRP?
KennyG9 said:
What error code? Can you try "Wipe" + "Format Data" in TWRP instead of just wiping in fastboot? If you are able to flash in TWRP at some point and Lineage Recovery asks you to factory reset, do it. Also, sideloading doesn't work in TWRP at the moment. You have to install from sdcard or USB stick.
But yeah, A/B partitions + Android 10's super partition makes it quite hard to work with this device at the moment unfortunately. I went through serious complications and weird issues while porting the ROM.
What do you mean by "reboots as soon as it boots"? Do you reach the boot animation and then it reboots? Did you extract the content of the payload.bin in the zip? Can you try the procedure I suggested to gerguter in TWRP?
Click to expand...
Click to collapse
It just says that it can't flash the zip. Nothing else. I'll try again later and see what happens.
gerguter said:
It just says that it can't flash the zip. Nothing else. I'll try again later and see what happens.
Click to expand...
Click to collapse
While you're at it, have a look at what "/tmp/recovery.log" says after trying to flash.
No windows mobile 8? lol
KennyG9 said:
What error code? Can you try "Wipe" + "Format Data" in TWRP instead of just wiping in fastboot? If you are able to flash in TWRP at some point and Lineage Recovery asks you to factory reset, do it. Also, sideloading doesn't work in TWRP at the moment. You have to install from sdcard or USB stick.
But yeah, A/B partitions + Android 10's super partition makes it quite hard to work with this device at the moment unfortunately. I went through serious complications and weird issues while porting the ROM.
What do you mean by "reboots as soon as it boots"? Do you reach the boot animation and then it reboots? Did you extract the content of the payload.bin in the zip? Can you try the procedure I suggested to gerguter in TWRP?
Click to expand...
Click to collapse
sorry what i mean is. I extracted the payload.bin then saw luks page on the 8pro and took the commands he did to flash the rom and applied them here. The rom infact boots but as soon as i see the welcome screen it pops up a screen that says shutting down. also i was able to get past that once by formatting in los recovery. but after that it was a no go. Cant get gapps to flash so couldnt get that. Magisk did flash tho and seemed to work? Other then those things I would just make images for flashing in fastboot instead of zips. twrp is super borked lmao
KennyG9 said:
While you're at it, have a look at what "/tmp/recovery.log" says after trying to flash.
Click to expand...
Click to collapse
Will do.
i can flash and use it just fine no problem at all only NO GMS and i can't install it because error 70 not sufficient partition space please fix it
Is there any group for testing and reporting bugs?
Thank you for your good work! By the way, do you know how to change the screen refresh rate to 90hz on LineageOS? I'm stuck at 60hz now
Is a kernel required to flash this? I can't get this rom to flash in twrp or to work by flashing the extracted payload files
Any news on being able to flash google play?
gerguter, can you update us? currently experiencing the same issue and unsure of how to get around it.
Any telegram channel for op8 los ROM?
Any updates? Last build is still dated from July.
TheCybrid said:
Any updates? Last build is still dated from July.
Click to expand...
Click to collapse
The one for the op8 pro works on the op8 but the fingerprint sensor is in the wrong spot on the screen but if you don't mind that it works fine.