Database Info

No baseband or data after flashing rom

Hi I've owned my one for a few months now and have flashed numerous ROMs since plus I've owned every nexus and have flashed countless roms on them. Yesterday I flashed Aicp on a clean wipe and all of a sudden my phone would get to the setup and reboot. I tried restoring 3 different nandroids and they would boot into the os but I had no access to data or WiFi and my hardware keys wouldn't work except the back key. I managed to get into settings and I'm missing my baseband. So I tried to fastboot the cm11s factory image and all I get is audiofx fc every second. I then did a bit of research and here on xda there were a few others with this issue and read that side loading the color os would bring back the files I lost. I'm now writing this from color os and I do indeed have data back but WiFi does not work and its showing my 64 GB one as a 16gb one. I'm lost what to do from here, will flashing stock cm11s work? I tried flashing liquid and same thing happened again. I'm getting extremely frustrated and do not want to send this in to oppo if I can help it. Any help would be so greatly appreciated.
Sent from my A0001 using XDA Premium HD app

1)Reboot into bootloader
2)reinstall cm11s using fastboot
http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed-fastboot.zip
fastboot flash boot boot.img
fastboot flash userdata userdata_64g.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot reboot
3)flash twrp recovery using fastboot
you can download here
http://techerrata.com/file/twrp2/bacon/openrecovery-twrp-2.8.0.1-bacon.img
rename it "recovery.img"
fastboot flash recovery recovery.img
4)boot into recovery
factory reset,advanced wipe-->dalvik,cache,system,data
and flash cm11 rom zip
https://download.cyanogenmod.org/get/jenkins/84302/cm-11-20140921-NIGHTLY-bacon.zip

kenzolo said:
1)Reboot into bootloader
2)reinstall cm11s using fastboot
http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed-fastboot.zip
fastboot flash boot boot.img
fastboot flash userdata userdata_64g.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot reboot
3)flash twrp recovery using fastboot
you can download here
http://techerrata.com/file/twrp2/bacon/openrecovery-twrp-2.8.0.1-bacon.img
rename it "recovery.img"
fastboot flash recovery recovery.img
4)boot into recovery
factory reset,advanced wipe-->dalvik,cache,system,data
and flash cm11 rom zip
https://download.cyanogenmod.org/get/jenkins/84302/cm-11-20140921-NIGHTLY-bacon.zip
Click to expand...
Click to collapse
I think its file system problem,because it shows 16gb instead 64gb.Pls also check your imei,probably its 0.

k3mik4l said:
Hi I've owned my one for a few months now and have flashed numerous ROMs since plus I've owned every nexus and have flashed countless roms on them. Yesterday I flashed Aicp on a clean wipe and all of a sudden my phone would get to the setup and reboot. I tried restoring 3 different nandroids and they would boot into the os but I had no access to data or WiFi and my hardware keys wouldn't work except the back key. I managed to get into settings and I'm missing my baseband. So I tried to fastboot the cm11s factory image and all I get is audiofx fc every second. I then did a bit of research and here on xda there were a few others with this issue and read that side loading the color os would bring back the files I lost. I'm now writing this from color os and I do indeed have data back but WiFi does not work and its showing my 64 GB one as a 16gb one. I'm lost what to do from here, will flashing stock cm11s work? I tried flashing liquid and same thing happened again. I'm getting extremely frustrated and do not want to send this in to oppo if I can help it. Any help would be so greatly appreciated.
Sent from my A0001 using XDA Premium HD app
Click to expand...
Click to collapse
Your issue clearly describes what's in this thread here. Have you tried it? What recovery are you using?

Flickering Stripes on Dispaly - OnePlus supplies patch

