Related
Unofficial LineageOS 13 (Android Marshmallow) for JBBL dated March 18, 2017 from the 4PDA forums courtesy of developer ilichva!
Again, this is only for JBBL. Flash at your own risk and please do a nandroid backup prior to doing so!
All credits and thanks go to the original developer ilichva!
____________________________________________
Latest Build - LineageOS 13:
lineage-13.0-20170318-port-ilichva-xt907_jbbl.zip (405.4 MB)
Mega
SolidFiles
PCloud
MD5 :: 63FB23666399844E5BB7A8D9C347374D
____________________________________________
Prior Build - CM13:
cm-13.0-20161205-ilichva-xt907_jbb.zip (411.9 MB)
Original Link
Mega
SolidFiles
PCloud
MD5 :: 3c786a57929d024010a0fce36287ea7d
____________________________________________
NOTE: If you are on KitKat Bootloader (KKBL), you will need to revert to the JellyBean Bootloader (JBBL) before you can flash this ROM. Instructions on how to do so may be found here and here and here
____________________________________________
Latest TWRP 3.0.2 recovery by ilichva may be found/downloaded here
Updated to 03.25.2016 build
Hallo Rahimali
Thanks for the share. I have tried this and apparently works ok. I'm unable to get WiFi working. Tried different gapps but there are force close issues. Any recommended gapps versions available?
Opengapps usually does the job. Flashing gapps with marshmallow is different than with prior android versions. With MM you have to flash gapps immediately after you flash the ROM (before booting up the ROM for the first time). Try and see if that resolves your FC issues
Updated to April 02, 2016 build!
I managed to get the force close issues resolved. Everything works fine except Wifi. I am unable to enable wifi as the button is greyed out. I tried enabling wifi from terminal using svc wifi enable, it enabled the button but wouldnt detect any available wireless networks. Any fixes for this?
Updated to April 05, 2016 build!
ultrasoniic said:
I managed to get the force close issues resolved. Everything works fine except Wifi. I am unable to enable wifi as the button is greyed out. I tried enabling wifi from terminal using svc wifi enable, it enabled the button but wouldnt detect any available wireless networks. Any fixes for this?
Click to expand...
Click to collapse
Sorry no idea. Nobody is complaining in the 4pda forums about any WiFi issues. Did you do a clean flash? Maybe the developer, @ilichva can help?
bootloader and recovery
My XT907 is showing that my bootloader is "0x109B" and I am unsure what version of TWRP supports 6.0.1 (currently running 2.8.6.0)
Can anyone verify their settings and let me know?
I am running CM12.1 currently, so I should be able to dirty flash correct?
Thanks guys!
KKBL?
Anyone know of a marshmallow based rom that works with the kitkat bootloader for this device?
crzypcdude said:
Anyone know of a marshmallow based rom that works with the kitkat bootloader for this device?
Click to expand...
Click to collapse
Marshmallow not yet available on KKBL
rahimali said:
Marshmallow not yet available on KKBL
Click to expand...
Click to collapse
Are there any significant reasons to stay on the KitKat bootloader? Otherwise I'll just downgrade now that I'm rooted with an unlocked bootloader.
One of the most compelling reasons to stick with the KKBL would be the availability of the 3.4x kernel as opposed to the 3.0x kernel on the JBBL but feel free make your own decision. I was on the JBBL (by choice) for a considerable length of time without any apparent side effects...
Would you mind adding dates to post #1?
Any updatefor this rom?
crzypcdude said:
Would you mind adding dates to post #1?
Click to expand...
Click to collapse
The dates are already present in post #1 as well as in the filenames.
dedik46 said:
Any updatefor this rom?
Click to expand...
Click to collapse
Updated!
Are all the builds being updated in the 4PDA post linked in #1 as well as TWRP builds?
crzypcdude said:
Are all the builds being updated in the 4PDA post linked in #1 as well as TWRP builds?
Click to expand...
Click to collapse
That is correct.
Confirmed Working!
Can confirm this works, flashed the recovery included in the 4pda post, used it to flash the rom, gapps, and supersu. Initially booted up in Russian, but after waiting for 30 seconds or so, switched to English on its own. Setup was flawless after that, no issues to report as of now. Anyone that needs help installing the rom or downgrading from kitkat to jellybean just message me.
I thought I was the only one that ended up with default language in Russian... All the previous builds defaulted to English on install... Also when I downloaded the latest update it downloaded on my phone as a .bin not a .zip I checked the file size and contents vs what is online (after changing the extension to .zip) and everything seemed to be Ok so I installed and been up and running on latest version for 24 hours....
Had a few FC's in the beginning while changing the language to English (I have a feeling that some of my already installed apk's caused the issue) . I did do a test run before restoring my stuff and didn't have any issues during initial setup and the phone auto corrected language based off sim during initial setup.
Haven't gotten a chance to fully test this build, but I know that the issue that I was having with the native tethering soft rebooting the phone every couple of hours when active is gone! After a few more days of messing with it I will post any other issues that I come across
Sent from my Moto Razr M on cm13 4-16-16 using XDA Free mobile app
Any clue about why I'm getting error 7 while finishing the last steps of the ROM flashing procedure?
Hi and sorry for the potential newb post
Been using CM / Lineage for years and never come across an individual firmware upgrade requirement until now.
I am on Lineage nightly Feb 8th and cant go any further due to:
comparing tz version TZ.BF4.0.1-83199 to tz.bf.4.0.1-76917
assert failed: oppo.verify_trustzone("TZ.BF.4.0.1-81399") == "1"
updater process ended with ERROR: 7 error installing zip file
I have the working 1+3 TWRP installed so Is it possible to upgrade the firmware only?
Or do I have to wipe and install the latest OOS then go back to Lineage?
I downloaded OOS 41 and there is a firmware folder in there with a few bin / mbn files so kinda hoping I can somehow flash just the firmware and keep my build.
Appreciate any help....
Cheers
Gaz
Here is the latest firmware (4.0.3). Download firmware + modem and flash in TWRP before LineageOS.
Spot on - thanks Fam im sorted
Familotel said:
Here is the latest firmware (4.0.3). Download firmware + modem and flash in TWRP before LineageOS.
Click to expand...
Click to collapse
great work!thanks
Familotel said:
Here is the latest firmware (4.0.3). Download firmware + modem and flash in TWRP before LineageOS.
Click to expand...
Click to collapse
Hey there, sorry to bug you guys. Unfortunately I'm noob so I can't comment on the main LOS thread, but I have an issue that hopefully someone can help with. Originally on CM14 nightlies, without any dramas, obviously with the change from CM on LOS I've flashed the experimental build, then the LOS nightly to get started, all went fine until the change to unified requiring the firmware update. I've installed 2nd March nightly (by editing the file to ignore the trustzone version) in case it was that, but no seems not.
I've flashed the latest FW as mentioned, and the Baseband version is M8996FAAAANAQM-1.85373.1.86546.1 so it appears I'm running definitely running the latest FW (and there were no errors on install) I then reboot to system, download the latest nightly and go to install - still getting the TZ.BF.4.0.1-83199 to TZ.BF.4.0.1-85373 error.... Have I missed a step somewhere? or is this blindingly obvious and I'm a muppet?
Any helps appreciated! cheers
Same issue with the same parameters!
Z-master said:
Hey there, sorry to bug you guys. Unfortunately I'm noob so I can't comment on the main LOS thread, but I have an issue that hopefully someone can help with. Originally on CM14 nightlies, without any dramas, obviously with the change from CM on LOS I've flashed the experimental build, then the LOS nightly to get started, all went fine until the change to unified requiring the firmware update. I've installed 2nd March nightly (by editing the file to ignore the trustzone version) in case it was that, but no seems not.
I've flashed the latest FW as mentioned, and the Baseband version is M8996FAAAANAQM-1.85373.1.86546.1 so it appears I'm running definitely running the latest FW (and there were no errors on install) I then reboot to system, download the latest nightly and go to install - still getting the TZ.BF.4.0.1-83199 to TZ.BF.4.0.1-85373 error.... Have I missed a step somewhere? or is this blindingly obvious and I'm a muppet?
Any helps appreciated! cheers
Click to expand...
Click to collapse
Hi, I have the exact same issue. I've flashed the firmware to 4.0.3 and successfully installed the nightly from 08/02/2017. Now when I try to flash the nightly from 09/03/2017 I get this issue again! This time nothing helps so far.
Please, if you find a solution - let me know!
devianity said:
Hi, I have the exact same issue. I've flashed the firmware to 4.0.3 and successfully installed the nightly from 08/02/2017. Now when I try to flash the nightly from 09/03/2017 I get this issue again! This time nothing helps so far.
Please, if you find a solution - let me know!
Click to expand...
Click to collapse
Install the firmware from the Open Beta here:
https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
Yeah i had the same issue - open beta 12 is required for the 9th Mar build
Is it possible to install security updates without upgrading to Nougat (currently on 6.0.1)? Before anyone suggests just upgrading to Nougat, I have some Xposed modules that are only stable in M and they are very important to my workflow.
Thanks
illBelief said:
Is it possible to install security updates without upgrading to Nougat (currently on 6.0.1)? Before anyone suggests just upgrading to Nougat, I have some Xposed modules that are only stable in M and they are very important to my workflow.
Thanks
Click to expand...
Click to collapse
Simple answer, possibly, if you use a custom ROM that's on andoid 6 it might merge in the security fixes. But other than that, no.
Answer to your question would be sultanxda rom for op3 which is regularly updated but if you want to remain on oxygen os then I don't think it's possible
I am also thinking about this option too, lots of phone company only have update their ROM for 1 year, that makes every android cell phone is not trustful after 1 year.
Johndawolf said:
Simple answer, possibly, if you use a custom ROM that's on andoid 6 it might merge in the security fixes. But other than that, no.
Click to expand...
Click to collapse
I do, I'm actually on Resurrection Remix but they moved to N quite a few patches ago. Are security updates something only the ROM dev's can include in their patches or is there a zip or apk I can flash in recovery?
illBelief said:
I do, I'm actually on Resurrection Remix but they moved to N quite a few patches ago. Are security updates something only the ROM dev's can include in their patches or is there a zip or apk I can flash in recovery?
Click to expand...
Click to collapse
Not that I'm aware of. It might be theoretically possible, but there's no way I know of to do it.
You can update your kernel to a custom version including further security fixes and update all your applications via Google Play, but there are some components of the ROM you can never update without a newer OS.
With time the small security holes will escalate to major bugs as cyber criminals take advantage of those to steal private data.
Hey Guys how's it going ... I'm having a little trouble getting twrp touch screen to work , running latest update 8.1 dec patch ...read many , many forum discussions here so i wouldn't make any mistakes but for some reason twrp touch is not responsive. Started from absolute stock brand new device , unlocked boot loader and critical and fastbooted pixel 2 xl twrp.img 3.2.1 and while in temporary twrp i flashed the twrp 3.2.1 zip and then the magisk 15.1 zip and absolutely nothing else and rebooted ....everything's fine except when i reboot in to twrp from my device, the touch screen does not work downloaded file from official twrp site and tried a couple times from scratch but never seems to change .... if there's something i've done wrong or if anyone might be able to help it would be very much appreciated and i apologize in advance if there is a solution on here that i haven't located yet
Mr. Blanco said:
Hey Guys how's it going ... I'm having a little trouble getting twrp touch screen to work , running latest update 8.1 dec patch ...read many , many forum discussions here so i wouldn't make any mistakes but for some reason twrp touch is not responsive. Started from absolute stock brand new device , unlocked boot loader and critical and fastbooted pixel 2 xl twrp.img 3.2.1 and while in temporary twrp i flashed the twrp 3.2.1 zip and then the magisk 15.1 zip and absolutely nothing else and rebooted ....everything's fine except when i reboot in to twrp from my device, the touch screen does not work downloaded file from official twrp site and tried a couple times from scratch but never seems to change .... if there's something i've done wrong or if anyone might be able to help it would be very much appreciated and i apologize in advance if there is a solution on here that i haven't located yet
Click to expand...
Click to collapse
Your issue has been well documented. From what I've read, it seems to be much more prevalent when using the stock kernel (boot.img) I would try flashing a custom kernel..ie..Flash, Elemental X, or electron to name a few. Hopefully that will solve your problem :good:
Yep, custom kernel seems to resolve it... I'm using Flash's latest.
Badger50 said:
Your issue has been well documented. From what I've read, it seems to be much more prevalent when using the stock kernel (boot.img) I would try flashing a custom kernel..ie..Flash, Elemental X, or electron to name a few. Hopefully that will solve your problem :good:
Click to expand...
Click to collapse
Thanks Badger , i really appreciate your help and suggestions ...i'm gonna give it a shot after work tonight
was on stock and having the touch issue... switched to flash kernel and all is well
dadoc04 said:
was on stock and having the touch issue... switched to flash kernel and all is well
Click to expand...
Click to collapse
thank you dadoc and also galaxyS for your guys support , really appreciate it !!! Do you notice any improvements using the Flash Kernal compared to stock ?
Mr. Blanco said:
thank you dadoc and also galaxyS for your guys support , really appreciate it !!! Do you notice any improvements using the Flash Kernal compared to stock ?
Click to expand...
Click to collapse
You'll have much more control over your kernel, such as, color control, gestures, memory, governors, schedulers, vibration, and wakelocks :good:
Badger50 said:
You'll have much more control over your kernel, such as, color control, gestures, memory, governors, schedulers, vibration, and wakelocks :good:
Click to expand...
Click to collapse
Thanks Badger .....between the Flash , Electron and ElementalX kernals , do you have a preference ?
Mr. Blanco said:
Thanks Badger .....between the Flash , Electron and ElementalX kernals , do you have a preference ?
Click to expand...
Click to collapse
Flash and Ex have been my 2 favorites for a long time. Flash does a great job keeping it up to date with upstream changes, and Ex has been a solid performer for many years. Can't go wrong with either :good::good:
Badger50 said:
Flash and Ex have been my 2 favorites for a long time. Flash does a great job keeping it up to date with upstream changes, and Ex has been a solid performer for many years. Can't go wrong with either :good::good:
Click to expand...
Click to collapse
agree 100% with what he said... been using flash since the 6p
using adb reboot recovery also works
Badger50 said:
Flash and Ex have been my 2 favorites for a long time. Flash does a great job keeping it up to date with upstream changes, and Ex has been a solid performer for many years. Can't go wrong with either :good::good:
Click to expand...
Click to collapse
Hey Badger i have a question , i'm on stock 8.1 dec patch . and wanted to flash Ex kernal but i've noticed that it and a couple other kernals are on jan patch ... if i flash kernal with new jan patch , will i still be able to revert back to factory image with dec patch ....as that is all that is available for my device presently
Mr. Blanco said:
Hey Badger i have a question , i'm on stock 8.1 dec patch . and wanted to flash Ex kernal but i've noticed that it and a couple other kernals are on jan patch ... if i flash kernal with new jan patch , will i still be able to revert back to factory image with dec patch ....as that is all that is available for my device presently
Click to expand...
Click to collapse
Yeah, no problem. When you flash your factory images, it will overwrite your system and return to stock kernel. Question, what do you mean by "that is all that's available for my device"? There are factory images for the P2XL on Google's site. Why not just upgrade to the January build?
Badger50 said:
Yeah, no problem. When you flash your factory images, it will overwrite your system and return to stock kernel. Question, what do you mean by "that is all that's available for my device"? There are factory images for the P2XL on Google's site. Why not just upgrade to the January build?
Click to expand...
Click to collapse
Thanks Badger . that's what i figured , but wanted to be safe as ive read you can't revert back but i'm assuming that's to the 8.0 os builds. Yeah i was all over it looking for my device build to flash the jan build but it's only showing the dec build for mine on the developers google site 8.1.0 (OPM2.171019.012, Dec 2017, Telus Only)
Mr. Blanco said:
Thanks Badger . that's what i figured , but wanted to be safe as ive read you can't revert back but i'm assuming that's to the 8.0 os builds. Yeah i was all over it looking for my device build to flash the jan build but it's only showing the dec build for mine on the developers google site 8.1.0 (OPM2.171019.012, Dec 2017, Telus Only)
Click to expand...
Click to collapse
im pretty sure you can use the version (OPM1.171019.013, Jan 2018)
as you see, there isn't a Telus only build for every single release.
Hopefully someone who is more familiar will chime in and give you some assurance
dadoc04 said:
im pretty sure you can use the version (OPM1.171019.013, Jan 2018)
as you see, there isn't a Telus only build for every single release.
Hopefully someone who is more familiar with chime in and give you some assurance
Click to expand...
Click to collapse
I was kind of wondering that myself as i've noticed that too about the available builds , never the less i really appreciate your help bro
Hi,
I am using Pixel2 and had same touch issue with TWRP and got a fix from other forum (Thanks to Google)
Before rebooting into recovery disable Ambient display in settings screen.
Settings -> Battery -> Ambient display >> Switch off Always On
Now try to reboot into TWRP and it should work.
If its still not working try with disabling all options under Ambient display option.
Thank You
tiniwings said:
Hi,
I am using Pixel2 and had same touch issue with TWRP and got a fix from other forum (Thanks to Google)
Before rebooting into recovery disable Ambient display in settings screen.
Settings -> Battery -> Ambient display >> Switch off Always On
Now try to reboot into TWRP and it should work.
If its still not working try with disabling all options under Ambient display option.
Thank You
Click to expand...
Click to collapse
Tried this solution doesnt work on my pixel 2
6alaal said:
Tried this solution doesnt work on my pixel 2
Click to expand...
Click to collapse
I know the P2 is a little different than the P2XL, but, have you tried disabling screen lock security and then fastbooting into twrp?
Badger50 said:
I know the P2 is a little different than the P2XL, but, have you tried disabling screen lock security and then fastbooting into twrp?
Click to expand...
Click to collapse
Yeah it's really weird all this happened lost my root after installing the screen fix module in magisk sorry I'm using the P2XL
Hello Everyone
Since I haven't flashed any custom ROM on my device in a while (I didn't like Pie much), and I am pretty bored with OOS 5.0.8 now, I would like to roll back to Nougat OOS 4.5.1 build. I've heard from multiple sources that Nougat has much better battery life and usual UI is more fluid that Oreo ROMs. Also, a user has intrigued me by saying that games in general perform much better than oreo builds.
So, I would like to give it a shot. But, I've found out so far that it isn't as easy as flashing the OOS build on top of 5.0.8. Many websites claim that I need to flash some special nougat build that will downgrade me to nougat and then I can flash OOS 4.5.1.
So, if anyone has rolled back from 5.0.8 or 5.0.7 to Nougat before, can you please guide me through the process?
abhibnl said:
Hello Everyone
Since I haven't flashed any custom ROM on my device in a while (I didn't like Pie much), and I am pretty bored with OOS 5.0.8 now, I would like to roll back to Nougat OOS 4.5.1 build. I've heard from multiple sources that Nougat has much better battery life and usual UI is more fluid that Oreo ROMs. Also, a user has intrigued me by saying that games in general perform much better than oreo builds.
So, I would like to give it a shot. But, I've found out so far that it isn't as easy as flashing the OOS build on top of 5.0.8. Many websites claim that I need to flash some special nougat build that will downgrade me to nougat and then I can flash OOS 4.5.1.
So, if anyone has rolled back from 5.0.8 or 5.0.7 to Nougat before, can you please guide me through the process?
Click to expand...
Click to collapse
Use this https://forums.oneplus.com/threads/guide-how-to-go-from-oreo-to-stock-nougat.661713/
That's the guide I also have gone through which advised to download the special build. Now the issue is that special build link is not working anymore. That's why I can't proceed with that one
abhibnl said:
That's the guide I also have gone through which advised to download the special build. Now the issue is that special build link is not working anymore. That's why I can't proceed with that one
Click to expand...
Click to collapse
https://downloadmirror.co/Waa/O2N_OBT_15811_OXYGEN_SIGN_wipe.zip
This is a link for an op3 build found on the last page of that link i gave you
v.konvict said:
https://downloadmirror.co/Waa/O2N_OBT_15811_OXYGEN_SIGN_wipe.zip
This is a link for an op3 build found on the last page of that link i gave you
Click to expand...
Click to collapse
Yeah sorry i was the one who posted that there. I did some digging on google yesterday and found that. The thing is, now i just need to have assurance from someone who did it on 5.0.8
That guide is old af and the original poster don't even have a oneplus 3 to test it.
OP changed few things with latest firmware and i hope it won't mess with my partitions if i flash the special build. This is my primary phone so, want to be sure before I do this procedure
abhibnl said:
Yeah sorry i was the one who posted that there. I did some digging on google yesterday and found that. The thing is, now i just need to have assurance from someone who did it on 5.0.8
That guide is old af and the original poster don't even have a oneplus 3 to test it.
OP changed few things with latest firmware and i hope it won't mess with my partitions if i flash the special build. This is my primary phone so, want to be sure before I do this procedure
Click to expand...
Click to collapse
Why don't u backup your existing data elsewhere and try flashing the nougat build because I am sure there will be quite a few of them who might have rolled back to Nougat.
Jigneshg said:
Why don't u backup your existing data elsewhere and try flashing the nougat build because I am sure there will be quite a few of them who might have rolled back to Nougat.
Click to expand...
Click to collapse
You still didn't read my last post properly. I have no issues if it formats my data partition. I'm concerned about the other partitions. I don't want to corrupt my partition table because of downgrading to a lower and older firmware. That's all my concern is.
Was on Omni 8.1 > then Leaked OOS 9.0 build > Official LOS16 > then downgraded to special Nougat build > and now on OOS 4.5.1 with latest Magisk build & Tolyan's last Gcam 5 (1.015 final fix version) release.
No issues with partitions or modems/firmware.
Only back up your data and internal memory as they will be wiped out.
abdozoon said:
Was on Omni 8.1 > then Leaked OOS 9.0 build > Official LOS16 > then downgraded to special Nougat build > and now on OOS 4.5.1 with latest Magisk build & Tolyan's last Gcam 5 (1.015 final fix version) release.
No issues with partitions or modems/firmware.
Only back up your data and internal memory as they will be wiped out.
Click to expand...
Click to collapse
Thanks! That's all the assurance I needed. I shall try it next weekend when I'll be free to do so.
i bricked my phone last week i finally unbricked with this tool it was so easy all u have to do is click on msm tool exe in folder after extracting and press start and that fixed my device and flash noughat stock rom on device,it will relock bootloader though,just make sure u put device in adb mode though with vol up when conecting to pc,hope that helps was soo easy heres link https://forum.xda-developers.com/oneplus-3/how-to/unbrick-phone-msmdownloadtool-v3-0-6-t3575801