[ROM][OFFICIAL][instantnoodlep][12] LineageOS 19

Search This thread

[email protected]_

Senior Member
Oct 18, 2012
79
3
So I decided to try the update from wiki



-Extract stock ROM using payload-dumper-go
-Boot up LineageOS recovery
-Go to “Advanced” -> “Enable ADB”
-Check your DDR type using the following command: adb shell getprop ro.boot.ddr_type, or in case getprop returns an empty value, use: adb shell cat /proc/devinfo/ddr_type instead
-Go to “Advanced” -> “Enter fastboot”
-Execute following commands:


These commands do not work:
-fastboot flash --slot=all abl abl.img
says: fastboot: unknown option --slot=all

Only this one works but it says: Failed: anyway
-fastboot flash -- slot=all abl.img

C:\adb-fastboot>fastboot flash -- slot=all abl.img
target reported max download size of 268435456 bytes
sending 'slot=all' (220 KB)...
OKAY [ 0.016s]
writing 'slot=all'...
FAILED (remote: No such file or directory)
finished. total time: 0.047s

Where exactly could the mistake be?
 

LuK1337

Recognized Developer
Jan 18, 2013
8,799
17,747
Samsung Galaxy S III I9300
Moto G 2014
So I decided to try the update from wiki



-Extract stock ROM using payload-dumper-go
-Boot up LineageOS recovery
-Go to “Advanced” -> “Enable ADB”
-Check your DDR type using the following command: adb shell getprop ro.boot.ddr_type, or in case getprop returns an empty value, use: adb shell cat /proc/devinfo/ddr_type instead
-Go to “Advanced” -> “Enter fastboot”
-Execute following commands:


These commands do not work:
-fastboot flash --slot=all abl abl.img
says: fastboot: unknown option --slot=all

Only this one works but it says: Failed: anyway
-fastboot flash -- slot=all abl.img

C:\adb-fastboot>fastboot flash -- slot=all abl.img
target reported max download size of 268435456 bytes
sending 'slot=all' (220 KB)...
OKAY [ 0.016s]
writing 'slot=all'...
FAILED (remote: No such file or directory)
finished. total time: 0.047s

Where exactly could the mistake be?
You don't need to manually update FW anymore. Official LineageOS builds ship with firmware.
 
  • Like
Reactions: Incineroar

[email protected]_

Senior Member
Oct 18, 2012
79
3
Really? That is great.
So only things should i do is
1)Flashing additional partitions
2) Installing a custom recovery using fastboot
3) Installing LineageOS from recovery

And that's all. Correct?
Thanks

Edit: one more thing... Should i do this too?

In some cases slot b can be unpopulated or contain much older firmware than slot a, leading to various issues including a potential hard-brick. We can ensure none of that will happen by copying the contents of slot a to slot b. This step is NOT optional.

To do this, sideload the copy-partitions-20210323_1922.zip package...
 
Last edited:

HolyHog

Senior Member
Jun 11, 2015
194
74
Alaska
Hey. Guys I wanted to ask you for help because I'm not exactly sure what to do here:

I downloaded an update via oxygen updater IN2023_11_C.36
So.. can I update via system update or do I have to follow this:
https://wiki.lineageos.org/devices/instantnoodlep/fw_update

If the option is to follow this wiki link - I noticed step 3 says: boot up lineageOS recovery. BUT I don't have a lineageOS recovery.
So as a first thing I should:
1.Flashing additional partitions
2.Installing a custom recovery using fastboot

And after this the process will continue with the update from the link above?

My bootloader is unlocked and phone is rooted running on android 11, build 11.0.11.11.IN11BA, model IN2023

And one more question. Will my phone stay rooted after flashing LineageOS or not?
Not sure what your question is here. I would not attempt this upgrade unless you are familiar with ADB and Fastboot commands. If you flash the wrong xbl file, you will destroy your phone.

The best and safest way to install the A12 Lineage is to OTA update your stock rom enough so you have A12 on both slots. That way you don't have to flash anything but the flash lineage files. To get the files you have to extract the Lineage rom by unzipping it. Then you have to use a program called Payload Dumper to extract the payload.bin to get the files you need. Once you have payload.bin unzipped you will then have 10 files, 3 of which you need to flash to get started.
You use fastboot commands to flash vbmeta.img, dtbo.img, & recovery.img.
Then you reboot to this new lineage recovery and there use ADB to flash the actual rom.
Then you have to factory reset.
Then you have to reboot recovery to install GAPPS if you want them.
Then your ready to boot your new Lineage rom.
 

[email protected]_

Senior Member
Oct 18, 2012
79
3
Not sure what your question is here. I would not attempt this upgrade unless you are familiar with ADB and Fastboot commands. If you flash the wrong xbl file, you will destroy your phone.

The best and safest way to install the A12 Lineage is to OTA update your stock rom enough so you have A12 on both slots. That way you don't have to flash anything but the flash lineage files. To get the files you have to extract the Lineage rom by unzipping it. Then you have to use a program called Payload Dumper to extract the payload.bin to get the files you need. Once you have payload.bin unzipped you will then have 10 files, 3 of which you need to flash to get started.
You use fastboot commands to flash vbmeta.img, dtbo.img, & recovery.img.
Then you reboot to this new lineage recovery and there use ADB to flash the actual rom.
Then you have to factory reset.
Then you have to reboot recovery to install GAPPS if you want them.
Then your ready to boot your new Lineage rom.
Thanks for your answer. Tomorrow I flash the vbmeta,dtbo and recovery but after that my phone didn't reboot in to recovery but stay in bootloop
Not sure what your question is here. I would not attempt this upgrade unless you are familiar with ADB and Fastboot commands. If you flash the wrong xbl file, you will destroy your phone.