Hi there!
EDIT2: WARNING! ONLY FOR 64GB INTERNATIONAL EDITION
Seems some people are having the same problem as me and are facing some screen issues. Mostly occuring as colorful or black flickering stripes along the display.
I contacted OnePlus support and they gave me a link to a patch.
I'm currently trying to figure out, what this patch is really doing and maybe just extract the patched part, as their batch files do (unlock oem locking, flashing, oem locking) wipe the phone.
If anyone is interested aswell,. here's the link they provided:
https://account.onepluscontent.com/downloads/tools/oneplus-one-reflash.zip
Edit: Content of the batch files:
ONEPLUS ONE - 0.bat
@echo off
fastboot devices
pause
Click to expand...
Click to collapse
ONEPLUS ONE - 1.bat
@echo off
fastboot oem unlock
fastboot reboot-bootloader
sleep 5
Click to expand...
Click to collapse
ONEPLUS ONE - 2.bat
@echo off
echo ######### This patch is Created by ONEPLUS Technical Support. #######
echo ###### This patch should only be used for ONEPLUS ONE 64GB Global Version. ######
@echo off
fastboot oem unlock
fastboot erase persist
fastboot flash persist persist.img
fastboot erase reserve4
fastboot flash reserve4 reserve4.img
fastboot flash boot boot.img
fastboot flash userdata userdata_64g.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot oem lock
fastboot reboot
echo It is done Now
pause
Click to expand...
Click to collapse
Anyone care matching the md5 sums of the img files or something to identify the ones with changes?
Maybe we can flash this without wiping...

Hi there.
This looks just like a complete factory reset to me. Its probably the same zip OnePlus provided to "fix" a GPS problem.
I don't think that there are really any relevant changes in this images, it is probably just a hard factory reset. In addition it even erases the whole phone including sd-partition and unlocks the bootloader, for whatever reason, so be warned.
I had the problems with the black flickering "lines" as well, I solved it by disabling hardware overlays in the developer options.
Just realized, that they relock the bootloader again in the last batch. Ts.

microserf said:
Hi there.
This looks just like a complete factory reset to me. Its probably the same zip OnePlus provided to "fix" a GPS problem.
I don't think that there are really any relevant changes in this images, it is probably just a hard factory reset. In addition it even erases the whole phone including sd-partition and unlocks the bootloader, for whatever reason, so be warned.
I had the problems with the black flickering "lines" as well, I solved it by disabling hardware overlays in the developer options.
Click to expand...
Click to collapse
Yep, I was suspecting something like this.
Anyone having the time to verify that the images are just the current ones?
Have been playing around with different kernels and disabling the HW overlays. But I'm not really happy, with this workaround - although the phone seems more smooth (which is quite odd in my opinion)

aliander said:
Yep, I was suspecting something like this.
Anyone having the time to verify that the images are just the current ones?
Have been playing around with different kernels and disabling the HW overlays. But I'm not really happy, with this workaround - although the phone seems more smooth (which is quite odd in my opinion)
Click to expand...
Click to collapse
Yeah, it is more a workaround than a fix. But I was kinda relieved that its software related and not a broken digitizer or something. Problem started to occur on 38R with stock and different revisions of Franco Kernel. Before that it was all fine.
There is also a bugreport in the cyanogenmod jira about this issue, so for now I am living with the workaround and will probably wait for the Lollipop Update.

Yea this is just a factory recovery image they provided. Saw this was posted as a "FIX" for other issues on the OnePlus forums as well. Seems like a very generic solution from OnePlus tbh, and i dont know if it actually fixes anything., looks more like their playing for time...

S M G said:
Yea this is just a factory recovery image they provided. Saw this was posted as a "FIX" for other issues on the OnePlus forums as well. Seems like a very generic solution from OnePlus tbh, and i dont know if it actually fixes anything., looks more like their playing for time...
Click to expand...
Click to collapse
Yeah seems so.
Thanks

