Thread abandoned due to change of phone, continued by kamilmirza here:
https://forum.xda-developers.com/oneplus-3t/how-to/firmware-beta-10-t3631166
----------------------------
Here you go, if you're not using the stock rom and want the latest firmware & modem.
Latest update (Official 4.1.6) added 10th June :
https://www.androidfilehost.com/?fid=673368273298962854
Latest beta - Beta 9 added, dated 14th June:
https://www.androidfilehost.com/?fid=817550096634779620
Just in case you have problems with the current release or feel like your phone runs better on a previous version, here's a link to my firmware folder, it contains all the previous versions if you have any problems :
https://www.androidfilehost.com/?w=files&flid=145813
Please don't post alternative sources, if you want to post your own source then make your own thread.
you can use on FreedoomOs 4.0.2?
Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
You should be able to, just be aware anyone flashing that you won't be able to flash your rom again without flashing the 4.0.2 firmware,
4.0.3 has different TZ version:
4.0.2 : TZ.BF.4.0.1-76917
4.0.3 : TZ.BF.4.0.1-83199
If you try flashing your rom back in you'll get a TZ error similar to the following:
{
"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"
}
I'm guessing it won't take roms long to update to the new firmware, as long as OP release the source quickly.
Did the same with LineageOS 2017-02-08 and it's working fine. But while flashing the ROM I get the same TZ error.
I think it's safe to change the TZ version in updater-script before updating to the newest LOS (until the ROM developers will update it) isn't it ?
Can you upload and post a modem only flashable zip for 4.0.2. and 4.0.3 please.
Separate flashable zip is appreciated.
Need a thread like this https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
for OnePlus 3T
if i flash this... whether it will bi unolcked baseband because i cant get 4g in serbian telenor with a3010 model?
Just updated and uploaded 7.1.1 firmware/modem.
you are the best, thank you
djsubterrain said:
Just updated and uploaded 7.1.1 firmware/modem.
Click to expand...
Click to collapse
It's ok to flash on RR and other custom 7.1.1 Roms??
evanxyj said:
It's ok to flash on RR and other custom 7.1.1 Roms??
Click to expand...
Click to collapse
The roms have latest included already.. If u feel. The don't.. U are ok to flash them.. No issues at all..
I saw your finger pointing to your Thanks button, OP.
I hit it. =)
evanxyj said:
It's ok to flash on RR and other custom 7.1.1 Roms??
Click to expand...
Click to collapse
I'm using it on the latest build of RR and it works fine.
djsubterrain said:
I'm using it on the latest build of RR and it works fine.
Click to expand...
Click to collapse
I tried. And trust zone check failed cause the new firmware one updated and RR ROM biulds on the old one.
Maybe because I'm using the unofficial RR.
evanxyj said:
I tried. And trust zone check failed cause the new firmware one updated and RR ROM biulds on the old one.
Maybe because I'm using the unofficial RR.
Click to expand...
Click to collapse
Probably, I'm on the official build of RR, you should advise the dev on the unofficial build to update their sources, it should be built on LOS which has been updated to latest firmware now.
Thanks! ☺
djsubterrain said:
Probably, I'm on the official build of RR, you should advise the dev on the unofficial build to update their sources, it should be built on LOS which has been updated to latest firmware now.
Click to expand...
Click to collapse
The latest unofficial RR has updated the updater script, I've checked the file.
djsubterrain said:
I'm using it on the latest build of RR and it works fine.
Click to expand...
Click to collapse
And will latest 7.1.1 firmware work with other kernel like boeffla or is that independent from firmware? Anyone tried that? thx
Exist firmware and modem from Last 4.1.0?
Enviado desde mi unknown mediante Tapatalk
I suggest not to upgrade firmware, until the custom ROM dev support it.
Yes, I'm also looking for this, but no pressure to you dev
rezaluchu said:
I suggest not to upgrade firmware, until the custom ROM dev support it.
Yes, I'm also looking for this, but no pressure to you dev
Click to expand...
Click to collapse
RR works with 4.1 fw :good:
Related
thread closed
Strictly no flashing the ROM from an AOSP KitKat build right?
give it a try
MrChaosDesire said:
Strictly no flashing the ROM from an AOSP KitKat build right?
Click to expand...
Click to collapse
You can give it a try, users who flashed from aosp, got bootloop problem, only one guy flashed through miui and he was able to boot into the system.
MK_Networks said:
Android L
{
"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"
}
Note this is a alpha build, Flash on your own risk!
Based on latest Android L build
You should be on MIUI Rom before flashing !!!!
Downloads
http://www.mediafire.com/download/r2j5vq5hdh6fsnr/MK_Android_L_Alpha_Build-01.zip
Use this recovery only!
CWM_recovery_r8_cancro_4.4.zip
Instructions:
1. Disable Dual Boot
2. Format /system 1 and system 2
3. Clean everything
4. Flash the ROM
5. Wipe cache
6. Factory Reset after flashing rom! (<--- Important xD)
7. Reboot
Some users reported bootloop!
Please provide me Logcats so that i could fix bugs
(You can take logcat in bootloop as well!)
This thread will be updated after Beta release
XDA:DevDB Information
MK's Android L, ROM for the Xiaomi Mi 3
Contributors
MK_Networks, MK_Networks
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
Version Information
Status: Testing
Current Stable Version: Under Testing
Current Beta Version: Soon to release!
Created 2014-11-22
Last Updated 2014-11-21
Click to expand...
Click to collapse
List of whats working and whats not please.
can you please list what are the bugs that are currently present ? that will make things easier to report Thanks for this
This is alpha build, and developer doesn't having mi3 with him. Please go and try by yourself. First of all, booting is a concern. If phone will boot. Please give a feedback.
And yes, no known bugs till now, because nobody knows. So, give it a try and provide logcats, it will give easiness to developer to understand bugs and root of bugs.
For anyone that's tried this on a Mi 4, how'd it go? Seeing as some people have luck flashing Mi 3 ROMs over their Mi 4s. Thanks!
thanks a lot man
do we have to flash gapps to ??
ZenR2 said:
thanks a lot man
do we have to flash gapps to ??
Click to expand...
Click to collapse
Gapps are already present.. Hope it boots well!
what sources did you use?
Thanks man! Will try this and repot bugs if there's any
Need a mirror on Google drive
Great effort without sources. Will try and report any bugs.
on google drive:
https://drive.google.com/file/d/0B8eEOfHgMjiAWnVXYzJqWHpwN2c/view?usp=sharing
Anyone managed to boot so far? I am keen to try too if it is confirmed that it boots. I have already downloaded the ROM and waiting for someone to confirm that it boots.
Presently on on 21st November weekly
tamilmad said:
Anyone managed to boot so far? I am keen to try too if it it confirmed that it boots. I have already downloaded the ROM and waiting for someone to confirm that it boot.
Presently on on 21st November weekly
Click to expand...
Click to collapse
+1
s4tch said:
what sources did you use?
Click to expand...
Click to collapse
Its a port
not booting
I installed this just now, I'm on miui 6 weekly and follow the step by step instruction. now my phone is just stuck with the boot screen. is it only me or do I have to do something else to make this work?
tamilmad said:
Anyone managed to boot so far? I am keen to try too if it is confirmed that it boots. I have already downloaded the ROM and waiting for someone to confirm that it boots.
Presently on on 21st November weekly
Click to expand...
Click to collapse
I am currently downloading the ROM and will then give it a try... But my internet speed sucks..
Meanwhile, I would suggest you guys to give it a try. Take the nandroid backup and flash the ROM... If it doesn't boot, you can restore the backup. More the number of users try, more are the chances of getting the issue fixed. ?
Sent from my MI 3W using Tapatalk
Please move this to the general section or its likely to be deleted by the moderators.. Since there are no kernel sources..
TWRP continued from the work of @KAsp3rd.
{
"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"
}
Instructions:
Marshmallow:
Refer HERE
If you are already running twrp in marshmallow then simply flash any recovery updates using the image install function within twrp.
If you are already updated to the official marshmallow update from T-Mobile then you must wait for a root fix and this cannot be flashed from fastboot commands!!
Lollipop:
Your bootloader must be unlocked prior to attempting installation.
Option 1: Flash using fastboot.
Option 2: Flash in previous installed version of TWRP.
Download:
Marshmallow
md5: 368f665abed83d839feaa14f5d975e7e
Lollipop
md5: b9ab4ac5b57b26c044db0f7be9ce1e5a
Previous versions may be found in the original posting HERE.
Changelog:
3.0.2-0 Marshmallow
05/01/16:
(REVISION) exfat enabled for testing
Device tree has been rebuilt and USB is operational for mtp, adb, and usb-otg.
INITIAL:
Recovery updated to v3.0.2-0
Kernel updated to Marshmallow
Fake epoch disabled in kernel
3.0.1-0 Lollipop
Fake epoch set for my device in the kernel (you will most likely experience incorrect date/time)
DST is now functional
Known issues:
The status bar is displayed in the 2nd screen area. (I have no plans on pursuing screen adjustment)
Time is not saved from Android to Recovery. Fake epoch time has been disabled in the kernel resulting in a year of '1971'. (The only way I've found of fixing this is with a custom fake epoch for each device based on build date. That simply is not going to happen...)
(Re)Sources:
Device tree is available HERE.
Compiled using twrp_omni 6.0 branch available HERE.
Kernel source is available HERE.
Get superSU from @Chainfire HERE.
Please report all issues on my github so I can track them HERE.
Special thanks:
@KAsp3rd @TheJesus @shabbypenguin @Dees_Troy @_that @bigbiff @helicopter88 @savoca @autoprime and anyone I've forgotten.
Reserved...
Just downloaded gonna check it out. Thank you
Thank You...
Thank you sir
Common sense isn't all that common
Thanks
Sent from my LG-VS985 using XDA-Developers mobile app
EDIT: Nevermind.
So far so good. Thanks!
Thank you, thank you
@GROGG88 v3.0.2-0 is out fyi.
Airtioteclint said:
@GROGG88 v3.0.2-0 is out fyi.
Click to expand...
Click to collapse
When sources are updated I will update the build, but you can see here that they remain at 3.0.1:
https://github.com/TeamWin/Team-Win-Recovery-Project/commits/android-6.0
GROGG88 said:
When sources are updated I will update the build, but you can see here that they remain at 3.0.1:
https://github.com/TeamWin/Team-Win-Recovery-Project/commits/android-6.0
Click to expand...
Click to collapse
We will need an update to support the 20e bootloader from the Marshmallow update released today - hope you can help!
siraltus said:
We will need an update to support the 20e bootloader from the Marshmallow update released today - hope you can help!
Click to expand...
Click to collapse
Yes. I am looking for MM compatible TWRP also. Will be great to see as soon as possible.
siraltus said:
We will need an update to support the 20e bootloader from the Marshmallow update released today - hope you can help!
Click to expand...
Click to collapse
sikander3786 said:
Yes. I am looking for MM compatible TWRP also. Will be great to see as soon as possible.
Click to expand...
Click to collapse
I updated to MM today, so I am currently working on it...
GROGG88 said:
I updated to MM today, so I am currently working on it...
Click to expand...
Click to collapse
Thank you VERY MUCH.
GROGG88 said:
I updated to MM today, so I am currently working on it...
Click to expand...
Click to collapse
Thank you!
Maybe with MM we can get the date/time correct in twrp.. (keeping fingers crossed)
NYLimited said:
Thank you!
Maybe with MM we can get the date/time correct in twrp.. (keeping fingers crossed)
Click to expand...
Click to collapse
The time is always correct for me... :laugh:
Seriously, the MM kernel source does not have any changes to fake epoch. Everyone will continue to suffer with 'grogg' time.
MM
GROGG88 said:
I updated to MM today, so I am currently working on it...
Click to expand...
Click to collapse
How is MM treating you on your device? And, thank you for all your work. We all appreciate it.
scloutkst said:
How is MM treating you on your device? And, thank you for all your work. We all appreciate it.
Click to expand...
Click to collapse
Full wipe and running just fine so far.
It seems that we're in the same boat with the tmo g5. Luckily team codefire has made progress. Hopefully we can benefit from it as well.
https://youtu.be/Zlieyd9CP7Q
@autoprime
{
"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"
}
-This firmware it's up to date with latest changes from Xiaomi.-
It is VoLTE working on this firmware?
It should work now, but i can't test It becouse my provider has no VoLTE. Try and tell me!
Any risk of relocking bootloader flashing this firmware?
Absolutely not.
Why i need this firmware?
If you want to flash a CM13/14/14.1/AOSP N rom, you need to flash this updated firmware first.
For what reason i have to choose this firmware instead of another one?
If you have flashed another firmware, you probably have those issues: battery percentage not working, camera autofocus not working, low signal strenght. If not, stay on your firmware.
In this firmware there's no emmc_appsboot.mbn, why?
There's no need to flash bootloader every time and yes, you can flash this firmware safely.
How to install?
-Reboot to TWRP recovery ( latest TWRP by TheStrix recommended)
-Flash firmware
-Factory reset (data, cache and dalvik-cache)
-Flash your favorite Marshmallow or Nougat ROM
-Reboot your phone
-Enjoy
Updated CM13/14/14.1 firmware. (12.04.2017)
Latest KENZO Firmware
Latest KATE Firmware
Old CM13/14/14.1 firmware.
KENZO
KATE
Enjoy your favourite ROM!
I found that emmc_appsboot.mbn doesn't be included in your new firmware if comparing to CM14.1 common firmware.
Is there any problem ?
Kris Chen said:
I found that emmc_appsboot.mbn doesn't be included in your new firmware if comparing to CM14.1 common firmware.
Is there any problem ?
Click to expand...
Click to collapse
There's no need to include the emmc_appsboot.mbn
Psy_Man said:
There's no need to include the emmc_appsboot.mbn
Click to expand...
Click to collapse
i see that file in unofficial ubl tutorial, so that file contain about bootloader?
Does it work on the latest Ressurection Remix 5.80 Nougat?
lazygenius2505 said:
i see that file in unofficial ubl tutorial, so that file contain about bootloader?
Click to expand...
Click to collapse
Yes
peeyaj said:
Does it work on the latest Ressurection Remix 5.80 Nougat?
Click to expand...
Click to collapse
Of course! Tested personally
just checked kenzo version. why choose miui 6.11.24 to use as cm14/14.1 firmware? there is any different with previous miui version?
Psy_Man said:
Yes
Click to expand...
Click to collapse
@Kris Chen said that that file included in common cm14 fw, there is no any effect if you didn't include that file?
What's the difference between this one and 11.15?
@Psy_Man
Does this fix the supersu messing up with sensors?
@Psy_Man Thats from 241116 miui8 based radio firmware?
Psy_Man said:
There's no need to include the emmc_appsboot.mbn
Click to expand...
Click to collapse
why do you think there is no need for that file?
Don't know yet, but it indeed no issue after flashing this firmware.
Is it my wrong image or not because I found signal more stable on this firmware.
lazygenius2505 said:
@Kris Chen said that that file included in common cm14 fw, there is no any effect if you didn't include that file?
Click to expand...
Click to collapse
Will this help in getting VoLTE to work?
Is this firmware from MiUi MM dev rom...so that we dont have to flash MM dev rom and backup efs to get VoLTE working??
Please give some details in OP.
Sent from my Redmi Note 3 using Tapatalk
Thanks.... its working perfectly in Kate
peeyaj said:
@Psy_Man
Does this fix the supersu messing up with sensors?
Click to expand...
Click to collapse
Use Phh's superuser instead of supersu
Psy_Man said:
Of course! Tested personally
Click to expand...
Click to collapse
Does volte works after flashing this on latest RR
kiran G. said:
Does volte works after flashing this on latest RR
Click to expand...
Click to collapse
My provider has no VoLTE and i can't confirm
kiran G. said:
Does volte works after flashing this on latest RR
Click to expand...
Click to collapse
No, volte does not work with this firmware (RR 7.1).
{
"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"
}
Flash at your own risk!
I'm not the developer of this rom, but I open this tread to save work for developers, and to discuss this fantastic ROM.
ROM Download: http://dl.omnirom.org/find7op/
Sources: (the Oneplus One source is called find7op)
Device Tree
Common Tree
Kernel
Gerrit: https://gerrit.omnirom.org/
Gapps: http://opengapps.org/
SuperSU: http://download.chainfire.eu/supersu
Recovery: TWRP
Bug reports: http://jira.omnirom.org
How to flash:
1. Boot into your TWRP recovery.
2. Backup your existing Rom.
3. Wipe partitions.
4. Flash the Rom.
5. Flash Gapps (and if you need root, flash SuperSU).
6. Wipe Cache and Dalvik.
Reboot your device.
Omnirom WEEKLY, ROM for the OnePlus One
Contributors
@samstone86 , @maxwen , @herna
Source Code: http://www.github.com/omnirom
Version Information:
ROM OS Version: 7.1.2 Nougat
ROM Kernel: Linux 3.4.x
Based On: AOSP
Status: WEEKLY
Created 2017-05-31
//
Jopejt said:
Guess this makes me the first visitor. Looking forward to this...
Click to expand...
Click to collapse
UPDATE News here
The bast
Moderator Information,
Thread has been moved to the General section. Only work built by the developer belongs in the development section. If you are merely linking to another persons work, it belongs in General.
Many thanks,
Stephen
thread*
Is f2fs supported?
Sent from my A0001 using Tapatalk
secondkai said:
Is f2fs supported?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Unfortunately, no.
Sent from my A0001 using Tapatalk
How about camera function in this ROM.
Thanks.
I've been using this ROM for the past few months as my daily driver. Meets all my daily needs. Ota updates weekly, camera functions fine for my needs. Battery life is fine for me, easily lasts a day based on my usage.
anyone can confirm?
https://forum.xda-developers.com/omni/help/google-search-app-freeze-oneplus-one-t3605486
Latest build, 20170618, causes the phone to crash and reboot when trying to view webm videos.
Just tried the previous build, 20170612, and same result. The last one that works is 20170604.
Does it have VoLTE support?
rohitkatre said:
Does it have VoLTE support?
Click to expand...
Click to collapse
Of course not
Anyone feedback on the latest weekly?
Update: Installed the August 20 build. I have used sultan's lineage OS and AospExtended before, Omni seems to be slow and laggy compared to these two. Battery life is good but the sluggish ui is a deal breaker.
Does this ROM use color os camera blobs and hal?
ThunderThighs said:
Does this ROM use color os camera blobs and hal?
Click to expand...
Click to collapse
yes.
find7op = bacon
daniga74 said:
anyone can confirm?
https://forum.xda-developers.com/omni/help/google-search-app-freeze-oneplus-one-t3605486
Click to expand...
Click to collapse
Take logcat and if nessesary verify if this happens only on Omni rom and report bug in the appropiate place.
Does anyone know if this ROM supports MultiROM?
Cheesethief said:
Latest build, 20170618, causes the phone to crash and reboot when trying to view webm videos.
Just tried the previous build, 20170612, and same result. The last one that works is 20170604.
Click to expand...
Click to collapse
problem has already been reported
temporary change your cpu gov to interactive
Reserved
[OP3T][FIRMWARE] 5.0 Stable - Oreo (19th November 2017) [FLASHABLE]
for OnePlus 3T only
FIRMWARE + MODEM only (NOT FULL ROM)
Latest Stable = OOS 9.0.6 (FINAL) - Pie 9.0 (20th November 2019)
OOS 9.0.6 (FINAL) - Pie 9.0
Latest Beta = Community Beta 2 - Pie 9.0 (7th May 2019)
Community Beta 2 - Pie 9.0
for Beta 10 and above, here's a link to my firmware folder
my FIRMWARE Folder
for previous versions before Beta 10, here's the link to @djsubterrain firmware folder
djsubterrain FIRMWARE folder
UNBRICK GUIDE without data loss for 1+3T by @Babloo289
MODDED FIRMWARE to avoid relocking and/or reformating/reencrypting by @nvertigo67
Anyone Tried it on latest ROM? like Candyo or AEX
xhitm3n said:
Anyone Tried it on latest ROM? like Candyo or AEX
Click to expand...
Click to collapse
ask in specified threads
firmware versions vary from ROM to ROM
Thanks for this. But as a semi-noob I'm curious: do I need to flash firmware updates manually like this if I'm running Lineage OS? I know the firmware gets updated when flashing stock rom, but I don't know about custom roms.
deedaleet said:
Thanks for this. But as a semi-noob I'm curious: do I need to flash firmware updates manually like this if I'm running Lineage OS? I know the firmware gets updated when flashing stock rom, but I don't know about custom roms.
Click to expand...
Click to collapse
like i said earlier that firmware versions varies from ROM to ROM
it depends on the developer of the ROM to make his build on which firmware version
and you have to ask your ROM dev for which firmware to use
where is beta 11 ? its already been a few days since it rolled out. will you upload it or should i download the whole rom to extract the files on my own ?
kessaras said:
where is beta 11 ? its already been a few days since it rolled out. will you upload it or should i download the whole rom to extract the files on my own ?
Click to expand...
Click to collapse
{
"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"
}
it is released today
thanks for the heads up BTW
downloading and will update in an hour or 2
kamilmirza said:
it is released today
thanks for the heads up BTW
downloading and will update in an hour or 2
Click to expand...
Click to collapse
Today ? Lol I saw it yesterday . Strange. Oke
thread updated with Open Beta 11 (18th July 2017)
link in OP
Is there a changelog what's new?
Lycox said:
Is there a changelog what's new?
Click to expand...
Click to collapse
Look here
https://forum.xda-developers.com/oneplus-3t/how-to/coming-update-oos-based-7-1-t3564240/post73071866
timobayl said:
Look here
https://forum.xda-developers.com/oneplus-3t/how-to/coming-update-oos-based-7-1-t3564240/post73071866
Click to expand...
Click to collapse
Looks like, these are ROM related changes, but not for the firmware.
Lycox said:
Looks like, these are ROM related changes, but not for the firmware.
Click to expand...
Click to collapse
OnePlus never released a FW changelog.
The FW is extracted from the OOS beta rom.
Lycox said:
Is there a changelog what's new?
Click to expand...
Click to collapse
yeah. in op forum
Hello all.
I have OP3T and lineageOS 14.1-20170713. Latest LineageOS 14.1-20170721 need to have most probably latest firmware and modem.
Can I just download flashable zip for Open Beta 11 and flash it via TWRP and then update my current LineageOS to the latest version? Or after flashing firmware/modem do I need clear data in TWRP? Is updating of firmware/modem via TWRP connected with erasing app data and so on?
thanks
edit: works fine with latest lineageOS 14.1-20170721
working front camera fine with this latest firmware? open beta?
i am not able take picture with front camera
I think you do not need to add
getprop("ro.display.series") == "OnePlus 3T" || abort("E3004: This package is for "OnePlus 3T" devices; this is a "" + getprop("ro.display.series") + "".");
Click to expand...
Click to collapse
Because not every rec will accurately identify the model, especially now are unified build
666biker said:
working front camera fine with this latest firmware? open beta?
i am not able take picture with front camera
Click to expand...
Click to collapse
No problem, vertexos, op3t