{
"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.
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.
What's not working :
IMS
Instructions :
Download the latest build and gapps
Boot to recovery
Flash the latest build
Boot to recovery again
Flash gapps
Reboot
Downloads :
Builds : https://download.lineageos.org/pioneer
Root addon : https://download.lineageos.org/extras
Google Apps : https://wiki.lineageos.org/gapps.html
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 /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (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][pioneer][8.1] LineageOS 15.1, ROM for the Sony Xperia XA2
Contributors
LuK1337
Source Code: https://github.com/LineageOS
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Created 2018-06-19
Last Updated 2019-11-01
How to flash latest firmware
[ protip: Currently Lineage builds depend on latest 8.0 firmware (50.1.A.13.123), they will not boot up on 50.2.A.0.* or newer ]
1. Download latest firmware with XperiFirm.
NOTE: When using mono XperiFirm will fail to unpack the firmware, you can do it manually using following commands:
Code:
for f in FILE_*; do unzip $f; done
unzip boot.zip -d boot
2. Go to the directory where the firmware got downloaded to and remove following files:
- kernel_X-FLASH-ALL-18AE_0x00.hash
- kernel_X-FLASH-ALL-18AE.sin
- persist_X-FLASH-ALL-18AE_0x00.hash
- persist_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-18AE_0x00.hash
- system_other_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-9B8D_0x00.hash
- system_X-FLASH-ALL-18AE_0x00.hash
- system_X-FLASH-ALL-18AE.sin
- system_X-FLASH-ALL-9B8D_0x00.hash
- userdata_X-FLASH-CUST-18AE.sin
- vendor_X-FLASH-ALL-18AE_0x00.hash
- vendor_X-FLASH-ALL-18AE.sin
- vendor_X-FLASH-ALL-9B8D_0x00.hash
3. Turn off your phone, hold vol dn and plug in the USB cable, the screen should be off and green LED lit.
4. Run Newflasher, it'll flash entire FW to your current slot then unplug the USB cable and power on your phone.
5. Turn off your phone, hold vol up and plug in the USB cable, the screen should be off and blue LED lit.
6. Enter this command: `fastboot getvar current-slot`, it should return something like this:
current-slot: _b
Finished. Total time: 0.001s
7. Now switch to the opposite slot by entering command: `fastboot set_active a` if the current slot is `_b` or `fastboot set_active b` if its `_a`, you should see this:
Setting current slot to 'a'...
OKAY [ 0.012s]
Finished. Total time: 0.014s
or
Setting current slot to 'b'...
OKAY [ 0.012s]
Finished. Total time: 0.014s
8. Unplug usb cable and repeat steps: 3, 4
9. Profit?
can't test right now but one question. it doesn't really matter at this stage but is it treble compatible? as you know stock rom is but it won't boot anything else
EDIT: what about vendor blobs? are they from stock rom or aosp? camera hal?
frantisheq said:
can't test right now but one question. it doesn't really matter at this stage but is it treble compatible? as you know stock rom is but it won't boot anything else
EDIT: what about vendor blobs? are they from stock rom or aosp? camera hal?
Click to expand...
Click to collapse
All blobs are from stock ROM and it's somewhat treble compatible (I could probably make it better by getting rid of /init extensions but eh).
What's performance and battery life versus the stock rom?
teardropcity said:
What's performance and battery life versus the stock rom?
Click to expand...
Click to collapse
I don't know; I never used that phone as my daily driver to begin with, nor did I ever run any benchmark on stock, SOD or Lineage.
Happy to see development for this device. I don't have a spare phone at the moment so I will flash this once it becomes a bit more stable. Also could you comment on dual sim support. Mine is the H4133 (Hong Kong Version), hopefully there shouldn't be any major hiccups getting it to work. Thanks for porting LOS
TRONTC said:
Happy to see development for this device. I don't have a spare phone at the moment so I will flash this once it becomes a bit more stable. Also could you comment on dual sim support. Mine is the H4133 (Hong Kong Version), hopefully there shouldn't be any major hiccups getting it to work. Thanks for porting LOS
Click to expand...
Click to collapse
>I will flash this once it becomes a bit more stable.
So never? I don't expect anything interesting happening with this device anytime soon so you're basically waiting for ~nothing~.
>Also could you comment on dual sim support.
Minimal support is there but it's untested as I only have single sim variant.
Does this work on Discovery the same way pioneer TWRP works on Discovery, or probably not?
Also, has Xposed been tested with this ROM?
li0nh3art3d said:
Does this work on Discovery the same way pioneer TWRP works on Discovery, or probably not?
Also, has Xposed been tested with this ROM?
Click to expand...
Click to collapse
No, this build does not support discovery. It has a chance to boot on it but you won't have camera.
( There are untested trees in nile-dev @ gitlab if you want to build it on your own )
***
frantisheq said:
if there's anyone interested i've set up jenkins on http://frantisheq.ml:8080
new builds will be available on basketbuild https://basketbuild.com/devs/frantisheq
Sent from my H4113 using Tapatalk
Click to expand...
Click to collapse
Can't say I really like hijacking my thread like this but I hope that you'll actually contribute in some more reasonable way later on.
sorry, i really didn't mean to. i did it for myself and it wasn't worth creating new thread but i wanted to share. my mistake, i don't plan to make this support thread for my builds
I wonder if this ROM works on H3123. Thanks.
jimzhong said:
I wonder if this ROM works on H3123. Thanks.
Click to expand...
Click to collapse
H3123 is a single sim pioneer, so I'd imagine it works fine.
li0nh3art3d said:
H3123 is a single sim pioneer, so I'd imagine it works fine.
Click to expand...
Click to collapse
Several months ago I compiled AOSP for my device according to instructions on the Sony Open Devices website. The system could boot, but I could not change the volume during calls. I think H3123 and H3113 has different modems.
jimzhong said:
Several months ago I compiled AOSP for my device according to instructions on the Sony Open Devices website. The system could boot, but I could not change the volume during calls. I think H3123 and H3113 has different modems.
Click to expand...
Click to collapse
>but I could not change the volume during calls
That was an issue for all XA2 and XA2 Ultra devices on SOD, it had nothing to do with modem FYI.
Just out of curiosity, anyone that flashed this ROM can you tell me what fingerprint sensor you have and if it works?
To check that you do `getprop ro.hardware.fingerprint` in adb shell or any terminal app. The output you should get is either "et516" or "fpc1035".
LuK1337 said:
Just out of curiosity, anyone that flashed this ROM can you tell me what fingerprint sensor you have and if it works?
To check that you do `getprop ro.hardware.fingerprint` in adb shell or any terminal app. The output you should get is either "et516" or "fpc1035".
Click to expand...
Click to collapse
Hey man, thanks for the build and your hard work my device runs like butter compared to stock. Thank you so much amigo. fcp1035 on device h3123 fingerprint not working at the moment. Also no clock or music controls on lock screen. though, I don't know if that's just how lineage 15.1 is.
RRRex said:
Hey man, thanks for the build and your hard work my device runs like butter compared to stock. Thank you so much amigo. fcp1035 on device h3123 fingerprint not working at the moment. Also no clock or music controls on lock screen. though, I don't know if that's just how lineage 15.1 is.
Click to expand...
Click to collapse
>fcp1035 on device h3123 fingerprint not working at the moment.
Can you add me on hangouts ([email protected]) / irc (#titandev @ freenode) / discord (LuK1337#3147)?
>Also no clock or music controls on lock screen. though, I don't know if that's just how lineage 15.1 is.
Uh, did you wipe data? That's just strange.
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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 9.0 (Pie), 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.
What's working :
Boots
RIL (Calls, SMS, Data)
Bluetooth
Dual-SIM
Wi-Fi
Camera
Video Recording
Video Playback
Audio ( Record and Playback )
Sensors
Flash
Led
Offline Charging
SELinux Enforcing
What's not working :
You tell me
Instructions :
Download the latest build and gapps
Reboot to recovery
Flash the latest build and gapps
Reboot
Downloads :
Builds : https://androidfilehost.com/?fid=1395089523397948075
Gdrive mirror - https://drive.google.com/file/d/1byxYWMV35fx-qQ_80qRoZLqFpnzN28oA/view?usp=drivesdk
Root addon : https://download.lineageos.org/extras (available for Lineage 16.0, use Magisk 18 or newer instead!)
Google Apps : http://opengapps.org/
Reporting Bugs
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--
Phone model:
Lineage version:
Lineage 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:
LineageSettings/Performance settings (other than stock):
Dual SIM:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Credits :
@Luk1337
@luca020400
@Somcom3X
@kaustubh88 and @crpalmer
@Thecrazyskull
@Carlos Arriaga
@RenanQueiroz
Motorola : For providing the Kernel Source Code
LineageOS Team
Kyle Harrison for his work on osprey
Contributors
anisgvr
chil360
NOTE:
Thanks a lot and lot to chil360 ( Kyle Harrison ) for his work in osprey . He helped a lot in bringing up pie for the device. Whole credits goes to him .
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Based On: AOSP
Version Information
Status: Stable , daily driver material
Created 2018-08-28
Last Updated 2019-04-20
Reserved
Screenshots
anisgvr said:
Screenshots
Click to expand...
Click to collapse
See charging speed in screenshots
Seems like you are on a roll with custom roms for osprey, @anisgvr. . Thanks for keeping osprey alive with your work:good:good:. Any plans to make the LOS build official?
superman234 said:
Seems like you are on a roll with custom roms for osprey, @anisgvr. . Thanks for keeping osprey alive with your work:good:good:. Any plans to make the LOS build official?
Click to expand...
Click to collapse
No one in community can make los official As of now because los needs the guy who brought up tree ... unfortunately Alberto97 is no longer developing for osprey.. and we have to wait some magic from sultan Qasim Khan (squid)
I don't understand. Could @squid2 or @Alberto97 or you explain that? This looks like a perfect good rom for official, I asume that you would be willing to carry on the torch but in the end we can't have a perfectly good phone?
Can it be dirty flashed over LineageOS 15.1?
Planning buy this phone as secondary phone, when i saw the development i went happy. Thx for keeping this phone alive!!
Error with wifi connection: buffer space
Hi,
I do not have yet logcat or anything like that. Will try to get some data if that could give more clue.
Flashed that software yesterday - added gapps and su from lineageos.
All looked very nice, but then I got wifi connected but no internet message. Only on that device, so no issues with my home network as first check.
So I used dirty hack with adding settings as suggested:
https://android.stackexchange.com/q...cted-no-internet-but-internet-works-just-fine
but it did not help - so my problem was not detection of internet - but connection on device itself.
In Brave browser the message was like ERR_NO_BUFFER_SPACE.
Restart helped. For a time like few hours.
Now my detection settings are indeed disabled but real problem shows up.
I found some topic on lenovo forum about G5 - close enough - but no real conclusion - for some update helped, some requested phone replacement, and so on. No real root cause explanation.
My plan is to restore back to previous 16 version or even further back to 14.1..
Before going that routine - anyone encountered something like that? Any ideas?
Restart helps, so maybe it is indeed some temp space filling out. Next time I can try to get more from adb - netstat?
Regards
Jan
I installed the PIE Lineage OS a few days ago on my Moto G3 x1541.I've not had one single problem.Fantastic rom.Best yet and the Lineage team have outdone themselves.
Build number Lineage_osprey-userdebug 9PQ2A
190305.002 eng.ubuntu.20190313.090534 test keys
Tip:Before I install any custom rom I do a Hard Reset/Factory reset.
Then once I've installed the rom I let it boot to normal phone mode(Can take quite a while) then reboot to Recovery and do another Hard Reset before setting up my phones.
Also I make Nandroid backups of my Setup Stock rom before installing any Custom roms then I can be up-and-running very quickly.Once I've setup my phone with a Custom rom I again make a Nanroid backup for fast reloading if required.
spljaa said:
Hi,
In Brave browser the message was like ERR_NO_BUFFER_SPACE.
Restart helped. For a time like few hours.
Click to expand...
Click to collapse
Now I was able to observe it via adb. Attaching logcat part. There is successful check, and then failed.
What is odd, DNS and ping like commands do work. It is HTTP calls that fail.
But I had no clue what shortage can be observed on resources.
That socket error in logcat might be something.
I'm quite confident that I run some wipe while installing ROM. But maybe I need to do it over again.
frogzz said:
Can it be dirty flashed over LineageOS 15.1?
Click to expand...
Click to collapse
Clean flash needed to avoid bugs
TWRP treble
https://drive.google.com/file/d/1JJ8bUBSHy5kLBqy3cX-hIAfoijdWKIK5/view?usp=drivesdk
here are almost all rom Osprey
https://androidfilehost.com/?w=search&s=Osprey&type=files
rom extended 6.4
https://builds.aospextended.com/osprey/
I have TWRP 3.2.3.0
Do I need the latest version of TWRP to use this ROM?
Thank you :3
nzkn said:
I have TWRP 3.2.3.0
Do I need the latest version of TWRP to use this ROM?
Thank you :3
Click to expand...
Click to collapse
Use latest
anisgvr said:
Use latest
Click to expand...
Click to collapse
Thanks, but I used the version that I had anyway and it worked without problems.
It is, as people said, a very good ROM. It could perfectly be official. I did not experience any problems at all.
(I did a factory reset before flashing the rom though. normal procedure, as I understand)
Tested:
>Camera: It works. Both photos and videos
>Screen Recording: It works
>Games: I do not play. Emulators work.
>Applications with real-time filters (eg SNOW): They work as expected.
>Netflix works
>Wi-fi and Mobile Data: They work, although in standby, and with Wi-fi, Data uses a lot of battery.
>VOLTE: Not available in my country, sorry
>Battery: It works much better than expected, but it's not magic. It works excellent because it kills applications in the background very aggressively. I did not see battery drains (and my phone is quite old).
Problems:
>Instagram, although it works well, does not show stickers, and neither those weird video recording modes that includes. And boomerang crash the app.
>The way it kills applications in the background is extremely aggressive by default. The first day I did not receive notifications until I opened those apps. I had to go to Battery settings, disable Battery Manager, and Optiization of battery in applications that I did not want it to kill.
This, if I'm not mistaken, is a general problem of Android Pie though
Tested on my Moto G3 8GB / 1GB ram variant.
Thanks for this marvelous 420 rom!
spljaa said:
Now I was able to observe it via adb. Attaching logcat part. There is successful check, and then failed.
What is odd, DNS and ping like commands do work. It is HTTP calls that fail.
But I had no clue what shortage can be observed on resources.
That socket error in logcat might be something.
Click to expand...
Click to collapse
As I saw some odd failed calls for some class with facebook in name I decided to remove one game: "Word Of Words". Plus removed AdAway. As other candidate for creating connections.
And so far so good. It might change, but based on above I'm thinking that even if OS could handle that better - the cause was in software I installed.
Regards
Jan
Does this rom have a separate vendor partition? What's the difference with althafvly's LineageOS 16.0 rom (also based on chil360's trees)?
does encryption work?
{
"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/pioneer
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][pioneer][10] LineageOS 17.1, ROM for the Sony Xperia XA2
Contributors
LuK1337
Source Code: https://github.com/LineageOS
ROM OS Version: Windows 8 Mobile
Version Information
Status: Testing
Created 2019-10-08
Last Updated 2020-04-01
[ protip: 20191010+ builds require 50.2 FW (at least bluetooth, dsp, modem from it) If you're still running 50.1 you can flash this package in TWRP: https://androidfilehost.com/?fid=4349826312261716572 unless you're fine with having partially broken audio and broken Egistec fingerprint sensor ;3 ]
However if you want to flash whole firmware package onto both slots, you can follow the guide below:
1. Download latest firmware with XperiFirm.
NOTE: When using mono XperiFirm will fail to unpack the firmware, you can do it manually using following commands:
Code:
for f in FILE_*; do unzip $f; done
unzip boot.zip -d boot
2. Go to the directory where the firmware got downloaded to and remove following files:
- boot_X-FLASH-ALL-18AE_0x00.hash
- boot_X-FLASH-ALL-18AE.sin
- persist_X-FLASH-ALL-18AE_0x00.hash
- persist_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-18AE_0x00.hash
- system_other_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-9B8D_0x00.hash
- system_X-FLASH-ALL-18AE_0x00.hash
- system_X-FLASH-ALL-18AE.sin
- system_X-FLASH-ALL-9B8D_0x00.hash
- userdata_X-FLASH-CUST-18AE.sin
- vendor_X-FLASH-ALL-18AE_0x00.hash
- vendor_X-FLASH-ALL-18AE.sin
- vendor_X-FLASH-ALL-9B8D_0x00.hash
3. Turn off your phone, hold vol dn and plug in the USB cable, the screen should be off and green LED lit.
4. Run Newflasher, it'll flash entire FW to your current slot then unplug the USB cable and power on your phone.
5. Reboot to recovery mode (both Lineage recovery and TWRP will work)
6. Flash https://androidfilehost.com/?fid=4349826312261712574
7. Profit?
first off, thanks a lot for your work and for sharing it with us, amazing!
i've installed the second build (lineage-17.0-20191008_192747-UNOFFICIAL-pioneer.zip), with magisk 19.4 and opengapps beta and it works like a charm!
although, i had to do some of the steps from the los16 procedure (like flashing pie .400 firmware on both slots and reboots between los, magisk and gapps flashing) since i've had oreo firmware.
for now, as for the little time spend on the build, it works great. the one thing i've noticed is that the fingerprint sensor is not working.
however, great bulid and thanks again!
olivrd said:
first off, thanks a lot for your work and for sharing it with us, amazing!
i've installed the second build (lineage-17.0-20191008_192747-UNOFFICIAL-pioneer.zip), with magisk 19.4 and opengapps beta and it works like a charm!
although, i had to do some of the steps from the los16 procedure (like flashing pie .400 firmware on both slots and reboots between los, magisk and gapps flashing) since i've had oreo firmware.
for now, as for the little time spend on the build, it works great. the one thing i've noticed is that the fingerprint sensor is not working.
however, great bulid and thanks again!
Click to expand...
Click to collapse
You just be on 50.1 if FP isn't working or you're using fpc10xx? Either way what does the baseband version say?
Hm it may be magisk too. I need to try that crap.
LuK1337 said:
You just be on 50.1 if FP isn't working or you're using fpc10xx? Either way what does the baseband version say?
Click to expand...
Click to collapse
with 50.1 fw and los16 it was fine. the baseband version now is "20190718_BY12O_Daily"
olivrd said:
with 50.1 fw and los16 it was fine. the baseband version now is "20190718_BY12O_Daily"
Click to expand...
Click to collapse
Yeah, it's probably magisk then. I'll try to do something about it...
Also what does adb shell getprop ro.hardware.fingerprint say?
Actually nvm. If it's fpc1035 then it's my fault, if getprop ro.hardware.fingerprint actually says fpc1035 then add me on Discord or Hangouts cause I'd need you to test it.
So better flash clear 50.2.X.X FW using newflasher in 2 slots and flash lineage?
LuK1337 said:
ROM OS Version: Windows 8 Mobile
Click to expand...
Click to collapse
what
Great work!With 50.2 FW，it just work fine.
iHusky said:
So better flash clear 50.2.X.X FW using newflasher in 2 slots and flash lineage?
Click to expand...
Click to collapse
Do whatever you want. I'm still on 50.1 FW myself, I just flashed bt, dsp, modem from #2
Also if you have fpc1035, you may as well wait like 20 mins for next build.
LuK1337 said:
Do whatever you want. I'm still on 50.1 FW myself, I just flashed bt, dsp, modem from #2
Also if you have fpc1035, you may as well wait like 20 mins for next build.
Click to expand...
Click to collapse
How check it?
iHusky said:
How check it?
Click to expand...
Click to collapse
`cat /proc/cei_fp_id` while in lineage or official <=3.3.1-1 twrp.
f. ****, best deal with this phone... Thanks a lot!
latest build "lineage-17.0-20191009_113230-UNOFFICIAL-pioneer.zip" fixes fingerprint sensor. will report eventual bugs. thx Luk!
I am currently on los16 and would like to help you with testing.
I don't know how to find out which firmware I have, but
cat /proc/cei_fp_id shows et516
and
getprop ro.hardware.fingerprint shows also et516
What can I do to support you?
emc02 said:
I am currently on los16 and would like to help you with testing.
I don't know how to find out which firmware I have, but
cat /proc/cei_fp_id shows et516
and
getprop ro.hardware.fingerprint shows also et516
What can I do to support you?
Click to expand...
Click to collapse
Nothing. fpc1035 is already fixed and et516 is what I have.
Ok, so I am on 50.1?
Can I flash 50.2 like discribed on post 2 with newflasher and then los17 will work without Audio and fingerprint problems?
Is firmware 50.2 compatile with los16?
Or is it like this:
50.1 only on los16
50.2 only on los17
Thanks for your development!
emc02 said:
Ok, so I am on 50.1?
Can I flash 50.2 like discribed on post 2 with newflasher and then los17 will work without Audio and fingerprint problems?
Is firmware 50.2 compatile with los16?
Or is it like this:
50.1 only on los16
50.2 only on los17
Thanks for your development!
Click to expand...
Click to collapse
50.2 for both now. Also you don't really need to flash whole 50.2 FW, you can just flash the zip linked in #2.
LuK1337 said:
50.2 for both now. Also you don't really need to flash whole 50.2 FW, you can just flash the zip linked in #2.
Click to expand...
Click to collapse
can I flash the FW Updates without doing full wipe and reflashing system (staying on los16), or is this not recommended?
emc02 said:
can I flash the FW Updates without doing full wipe and reflashing system (staying on los16), or is this not recommended?
Click to expand...
Click to collapse
Why are you asking this in 17.0 thread?
If you're on 16.0 then just OTA to next available build then boot TWRP and flash FW zip.
{
"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 11, 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 :
https://wiki.lineageos.org/devices/instantnoodlep
Downloads :
https://download.lineageos.org/instantnoodlep
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:
Anyone up and running yet?
Canti Firestarter said:
Anyone up and running yet?
Click to expand...
Click to collapse
Just flashed. Roms fast as hell out the gate. I wasn't prompted to restore my apps on a fresh install but not a huge deal to me.
Wickidmasshole said:
Just flashed. Roms fast as hell out the gate. I wasn't prompted to restore my apps on a fresh install but not a huge deal to me.
Click to expand...
Click to collapse
Any trouble with Wfd not working?
Canti Firestarter said:
Any trouble with Wfd not working?
Click to expand...
Click to collapse
I feel stupid for not knowing what WFD is lol
LuK1337 said:
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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.
What's not working :
WFD
Instructions :
Download the latest build
$ adb reboot bootloader
$ fastboot -w (this will wipe your data)
$ fastboot flash recovery recovery.img
$ fastboot reboot fastboot
$ fastboot erase scratch
$ fastboot flash boot boot.img
$ fastboot flash dtbo dtbo.img
$ fastboot flash system system.img
$ fastboot flash system_ext system_ext.img
$ fastboot flash product product.img
$ fastboot flash vbmeta vbmeta.img
$ fastboot flash vbmeta_system vbmeta_system.img
$ fastboot reboot
Downloads :
Builds :
https://www.androidfilehost.com/?w=files&flid=318026
http://downloads.codefi.re/jdcteam/luk/lineage-18_0/instantnoodlep
https://sourceforge.net/projects/luk-lineageos/files/instantnoodlep/lineage-18.0
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][UNOFFICIAL][instantnoodlep][11] LineageOS 18.0, ROM for the OnePlus 8 Pro
Contributors
LuK1337
Source Code: https://github.com/luk1337
ROM OS Version: Windows 8 Mobile
Version Information
Status: Testing
Created 2020-11-20
Last Updated 2020-11-20
Click to expand...
Click to collapse
is there an easier way to flash this? having to flash like 20 files just to test a ROM can put a lot of any users off. being able to flash as just one single wrong would be so welcoming and amazing. making it a nice easy experience for flashing will create such a stronger and more populated user base.
Burt Squirtz said:
is there an easier way to flash this? having to flash like 20 files just to test a ROM can put a lot of any users off. being able to flash as just one single wrong would be so welcoming and amazing. making it a nice easy experience for flashing will create such a stronger and more populated user base.
Click to expand...
Click to collapse
well that's kind of tough to do when there isn't a working TWRP for A11 yet......
Just open up a command shell in the unzipped folder and copy and paste line for line from OP. Took like 5 mins at best
Burt Squirtz said:
is there an easier way to flash this? having to flash like 20 files just to test a ROM can put a lot of any users off. being able to flash as just one single wrong would be so welcoming and amazing. making it a nice easy experience for flashing will create such a stronger and more populated user base.
Click to expand...
Click to collapse
Yes? https://toolaio.tk/download/
Wickidmasshole said:
Just flashed. Roms fast as hell out the gate. I wasn't prompted to restore my apps on a fresh install but not a huge deal to me.
Click to expand...
Click to collapse
Does it support changing resolutions and refresh rates?
Yashmishra said:
Does it support changing resolutions and refresh rates?
Click to expand...
Click to collapse
Not seeing either of those options yet
Wickidmasshole said:
I feel stupid for not knowing what WFD is lol
Click to expand...
Click to collapse
Ever figure out what WFD is? Google says... WiFi direct - which is a feature I could care less about.
I am on oos11 do i ned to go back to oos11 to flash this?
MariusKv said:
I am on oos11 do i ned to go back to oos11 to flash this?
Click to expand...
Click to collapse
You are on oos11 and you want to go back to oos 11??
cultofluna said:
You are on oos11 and you want to go back to oos 11??
Click to expand...
Click to collapse
opps i oos10
do i need to go back to oos10 hehe
MariusKv said:
opps i oos10
do i need to go back to oos10 hehe
Click to expand...
Click to collapse
No
cultofluna said:
No
Click to expand...
Click to collapse
Ok tnx
Does this recovey work to sideload magisk?
tryed to sideload magisk got qualcom crashdump heh
MariusKv said:
Ok tnx
Does this recovey work to sideload magisk?
tryed to sideload magisk got qualcom crashdump heh
Click to expand...
Click to collapse
What recovery are you talking about? This is LOS, it's a custom ROM lol
Pappilo said:
What recovery are you talking about? This is LOS, it's a custom ROM lol
Click to expand...
Click to collapse
I used los recovery. Sideloaded magisk booted inn to crashdump
Nice
MariusKv said:
I used los recovery. Sideloaded magisk booted inn to crashdump
Click to expand...
Click to collapse
I'm not on LOS atm but you can use payload dumper and flash Magisk that way. There are guides in the forums
{
"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 12, 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:
Follow the instructions on the wiki page of your device https://wiki.lineageos.org/devices/#samsung
Note: You may use Odin instead of Heimdall, for this you will need to rename the recovery image to recovery.img and pack it into a tar archive.
Downloads:
Builds: https://download.lineageos.org
Firmware:
gta4xlwifi: https://lineage.linux4.de/fw_update/gta4xlwifi.html
gta4xl: https://lineage.linux4.de/fw_update/gta4xl.html
GApps: https://wiki.lineageos.org/gapps.html
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:
Support
Telegram group
Contributors
Linux4, haggertk, programminghoch10
Source Code: https://github.com/LineageOS
Kernel source: https://github.com/LineageOS/android_kernel_samsung_gta4xl
reserved
reserved
You are the best. Really appreciate your efforts.
Thank you so much!
Upgrading the Samsung Firmware Without Losing Your Data, Apps & Settings
Thanks for supporting this device & others @Linux4.
Linux4 said:
...Follow the instructions on the wiki page of your device...
Click to expand...
Click to collapse
In both wiki pages Installation and Upgrade to a higher version of LineageOS (e.g. lineage-18.1 -> lineage-19.1) it says in a red box:
WARNING: Before following these instructions please ensure that the device is currently using Android 12 firmware.
Click to expand...
Click to collapse
And you created a convenient custom Samsung Android 12 firmware package that one can use without losing Data, apps & settings: Update Firmware on Samsung Galaxy Tab S6 Lite (Wi-Fi) (gta4xlwifi)
It's also a much smaller download than the full Samsung OS.
Why not include a link to it in the OP of this thread?
For example haggertk did that for the Galaxy S5 klte* family:
haggertk said:
Downloads:
Lineage - https://download.lineageos.org/
Firmware - https://www.androidfilehost.com/?w=files&flid=325192
Click to expand...
Click to collapse
***
curiousrom said:
Upgrading the Samsung Firmware Without Losing Your Data, Apps & Settings
Why not include a link to it in the OP of this thread?
Click to expand...
Click to collapse
Done, thanks for the suggestion
Cool, thanks for all your work Linux4!
- Am I correct that you need to flash the firmware, lineage 19.1, gapps 12 arm 64 in one session before booting for the first time in order to not have to factory reset?
- Does one have to flash firmware before first boot in heimdall, then lineage (via adb), then gapps (via adb)?
- can the android 12 firmware be kept when downgrading back to lineage 18/ can I flash it and use it with lineage 18 before installing lineage 19?
SvenHee said:
Cool, thanks for all your work Linux4!
- Am I correct that you need to flash the firmware, lineage 19.1, gapps 12 arm 64 in one session before booting for the first time in order to not have to factory reset?
- Does one have to flash firmware before first boot in heimdall, then lineage (via adb), then gapps (via adb)?
- can the android 12 firmware be kept when downgrading back to lineage 18/ can I flash it and use it with lineage 18 before installing lineage 19?
Click to expand...
Click to collapse
I'm not Linux4, but I'll still try to answer.
1. Yes, you flash the firmware and all those in one session via Lineage recovery and then you restart
2. You have to use heimdall first, then flash recovery with it and then flash lineage and gapps with adb
3. Don't know
Also sorry if something is incorrect, I'm new to the ROM world and I just flashed Lineage today and this is what I did
- sheep
hey....why there is no lineage os 19.1 for lte version?
And Is it okay to flash linux4's link in my tab s6 lite lte which runs on oneui4.1?
I need to flash my tab before leaving for collge...please reply
lol69 96 said:
hey....why there is no lineage os 19.1 for lte version?
And Is it okay to flash linux4's link in my tab s6 lite lte which runs on oneui4.1?
I need to flash my tab before leaving for collge...please reply
Click to expand...
Click to collapse
DO IT YOUR OWN RISK.
Truelan said:
DO IT YOUR OWN RISK.
Click to expand...
Click to collapse
Yea Ik the risks.I guess it's an upgrade rather than downgrade but problem is it will have lower security patch.Will it pose any risk?
@devs Ty for your work! I just flashed firmware and upgraded from los 18.1 to last nightly (lineage-19.1-20220511-nightly-gta4xlwifi-signed.zip).
I just want to report a minor bug: Mostly (not always) I can't add an installed app (drag and drop) to the screen.
Thanks for the work!
Now that LOS 19 has official support, can I expect the S Pen issues to be resolved?
Last time I installed an unofficial port of the ROM there were some major issues around responsiveness and lag when using the S Pen and it is critical to me (student).
Hi, how to root this rom?
Nevermind, just sideload magisk from adb. Anyway, the rom is great, the pen is working well. I confirm the bug that you can't drag app on the homescreen. Also, I'm facing a weird bug: when I lock the screen through the power button, sometimes the tablet stops responding, pressing the power button does nothing and the screen stays black, I have to force restart with power + volume down
P615. Recovery flashed by Odin and next sideload with ROM, Gapps, Lygisk. Work fine since flash. Zero reboots, crashes, etc.
Bug report
LineageOS version: lineage-19.1-20220525-nightly-gta4xlwifi-signed
LineageOS Download url: https://mirrorbits.lineageos.org/fu...e-19.1-20220525-nightly-gta4xlwifi-signed.zip
Gapps version: not installed
The bug appears after a fresh clean installation. I've installed the required firmware before the update.
I've rebooted after I've first seen the issue.
Modifications: none, it's pure LOS installation without anything else
Here's what happens:
I'm german and therefore sometimes I write in german, sometimes in english. I like to switch my keyboard according to the language I'm using.
With two keyboard languages activated in settings, I cannot get off the lock screen, because the keyboard doesn't appear and it looks weird over all.
I've recorded the screen right after a completely fresh installation and after finishing the setup wizard. First I switch to the lock screen, which I get out of with my password. Then after activating the second language, I cannot get out of the lock screen anymore.
I normally have another setup. I normally use the microG version and have Lygisk installed. But I'll keep my tablet in the current state for the next 2, maybe 3 days to be able to give more information if required.
Same keyboard issue here, when switching to digits --> blank screen.
Another thing. The installation is the same as in my bug report from yesterday.
I've started testing a few things. I use ACCA from the Fdroid repos for battery management. In LineageOS 18.1 the kernel supported battery idle mode, now with LOS 19 it looks like this isn't supported anymore.
Would you please implement this again? It's really helpful for a good battery management so it doesn't charge up to 100%.
New update for LTE version from 28th may.
{
"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 12, 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 :
https://wiki.lineageos.org/devices/kebab
Downloads :
https://download.lineageos.org/kebab
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 /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (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:
Thank you for making this. Lineageos's been a blessing ever since the oxygenos became what it is now.
I want to migrate from another rom and wanted to ask if lineageos 19 uses oos12 or oos11 firmware.
Artifter said:
Thank you for making this. Lineageos's been a blessing ever since the oxygenos became what it is now.
I want to migrate from another rom and wanted to ask if lineageos 19 uses oos12 or oos11 firmware.
Click to expand...
Click to collapse
I believe you can find the answer for that in the installation instructions.
Thank you very much for your effort!
I would like to pose a question, although it's not specifically related to LOS 19, is there a way to bypass SafetyNet without rooting the phone? I've always found very irritating to have this kind of problems with some apps, when the turth is one can expect a better longlife service with LOS than with the official OS. Yes, I know it doesn't have to do with LOS but it would be the cherry on top of the cake.
Hello, can i use twrp instead of LOS recovery or is mandatory? Just wondering, thank you.
Thank you for the update !
Sry am now on Android 13 Evolution X
Unfortunately the update does not work on my device. Entering the new recovery build just ends up in a blank screen and booting the ROM enters the crash dump mode. Updating the device firmware to the latest state did not help either.
Reverted back to the other slot without any issue, so no harm was done.
@Draylin Did you follow these steps https://wiki.lineageos.org/devices/kebab/fw_update before installation of LinageOS 12.1?
Do i have DDR4 or DDR5?
Code:
D:\adb>adb shell getprop ro.boot.ddr_type
1
D:\adb>adb shell cat /proc/devinfo/ddr_type
cat: /proc/devinfo/ddr_type: No such file or directory
D:\adb>
edit:
found: 0 for LPDDR4X RAM and 1 for LPDDR5 RAM
right?
exthomeboy said:
Sry am now on Android 13 Evolution X
Click to expand...
Click to collapse
don't care didn't ask
Draylin said:
Unfortunately the update does not work on my device. Entering the new recovery build just ends up in a blank screen and booting the ROM enters the crash dump mode. Updating the device firmware to the latest state did not help either.
Reverted back to the other slot without any issue, so no harm was done.
Click to expand...
Click to collapse
You can also try to flash dtbo, https://mirrorbits.lineageos.org/full/kebab/20220825/dtbo.img. B-but if new recovery boots then you'll want to flash FW to both slots instead of just one.
I added flashing dtbo to wiki, not like it's going to hurt anyway.
If you follow all the step-by-step instructions (https://wiki.lineageos.org/devices/kebab/upgrade), the upgrade process works perfectly.
Many thanks to LuK1337 and the whole Lineage team for their work.
I am doing a complete reset and can't make it boot to lineageos19 at all.
Steps:
1 - Flash dbto
2 - Flash recovery.18.1
3 - Sideload lineageos 19
4 - Reboot to recovery again to install MindGapps
5 - Blank, I can't go again to the recovery screen at all
back2live said:
@Draylin Did you follow these steps https://wiki.lineageos.org/devices/kebab/fw_update before installation of LinageOS 12.1?
Click to expand...
Click to collapse
Yes, I followed these steps.
@LuK1337 Thank you for your response. I flashed the linked dtbo to the new slot, but this did not help. Since it seems to be working fine for others, I think the error must be somwhere on my side.
Draylin said:
Yes, I followed these steps.
@LuK1337 Thank you for your response. I flashed the linked dtbo to the new slot, but this did not help. Since it seems to be working fine for others, I think the error must be somwhere on my side.
Click to expand...
Click to collapse
I had the same problem, but forgot flash the vendor data before.
I am now installing lineageos18 again and try to upgrade.
Draylin said:
Yes, I followed these steps.
@LuK1337 Thank you for your response. I flashed the linked dtbo to the new slot, but this did not help. Since it seems to be working fine for others, I think the error must be somwhere on my side.
Click to expand...
Click to collapse
Just wondering but what firmware version did you flash?
LuK1337 said:
Just wondering but what firmware version did you flash?
Click to expand...
Click to collapse
I used the latest file from the linked site: OnePlus8TOxygen_15.E.31_OTA_0310_all_2202182356_edc3927f4900402e.zip and extracted it using the payload dumper.
Draylin said:
I used the latest file from the linked site: OnePlus8TOxygen_15.E.31_OTA_0310_all_2202182356_edc3927f4900402e.zip and extracted it using the payload dumper.
Click to expand...
Click to collapse
That's OxygenOS 11 firmware.
LuK1337 said:
That's OxygenOS 11 firmware.
Click to expand...
Click to collapse
Could well be, the filename is not very telling to me. I just assumed that the firmware provided would be the latest one.