[ROM][UNOFFICIAL][instantnoodlep][10] LineageOS 17.1

[LuK1337]

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
• $ 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 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=314077
  • http://downloads.codefi.re/jdcteam/luk/lineage-17_1/instantnoodlep
  • https://sourceforge.net/projects/luk-lineageos/files/instantnoodlep/lineage-17.1

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.

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][10] LineageOS 17.1, ROM for the OnePlus 8 Pro

Contributors
LuK1337
Source Code: https://github.com/luk1337

ROM OS Version: Windows 8 Mobile
ROM Kernel: Linux 4.x

Version Information
Status: Testing

Created 2020-06-25
Last Updated 2020-11-20

 

[zanderzone]

Yessss, thanks mate. Any known bugs?

 

[areyouanand]

Great to see LOS builds popping up, thanks for the efforts.

 

[TheKnux]

"ROM OS Version: Windows 8 Mobile" dafuq? ?

 

[Burt Squirtz]

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
• $ adb reboot bootloader
• $ fastboot -w (this will wipe your data)
• $ fastboot reboot fastboot
• $ fastboot update lineage-*-UNOFFICIAL-instantnoodlep(-gms).zip

Downloads :

• Builds :
  • https://www.androidfilehost.com/?w=files&flid=314077
  • http://downloads.codefi.re/jdcteam/luk/lineage-17_1/instantnoodlep
  • https://sourceforge.net/projects/luk-lineageos/files/instantnoodlep/lineage-17.1

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.

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][10] LineageOS 17.1, ROM for the OnePlus 8 Pro

Contributors
LuK1337
Source Code: https://github.com/luk1337

ROM OS Version: Windows 8 Mobile
ROM Kernel: Linux 4.x

Version Information
Status: Testing

Created 2020-06-25
Last Updated 2020-06-25

Can this be flashed in TWRP?

 

[Burt Squirtz]

Can this be flashed in TWRP?

 

[LuK1337]

Can this be flashed in TWRP?

No.

 

[blaze9090]

Are gapps included or do we need to flash separately?

 

[LuK1337]

Are gapps included or do we need to flash separately?

Look at downloads list and answer this question yourself.

 

[Panzer87]

Running great on my end. Fingerprint is working too!! Awesome work Dev!

 

[areyouanand]

Flashing ROM via fastboot for the first time, getting the following error


PS E:\android\platform-tools_r30.0.3-windows\platform-tools> fastboot -w
Erase successful, but not automatically formatting.
File system type f2fs not supported.
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
erasing 'userdata'...
OKAY [ 5.457s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 5.466s
PS E:\android\platform-tools_r30.0.3-windows\platform-tools>


PS: proceeded to flash the files anyway and it is stuck in OOS bootanimation.

 

[garretts228]

Thanks for your work!

 

[Panzer87]

Flashing ROM via fastboot for the first time, getting the following error


PS E:\android\platform-tools_r30.0.3-windows\platform-tools> fastboot -w
Erase successful, but not automatically formatting.
File system type f2fs not supported.
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
erasing 'userdata'...
OKAY [ 5.457s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 5.466s
PS E:\android\platform-tools_r30.0.3-windows\platform-tools>


PS: proceeded to flash the files anyway and it is stuck in OOS bootanimation.

What recovery are you using?

 

[areyouanand]

What recovery are you using?

Latest TWRP, but was flashing through bootloader using the given commands.

 

[bencozzy]

Flashing ROM via fastboot for the first time, getting the following error


PS E:\android\platform-tools_r30.0.3-windows\platform-tools> fastboot -w
Erase successful, but not automatically formatting.
File system type f2fs not supported.
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
erasing 'userdata'...
OKAY [ 5.457s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 5.466s
PS E:\android\platform-tools_r30.0.3-windows\platform-tools>


PS: proceeded to flash the files anyway and it is stuck in OOS bootanimation.

Change file type to ext4 then try again

 

[areyouanand]

Change file type to ext4 then try again

Format to ext4 from TWRP?

 

[LuK1337]

Format to ext4 from TWRP?

Only if you don't want to boot up.
You can also just flash recovery from my package and wipe data there.

 

[areyouanand]

Only if you don't want to boot up.
You can also just flash recovery from my package and wipe data there.

Following are the steps i followed.
1. Reboot to bootloader from OOS.
2. fastboot reboot fastboot > gave an error related non recognized command, so i booted into TWRP and adb rebbot fastboot.
3. fastboot erase scratch > Filed with an error saying "check device console".
4. fastboot -w > wipe everything, with log provided in original post.
5 follow the instructions to flash all the images and reboot.

Lineage recovery boots, fastbootD works, gets stuck in OOS boot animation.

6. wipe/format from Lineage recovery> no profit.

When i tried to redo the step, it said "no such file/partition".
Did MSM and back to OOS. Please let me know if i have to do something differently.

 

[LuK1337]

Following are the steps i followed.
1. Reboot to bootloader from OOS.
2. fastboot reboot fastboot > gave an error related non recognized command, so i booted into TWRP and adb rebbot fastboot.
3. fastboot erase scratch > Filed with an error saying "check device console".
4. fastboot -w > wipe everything, with log provided in original post.
5 follow the instructions to flash all the images and reboot.

Lineage recovery boots, fastbootD works, gets stuck in OOS boot animation.

6. wipe/format from Lineage recovery> no profit.

When i tried to redo the step, it said "no such file/partition".
Did MSM and back to OOS. Please let me know if i have to do something differently.

>fastboot reboot fastboot > gave an error related non recognized command, so i booted into TWRP and adb rebbot fastboot.
Update your fastboot and then follow the guide again... If you'll be stuck feel free to join my irc channel and ask me there.
( also don't use twrp, either stay on OOS recovery for now or use lineage recovery )
( btw updated the guide to make user flash proper recovery+dtbo images before rebooting to fastbootd )

 

[Nekromantik]

does magisk work?