So I downloaded a fastboot factory image version R38
MD5 Results:
Code:
$ md5sum.exe ONEPLUS\ ONE-Patch/*.img
46276588ab8cb0e2b68a813012c5c332 *ONEPLUS ONE-Patch/boot.img
eb6bf677953fd446d16336f627e28f24 *ONEPLUS ONE-Patch/cache.img
7800fb3768c5a5f310c3b6bc443e4f72 *ONEPLUS ONE-Patch/persist.img
3b0dba90ea6ecdf27a201cb16af940b8 *ONEPLUS ONE-Patch/recovery.img
2c72217c90be4175c9e9092929839bfd *ONEPLUS ONE-Patch/reserve4.img
732ef3ce979960be5eb225bad14d4e80 *ONEPLUS ONE-Patch/system.img
9cd750b19b7c30c640647b6f0df8f6b4 *ONEPLUS ONE-Patch/userdata.img
07b9774134f26f72ea7e73e580b19c17 *ONEPLUS ONE-Patch/userdata_64G.img
Code:
$ md5sum.exe cm-11.0-XNPH38R-bacon-signed-fastboot/*.img
46276588ab8cb0e2b68a813012c5c332 *cm-11.0-XNPH38R-bacon-signed-fastboot/boot.img
eb6bf677953fd446d16336f627e28f24 *cm-11.0-XNPH38R-bacon-signed-fastboot/cache.img
3b0dba90ea6ecdf27a201cb16af940b8 *cm-11.0-XNPH38R-bacon-signed-fastboot/recovery.img
732ef3ce979960be5eb225bad14d4e80 *cm-11.0-XNPH38R-bacon-signed-fastboot/system.img
9cd750b19b7c30c640647b6f0df8f6b4 *cm-11.0-XNPH38R-bacon-signed-fastboot/userdata.img
07b9774134f26f72ea7e73e580b19c17 *cm-11.0-XNPH38R-bacon-signed-fastboot/userdata_64G.img
Seems everything is identical, but reserve4.img and persist.img missing in factory image.

Help flashing etc

Hi there, so recently I was forced to update OTA from CM11 to the latest CM13 and it has made my phone unreliable. Problems receiving calls, making calls, mobile internet, etc, etc
So I have been trying to get my phone back working again, and have been introduced to using fastboot to install different versions of CM and also tried Oxygen but none of it seems to fix it.
Not sure what else to try =( any suggestions?
I've been trying to learn from reading this forum but have been getting confused with the terms ROM and firmware. People in some threads saying to flash the ROM then update the firmware. Aren't they the same thing?
Is using the fastboot method as clean an install as you can get? I find using different recoveries confusing at this point so have just been using fastboot as it seems like the most straightforward method. Is the only time you would use TWRP is when you want to keep data?
If I am just trying to fix my phone network functionality, do I just need to flash the modem? or do I need to do ALL the following?
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oppostanvbk static_nvbk.bin
I read somewhere that I need to wait 5 minutes after turning on the phone following any flashing activity before I should test anything out. Is that right?
Thanks for any help. Hopefully I can get caught up on all this flashing stuff. Seems like every time I need to do some type of flashing (every few years) the whole process changes and I need to relearn the whole process again.

Serious OnePlus One Bootloop Issue

Hey guys, I have a 64gb OnePlus One and it's seems to be stuck on an infinite bootloop(soft-brick). I am able to access both fastboot mode and recovery. My phone's bootloader is unlocked and I have the stock cyanogen recovery presently.
I had run into this issue several times earlier, and was quickly able to resolve it... Either by flashing a different custom rom or factory resetting the phone using TWRP recovery and it all worked out, but this time, nothing seems to work. After reading several guides and watching many videos, I frequently came across that flashing the stock(cm12.1 factory image) would fix the bootlooping issue once and for all, and it turns out and it did work, but only momentarily and it was quite weird infact... After the fastboot flashing process was done, the phone started bootlooping once again and I let it happen for 5-10 mins, after which I gave up and turned it off. But after leaving it off for sometime and then turning it on later, it did boot up once for sometime to the initial boot setup screen, only to start rebooting again.
I gave it some more time to be turned off and the next time I turned it on, it booted normally and everything seemed to be working fine... I installed whatever apps I needed, downloaded music and everything looked great, but then it started crashing into random reboots once again, at random instances, but using the temporary power off technique I talked about earlier, I made it work somehow, until even that stopped working.
I've tried literally every method, even locking and unlocking the bootloader and then flashing stock again... Also... using the single command method mentioned which fixed persist partitions on that phone, and even that was in vain.
Infact, now my phone is in an even worse condition, it won't even make it past the 1+ logo, just keeps on rebooting there. Any help with this issue would be greatly appreciated... Thank you.

Sounds like the exact final stage issue that my friend was having. Finally his phone even bootlooped in fastboot when he was on holiday.
I had the phone with me for a couple of hours when he returned and nothing worked. I couldn't even connect to the pc in the end. I personally think his memory had an issue.
Seems like you tried all you could. Does it stay on in fastboot?
In the end I had my friend rma his phone and Oneplus said the warranty was void because one sticker was slightly red .... complete bull story since the phone was never ever in contact with water or other liquid stuff and they would not answer a single question in regards to that. So my advice if someone else doesn't have a hocus pocus solution is to check if you have warranty and see if you can't see these moisture indicator through the headphone jack and try to go for warranty repair.

Download the latest fastboot signed ROM from here: https://forums.oneplus.net/threads/mirrors-for-official-cyanogen-roms-ota-updates.141825/
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash recovery recovery.img
fastboot flash userdata userdata_64G.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img

[DEV] Lineage OS for Oppo F1 (f1f)

Hi there!
I've been trying to port CM14.1 to my Oppo F1 (code f1f with Snapdragon 616). I got a build with backlight always on and a lot of things already working (touchscreen, 4G, camera).
After a few hours digging into the code and a dozen of kernel builds, I couldn't find a way to make the backlight brightness level work correctly. From my understanding, this Oppo device (among other CM friends sharing the same kernel repo) seems to be the only one using GPIO to initialize the backlight. It seems that the MSM video driver is using this kind of Qualcomm SoC « magic » registers to control the backlight.
Has anyone been working on this? Any repo recommandations from where I could take inspiration to fix this?
A picture to encourage anyone to work on this…

kdd998 said:
Hi there!
I've been trying to port CM14.1 to my Oppo F1 (code f1f with Snapdragon 616). I got a build with backlight always on and a lot of things already working (touchscreen, 4G, camera).
After a few hours digging into the code and a dozen of kernel builds, I couldn't find a way to make the backlight brightness level work correctly. From my understanding, this Oppo device (among other CM friends sharing the same kernel repo) seems to be the only one using GPIO to initialize the backlight. It seems that the MSM video driver is using this kind of Qualcomm SoC � magic � registers to control the backlight.
Has anyone been working on this? Any repo recommandations from where I could take inspiration to fix this?
A picture to encourage anyone to work on this�
Click to expand...
Click to collapse
Backlight works fine on cm13 builds. Are you using kernel source from the cyanogenmod git? Did you have to make any changes to the kernel source? CM kernel source was working fine for me with cm13 up to about a month ago but then started causing bootloops (seems to be something in the dtb). Also, does rotation work, I have been having problems using their sources with accelerometer. I do have a build of cm13 with everything working well, but it is using @uberlaggydarwin kernel source from github and I don't think he wants me to share things built from it (better moving forward to be on official cm sources anyway).

Try this op2 also has backlight issue in custom rom.
Group Butler [beta]:
Type the below commands in terminal to turn off backlight
su (give permission when prompted)
echo 0 > /sys/class/leds/button-backlight/max_brightness
chmod 755 > /sys/class/leds/button-backlight/max_brightness

MiniBlu said:
Backlight works fine on cm13 builds. Are you using kernel source from the cyanogenmod git?
Click to expand...
Click to collapse
Yes, the msm8939 kernel common to Oppo devices.
MiniBlu said:
Did you have to make any changes to the kernel source?
Click to expand...
Click to collapse
Yes, changes are necessary. I didn't have a look at audio yet, but the touchscreen driver needs changes, dtsi files to clear warnings and the lm3630 driver needs a lot of changes to make the probe work.
MiniBlu said:
CM kernel source was working fine for me with cm13 up to about a month ago but then started causing bootloops (seems to be something in the dtb).
Click to expand...
Click to collapse
Yes, but with cm-14.1, there's a big gap in the kernel source. It seems to be nearer the CAF source and all the ugly Oppo ifdefs are out (seriously, Oppo's coding style is awful ).
MiniBlu said:
Also, does rotation work, I have been having problems using their sources with accelerometer.
Click to expand...
Click to collapse
I'll try to see if rotation is OK but I have doubts. I didn't have a look at it yet. Which device is it?
Ucihaflash said:
Type the below commands in terminal to turn off backlight
su (give permission when prompted)
echo 0 > /sys/class/leds/button-backlight/max_brightness
chmod 755 > /sys/class/leds/button-backlight/max_brightness
Click to expand...
Click to collapse
Thanks for the tip, I'll have a look, but I find it strange that this device is in the leds class, I thaught it was in the backlight class. It needs to be tried anyway

So, rotation doesn't work. But button-backlight is there, but I cannot control backlight. I'll continue digging…

Wow u actually been able to put cm14 on oppo f1. C
When you finish this will you make it public? Many people would love this

Of course, if ever I succeed, it's open source. The goal is to have an official device in CM. But on CM14.1, we're far from it. On CM13, I believe it's almost ready, but i'll let the actual devs who did the job take care of it.

Thanks so much. Good luck with cm14. Hope u succeed! ?

verry happy to see that, good luck thank's:good::good::good::good::good::good:

kddoran said:
verry happy to see that, good luck thank's:good::good::good::good::good::good:
Click to expand...
Click to collapse
- 6months latter
........... . .when you guys realize that Oppo has the worst vendor ive ever seen on the planet, bad,slowest(never)get update at all..

MiniBlu said:
Backlight works fine on cm13 builds. Are you using kernel source from the cyanogenmod git? Did you have to make any changes to the kernel source? CM kernel source was working fine for me with cm13 up to about a month ago but then started causing bootloops (seems to be something in the dtb). Also, does rotation work, I have been having problems using their sources with accelerometer. I do have a build of cm13 with everything working well, but it is using @uberlaggydarwin kernel source from github and I don't think he wants me to share things built from it (better moving forward to be on official cm sources anyway).
Click to expand...
Click to collapse
Which sources did you use to build? Last time I tried compiling from the official sources I got some errors building the kernel so I gave up but that was a while ago.

As an Oppo f1 user, good luck to your project since oppo never update its thing

kdd998 said:
Of course, if ever I succeed, it's open source. The goal is to have an official device in CM. But on CM14.1, we're far from it. On CM13, I believe it's almost ready, but i'll let the actual devs who did the job take care of it.
Click to expand...
Click to collapse
Is there a hope for getting officially build on CM

i am currently on project spectrum and want to flash back colour os through fastboot. has anyone done it before. i want to do it but have a habit of bricking my device. Would this be correct.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery.img
or
flashall
or will fastboot -w and fastboot update colouros.zip work?
which would work?

Jamie_oppo said:
i am currently on project spectrum and want to flash back colour os through fastboot. has anyone done it before. i want to do it but have a habit of bricking my device. Would this be correct.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery.img
or
flashall
or will fastboot -w and fastboot update colouros.zip work?
which would work?
Click to expand...
Click to collapse
no. none of the above will work. System image is to large to flash by fastboot.
To return to coulouros you would need to pull these files form the colouros.zip and put them in you fastboot folder
boot.img
logo.bin
NON-HLOS.bin
reserve4.img
rpm.mbn
sbl1.mbn
static_nvbk.bin
tz..mbn
then pull emmc_appsboot.mbn from magictricks.zip, and put it in fatboot folder.
then put twrp-3.0.2-0-f1f.img in fastboot folder.
then put modified colouroszip file from here on your external sdcard.
From cmd in fastboot folder run
fastboot flash boot boot.img
fastboot flash LOGO logo.bin
fastboot flash modem NON-HLOS.bin
fastboot flash reserve4 reserve4.img
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash oppostanblk static_nvbk.bin
fastboot flash tz tz.mbn
fastboot flash recovery twrp-3.0.2-0-f1f.img
fastboot boot recovery twrp-3.0.2-0-f1f.img
Unplug usb cable.
This should have flashed all firmware back to stock (except bootloader to magicktricks unlocked bootloader and recovery to twrp) and rebooted you into twrp. You can now WIPE data and cache then flash the colouros.zip. (once in colouros you may need to enable oem unlocking in developer settings and then do a fastboot oem unlock.)
From here if you want to go back to project spectrum you can just flash the colouros recovery I sent you earlier and the flash project spectrum from it.
*NOTE* all the above should work but you attempt this at your own risk. I take no responsibility for possible bad outcome.

Thanks so much. I will try this as soon as I can. If something goes wrong after fastboot boot the twrp image will I still have fastboot just in case??

MiniBlu said:
no. none of the above will work. System image is to large to flash by fastboot.
To return to coulouros you would need to pull these files form the colouros.zip and put them in you fastboot folder
boot.img
logo.bin
NON-HLOS.bin
reserve4.img
rpm.mbn
sbl1.mbn
static_nvbk.bin
tz..mbn
then pull emmc_appsboot.mbn from magictricks.zip, and put it in fatboot folder.
then put twrp-3.0.2-0-f1f.img in fastboot folder.
then put modified colouroszip file from here on your external sdcard.
From cmd in fastboot folder run
fastboot flash boot boot.img
fastboot flash LOGO logo.bin
fastboot flash modem NON-HLOS.bin
fastboot flash reserve4 reserve4.img
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash oppostanblk static_nvbk.bin
fastboot flash tz tz.mbn
fastboot flash recovery twrp-3.0.2-0-f1f.img
fastboot boot recovery twrp-3.0.2-0-f1f.img
Unplug usb cable.
This should have flashed all firmware back to stock (except bootloader to magicktricks unlocked bootloader and recovery to twrp) and rebooted you into twrp. You can now WIPE data and cache then flash the colouros.zip. (once in colouros you may need to enable oem unlocking in developer settings and then do a fastboot oem unlock.)
From here if you want to go back to project spectrum you can just flash the colouros recovery I sent you earlier and the flash project spectrum from it.
*NOTE* all the above should work but you attempt this at your own risk. I take no responsibility for possible bad outcome.
Click to expand...
Click to collapse
i extacted all the files and put twrp and the magictricks thing in the fastboot folder
fastboot flash boot boot.img
fastboot flash LOGO logo.bin
fastboot flash modem NON-HLOS.bin These all worked fine
but when i got to reserve4 i got C:\Users\ponyd\Desktop\back to colour os>fastboot flash reserve4 reserve4.img
target reported max download size of 268435456 bytes
sending 'reserve4' (5176 KB)...
OKAY [ 0.200s]
writing 'reserve4'...
FAILED (remote: size too large)
finished. total time: 0.216s
i shat my self when that happened? i then flashed the boot.img logo and modem of project spectrum and went back to spectrum. DId i do something wrong?

Backlight fix
Try coloros setting app. Search and u will get it.

I'm actually under spectrum project hope you could port this cm14.1 for OPPO f1...
Thanks

I know this may be abit reluctance but you may want to open source the project on what you have now and list what is working and what's isn't, and I'm sure people will contribute to the project given that is qcom there should not be much of an issue to get it working.