The best and safest way to install the A12 Lineage is to OTA update your stock rom enough so you have A12 on both slots. That way you don't have to flash anything but the flash lineage files. To get the files you have to extract the Lineage rom by unzipping it. Then you have to use a program called Payload Dumper to extract the payload.bin to get the files you need. Once you have payload.bin unzipped you will then have 10 files, 3 of which you need to flash to get started.
You use fastboot commands to flash vbmeta.img, dtbo.img, & recovery.img.
Then you reboot to this new lineage recovery and there use ADB to flash the actual rom.
Then you have to factory reset.
Then you have to reboot recovery to install GAPPS if you want them.
Then your ready to boot your new Lineage rom.
thanks for your answer. i will try. but how can i get OTA update on both slots?
 

HolyHog

Senior Member
Jun 11, 2015
194
74
Alaska
Thanks for your answer. Tomorrow I flash the vbmeta,dtbo and recovery but after that my phone didn't reboot in to recovery but stay in bootloop

thanks for your answer. i will try. but how can i get OTA update on both slots?
Bootloop is caused by not having A12 on both slots. You have to install A12 twice by OTA update. Updating your phone is in settings. Since it can be in different in different versions of roms it might be easier to go to settings and do a search for Update. You should have 2 or 3 A12 updates you can do. They have out C33, C35, C36 and maybe more.
Once you have 2 or 3 of these installed you will be ready to flash lineage.
It is a good practice to have the latest MSM installed in case things go wrong.
 
Last edited:

yarpen83

New member
Jan 18, 2014
1
0
Hi, how to recover from not working touch after flashing lineageos 19.1? How to turn off device?

Edit: Ok, I have read this thread and see what to do.
 
Last edited:

[email protected]_

Senior Member
Oct 18, 2012
79
3
Everything works great except wireless charging. I have a OnePlus Warp Charge 30 Wireless Charger. Charging on oxygenOS was fast but now is really slow. +5% / hour
How can i fix this?
Thanks
 

sToRm1nG

Senior Member
@LuK1337
I'm not sure if I have some race condition on my phone but when I turn my OP8Pro off and plug it in, the phone gets stuck at the logo (circle with lightning) before it should switch to the charging percentage.
Even unplugging doesn't help, the phone will simply stay on and I have to long-press Vol-Up+Power button to hard reboot the phone.

Are you aware of this issue?
I'm currently using EU C36 firmware.
 

LuK1337

Recognized Developer
Jan 18, 2013
8,799
17,747
Samsung Galaxy S III I9300
Moto G 2014
@LuK1337
I'm not sure if I have some race condition on my phone but when I turn my OP8Pro off and plug it in, the phone gets stuck at the logo (circle with lightning) before it should switch to the charging percentage.
Even unplugging doesn't help, the phone will simply stay on and I have to long-press Vol-Up+Power button to hard reboot the phone.

Are you aware of this issue?
I'm currently using EU C36 firmware.
You forgot to mention that you also aren't on the latest lineage build ^.^
BTW, you most likely aren't running C36 FW, since 19.1 ships with C33 FW.
 
  • Like
Reactions: manu_jedi

[email protected]_

Senior Member
Oct 18, 2012
79
3
One more question. Is it possible to use TWRP recovery for full ROM backup if i have a lineage recovery? I don't want flash TWRP recovery. I just want to boot into TWRP - make a full backup and if something goes wrong with my system then boot into TWRP via fastboot and restore LineageOS from backup.
 

d3viou5

Senior Member
Jun 4, 2007
236
58
One more question. Is it possible to use TWRP recovery for full ROM backup if i have a lineage recovery? I don't want flash TWRP recovery. I just want to boot into TWRP - make a full backup and if something goes wrong with my system then boot into TWRP via fastboot and restore LineageOS from backup.
I don't believe so. Twrp A12 support is sketchy at best and is not officially supported. You may have better luck with orangefox recovery, but even that is is questionable on 8pro. Happy to be corrected on this.....
 

Top Liked Posts

  • There are no posts matching your filters.
  • 14
    2okPze5.png


    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 :
    Downloads :
    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:
    3
    If someone has a workaround to get past the "The current image boot/recovery have been destroyed" after flashing dtbo&recovery images please let us know. I am stuck with oos12 which has become intolerable to use nowadays.
    Any advice or suggestion is welcome :)
    Can you try flashing vbmeta from https://mirror.math.princeton.edu/pub/lineageos/full/instantnoodlep/20220825/?
    2
    Does someone have a cheat on installing gapps? I've tried all of them with installing alongside lineage or installing after a reboot. NikGapps, Opengapps, and MindtheGapps from 12.1 arm64. One of the major problems I see is that the play store is hanging.

    I am using mindthegapps without having any kind of issue so far.
    How to pass SafetyNet and user GPay?

    I used magisk to flash "safetynet fix" and "magiskhide props config" modules. After that you need to run props configuration via terminal (search for termux app in playstore) and change the fingerprint of your device.
    That's it. You can also use yasnac app from play store to see if your device can pass safenet attestation successfully.

    good morning, does 5 g, face unlock and fingerprint work on the oneplus 8 pro (EU)?
    5g and fingerprint are working fine. Never checked face unlock, so i can't tell.
    2
    Same issue here.
    Used msm tool to go back to oos 11.0.4.4 and then updated the device up to c33.
    Flashing the dtbo and then the recovery images damage the boot.

    I have also tried flashing recovery from unofficial los and twrp. Nothing seems to be working
    Msmtool,
    local update to c33,
    reboot,
    local update to c33 again to make sure both slots are C33
    reboot,
    flash dtbo
    flash recovery
    Sideload LOS.